New Problem
01 Nov 2018 02:36 #119745
by islander261
New Problem was created by islander261
I've waited a bit over a week but haven't heard any discussion about these problems. I recently updated my EO branch and things haven't been going smoothly. Please look at the state of the commits I have installed:
Every time I start LinuxCNC I get the following message box popup:
Then on top of all this when I look in the terminal that I started LinuxCNC from it is flooded with these measages;
This is the last little bit, after the upgrade I am getting this message in the terminal when I am setting up my work piece ( I haven't changed what I do and never had these errors before):
I do have my system running after chasing down all the new spindle names in my pendant hal files and fixing them.
Will all this be fixed with the next update? When will pull request #509 or apparently renumbered to #512 be included in an update?
John
jd@plasma1 ~/linuxcnc-dev $ git log --oneline -5
784db03 External Offsets: Axis coordinate offset hal pins
0cab365 Hostmot2: Fix #513 - Cause an error message to show on watchdog timeout.
2e8f4d3 Multispindle: Further docs updates
1343487 Multispindle: Docs Update
826232c Multispindle: CLean up some commands that needed a spindle choice but lacked oneEvery time I start LinuxCNC I get the following message box popup:
Then on top of all this when I look in the terminal that I started LinuxCNC from it is flooded with these measages;
Before: spindle 0 speed 0.000000
Before: spindle 1 speed 0.000000
Before: spindle 2 speed 0.000000
After: spindle 0 speed 100.000000
After: spindle 1 speed 0.000000
After: spindle 2 speed 0.000000This is the last little bit, after the upgrade I am getting this message in the terminal when I am setting up my work piece ( I haven't changed what I do and never had these errors before):
Emit interp-run
wrong motion mode, change to the correct one
(<__main__.gmoccapy object at 0x7f2e85f03b90>, <Dialogs object at 0x7f2e85f22aa0 (Dialogs at 0x346ed40)>, 'alert')
(<__main__.gmoccapy object at 0x7f2e85f03b90>, <Dialogs object at 0x7f2e85f22aa0 (Dialogs at 0x346ed40)>, 'alert')
(<__main__.gmoccapy object at 0x7f2e85f03b90>, <Dialogs object at 0x7f2e85f22aa0 (Dialogs at 0x346ed40)>, 'alert')I do have my system running after chasing down all the new spindle names in my pendant hal files and fixing them.
Will all this be fixed with the next update? When will pull request #509 or apparently renumbered to #512 be included in an update?
John
Please Log in or Create an account to join the conversation.
Time to create page: 0.163 seconds