wrong dro after start, and axis tool change window

More
23 Nov 2021 07:09 #227379 by DoWerna
strangely, when I start a simulation are immediately displayed the correct values in the dro.

Yesterday I also copied my configuration into a new folder and deleted all files except the *.hal and *.ini.

so even without *.var *.pref starts the DRO wrong.

Please Log in or Create an account to join the conversation.

More
18 Dec 2021 16:46 #229412 by DoWerna
another thing in this context today.

When I run a program that uses G55, for example, the DRO displays the correct values, but the values in the DRO are labelled G54 instead of G55.

 

Please Log in or Create an account to join the conversation.

More
14 Jan 2022 21:38 - 15 Jan 2022 01:27 #231804 by CMB
I just updated to LinuxCNC 2.8.2-72-gbcb0b7c4e with Gmoccapy 3.1.3.8 and I have the same issue.

I have G54 in my "RS274NGC_STARTUP_CODE =" line and get absolute coordinates for the work DRO, until some other work offset is entered in MDI followed by G54 then the DRO reads correctly.

My temporary workaround is to place G55 (set to the same offset values as G54)  in the "RS274NGC_STARTUP_CODE =" section of my ini file. Then when a program is run with G54 or a macro button that includes G54 is pressed, the DRO then corrects itself.  

Regardless of what work offset is set in the ini file the Work DRO defaults to absolute coordinates.  I can confirm the machine is indeed using the work offset specified in the startup line, just the DRO is wrong upon startup. I must enter some different work offset for the DRO to update or "refresh itself to the actual active work offset coordinate system. The DRO correctly displays G54, G55, etc but in absolute coordinates and not active coordinates until the work offset is changed.

One thing to note, if I go to manual mode then open the touch-off button list none of the work offsets are highlighted, after a successful Gxx followed by G54 (or any desired work offset) the active offset text is highlighted light blue in color and the DRO is then correct.

Hope this helps, let me know what other info I can provide to help troubleshoot.

-edit...this is only an issue upon starting LinuxCNC.
 
Last edit: 15 Jan 2022 01:27 by CMB.

Please Log in or Create an account to join the conversation.

More
27 Feb 2022 23:15 #235955 by depronman
I am also suffering this bug
on 2.8.2. and the associated version of gmoccapy

Please Log in or Create an account to join the conversation.

Moderators: newbynobi
Time to create page: 0.132 seconds
Powered by Kunena Forum