cmcgrath5035

Bummer.
Send a message to synthetos at gmail dot com.
They will assist.

So you are running FW 440.18 or FW 440.19?
Sending Gcode from CoolTerm or from Chilipeppr; if CP, what SPJS version?

Sorry, I guess this was your first FW upgrade.
Almost everybody gets to learn the “Parameters get Reset” the hard way.

I have no better ideas than to try backing down to SPJS 1.80. But do check first that a new SPJS has not appeared before you proceed (that will be version > 1.83).
As you likely recall, SPJS 1.80 does not have the downloader feature you just used, but it will be in the next version, I would imagine.

The problem with many items like the YouTube turtorialls, including many old posts in this forum, is that recommendations are made for then-current situations. When new FW builds appear, sometimes parameters change meaning or recommended value. Be wary of suggestions/recommendations older than a few weeks/months. This is a fast moving business.
If you don’t use an axis (e.g. A, B, C), best to disable it (e.g. $aam=0), but should be a ‘don’t care).

Wow, when I saw this line of Gcode “4 N4 (Bit diameter: 2,000000mm)” I wondered what on earth is that, then realized that you are likely in Europe, where 2,0000mm = 2.0000mm to us yanks.
That can be confusing!

Great Dropbox set of data, by the way.

1. My error, Typical Ox are $tr=60mm with Nema23s. Typical ShapeOkos are 40mm with Nema23s, different belts and pulleys
2. Your other parameters are OK. 1.8deg on motor means 200 (360/1.8) steps per revolution.
3. TinyG’s minimum move on any motor is, for you, 0.0375mm. If told to move less than that, tinyG accumulates moves it can’t make until it can move. Hint: if you try to jog with 0.01mm precision, you will have to hit the arrow key 4 times (4*0.01=0.04, > 0.0375) for the motor to actually move.

4. From your screenshot, I see you are running SPJS 1.83. A bug has been found in this new SPJS and MAY be your issue (because the location is random, I don’t think it is Gcode). See

https://plus.google.com/114830724231985905451/posts/27SJ8VDuvD3

Backing down to SPJS 1.80 may resolve your issue

Keep an eye out for a newer (>1.83) SPJS

See if that helps.

Here is my suggestion for including files in posts here:

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

Obviously, direct embedding gets the job done by is a veryinefficent use of the interface.

Any chance your Gcode generator can add line numbers?
Impossible to have a lot of dialog on a list like that.

Also, any particular reason you chose pulleys that result in $_tr=60mm? Most Ox I have seen are $_tr=40 . You loose a lot of torque when the pulleys get large.

The title of your post implies that the CCW moves are the problem.
Are you sure it is the G03 moves?

With your machine, the minimum X and Y move is 60/(200*8)=0.0375mm (the distance a microstep moves)
Looking at this snipet:

(Pass: 8)
G01 Z-3.900 F120
G03 X27.4065 Y14.5802 R0.2500 F160
X27.4332 Y14.6372 R0.2500
X27.4443 Y14.6993 R0.2500
X27.4389 Y14.7621 R0.2500
X27.4175 Y14.8213 R0.2500
X27.3815 Y14.8730 R0.2500
X27.3333 Y14.9136 R0.2500
X27.2762 Y14.9403 R0.2500
X27.2142 Y14.95

Seems a lot of the Gcode won’t cause moves to be made; are you sure tinyG isn’t busy doing nothing?

• This reply was modified 9 years ago by cmcgrath5035.

Read This: https://plus.google.com/+FlorianSeffert/posts/eW3Yio7DChf

Do you think any of this would cause the motors to move so fast? I’ll see if I can get a dropbox set up and load a video of the machine and what it’s doing when trying to jog.

Maybe, depend if whatever is causing 5000 to become 5004 (etc) is causing other parameter issues.

I believe CP jogs at G0 speed

You can compare
G0 X30Y30
to
G1 X30Y30 F800

Maybe G0 speed is just ‘fast’ to you”
that would be $xvm=16002, if we trust that value.

I highly recommend the $defa=1 procedure.
Enter parameters via CoolTerm or the Serial port console.