Motion test?

Home › Forums › TinyG › TinyG Support › Motion test?

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • October 1, 2013 at 4:18 pm #4672
    therenegademaster
    Member

    I have just set up TinyG with my Zen Toolworks 7×7 machine, and I can’t get any visible response from the machine. I hear a high pitched hum in the motors, but they don’t move. Sometimes one of them will get very hot.

    What is the most basic command I could send via CoolTerm which would make something move? I’m having trouble now because I don’t know if its my wiring, my ignorance of gcode, or something else which is causing the problem.

    I tried sending “$test=4” which I thought would start the motion test, but nothing happened. I’ve also tried sending coordinates like X10 Y10 Z10, and files, but nothing I do seems to work.

    Also, I’m using a mac, but that should still work with Tinyg, right?

    October 1, 2013 at 6:09 pm #4673
    Riley
    Keymaster

    Lets get some more info here.

    When you say nothing happens what do you mean? Do you get any text back from your tinyg via coolterm? What port are you connecting to? at 115200?

    Try sending this..

    G0 X10 Y10 Z10

    The command you issued is not going to work 🙂
    Even if your motors do not move (because of faulty wiring) you should get green lights blinking.

    Riley

    October 2, 2013 at 6:24 pm #4684
    therenegademaster
    Member

    Thank you for your reply- let me clarify.

    I have blinking green lights, and can send set variables through CoolTerm. So I know I’m connecting to the board. When I try sending G0 X10 Y10 Z10 I see the green lights for motor 2 and 3 light up, but for some reason, not motor 1. (Motors 1-3 are connected to X, Y, and Z respectively).

    None of the motors move, but I hear something going on with them- kind of a high pitched whine and sometimes a sound like they want to move, but they don’t.

    Also, last time I tried, the Z motor got really hot, though as far as I can tell it’s wired the same way as the others.

    Are there particular configuration settings for each motor that I should be sure to set?

    Brad

    October 2, 2013 at 6:51 pm #4685
    mcgyvr
    Member

    send a $$ in coolterm and post the configuration..
    What are the current pots set to?
    Sure its not mechanical binding?

    stepper motors DO get fairly hot..

    October 2, 2013 at 8:58 pm #4686
    therenegademaster
    Member

    When send $$ in coolterm I get this:

    [fb] firmware build 380.05
    [fv] firmware version 0.96
    [hv] hardware version 8.00
    [id] TinyG ID 1H4973-HKY
    [ja] junction acceleration nan in
    [ct] chordal tolerance nan in
    [st] switch type 0 [0=NO,1=NC]
    [mt] motor disble timeout 0 Sec
    [ej] enable json mode 0 [0=text,1=JSON]
    [jv] json verbosity 0 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
    [tv] text verbosity 0 [0=silent,1=verbose]
    [qv] queue report verbosity 0 [0=off,1=filtered,2=verbose]
    [sv] status report verbosity 0 [0=off,1=filtered,2=verbose]
    [si] status interval 0 ms
    [ic] ignore CR or LF on RX 0 [0=off,1=CR,2=LF]
    [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]
    [gpl] default gcode plane 0 [0=G17,1=G18,2=G19]
    [gun] default gcode units mode 0 [0=G20,1=G21]
    [gco] default gcode coord system 0 [1-6 (G54-G59)]
    [gpa] default gcode path control 0 [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 0.049 in
    [1mi] m1 microsteps 8 [1,2,4,8]
    [1po] m1 polarity 0 [0=normal,1=reverse]
    [1pm] m1 power management 1 [0=remain powered,1=shut off when idle]
    [2ma] m2 map to axis 1 [0=X,1=Y,2=Z…]
    [2sa] m2 step angle 1.800 deg
    [2tr] m2 travel per revolution 0.049 in
    [2mi] m2 microsteps 8 [1,2,4,8]
    [2po] m2 polarity 0 [0=normal,1=reverse]
    [2pm] m2 power management 0 [0=remain powered,1=shut off when idle]
    [3ma] m3 map to axis 2 [0=X,1=Y,2=Z…]
    [3sa] m3 step angle 1.800 deg
    [3tr] m3 travel per revolution 0.049 in
    [3mi] m3 microsteps 8 [1,2,4,8]
    [3po] m3 polarity 0 [0=normal,1=reverse]
    [3pm] m3 power management 0 [0=remain powered,1=shut off when idle]
    [4ma] m4 map to axis 3 [0=X,1=Y,2=Z…]
    [4sa] m4 step angle 1.800 deg
    [4tr] m4 travel per revolution 14.173 in
    [4mi] m4 microsteps 8 [1,2,4,8]
    [4po] m4 polarity 0 [0=normal,1=reverse]
    [4pm] m4 power management 1 [0=remain powered,1=shut off when idle]
    [xam] x axis mode 1 [standard]
    [xvm] x velocity maximum 23.622 in/min
    [xfr] x feedrate maximum 23.622 in/min
    [xtm] x travel maximum 5.906 in
    [xjm] x jerk maximum 787402 in/min^3
    [xjh] x jerk homing 787402 in/min^3
    [xjd] x junction deviation 0.0020 in (larger is faster)
    [xsn] x switch min 1 [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 19.685 in/min
    [xlv] x latch velocity 3.937 in/min
    [xlb] x latch backoff 0.079 in
    [xzb] x zero backoff 0.039 in
    [yam] y axis mode 1 [standard]
    [yvm] y velocity maximum 23.622 in/min
    [yfr] y feedrate maximum 23.622 in/min
    [ytm] y travel maximum 5.906 in
    [yjm] y jerk maximum 787402 in/min^3
    [yjh] y jerk homing 787402 in/min^3
    [yjd] y junction deviation 0.0020 in (larger is faster)
    [ysn] y switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
    [ysx] y switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
    [ysv] y search velocity 19.685 in/min
    [ylv] y latch velocity 3.937 in/min
    [ylb] y latch backoff 0.079 in
    [yzb] y zero backoff 0.039 in
    [zam] z axis mode 1 [standard]
    [zvm] z velocity maximum 23.622 in/min
    [zfr] z feedrate maximum 23.622 in/min
    [ztm] z travel maximum 2.953 in
    [zjm] z jerk maximum 787402 in/min^3
    [zjh] z jerk homing 787402 in/min^3
    [zjd] z junction deviation 0.0020 in (larger is faster)
    [zsn] z switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
    [zsx] z switch max 1 [0=off,1=homing,2=limit,3=limit+homing]
    [zsv] z search velocity 15.748 in/min
    [zlv] z latch velocity 3.937 in/min
    [zlb] z latch backoff 0.079 in
    [zzb] z zero backoff 0.039 in
    [aam] a axis mode 3 [radius]
    [avm] a velocity maximum 172800.000 deg/min
    [afr] a feedrate maximum 172800.000 deg/min
    [atm] a travel maximum -1.000 deg
    [ajm] a jerk maximum 5760000000 deg/min^3
    [ajh] a jerk homing 226771650 in/min^3
    [ajd] a junction deviation 0.0500 deg (larger is faster)
    [ara] a radius value 0.1989 deg
    [asn] a switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
    [asx] a switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
    [asv] a search velocity 600.000 deg/min
    [alv] a latch velocity 100.000 deg/min
    [alb] a latch backoff 5.000 deg
    [azb] a zero backoff 2.000 deg
    [bam] b axis mode 0 [disabled]
    [bvm] b velocity maximum 3600.000 deg/min
    [bfr] b feedrate maximum 3600.000 deg/min
    [btm] b travel maximum -1.000 deg
    [bjm] b jerk maximum 20000000 deg/min^3
    [bjd] b junction deviation 0.0500 deg (larger is faster)
    [bra] b radius value 1.0000 deg
    [cam] c axis mode 0 [disabled]
    [cvm] c velocity maximum nan deg/min
    [cfr] c feedrate maximum nan deg/min
    [ctm] c travel maximum nan deg
    [cjm] c jerk maximum nan deg/min^3
    [cjd] c junction deviation nan deg (larger is faster)
    [cra] c radius value nan deg
    [p1frq] pwm frequency nan Hz
    [p1csl] pwm cw speed lo nan RPM
    [p1csh] pwm cw speed hi nan RPM
    [p1cpl] pwm cw phase lo nan [0..1]
    [p1cph] pwm cw phase hi nan [0..1]
    [p1wsl] pwm ccw speed lo nan RPM
    [p1wsh] pwm ccw speed hi nan RPM
    [p1wpl] pwm ccw phase lo nan [0..1]
    [p1wph] pwm ccw phase hi nan [0..1]
    [p1pof] pwm phase off nan [0..1]
    [g54x] g54 x offset nan in
    [g54y] g54 y offset nan in
    [g54z] g54 z offset nan in
    [g54a] g54 a offset nan deg
    [g54b] g54 b offset nan deg
    [g54c] g54 c offset nan deg
    [g55x] g55 x offset nan in
    [g55y] g55 y offset nan in
    [g55z] g55 z offset nan in
    [g55a] g55 a offset nan deg
    [g55b] g55 b offset nan deg
    [g55c] g55 c offset nan deg
    [g56x] g56 x offset nan in
    [g56y] g56 y offset nan in
    [g56z] g56 z offset nan in
    [g56a] g56 a offset nan deg
    [g56b] g56 b offset nan deg
    [g56c] g56 c offset nan deg
    [g57x] g57 x offset nan in
    [g57y] g57 y offset nan in
    [g57z] g57 z offset nan in
    [g57a] g57 a offset nan deg
    [g57b] g57 b offset nan deg
    [g57c] g57 c offset nan deg
    [g58x] g58 x offset nan in
    [g58y] g58 y offset nan in
    [g58z] g58 z offset nan in
    [g58a] g58 a offset nan deg
    [g58b] g58 b offset nan deg
    [g58c] g58 c offset nan deg
    [g59x] g59 x offset nan in
    [g59y] g59 y offset nan in
    [g59z] g59 z offset nan in
    [g59a] g59 a offset nan deg
    [g59b] g59 b offset nan deg
    [g59c] g59 c offset nan deg
    [g92x] g92 x offset 0.000 in
    [g92y] g92 y offset 0.000 in
    [g92z] g92 z offset 0.000 in
    [g92a] g92 a offset 0.000 deg
    [g92b] g92 b offset 0.000 deg
    [g92c] g92 c offset 0.000 deg
    [g28x] g28 x location 0.000 in
    [g28y] g28 y location 0.000 in
    [g28z] g28 z location 0.000 in
    [g28a] g28 a location 0.000 deg
    [g28b] g28 b location 0.000 deg
    [g28c] g28 c location 0.000 deg
    [g30x] g30 x location 0.000 in
    [g30y] g30 y location 0.000 in
    [g30z] g30 z location 0.000 in
    [g30a] g30 a location 0.000 deg
    [g30b] g30 b location 0.000 deg
    [g30c] g30 c location 0.000 deg

    October 3, 2013 at 6:19 pm #4690
    Riley
    Keymaster

    Woah… OK so that explains it. Did you flash this firmware or did you get it directly from us?

    You can see the NaN values where floating point numbers should be. Typically this is caused because the floating point lib was not linked during compile time. When you hit reset on your board do you get a flashing red light for about 3 seconds? (verifying the bootloader is on there).

    While I am normally the most perfect person the whole world (read mistake free.. ) I have been known to make mistakes. Perhaps we got a bad flash on here. Either way it looks like we need to reflash your firmware.

    The instructions are here for doing so:
    https://github.com/synthetos/TinyG/wiki/TinyG-Boot-Loader#updating-tinyg-firmware-using-the-boot-loader

    Lets see what that does.

    Riley

    October 4, 2013 at 11:25 pm #4699
    therenegademaster
    Member

    Ok, the spindle direction LED flashes when I hit reset, so I have the bootloader. Where do I find tinyg.hex? Am I supposed to compile it myself?

    Thank you for your help and your patience.

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