Getting this error with Z axis Jog function?....If I map the motor to a

Getting this error with Z axis Jog function?..If I map the motor to a different axis it works fine? If I try to jog twice it will also kick native units back to mm?

Using most recent JSON server…1.95. Been a while since I used Chili…

2018/07/29 23:37:38 bufferflow_tinyg_v2.go:231: BlockUntilReady() End
2018/07/29 23:37:38 serialport.go:268: Got p.sendNoBuf. id:jog110, pause:0, data:G91 G0 Z-0.1\n
2018/07/29 23:37:38 serialport.go:275: Items In SPJS Queue List:1
2018/07/29 23:37:38 serialport.go:268: Got p.sendNoBuf. id:jog110-part-2-2, pause:0, data:G90\n
2018/07/29 23:37:38 serialport.go:275: Items In SPJS Queue List:0
2018/07/29 23:37:38 bufferflow_tinyg_v2.go:277: OnIncomingData() Start.
2018/07/29 23:37:38 bufferflow_tinyg_v2.go:283: < {“er”:{“fb”:440.20,“st”:31,“msg”:“Move time is NAN”}}

I’ve never seen a “Move time is NAN” error. What do the TinyG folks say on that one?

JL asking TinyG may be a hint. So I was explaining to a friend how linear motion works. TinyG powered off, but I had a laser attached;also powered off. I manually rotated an axes to the demonstrate the lead screw…to my surprise my laser fired on and burnt some wood. Any move in steppers generates enough back current to fire my laser. Wonder if my Tiny G is fried?

Re-mapped all axis…doesn’t matter. Z axis on chilipepper gives me the error. So all motors are accessible and working via x+,x-,y+,y-…just not z+ or z-. Even tried using my phone as a pendent…same problem. Only thing I can think of is maybe the cable?

It seems like your settings on your Z axis are messed up with respect to some of the integer or float values. Are your jerk settings ok? It seems like when it calculates steps on your Z your TinyG gets errors and craps out. Whatever calculations it’s doing on Z are my best guess to the problem. This would be a TinyG config issue, not a ChiliPeppr issue.

This is possible. I’m running a different lead screw and pullies on Z. It’s worked fine since initially set them year ago. I will futz with with that when I get a chance. T.y. for taking a look at the code. 2nd long code post erased.

Reset Jerk to default and solved the issue.

Damn that was a good guess then