cmcgrath5035

I did not pull down your code.

Any chance the code is (improperly) seeing incoming {sr…. responses as {r… responses and incrementing ?

Just a wild guess……

Interesting; I am not all that familiar with the 3040 mill standard configuration.
Can I assume git SHA: af26ad8966d4cd065c9fb08ebdc6eee6264daef0 yields a $fb=100.26 build? That would be most current Edge, but there are a lot of them floating around.
From your other post, on line mode, that would be my guess.

Sounds like your parameters have become corrupted.
SPJS should have no direct effect like this.

Check values of $1ma, $2ma, $3ma and $4ma (motor -> axis assignments)

Or, run a $$ parameter dump from the Serial Console Widget, then copy the results and paste to a text file.
Post the text file to a cloud drive, post a URL here for review.

• This reply was modified 7 years, 4 months ago by cmcgrath5035.

Have you tried running the rather simple 2D Chilipeppr Logo Gcode on your setup?
That should be a way to determine if your physical concept of what is +x, +y and +z direction, as set with motor wiring and polarity settings, matches a simple 2d drawing.
You are using rather sophisticated tool chains that have a lot of flexibility, its difficult to identify what might be off on your design relative to your machine setup.

I do see in your Gcode a number of codes that are not supported by tinyG, it is difficult to tell if skipping those commands has material effect on how your code runs.
Here is the tinyG reference:

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

$$ file is good.

Comments on $$:
1. It looks odd to have 2 motors mapped to Y of the same polarity, but that is likely correct assuming the lead screws are the same rotation. Most legacy dual Y machines are belt drive and the Y motors rotate in opposite directions.
2. Do you actually have a Zmax homing switch? Your parameters enable it.
If you do, and you use Z homing, then you should set $ztn=-24 and $ztm=0.
By convention, tinyG homes Z to Zmax and all travel into your work is travel to “-” location.
More info:

https://github.com/synthetos/TinyG/wiki/Homing-and-Limits-Description-and-Operation

If you have no Zmax home/limit switch, set $zsx=0
Note that should you decide to use soft limits($sl=1) then you must make the #2 correction. In this parameter set $sl=0, so not really necessary unless you manually set home on Z.

Any of this help?

If not, perhaps post your Gcode to the cloud drive for a look, perhaps something in there.

Just looked at Cbeam URL so have an idea what you have.

Assuming you are using tinyG onboard motor drivers, the dir signal will be in proper state when step pulse signal is sent.
If you are using motor external drivers, please describe them and how you interface to them.

A look at your parameter set might help – run $$ command from serial port widget, copy and paste the results to a text file, put the text file on a cloud drive and post the URL here.

Does this behavior (erratic up/down) occur only when running Gcode, or does jogging also misbehave?

Hits switch and stops, or hits switch and dies/reboots/flashes(as it would if the switch was a limit)?

Anything unusual happen since last it worked?

How do you send commands to tinyG: CoolTerm, Chilipeppr, etc?

Observation:Your parameter values look a bit strange.
Not necessarily invalid, just strange.
For example, why would you enter $xlv=4 in/min (a nice, round number) but $xlb=0.787in? A quick calc finds 0.787= approx 20mm.
Did you enter machine settings in mm mode or inch mode?
If issues continue, you might want to try sending $def=1 to tinyG, resetting all parameters to default.
Then reenter your parameters in mm mode from a Command Line Interface.
A reminder, save a copy of $$ listing so you have a reference point for reloading.

Another thing to try:
Position (via jog ) the machine at X= 8in or so (good distance from Home).
Send the Home X command as machine starts to move, then manually operate the limit switch to see if the behavior repeats that far away from the switch.
What should happen is the machine stop, then start to back away.

Best guess – parameter corruption.
I while ago folks using the Chilipeppr Parameter widget in inch mode were sometimes seeing a parameter corruption issue. The root cause was never found, have not seen it recently.

• This reply was modified 7 years, 4 months ago by cmcgrath5035.
• This reply was modified 7 years, 4 months ago by cmcgrath5035.