elapsed clocks between calls to the motion control
- schmidtmotorworks
- Offline
- Elite Member
Less
More
- Posts: 281
- Thank you received: 6
19 Dec 2013 09:33 #41805
by schmidtmotorworks
I found this in my bootmsg.txt
Is the any procedure to trouble shoot this?
[ 275.545143] In recent history there were
[ 275.545146] 1425380, 1663080, 1650830, 1686080, and 1857990
[ 275.545150] elapsed clocks between calls to the motion controller.
[ 275.545163] This time, there were 1715460 which is so anomalously
[ 275.545166] large that it probably signifies a problem with your
[ 275.545170] realtime configuration. For the rest of this run of
[ 275.545173] EMC, this message will be suppressed.
Is the any procedure to trouble shoot this?
[ 275.545143] In recent history there were
[ 275.545146] 1425380, 1663080, 1650830, 1686080, and 1857990
[ 275.545150] elapsed clocks between calls to the motion controller.
[ 275.545163] This time, there were 1715460 which is so anomalously
[ 275.545166] large that it probably signifies a problem with your
[ 275.545170] realtime configuration. For the rest of this run of
[ 275.545173] EMC, this message will be suppressed.
Please Log in or Create an account to join the conversation.
19 Dec 2013 18:48 - 19 Dec 2013 18:50 #41817
by ArcEye
Replied by ArcEye on topic elapsed clocks between calls to the motion control
Hi
That is the tail end of the real time error message.
Run a latency test. If that is OK it is quite possible that you get this error once at startup of linuxcnc and then not thereafter.
Some systems seem to do this when there is a sudden load on resources but are fine for the rest of the session.
Alternately you could have a new problem you were not aware of.
( happened to me once, when the BIOS backup battery went dead, BIOS reverted to defaults and I lost all the settings I had made to turn off power saving, hyperthreading, fan temp sensing etc
took me a while to realise what was happening )
regards
That is the tail end of the real time error message.
Run a latency test. If that is OK it is quite possible that you get this error once at startup of linuxcnc and then not thereafter.
Some systems seem to do this when there is a sudden load on resources but are fine for the rest of the session.
Alternately you could have a new problem you were not aware of.
( happened to me once, when the BIOS backup battery went dead, BIOS reverted to defaults and I lost all the settings I had made to turn off power saving, hyperthreading, fan temp sensing etc
took me a while to realise what was happening )
regards
Last edit: 19 Dec 2013 18:50 by ArcEye.
Please Log in or Create an account to join the conversation.
Time to create page: 0.053 seconds