Firmware update has broken my limit switches.

Home › Forums › TinyG › TinyG Support › Firmware update has broken my limit switches.

Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • June 20, 2014 at 9:44 am #6203
    RodeoClown
    Member

    So I updated my firmware today as I wanted to use the newer TGFX and it told me I had to upgrade.

    I was running 380.08 and it worked fine, all limit switches worked no problems.

    I updated to 429.01 and my machine refuses to work and tgfx crashes after reporting that I have hit a limit(both new and old version of tgfx)

    I checked the config and it was set to NO instead of NC, so I typed $st=1 and the response I got was:
    [st] switch type 0 [0=NO,1=NC]
    tried again and got
    [st] switch type 0 [0=NO,1=NC]

    I had this same issue the last time I upgraded firmware to 412.something. So I rolled back to 380.

    Tonight I disconnected my switches, effectively making the system think it was NO instead of NC and I still got told I had hit a limit.

    Firstly, on my 3d printer running marlin, there is gcode I can enter and it will spit me out the state of each limit swtich. Is this possible for TinyG?

    Secondly, am I the only one that has NC limit switches, I was expecting to find more people with this issue.

    I am planning on rolling back to 380.08 tomorrow morning, I just thought I would double check that no one has a workaround.

    June 20, 2014 at 10:00 am #6204
    cmcgrath5035
    Moderator

    The more recent tgFXs report an out of range if your motion exceeds the set travel limits on X,Y and Z.
    Also, with 429.xx, there are several new parameters that need config. The defaults may not be correct for your machine. Have you checked closely a $$ dump?

    Not being able to set $st=1 is clearly an issue. Are you trying that from cli or from settings button on tgFX?

    And, what newer version of tgFX are you running(and on what OS?)

    June 20, 2014 at 5:25 pm #6205
    RodeoClown
    Member

    Trying to set it from both CoolTerm and tgfx.

    Running TGFX build 3259 on windows.

    My travel limits are 450x450x100, and tgfx loads up at 0,0,0 and I immediately get the error that I have triggered a limit switch.

    Is there a list of the new features that could lead to this error?

    June 21, 2014 at 6:33 am #6209
    RodeoClown
    Member

    I think I have narrowed this down further, when I try to move on any axis using the arrow keys or +/- I seem to try to move 450mm at a time on x and y or 100mm on z, which is my max travel specs.

    My settings are as follows, can anyone see anything wrong.

    Funny thing is, it worked fine right after I flashed it, I was able to move around with no problems. Then when I went to actually do some work, it stopped.

    [fb] firmware build 429.01
    [fv] firmware version 0.97
    [hp] hardware platform 1.00
    [hv] hardware version 8.00
    [id] TinyG ID 2X2660-GQX
    [ja] junction acceleration 100000 mm
    [ct] chordal tolerance 0.010 mm
    [sl] soft limit enable 0
    [st] switch type 1 [0=NO,1=NC]
    [mt] motor idle timeout 2.00 Sec
    [ej] enable json mode 0 [0=text,1=JSON]
    [jv] json verbosity 3 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
    [js] json serialize style 1 [0=relaxed,1=strict]
    [tv] text verbosity 0 [0=silent,1=verbose]
    [qv] queue report verbosity 0 [0=off,1=single,2=triple]
    [sv] status report verbosity 1 [0=off,1=filtered,2=verbose]
    [si] status interval 100 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 2 [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 3 [0=X,1=Y,2=Z…]
    [1sa] m1 step angle 1.800 deg
    [1tr] m1 travel per revolution 1.2500 mm
    [1mi] m1 microsteps 8 [1,2,4,8]
    [1po] m1 polarity 0 [0=normal,1=reverse]
    [1pm] m1 power management 1 [0=disabled,1=always on,2=in cycle,3=when moving]
    [1pl] m1 motor power level 0.000 [0.000=minimum, 1.000=maximum]
    [2ma] m2 map to axis 0 [0=X,1=Y,2=Z…]
    [2sa] m2 step angle 1.800 deg
    [2tr] m2 travel per revolution 5.0000 mm
    [2mi] m2 microsteps 8 [1,2,4,8]
    [2po] m2 polarity 1 [0=normal,1=reverse]
    [2pm] m2 power management 1 [0=disabled,1=always on,2=in cycle,3=when moving]
    [2pl] m2 motor power level 0.000 [0.000=minimum, 1.000=maximum]
    [3ma] m3 map to axis 2 [0=X,1=Y,2=Z…]
    [3sa] m3 step angle 1.800 deg
    [3tr] m3 travel per revolution 4.0000 mm
    [3mi] m3 microsteps 8 [1,2,4,8]
    [3po] m3 polarity 1 [0=normal,1=reverse]
    [3pm] m3 power management 1 [0=disabled,1=always on,2=in cycle,3=when moving]
    [3pl] m3 motor power level 0.000 [0.000=minimum, 1.000=maximum]
    [4ma] m4 map to axis 1 [0=X,1=Y,2=Z…]
    [4sa] m4 step angle 1.800 deg
    [4tr] m4 travel per revolution 5.0000 mm
    [4mi] m4 microsteps 8 [1,2,4,8]
    [4po] m4 polarity 0 [0=normal,1=reverse]
    [4pm] m4 power management 1 [0=disabled,1=always on,2=in cycle,3=when moving]
    [4pl] m4 motor power level 0.000 [0.000=minimum, 1.000=maximum]
    [xam] x axis mode 1 [standard]
    [xvm] x velocity maximum 600 mm/min
    [xfr] x feedrate maximum 600 mm/min
    [xtn] x travel minimum 0.000 mm
    [xtm] x travel maximum 450.000 mm
    [xjm] x jerk maximum 100 mm/min^3 * 1 million
    [xjh] x jerk homing 20 mm/min^3 * 1 million
    [xjd] x junction deviation 0.0500 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 2.000 mm
    [xzb] x zero backoff 1.000 mm
    [yam] y axis mode 1 [standard]
    [yvm] y velocity maximum 600 mm/min
    [yfr] y feedrate maximum 600 mm/min
    [ytn] y travel minimum 0.000 mm
    [ytm] y travel maximum 450.000 mm
    [yjm] y jerk maximum 100 mm/min^3 * 1 million
    [yjh] y jerk homing 20 mm/min^3 * 1 million
    [yjd] y junction deviation 0.0500 mm (larger is faster)
    [ysn] y switch min 0 [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 500 mm/min
    [ylv] y latch velocity 100 mm/min
    [ylb] y latch backoff 2.000 mm
    [yzb] y zero backoff 1.000 mm
    [zam] z axis mode 1 [standard]
    [zvm] z velocity maximum 600 mm/min
    [zfr] z feedrate maximum 600 mm/min
    [ztn] z travel minimum 0.000 mm
    [ztm] z travel maximum 100.000 mm
    [zjm] z jerk maximum 100 mm/min^3 * 1 million
    [zjh] z jerk homing 20 mm/min^3 * 1 million
    [zjd] z junction deviation 0.0500 mm (larger is faster)
    [zsn] z switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
    [zsx] z switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
    [zsv] z search velocity 400 mm/min
    [zlv] z latch velocity 100 mm/min
    [zlb] z latch backoff 2.000 mm
    [zzb] z zero backoff 1.000 mm
    [aam] a axis mode 0 [disabled]
    [avm] a velocity maximum 172800 deg/min
    [afr] a feedrate maximum 172800 deg/min
    [atn] a travel minimum -1.000 deg
    [atm] a travel maximum -1.000 deg
    [ajm] a jerk maximum 5760 deg/min^3 * 1 million
    [ajh] a jerk homing 5760 deg/min^3 * 1 million
    [ajd] a junction deviation 0.0500 deg (larger is faster)
    [ara] a radius value 0.1989 deg
    [asn] a switch min 0 [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 deg/min
    [alv] a latch velocity 100 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 deg/min
    [bfr] b feedrate maximum 3600 deg/min
    [btn] b travel minimum -1.000 deg
    [btm] b travel maximum -1.000 deg
    [bjm] b jerk maximum 20 deg/min^3 * 1 million
    [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 3600 deg/min
    [cfr] c feedrate maximum 3600 deg/min
    [ctn] c travel minimum -1.000 deg
    [ctm] c travel maximum -1.000 deg
    [cjm] c jerk maximum 20 deg/min^3 * 1 million
    [cjd] c junction deviation 0.0500 deg (larger is faster)
    [cra] c radius value 1.0000 deg
    [p1frq] pwm frequency 100 Hz
    [p1csl] pwm cw speed lo 1000 RPM
    [p1csh] pwm cw speed hi 2000 RPM
    [p1cpl] pwm cw phase lo 0.125 [0..1]
    [p1cph] pwm cw phase hi 0.200 [0..1]
    [p1wsl] pwm ccw speed lo 1000 RPM
    [p1wsh] pwm ccw speed hi 2000 RPM
    [p1wpl] pwm ccw phase lo 0.125 [0..1]
    [p1wph] pwm ccw phase hi 0.200 [0..1]
    [p1pof] pwm phase off 0.100 [0..1]
    [g54x] g54 x offset 0.000 mm
    [g54y] g54 y offset 0.000 mm
    [g54z] g54 z offset 0.000 mm
    [g54a] g54 a offset 0.000 deg
    [g54b] g54 b offset 0.000 deg
    [g54c] g54 c offset 0.000 deg
    [g55x] g55 x offset 75.000 mm
    [g55y] g55 y offset 75.000 mm
    [g55z] g55 z offset 0.000 mm
    [g55a] g55 a offset 0.000 deg
    [g55b] g55 b offset 0.000 deg
    [g55c] g55 c offset 0.000 deg
    [g56x] g56 x offset 0.000 mm
    [g56y] g56 y offset 0.000 mm
    [g56z] g56 z offset 0.000 mm
    [g56a] g56 a offset 0.000 deg
    [g56b] g56 b offset 0.000 deg
    [g56c] g56 c offset 0.000 deg
    [g57x] g57 x offset 0.000 mm
    [g57y] g57 y offset 0.000 mm
    [g57z] g57 z offset 0.000 mm
    [g57a] g57 a offset 0.000 deg
    [g57b] g57 b offset 0.000 deg
    [g57c] g57 c offset 0.000 deg
    [g58x] g58 x offset 0.000 mm
    [g58y] g58 y offset 0.000 mm
    [g58z] g58 z offset 0.000 mm
    [g58a] g58 a offset 0.000 deg
    [g58b] g58 b offset 0.000 deg
    [g58c] g58 c offset 0.000 deg
    [g59x] g59 x offset 0.000 mm
    [g59y] g59 y offset 0.000 mm
    [g59z] g59 z offset 0.000 mm
    [g59a] g59 a offset 0.000 deg
    [g59b] g59 b offset 0.000 deg
    [g59c] g59 c offset 0.000 deg
    [g92x] g92 x offset 0.000 mm
    [g92y] g92 y offset 0.000 mm
    [g92z] g92 z offset 0.000 mm
    [g92a] g92 a offset 0.000 deg
    [g92b] g92 b offset 0.000 deg
    [g92c] g92 c offset 0.000 deg
    [g28x] g28 x position 0.000 mm
    [g28y] g28 y position 0.000 mm
    [g28z] g28 z position 0.000 mm
    [g28a] g28 a position 0.000 deg
    [g28b] g28 b position 0.000 deg
    [g28c] g28 c position 0.000 deg
    [g30x] g30 x position 0.000 mm
    [g30y] g30 y position 0.000 mm
    [g30z] g30 z position 0.000 mm
    [g30a] g30 a position 0.000 deg
    [g30b] g30 b position 0.000 deg
    [g30c] g30 c position 0.000 deg

    Rolling back now to 380 firmware as I have work to do.

    Also, what has changed with the Jerk settings, they seem to max out now at a million where I used to have them set a lot higher than that as I am on ballscrews.

    June 21, 2014 at 6:35 am #6210
    cmcgrath5035
    Moderator

    Try tgFX build 3256 if problems persist; there are known bugs in 3259.

    But Coolterm should be able to set $st. Until it can do that, it would seem that your inverted sense of switches (NO vs NC) “should” trigger a limit switch action, as far as the FW is concerned.

    You could try to run with limit switches disabled, but not being able to set a proper $st=1 indicates a fundamental communications issue.
    Try issuing a json command from Coolterm, does that work?
    I believe, on boot, tinyG is in json mode and tries to switch.

    June 21, 2014 at 6:50 am #6211
    cmcgrath5035
    Moderator

    Ah so, we were typing at same time.

    Riley aware of the intermittent jogging (arrow key) bug and working it now.

    Read your parameters and comments fields carefully – some(not all) of the huge numbers have new parameter scaling; e.g. what used to be 1000000 is now 1, but both are 1 million.

    Funny thing is, it worked fine right after I flashed it, I was able to move around with no problems. Then when I went to actually do some work, it stopped

    I believe one aspect of the bug Riley is chasing is that tinyG and tgFX are “in-sync” mode wise at boot, but get out of sync

    June 21, 2014 at 6:57 am #6212
    cmcgrath5035
    Moderator

    I see you managed to get the $st=1 set.

    Nothing jumps out on your configs with quick review.
    Easier to analyze in a text file (dropbox, etc).
    The forum tool removes spaces, making it harder to visualize.

    If you do revert to 380.08, you’ll need tgFX < build 3256 (or Coolterm)

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