LinuxCNC 2.8 wrong stat update in auto mode
- Qenf
- Offline
- New Member
Less
More
- Posts: 4
- Thank you received: 0
02 Oct 2019 07:51 - 02 Oct 2019 12:04 #146862
by Qenf
LinuxCNC 2.8 wrong stat update in auto mode was created by Qenf
Hello! I use linuxcnc 2.8.0-pre1 and noticed that in the automatic mode F-commands and M-comands are not updated. In MDI mode, linuxcnc.stat.mcodes return tuple with correct code values and linuxcnc.stat.settings[1] return correct feed rate. In AUTO mode, stat any case return "M0 M2 M5 M9 M48 M53" and settings return "F900" if F-command executed without G-code. Active G-code updated correctly before first move. S-commands are updated correctly in all modes. The stat.poll function is executed every 100ms. Any ideas how to get the correct values of active codes?
Last edit: 02 Oct 2019 12:04 by Qenf.
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
Less
More
- Posts: 7780
- Thank you received: 2075
02 Oct 2019 19:43 #146891
by cmorley
Replied by cmorley on topic LinuxCNC 2.8 wrong stat update in auto mode
This sounds like the know limitation of linuxcnc reporting of some code.
In auto mode the task component reads as gcode fast as it can to have a list of motion commands for the trajectory planner to pull from. Unfortunately task is what sends status commands to the screens. So you will usually find that some codes will show the state at the end of a short program - in a very long one you can sometimes see the changes happen as task get ahead.
There has been work on a fix but it seems that it will be quite some time to incorporate it.
If that doesn't sound like the problem you see we can look into it again.
Chris
In auto mode the task component reads as gcode fast as it can to have a list of motion commands for the trajectory planner to pull from. Unfortunately task is what sends status commands to the screens. So you will usually find that some codes will show the state at the end of a short program - in a very long one you can sometimes see the changes happen as task get ahead.
There has been work on a fix but it seems that it will be quite some time to incorporate it.
If that doesn't sound like the problem you see we can look into it again.
Chris
Please Log in or Create an account to join the conversation.
- fixer
- Offline
- Premium Member
Less
More
- Posts: 132
- Thank you received: 27
02 Oct 2019 20:37 #146897
by fixer
Replied by fixer on topic LinuxCNC 2.8 wrong stat update in auto mode
Yes, this one is very annoying. It would be a huge improvement if only feed and current coordinate offset (F, G54-G59.3) showed "current status".
Also another annoying one is broken run from line with remaped tool change.
Also another annoying one is broken run from line with remaped tool change.
Please Log in or Create an account to join the conversation.
- Qenf
- Offline
- New Member
Less
More
- Posts: 4
- Thank you received: 0
03 Oct 2019 06:03 #146954
by Qenf
Replied by Qenf on topic LinuxCNC 2.8 wrong stat update in auto mode
It would be nice if the status was updated during a pause or in a step-by-step mode.
Please Log in or Create an account to join the conversation.
Time to create page: 0.057 seconds