Combi DRO
30 Mar 2017 21:20 #90607
by mmt
I am running Debian Wheezy with LinuxCNC 2.7.8.
I have a glade panel that I created for Axis and I have a CombiDRO. It shows the coordinate system as G54, G55, G56, etc etc.
I noticed that when I change it in MDI from G54 to G55 for example, it changes it in the CombiDRO in the Glade panel. When it changes in a program it does not update the CombiDRO. It is definitely changing the coordinates in Axis and on the DRO tab.
Can anyone explain why it is doing this and how to correct it, or is it a bug?
I have a glade panel that I created for Axis and I have a CombiDRO. It shows the coordinate system as G54, G55, G56, etc etc.
I noticed that when I change it in MDI from G54 to G55 for example, it changes it in the CombiDRO in the Glade panel. When it changes in a program it does not update the CombiDRO. It is definitely changing the coordinates in Axis and on the DRO tab.
Can anyone explain why it is doing this and how to correct it, or is it a bug?
Please Log in or Create an account to join the conversation.
31 Mar 2017 11:40 #90637
by andypugh
Does it change once the program stops?
The DRO widget appears to look in the "current G-codes" structure:
github.com/LinuxCNC/linuxcnc/blob/fcf042...cp/combi_dro.py#L274
I don't know if that is updated while a program is running.
The DRO widget appears to look in the "current G-codes" structure:
github.com/LinuxCNC/linuxcnc/blob/fcf042...cp/combi_dro.py#L274
I don't know if that is updated while a program is running.
Please Log in or Create an account to join the conversation.
31 Mar 2017 15:15 #90649
by mmt
No it does not change when the program stop. If i call a G58 In MDI it changes the combidro. As soon as i run the program it changes to G54 in the combidro even if a G54 is not called in the program.
The github lonk you posted looks to me like it should change when called from a running program.
The github lonk you posted looks to me like it should change when called from a running program.
Please Log in or Create an account to join the conversation.
21 Apr 2017 06:56 #91750
by newbynobi
Hallo,
this can be caused due to the read ahead of the interpreter.
The interpreter reads a program very fast, so if you finish your program with M2 or M30, the coordinate system will be reseted to default G54.
If you begin and finish your program with % sign, the coordinate system will not be reseted.
Have you tried that?
Norbert
this can be caused due to the read ahead of the interpreter.
The interpreter reads a program very fast, so if you finish your program with M2 or M30, the coordinate system will be reseted to default G54.
If you begin and finish your program with % sign, the coordinate system will not be reseted.
Have you tried that?
Norbert
Please Log in or Create an account to join the conversation.
Moderators: HansU
Time to create page: 0.142 seconds