Heightmap.csv does not get loaded when using M505
wildblue last edited by
Currently on RRF3 and DWC2 the heightmap does not get loaded when using M505 to work with multiple configurations.
Danal last edited by Danal
I would assume that the correct directory must be specified in G29, M374 and M375. I would not expect M505 to change this.
To be clear, I don't "know" the intent; I'm just saying how the documentation reads to me.
Veti last edited by Veti
where is the heightmap located.
what is the exact command you are using to load the heightmap.
Phaedrux last edited by
Is there a heightmap in the secondary config directory?
Which heightmap are you expecting to be loaded?
I appreciate the reports, but it would be great to get a little more detail. It may seem pedantic, but it really helps to offer as much information as possible so that we can determine if it's a configuration issue, a documentation issue, or truly a bug.
Danal last edited by
FWIW, I think it is "working as designed". M505 should have no effect on commands that accept an argument with a full path. And the documentation reads that way. It might not hurt to add a sentence or two making it more clear what it does and doesn't affect.
As another example, I would NOT expect an M505 being active to affect an M98 command. If a command says M98 P"/sys/test.g" I would full expect it to (attempt to) execute that filename on that path. Otherwise, you get into real wierdness. For example, if M505 did override "/sys/" paths...
M98 P"/sys/test.g" ; Would be overridden
M98 P"/tst/test.g" ; Would not.
And that would be confusing as heck.
Again, might be worthwhile to update the doc. I'd be happy to do that update, once we've verified 'working as intended'
droftarts last edited by
I reported this to @dc42 and @chrishamm the other day. It’s because the path to the M505 working directory doesn’t get passed to DWC. I think (didn’t test though) you can move the heightmap.csv to sys/ and it should work. Or use G29 S3 P"/sys/height map.csv" to save it in the right place (also not tested). It will need the working path to be added to an M408 response, and for DWC to read that path to fix.
It will need the working path to be added to an M408 response, and for DWC to read that path to fix.
The M408 part is already implemented in RRF 2.05 and 3.0RC1. The other part should be in DWC 2.0.5.