Newbie Help Installing: Motor not moving

Home › Forums › TinyG › TinyG Support › Newbie Help Installing: Motor not moving

Tagged: 

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • July 10, 2015 at 11:37 am #7967
    reganissu
    Member

    Hi all,

    I am installing my tinyg to my shapeoko 2
    I had done a few test going trough the configuration wiki and I got success in moving a spare nema17 motor with coolterm.

    Then I uploaded all the required settings for the shapeoko (see the $$ dump below) and made all the wiring (i am upgrading the electronics from arduino/gshield setup). I hooked the tinyg (v8) to a 24V 5A supply and tried some basic testing trough chilipeppr, but got only some hums from the motor, then only silence (I acannot remember precisely but i think i could not get even serial port console messages). I had done all the testing turning voltage pots on tinyg board with no success

    I searched the wiki for troubleshooting and then tried another powersupply, a hacked hp server dps-600pb that delivers about 24A at 12,5V.
    then tested motor movement and everething seems dead, except for tx/rx led blinking on the board when I send movement command. Good news is serial communication on chilipeppr looks fine, with coordinates logging ok. Nothings moves or makes any sound, anyway. Trying to adjust voltages on board is still useless.
    I also tried to switch two poles on a driver, to check if anything could be wrong in the wiring, but that changed nothing.

    Here is my setup:

    Tinyg v8
    12.5v 24a Power Supply
    4 steppers, nema17, specs:
    Bipolar 4-wire
    Step angle: 1.8°
    Holding Torque: 4800g-cm @ 2.5 Amps

    $$ dump:
    fb] firmware build 440.14
    [fv] firmware version 0.97
    [hp] hardware platform 1.00
    [hv] hardware version 8.00
    [id] TinyG ID 2U2971-QJF
    [ja] junction acceleration 2000000 mm
    [ct] chordal tolerance 0.0100 mm
    [sl] soft limit enable 0
    [st] switch type 1 [0=NO,1=NC]
    [mt] motor idle timeout 10.00 Sec
    [ej] enable json mode 0 [0=text,1=JSON]
    [jv] json verbosity 1 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
    [js] json serialize style 1 [0=relaxed,1=strict]
    [tv] text verbosity 1 [0=silent,1=verbose]
    [qv] queue report verbosity 1 [0=off,1=single,2=triple]
    [sv] status report verbosity 2 [0=off,1=filtered,2=verbose]
    [si] status interval 250 ms
    [ec] expand LF to CRLF on TX 0 [0=off,1=on]
    [ee] enable echo 0 [0=off,1=on]
    [ex] enable flow control 1 [0=off,1=XON/XOFF, 2=RTS/CTS]
    [baud] USB baud rate 5 [1=9600,2=19200,3=38400,4=57600,5=115200,6=230400]
    [net] network mode 0 [0=master]
    [gpl] default gcode plane 0 [0=G17,1=G18,2=G19]
    [gun] default gcode units mode 1 [0=G20,1=G21]
    [gco] default gcode coord system 1 [1-6 (G54-G59)]
    [gpa] default gcode path control 2 [0=G61,1=G61.1,2=G64]
    [gdi] default gcode distance mode 0 [0=G90,1=G91]
    [1ma] m1 map to axis 0 [0=X,1=Y,2=Z…]
    [1sa] m1 step angle 1.800 deg
    [1tr] m1 travel per revolution 39.9900 mm
    [1mi] m1 microsteps 8 [1,2,4,8]
    [1po] m1 polarity 0 [0=normal,1=reverse]
    [1pm] m1 power management 0 [0=disabled,1=always on,2=in cycle,3=when moving]
    [2ma] m2 map to axis 1 [0=X,1=Y,2=Z…]
    [2sa] m2 step angle 1.800 deg
    [2tr] m2 travel per revolution 39.9900 mm
    [2mi] m2 microsteps 8 [1,2,4,8]
    [2po] m2 polarity 0 [0=normal,1=reverse]
    [2pm] m2 power management 0 [0=disabled,1=always on,2=in cycle,3=when moving]
    [3ma] m3 map to axis 1 [0=X,1=Y,2=Z…]
    [3sa] m3 step angle 1.800 deg
    [3tr] m3 travel per revolution 39.9900 mm
    [3mi] m3 microsteps 8 [1,2,4,8]
    [3po] m3 polarity 1 [0=normal,1=reverse]
    [3pm] m3 power management 0 [0=disabled,1=always on,2=in cycle,3=when moving]
    [4ma] m4 map to axis 2 [0=X,1=Y,2=Z…]
    [4sa] m4 step angle 1.800 deg
    [4tr] m4 travel per revolution 1.2500 mm
    [4mi] m4 microsteps 4 [1,2,4,8]
    [4po] m4 polarity 0 [0=normal,1=reverse]
    [4pm] m4 power management 0 [0=disabled,1=always on,2=in cycle,3=when moving]
    [xam] x axis mode 1 [standard]
    [xvm] x velocity maximum 16000 mm/min
    [xfr] x feedrate maximum 16000 mm/min
    [xtn] x travel minimum 0.000 mm
    [xtm] x travel maximum 800.000 mm
    [xjm] x jerk maximum 5000 mm/min^3 * 1 million
    [xjh] x jerk homing 10000 mm/min^3 * 1 million
    [xjd] x junction deviation 0.0100 mm (larger is faster)
    [xsn] x switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
    [xsx] x switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
    [xsv] x search velocity 500 mm/min
    [xlv] x latch velocity 100 mm/min
    [xlb] x latch backoff 5.000 mm
    [xzb] x zero backoff 1.000 mm
    [yam] y axis mode 1 [standard]
    [yvm] y velocity maximum 16000 mm/min
    [yfr] y feedrate maximum 16000 mm/min
    [ytn] y travel minimum 0.000 mm
    [ytm] y travel maximum 220.000 mm
    [yjm] y jerk maximum 5000 mm/min^3 * 1 million
    [yjh] y jerk homing 10000 mm/min^3 * 1 million

    • This topic was modified 9 years, 4 months ago by reganissu.
    July 10, 2015 at 1:08 pm #7971
    cmcgrath5035
    Moderator

    Go back to 24V 5A. That should be enough current for test motion at least.
    24V at 6-8 A probably better, but for now 5A should work for you.

    MEMA17 motors usually have smaller(#teeth) pulleys. What pulleys and belts are you using?
    My NEMA17 SH2 had $_tr=36.54 (11 teeth, MXL belts)

    In you parameters, all motors are disabled, $_pm=0. Try $_pm=2.

    Motors will hum for 10 seconds after tinyG reboot, locking current position for $mt seconds then release holding current.

    (Gently) turn all 4 current (not voltage) pots to max until you get a bigger PS.

    See if this helps

    July 12, 2015 at 11:55 am #7977
    Riley
    Keymaster

    Be careful when adjusting the current pots as they will break if over torqued! Also Verify you have the motor stepper wire pairs wired correctly.

    July 14, 2015 at 12:31 pm #8000
    reganissu
    Member

    Hi,

    I finally got to the machine and tried some of your solutions, thanks a lot
    By the way cmcgrath5035 my pulleys are 20 theeth pulleys, moving on GT2 (2mm per thoot belts). MXL are very interesting belts to get more torque, being 1 mm wider than mine (I measured about 5,35 mm with a caliper). I am a little worried for my tr=39.9, because it seems strange to me that your tr=36.54 is close to mine, with such a different theeth count.

    I got some interesting findings changing motor parameters as you suggested:

    $_pm change from 0 to 2 gave to me 10 senconds of motor hum as you said, but no moving of the axes. I noticed the supposed moving motor was holding torque as well as the others. Not sure what does this mean. Another change has been the chilipeppr GUI showing no movements of the tool, while in $_pm=0 I had it showing its supposed position, without any move from the motors.

    I also turned pots to the maximum.

    Any suggestion to help hunting the problem will be welcome!

    • This reply was modified 9 years, 4 months ago by reganissu.
    July 14, 2015 at 8:57 pm #8005
    cmcgrath5035
    Moderator

    $_tr: There are numerous combinations out there, if your have 20 teeth and GT2 belts, then $_tr=40mm (nominal) is correct. My belts have longer pitch

    Your $_pm setting results are strange. A $_pm=2 means that all the motors( with $_pm=2) will be energized when any of the motors is moving, each motor will either be moving or holding it’s current position.
    How are you entering move commands – direct on the command line, Gcode file, jogging, other?

    I am sort of bypassing questions about wiring and mechanical assembly, since (I believe) you were up and running with Uno/Gshield.
    Does tha gantry move freely by hand when the motors are deenergized?

    July 16, 2015 at 10:48 am #8033
    reganissu
    Member

    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

    July 16, 2015 at 10:57 am #8034
    reganissu
    Member

    By the way, one of the reasons I chose tinyg upgrade for my electronics is to get rid of interferences issues I had while trying autoleveling for pcbs trough probing (i tried chilipeppr option and others from the opensource community). That could be another suspect sign of a bad wiring on my SO2?

    July 16, 2015 at 11:26 am #8035
    reganissu
    Member

    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}

    July 16, 2015 at 11:49 am #8037
    reganissu
    Member

    I did some further testing and I realize a mistake i made: I wired motor1 on tinyg to z axis, while I declared it as x axis. I don’t know other wrong connection because i unwired everything else to get back to the first test I made, that gave me movements on the spare nema 17 motor.
    Then I wired back the spare motor as the very first try, again with Coolterm.
    Typed G91 G0 X0.001
    This time i have got no movement, but the same 10 seconds motor holding torque. Could this indicate that i corrupted something in the firmware? Still I am hoping that a firmware upgrade can solve my problem…

    • This reply was modified 9 years, 4 months ago by reganissu.
    July 16, 2015 at 1:49 pm #8041
    cmcgrath5035
    Moderator

    G0 X0.001 is likely too short a distance to move (or try to jog with CP.

    Try G0 X5.0, get movement?

    July 17, 2015 at 7:19 am #8054
    reganissu
    Member

    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

    July 17, 2015 at 9:46 am #8059
    cmcgrath5035
    Moderator

    I am not exactly sure what you plan to do to create 24V from a server supply, 30A is way more than tinyG can control and way more than the steppers can dissipate. If you are thinking to put 12V outputs in series, that may or may not work due to indeterminate ground references. Depends on power supply; a user recently fried his tinyG when he connected 2 12V power bricks in series, and tinyG ground ended up 12V higher than his PC chassis, buring up his USB cable. Know what you are doing.

    Review this for explaination of Power Trimming:

    July 17, 2015 at 1:18 pm #8061
    reganissu
    Member

    I am defintely going to tune things up once I have finished my setup, thanks for the hints about PS. I think I am fine with the 5A now, since I am mainly milling pcbs, not too much power is required. If I have got to upgrade things for new kind of workflows I’ll do homework and a careful testing before.
    Thanks again!

    July 17, 2015 at 3:05 pm #8064
    cmcgrath5035
    Moderator

    I would agree, 5A should be plenty for PCB loads.
    Enjoy

  • Author
    Posts
Viewing 14 posts - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.