G54-59 not working in start.g?

TC

Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC1 (2020-02-08b3)
Duet WiFi Server Version: 1.23

TC

But the problem allready existed before the upgrade to RRF3

Danal

@TC said in G54-59 not working in start.g?:

Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC1 (2020-02-08b3)
Duet WiFi Server Version: 1.23

Hmmm... you could try RC2, just for completeness. It uploads just fine via web "system" tab.

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

Danal

@TC said in G54-59 not working in start.g?:

But the problem allready existed before the upgrade to RRF3

Ahhh... interesting. I'm really stumped as to what would cause this, it would seem this is a function of a very basic parser that should work for you and me both.

Hmmm... @dc42 will probably need to look at this one.

dc42

Commands in macro files in the /sys folder always ignore workplace offsets. This is so that movement commands in homing files, pause.g and so on always go to the same places regardless of what coordinate system you are in.

TC

Ah ok. In my case I set the origin and therefor the place to print before each print job. That is important because I need to print on prepared objects. Is it possible to add the function that if there is a G55 command directly in front of a G1 command it applies the offset?

TC

Or is it possible to get the offsets of the coordinate systems from the object model?

TC

Ah looks like I found it

TC

Thanks to your awsome object model it was easy to solve!

Danal

@dc42 said in G54-59 not working in start.g?:

Commands in macro files in the /sys folder always ignore workplace offsets. This is so that movement commands in homing files, pause.g and so on always go to the same places regardless of what coordinate system you are in.

Very interesting and good to know. THANKS!