axis.5.motor-pos-cmd = -nan

More
06 Nov 2017 09:47 #101404 by andypugh
As my next step I would comment-out everything related to the axis in HAL and see if the problem still occurs.
You can then run the HAL commands one-by-one in an interactive HAL session (halcmd -kf after LinuxCNC loads) to see if you can work out where the problem starts.

Are you using Trivkins?

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

More
06 Nov 2017 11:17 #101408 by Henk
Replied by Henk on topic axis.5.motor-pos-cmd = -nan
Hi Andy
Yes, I'm using trivkins.

Ill try that, thanks

Henk

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

More
06 Nov 2017 11:23 #101410 by andypugh
Bad kinematics code can give the effect seen, but Trivkins doesn't do any mathematics, so it can't be that.

I have once seen this when a HAL component was writing out of its memory space (array bounds problem). I doubt that is the case here, but changing the order of the "loadrt" lines in the HAL would give some indication if this was the case.

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

More
06 Nov 2017 12:59 #101420 by Henk
Replied by Henk on topic axis.5.motor-pos-cmd = -nan
With everything removed from the HAL file relating to the C-axis, the gui loads and immediately axis.5.motor-position-cmd show -nan.
I have checked the .ini file and cannot see anything wrong.

maybe I should try to update, current version is 2.7.8 I think

Henk

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

More
06 Nov 2017 14:01 #101424 by andypugh
Updating will certainly fix some problems, and is a very simple process via the package manager.

But I doubt that it will help with this problem.

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

More
07 Nov 2017 12:33 #101489 by Henk
Replied by Henk on topic axis.5.motor-pos-cmd = -nan
Hi
I managed to correct this error, but unfortunately I still don't know what caused it....

I copied the previous config and made the changes required and this issue didn't show up. Is it possible that something in the .ini file can cause this?

Anyway, I can now start testing and debugging gearhob.comp

Thanks

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

More
07 Nov 2017 13:00 #101490 by andypugh
Possibly, if the INI file had a zero in it that something was getting divided by.

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

Time to create page: 0.131 seconds
Powered by Kunena Forum