cmcgrath5035

Need to see your parameters:

https://www.synthetos.com/topics/forum-information-sharing-readme/

Please be very specific when your report in, Versions sometimes change on an hourly basis.

SPJS 1.83?
Your parameter dump will provide $fw
Jogging should be ~instantaneous, so lag is not the end of the world but is an indicator of problem(s)

Weatherman: It is hard to tell what else might be going on that you don’t mention, but I am guessing for sure given the time frame that tinyG is getting reset a lot due to power down, power up.

So simply rebooting does not help, I guess.
Or would you say that jogging is directionally consistent after a reboot until you try to change a parameter?
If that is true, would you also say that , after a reboot, changes made from the command line are OK but changes made with the CP configuretinyG widget cause the direction to be erratic for a while?

Regarding you dimension errors (1″ circle resulted in 0.97″.
That’s a 3% error, should be better than that .
You are talking the bit diameter into account when you run the Gcode, correct?

If you stay in mm, do the reversals occur as well?

What I mean is:
1. reboot, machine comes up in mm.
2. G1 X10 to move to right 10mm
3. G1 X-10 to move back to zero.
Does this work?

inbasys: For starters, what OS and release runs Atmel Studio? Win8 and beyond are known to be overly fussy about driver signing .
And, what branch of the tinyG2 are you attempting to build?
Clean build, or have you made local Modifications to the files?

First I have seen it here, perhaps others will stop by

Thanks for the info.
Some items for the devs to review, some unusual behavior.

Alex
What sort of machine do your have, just curious?
$_tr=60 and minimal microstepping sort of unusual around here, but
the settings are legitimate.
It is, for sure, a big machine, based on $xtm and $ytm.

How do you define “connecting perfectly” ?

When connections initiated, do $ and $pos commands return reasonable responses?

FW 440.19 is now available, upgrade when you can.
It addresses a corner case in Arc processing and is not directly related to your issues, I believe

I can test the jogs via the cp widget and the machine will move fine. I’ll go into the settings and make adjustments, save them, and then the fun begins.

I assume you are using the configuretinyG widget?
I am not 100% sure if that widget is working properly given all the recent changes in CP and tinyG FW.

Try this:
1. Exit CP, kill the SPJS process
2. reset (push button) tinyG
3. Restart SPJS and CP
4. Reconnect to tinyG
5. Jogging working again?
6. Post a $$ dump for review
7. Try making your parameter changes one at a time on the Serial Port Console widget.
8. That work better?