reganissu

My friend… you are right!!!
After the change in $_pm settings everything was right but i could not observe anything because I was trying too short distances… hemmm, the beauty of the newbie, I suppose 😀 :D. I am very happy to get movements. And what a quality driver is tinyg… just from two or three moves I achieved things (kinda auto-solved little mechanical issues on S02) I never have been able to get with my old electronics.
Going back to configure things, a lot to do… homing switches, probe …
just I’d like to ask a little question that came to my mind earlier in this thread: what if i put a PowerSupply of 24v and 30A (I can build it combining server PS)?
Can I take care of current adjusting pots ? Or is better to stick to the 24v 5a PS?
Anyway thanks a lot cmcgrath5035 !!! you solved my problem

I tried the same connection with another spare motor in Coolterm. I got the software indicating the right port in the portscan option, but the connection was not working

I rewired to the SO2 wiring setup and run your experiment again but in Coolterm. this time I had communication, but not the “logging dump” i had the very first time i connected the tinyg: they refer at it in tinyg wiki as “some JSON startup messages wrapped in JSON curly braces”.

I typed a command in Coolterm
G91 G0 X0.001
I got the same results of 10 seconds of motor energizing.
plus some JSON messaging:
{“sr”:{“posx”:0.003,”posy”:0.000,”posz”:0.000,”posa”:0.000,”feed”:0.00,”vel”:0.00,”unit”:1,”coor”:1,”dist”:1,”frmo”:1,”stat”:3}}
{“qr”:32}

Hello cmcgtah5035, thanks for the info, got it about belts.

I had been thinking about your consideration about having a tested setup in my Shapeoko2 wiring, which is a true thing (got all running with a arduino 2009 + a GAUPS shield, european equivalent of bart dring gshield, strangely arduino unos has proved not being right for the job – don’t know why). I needed a little testing to make things cleare and I have done a try on the wiring: I just swapped x axis motor (motor 1 on my tinyg) with the nema17 motor I had used for the intial testing with Coolterm. Then I tried to connect to chilipeppr, with no success: the port was showing in the port widget, I could check it, but then comment about communication in the serial port widget was not “turning blue”. that meant to me a failed sent message from the computer to the tinyg (I have been very careful to unpower tinyg before making any change in motor wiring). That way I was not able to send move command at all trough serial port console in chilipeppr.
Then I went back to the wiring I had up when I have done the configuration you suggested above, with $_pm=2.
This time it had been possible to have a serial communication in chilipeppr, and I was able to send move commands. The results have been the same of previous test, with all motors energizing for 10 seconds and no moves.

The methods I used to send move commands was either typing them in the serial port console or pushing arrows on the Axes widget upright in the chilipeppr GUI (I also changed the value in the number below arrows, which change how large movements are – that gave me the same 10 seconds of energizing with no moves). I also used keyboard input for the moves, having the same results.

Lastly, yes, the gantry moves freely when motors are deenergized.

I would like to try the upgrade to tinyG Firmware 440.16. What do you suggest? Could it be a useless fix or mess something up in my faulty setup?

thanks