cmcgrath5035

It has been a long time since I have done a FW download and never under windows, so I need to reboot a few brain cells.

Are you referring to the tinyG Updater built in to Chilipeppr, or to the updater here: https://github.com/synthetos/TinyG-Updater ?

When you say from Command Prompt, are you running CoolTerm (or similar emulator) or might you mean the Chilipeppr console.

I always had reproducible good luck using the direct avrdude method here in the wiki: https://github.com/synthetos/TinyG/wiki/TinyG-Updating-Firmware#updating-tinyg-with-avrdude.

If you are using Chilipeppr, from what browser do you run?
I have never seen anyone try the Edge browser, but that does not mean it does not work for this, just new ground being plowed.

Hmmm, that format will make it difficult for me to spot obvious issues.
The data is there, but organized differently than $$ report

Here is a hint for you to contemplate:
tinyG computes the degrees revolution per step pulse by dividing the $sa parameter by the $mi parameter. So, for a simple 200 step per revolution bipolar stepper driven by the tinyG onboard driver, with $mi=8, tinyG sends step pulses as if the effective step angle is 1.8/8=0.125 degrees.
so your step angle is not all that out of whack.

I have no simple way to ask all the pertinent questions on your level translators, polarity of connections (remember Enable is active low on tinyG) and all the other details.

• This reply was modified 4 years ago by cmcgrath5035.

Welcome to the Forum.
First I have seen this question.
How do you interface tinyG to this motor?
A specific reference to data on the motor might help.

The $SA parameter is simply used in a calculation (by tinyG) to determine how far each step pulse (or microstep) will move

I am sort of assuming that you are using a logical interface to an external BDLC controller, but don’t want to speculate too much.

• This reply was modified 4 years ago by cmcgrath5035. Reason: turn on Notify

From the serial console, sending $ct=0.01 should work.
You can read back (manually verify) by sending a $ct
See https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97#ct—chordal-tolerance

The typical default setting is $ct=0.01 mm.
Any reason why yours is set to 0.001 ? (mm, I assume)?

In this I will call your failed motor Y2 connected to Motor(driver)3.

The most frequent cause of problems are wiring. Next could be driver devices on tinyG,

For starters, press reset,
Do all four Motor leds flash Green for 2 seconds on reboot?
2 seconds is the default $mt motor timeout. All motors power up on reboot, holding current position, for $mt time interval.
A green LED(on) for M3 would say voltage was sent from driver device to motor, but driver has no idea if it made it there due to broken wire.

Whats sort of machine? If you can, manually move the machine along the Y axis (probably will not work with a screw machine.

A copy of your parameters ($$dump) will help with the next round of suggestions, gather the info, save to a text file and post the file to a cloud drive (Gdrive, etc.) and provide me a URL

Sorry, system did not tell me you had responded.

I have a general physical idea now of what you are building, I have help install a couple off the shelf such covers, not at this scale.

I assume you are targeting rather large steppers, sound like a rather large mass. Tinyg can source no more 2.8A per output, thus you will likely need external drivers.

Assuming Drum is the rotational element, I would call it Drum(A).
In tinyG Gcode there are three linear motions (X,Y,Z) and 3 rotational (A,B,C). Obviously mechanical converstion from linear to rotational motion is possible, but you will have more math to do when figuring parameters.
You don’t want to “waste” a linear action on a rotational task, maybe.

tinyG may or may not have enough I/O for your complete job. Some folks have used RasPIs to supplement I/O. You may also want to look at G2Core, especially if external drivers are required. G2Core had more extensive I/O and a richer build environment for software.

I don’t have a good idea of what a tensioner might be. By design, tinyG has kinematic concepts built in. When you issue a line of Gcode that makes a move, e.g G1 XxYyZz. tinyG will make sure the point x,y,z will be reached by each of the three actions simultaneously, each component with it’s own Jerk parameter controlling the aggressiveness of speed change along the S curve.

I have not heard this one before, but then cnc.js is much more aggressive in displaying returned (from tinyG) status and error messaging.

A common issue with tinyG and Arcs is end point errors due to lost precision in the 8 bit math environment.
Is your Gcode in inch or mm? MM runs with better precision, due to fewer mm to inch conversions.
You might also try generating your Gcode without arcs (will use short linear segments)to see if that Gcode runs.

Have you browsed the tinyG wiki at https://github.com/synthetos/tinyg/wiki ?

For possible methods to modify the buffer allocations, I’ll suggest to post at https://github.com/synthetos/tinyg/issues where the developers pop in on occasion and heavy modifiers share ideas as well.