cmcgrath5035

Do you think this will fix my run away issue.

No, but it will runaway much faster.

1. Enter these parameters.
2. Then shutdown (powerdown) tinyG
3. Then manually drag your spindle to the middle of your worspace.
4. Power up tinyG

Start up Coolterm and create a $$ report – look it over, verify you entered parameters correctly.

At this point, the 0,0 point for your machine is where the gantry is.
A reset, or power cycle, of tinyG resets 0,0 to the current location.

Now enter the following command
G1 X20 F800
Gantry should move 20mm in +x direction at moderate speed
G1 Y10 F800
Gantry should move 20 mm in +Y direction at moderate speed.
(If it runs away in either x or y direction, put you parameter list on the cloud drive and send a not back here.)

G0 X0 Y0
Gantry should return to starting point, x and y simultaneously, at twice
the moderate speed.

What command did you vie the machine to initiate “running away”?

There are 2 ways to stop a machine from running away
1. Don’t tell it to runaway – give it reasonable goto commands
2. install limit switches – you don’t have them provisioned yet.

Do you actually have limit switches?
Limit switches add an additional layer of complexity – good to master manual short distance movement first, to get your basic motion set correctly.

Experiment with longer moves.
Experiment with the F parameter to go slower and faster.

The devs don’t hang around here much.

You questions might be better addressed at

https://github.com/synthetos/TinyG/issues

You are the first in a long time trying to build tinyG

Only way I know you can make this happen is to uses Chilipeppr and a RaspbPi2. Load SPJS into the RaspbPi 2, insert a wifi dongle into RasbPi2 as well as connecting Due to RaspBPi 2 with usb cable.

tinyG2 USB port support is rather generic, if you have a wiUSB over wifi solution that needs no special client support (from the DUE) you may be able to make that work as well. I am not aware of anyone trying.

Do you have a Cloud Drive Account?
Dropbox, Gdrive, etc. There are numerous free offers out there.

Copy your CoolTerm screen to a text file, then place the text file in the cloud.
Get the URL for your shared file and post it here.

Spindle may actually use $tr=1.25mm

There are many different ways to build an Ox, so theses are just some quick observations.

$mt should be something more like 10 seconds, not 0.1 seconds; $mt=10

Most new OX builds use NEMA23 motors, GT3 belts (3mm pitch) and 20 tooth pulleys. If that is what you have, then $tr (travel per motor revolution) should be $_tr=60 , which is 3mm x 20 teeth. Check your belts and pulleys, there are other combinations in the market.

$_tr = 1.25mm may be correct for your Z axis, depending on the thread pitch of your drive screw. There are many variations available there as well.

I think your jerk values are low, but will work for now.
More typical would be 5000 max, 10000 homin on X and Y axis.

Give those parameters a try, then come back for some fine tuning.

$$ parameter sets are much easier to review if you put them into a cloud drive file and provide a link here.

Also – how do you connect to your machine? CoolTerm, Chilipeppr, etc.

• This reply was modified 10 years, 1 month ago by cmcgrath5035.

Look carefully at the DUE schematics.
For sure you don’t want to apply 5V to the 3.3V VCC line or you DUE wil be history.

That’s good, because I always do it in Linux and struggle to help Win users…. 🙂

Sort of hard to tell if you will have introduced side effects.
Keep your eyes open as FW evolves (later versions may have a different sort of fix).