Height Map recall

3DPrintingWorld

Is there a way to verify what height map is being used if one is called before a print?

I have two csv files, one for each one of my flex plates. When I call a previous mesh the current map is the web interface does not change. Should it change or does it always display the last map probed?

Phaedrux

How are you loading it?
How are they named?

G29 S1 will load heightmap.csv

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation#Section_Summary_of_gcode_commands_related_to_mesh_bed_compensation

3DPrintingWorld

Thanks but I am ware of that page. Below is how I am calling up the height map after a G30.

G29 S1 P"buildtak.csv"

Can you verify if the height map should change, like I asked previously? Also you would think the name of the height map would be displayed so you know which one was active.

Phaedrux

Firmware and DWC version?

3DPrintingWorld

3.01
2.0.4

Phaedrux

Please test 3.01-RC9 and DWC 2.1.4

https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC9

3DPrintingWorld

Yeah, but do you not know the answer to my original questions?

chrishamm

There are a couple of indicators:

When you click on "Compensation & Calibration", the popup menu displays the current compensation type.
If that shows that you are using a heightmap, you can see on the Heightmap page what the loaded heightmap looks like (provided you are using 3.01-RC7 or newer)

nickpgre

@3DPrintingWorld said in Height Map recall:

ay to verify what height map is being used if one is called before a print?

I am coming with the same question. On duet wifi 2, I upgraded to 3.01-RC9 and Duet Web Control 2.1.4 but loading the height map either with G29 S1 or through the Dashboard tab -> Compensastion & Calibration -> Load saved height map from SD Card the "Disable Mesh compensation" remains disabled.

I see in the diagnostics the following even after I Execute G29 S1 or G29 S2

=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: mesh, comp offset 0.000

Is this an issue with my configuration, some bug or anything else? I can see the height map from the height map tab but cannot tell whenever it is active or not even if i turn debugging on/off.

chrishamm

@nickpgre I can confirm that, it will be fixed in the next DWC version.

nickpgre

Thanks @chrishamm !

The only way to figure if it could be loaded, was to load the height map before homing so to get the warning message!

Have a good day!

gtj0

@chrishamm said in Height Map recall:

There are a couple of indicators:

When you click on "Compensation & Calibration", the popup menu displays the current compensation type.

If that shows that you are using a heightmap, you can see on the Heightmap page what the loaded heightmap looks like (provided you are using 3.01-RC7 or newer)

Actually, you only see what's in the file "heightmap.csv" not necessarily what was loaded, at least by my testing.

If I start with no heightmap loaded and no heightmap.csv, DWC shows "File 0:/sys/heightmap.csv not found".

If I do a G29 S1 P"heightmap-hot.csv", the DWC will automatically update and show the map but if I refresh, it goes back to "File 0:/sys/heightmap.csv not found".

I also note that move.compensation.file is always NULL in the DSF OM and missing altogether in the RRF OM.

garyd9

@gtj0 said in Height Map recall:

I also note that move.compensation.file is always NULL in the DSF OM and missing altogether in the RRF OM.

On RRF 3.01-RC9+1 (duet3 standalone):

4/22/2020, 10:15:26 PM	m409 K"move.compensation.file"
{"key":"move.compensation.file","flags":"","result":"0:/sys/heightmap.csv"}

; after running : G29 S1 P"another_map.csv"

4/22/2020, 10:19:23 PM	m409 K"move.compensation.file"
{"key":"move.compensation.file","flags":"","result":"0:/sys/another_map.csv"}

gtj0

@garyd9 said in Height Map recall:

m409 K"move.compensation.file"

Well, that's quite odd...

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.01-RC9+1 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-04-22b1
G29 S1 P"heightmap.csv"
Height map loaded from file heightmap.csv
m409 K"move.compensation.file"
{"key":"move.compensation.file","flags":"","result":null}
G29 S1 P"heightmap-hot.csv"
Height map loaded from file heightmap-hot.csv
m409 K"move.compensation.file"
{"key":"move.compensation.file","flags":"","result":null}

OK maybe it's just me.

garyd9

@gtj0

SBC vs standalone?

No idea, but seems like a bug. @dc42?

gtj0

@garyd9 said in Height Map recall:

@gtj0

SBC vs standalone?

No idea, but seems like a bug. @dc42?

Maybe. I'll create a separate thread for it.

3DPrintingWorld

To update DWC to 2.1.5 do I not just upload the .zip like I do for RRF? After I do this the status on the general tab does not change from 2.0.4.

Phaedrux

@3DPrintingWorld said in Height Map recall:

To update DWC to 2.1.5 do I not just upload the .zip like I do for RRF? After I do this the status on the general tab does not change from 2.0.4.

Yes, you should be able to. You can also do it manually by pulling the SD card and using a PC to extract the zip file into the /www folder.

Try uploading DWC version 2.0.7 first. Maybe it's too out of sync.

3DPrintingWorld

Thanks! Updated RRF and DWC to the latest RC and the height map is now displaying properly.