cmcgrath5035

I suggest you post a question here:

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

There has not been much discussion on this topic in past couple years.

I believe the simple answer is no, not out of the box.

But do some Google Search on “kinematics tinyG” several rather old topics such as

https://www.synthetos.com/the-robot-arm-is-working/

Please report any success you have on your search – others have asked similar

I am a little confused as to what is actually being sent to tinyG.
Per tinyG Wiki

https://github.com/synthetos/TinyG/wiki/Gcode-Support

The M6 Gcode command is “no operation at this time”, which to me translates to Not supported , but I have never tried it.
If you are sending M6, what internal state tinyG ends up in might be indeterminate.

Perhaps it would be helpful to post (Pastebin worked just fine) a short Gcode file that exhibits the issue.

You might also want to review this (somewhat dated) thread

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

After a quick chat with the Devs, it appears a CRV file is binary.
The CP widget still attempts to format it as Gcode, but the resulting download is binary, contains codes that overwrite the FW, as you experiencd.

You will have to find a way to get Vcarve to create Gcode

Params look OK, with these suggestions:
Set
$p1pof = 0.0 (That will shut off pwmled when spindle should be off)
$xvm, $xfr, $yvm and $yfr are normally suggested at 16000, where you have 2500. That will simply make you machine run a bit slower, should not be an issue
Set $ex=2 when running Coolterm (RTS/CTS works better). The $ex setting when running Chilipeppr/SPJS does not matter; SPJS uses buffer fill flow control.

What version of SPJS are you running?
Is you XP machine 32bit? I don’t see a lot of folks running on XP anymore.
Is the XP machine sort of “brain dead”?

Open Windows task manager and look at CPU utilization.

I have no Mach3 experience, but since it was born and matured on what we today would call brain dead hardware, it is likely more tolerant of the typical legacy XP machine performance.
Chilipeppr and SPJS are both aggressively multithreaded and use the latest in javascript,

You could try shutting Limits and homing to OFF ($xsn=0, etc) to see if that performs better with $test=3 or other simple test code.If it does, that might point to noise issues.

Are you running SPJS under MAC as well as the Chrome browser?
What version of SPJS?

I assume you mean you tried the tinyGupdater app from here:

https://github.com/synthetos/TinyG-Updater/releases

You might give the tinyG flashing application that is part of SPJS 1.88 or later.

The ftdi front end to tingG is a stand alone chip, so it is not unusual for the tinyG port interface to appear ‘OK’ from the server side, yet not have proper message flow to/from tinyG firmware.

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

Have you seen this:

https://github.com/synthetos/TinyG/wiki/Stepper-Motors-and-Power-Supplies

Parameters: It is much easier to spot configuration issues when parameters are reported in mm, not inch. Also highly recommended that parameters be entered and managed in mm mode, not inch. TinyG is native mm, all inch infor gets converted.
Also, please put your configs in a cloud drive folder and post a URL, much easier to compare from there to a “known-working” parameter set.

How did you initially enter parameters? CoolTerm, Chilipeppr, ?

What is can quickly see is a 3 axis screw machine ($_tr=0.1 in).

Are you sure that the screws are not binding along route of travel?

Add URLs to your motor specs as well for easier location. I am not familiar with those specific motors. We seldom have to discuss motor specifics, they just work(when wired correctly).