save skew using M98 in config override

R006

hey,

Could any one please provide guidance on how to incorporate skew or backlash values into a config override file?

is this possible using M98?

oliof

@R006 if your config-override.g exist, you can add M501 at the end of config.g (adding M98 P"config-override.g" would also work, but some tuning commands check for the existence of M501 which is used to be compatible with Marlin GCode syntax).

Then you would add your skew/backlash compensation commands to config-override.g by editing that file like any other macro.

gloomyandy

@oliof What happens if you ever run M500 after making edits to the config-override.g file? Would those changes be lost?
Not something I've ever tried (I'm not fan of the M500/m501 system).

oliof

@gloomyandy I avoid M500 (and config-override.g most of the time) for that reason and tend to plop things directly into config.g instead. I think it only overrides values/commands it knows about and does not change anything else, but I haven't checked in detail.

T3P3Tony

@oliof it will overwrite the file so editing config-override.g is not recommended.

@R006 if you want to save the commands in a different file from config.g then you can create that file (lets call it skew.g) and then call skew.g using M98 from config.g

oliof

@T3P3Tony that's ... kind of terrifying.

I did play around with putting different things in different includes, but due to the terseness of the RRF gcode, I don't feel I win much over a well structured and fairly commented singular file. So I come back to putting everything in one place.

T3P3Tony

@oliof M500/M501 was implemented in RRF to mimic the behaviour of the old Marlin save to EEPROM so it's not designed to be user editable.

It's really there for things that are automatically calculated by the firmware and the user may want to save. Like heater tuning parameters (the original use).

I personally do not use it, but we needed to include the concept of "save tuning settings" in RRF back in the day because most users still had the mindset of Marlin where to make changes (other than values stored in EEPROM) you had to recompile the firmware.

Not sure why it's terrifying - if you dont use it it has no impact.

oliof

@T3P3Tony maybe terrifying is the wrong word. I understand the engineering intent behind M500/M501, but on the other hand I would say the things you need to learn about RRF being different to Marlin these days are so many that not supporting M500 would be low on the list of things ... but yeah, this tells me I should stop using config-override.g and either keep using a single file or maybe not more than a handful of specific macros.

T3P3Tony

@oliof true, if we were looking at this now and not in 2014 then it might be different!