Limit switches not working, config changes not being saved

Hi Alden,

I’ve verified this bug. The values are being saved, but not the units. Here’s an example where I reboot the TinyG, explicitly forcing inches with G20, verifying the system is in inches via $gun, set the X seek rate to 100 inches / minute, and reboot again. You’ll see the X seek rate goes to 3.937 inches / min, which works out to 100 (3.937 * 25.4).

Similar to what n7qvu says above, I’m just going to switch over to mm so I won’t have to deal with this problem, but I do want to make sure you’re aware of it.

Chris


{"r":{"fb":370.050,"fv":0.950,"hv":7.000,"id":"9H3906-XWP","msg":"Loading configs from EEPROM","f":[1,15,0,38]}}
{"r":{"fb":370.050,"fv":0.950,"hv":7.000,"id":"9H3906-XWP","msg":"SYSTEM READY","f":[1,0,0,960]}}
tinyg [inch] ok>
g20
tinyg [inch] ok>
$
[fb] firmware build 370.05
[fv] firmware version 0.95
[hv] hardware version 7.00
[id] TinyG ID 9H3906-XWP
[ja] junction acceleration 3937 in
[ct] chordal tolerance 0.000 in
[st] switch type 0 [0=NO,1=NC]
[ej] enable json mode 0 [0=text,1=JSON]
[jv] json verbosity 4 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
[tv] text verbosity 1 [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 100 ms
[ic] ignore CR or LF on RX 0 [0=off,1=CR,2=LF]
[ec] expand LF to CRLF on TX 1 [0=off,1=on]
[ee] enable echo 1 [0=off,1=on]
[ex] enable xon xoff 1 [0=off,1=on]
[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 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]
tinyg [inch] ok>
$x
...
[xvm] x velocity maximum 19.685 in/min
...
tinyg [inch] ok>
$xvm=100
[xvm] velocity maximum 100.000 in/min
tinyg [inch] ok>
$x
...
[xvm] x velocity maximum 100.000 in/min
...
tinyg [inch] ok>
{"r":{"fb":370.050,"fv":0.950,"hv":7.000,"id":"9H3906-XWP","msg":"Loading configs from EEPROM","f":[1,15,0,38]}}
{"r":{"fb":370.050,"fv":0.950,"hv":7.000,"id":"9H3906-XWP","msg":"SYSTEM READY","f":[1,0,0,960]}}
tinyg [inch] ok>
g20
tinyg [inch] ok>
$gun
[gun] default gcode units mode 0 [0=G20,1=G21]
tinyg [inch] ok>
$x
...
[xvm] x velocity maximum 3.937 in/min
...


Hi,

I tried this. Same result. Please see above. I understand everything is being saved in mm etc. but the problem is if I specify a parameter (e.g. X seek velocity $xvm) the value is being saved but not converted.

I’m doing everything in inches. I reboot the TinyG and explicitly type G20 and $gun=0. The TinyG is reporting “[inch]”. I set $xvm to 500. The system now uses 500 inches / minute, and if I do something like “G0 X5” the X axis moves 5 inches at the correct speed (about a second). So far so good.

Now I reboot. Everything’s still in inches. $gun still reports 0, and the TinyG prompt is still “[inch]”. $xvm, however, is now 19.68 inches / minute. Even if I issue “G20”, when I do something like “G0 X5” the X axis moves really slowly (because it’s only moving at 0.3 inch / sec).

So yes I believe everything in the base code etc. is working fine with regard to inches / mm, but I believe there’s a bug in whatever code writes the parameters to EEPROM. I believe the “500” is being saved verbatim; since the units aren’t being converted on reboot the startup code is reading the “500” and assumes its mm, which is 19.68 inches.

I hope this helps.

Chris

Hi everybody,

I just got my board back from Synthetos, now with the bootloader and version 370.08 of the code.

I haven’t had a chance to hook it up to my ShapeOko yet, but I can verify both the limit switch bug and the saving parameters in inches bug are now fixed.

A special note of thanks to Synthetos for both the quick bug fixes and the immediate turnaround in upgrading the firmware on my board (they got it Friday; I got it back today). You guys are great!

Chris