cmcgrath5035

Sorry to hear of your problems.

You may be integrating several different flavors of issues in concluding that your need a low level reflash (with the ICE tool).

You should connect with Synthetos at this URL :

https://www.synthetos.com/contact-us/

Information about when you purchased may help identify if you tinyG was in the population that likely has a fuse issue. Returning the board to Synthetos for a reflash would be an option if you don’t want to try the ICE.

Is the Spindle (SPIN) LED flashing or solid on, or is it the SpinDir LED?
How long have you had your tinyG?

What OS are you using to run SPJS?

See post above.
Yes, can reassign pins on the Due to match your development board.

Motate is the abstraction of hardware.
Read the above references to Motate

Wait a minute, your said developed, not development board.

Motate is still your answer, as long as the tinyG signalling characteristics are compatible between tinyG and Allegro drivers

The perils of living near the EDGE, but you seem to know how to help yourself.

Good luck

Table shaking, particularly with the relatively heavy spindle you have, is not unusual. It one reason I migrated to a 400W quiet cut DC spindle, my original dewalt was overkill for what I was doing.

You experiment by reducing the values of $xjm and $yjm from 5000 to , say 500, a dramatic reduction in ‘aggressiveness’. Run the job in air(or on waste material), see if you can discern a difference in shaking between 500 and 5000.
If you milling speeds (F speed) are relatively high, that would increase shaking as well,
Run a separate experiment, using the Gcode widget to slow speed down by factor of 0.5

• This reply was modified 8 years, 10 months ago by cmcgrath5035.

Many legacy interfaces are really slow (8 bit slow uC) so perhaps this was a chance for them to catch up.

I would try first
Eliminate them, let interface flow control (RTS/CTS recommended) do it’s job.

If no work, tun back on with P1 or perhaps P0.5 (?)

My guess is that P0 won’t get fixed soon, assuming it really is a bug

Is your developer board pinout same as Gshield?

I’d start by wandering thru

https://github.com/synthetos/Motate

where you will get a general idea of how the Motate layer works.

Then compare your develope pinouts to Gshield, and hack away at a My_development_board.h following the example you see.
then recompile.
Or, perhaps better yet, remap the pin assignments on your developer board to match Gshield.

FYI, I don’t know what your development board looks like, but my initial suspicion would be limited thermal conductivity. Your drivers, like the TI drivers used on Gshield, are in special heat slug packages.
Don’t drive the proto very hard, and don’t expect to do much real ‘work’ without a good thermal solution.

Is there a particular reason you are using these drivers?

The minimum move tinyG can make in the X direction is the distance moved in a microstep.
That is 60mm_per_rev/(200 steps/rev *8 microsteps/step) = 0.0375mm

If your Jog increment is set to 0.1, it will take 3 pushes of the arrow key to yield a 0.1mm move, with some remainder.

If my quick math is correct, if your setting is 0.1, it will take three arrow pushes to get a move, 3 more to get a second move, but only two more to get a third move.
Welcome to the world of quantized movement

What jog increment setting are you using?