Home X sets magic number and crashes machine (FIXED)

[kvide]

I'm experiencing the same issue as Malte documented in github issue #3, that is that the X-axis rams into the left side of the frame the second time "Home X" is pressed.

Y-axis works ok and after homing the Y co-ordinate is set to 0.000, but for X-axis the software sets the X co-ordinate to some negative magic number. The value varies somewhat but typically it is set to -608.000.

The result is that no movements aren't allowed any more as x-axis is out of boundary; "Attempt to move outside safe limits (X -607.900)" and re-homing will move past the limit switch an hit the left wall until reset is pressed.

whut_small.jpg (36.18 KiB) Viewed 2963 times

Home X
Homing axis X, timeout value: 21
==> {"gc":"G28.2 X0"}
{"r":{},"f":[1,0,18,77]}
{"sr":{"coor":0,"dist":1,"stat":9}}
{"qr":32,"qi":1,"qo":1}
{"qr":31,"qi":1,"qo":0}
{"sr":{"posx":-4.500,"feed":2000.00,"vel":2000.00}}
{"sr":{"posx":-11.000}}
{"sr":{"posx":-17.500}}
<snip>
...
...
</snip>
{"sr":{"posx":-127.833}}
{"sr":{"posx":-134.333}}
{"sr":{"posx":-140.559,"vel":1000.00}}
{"sr":{"posx":-140.833,"vel":0.16}}
{"sr":{"posx":-608.000,"feed":0.00,"vel":0.00,"coor":1,"dist":0,"stat":3}}
ReadyEvent stat
{"qr":32,"qi":1,"qo":1}
Homing X done.

Any ideas why X-axis is not set to zero when homing?

Christian

[kvide]

Ok, some further testing and X-homing procedure stops when the home/min switch is hit.

TinyG wiki on Homing and Limits Description and Operation says:

Once the switch is hit a Latch Backoff move is performed. This backs off the switch until the switch opens again. This is the repeatable zero location.

If the switch does not open the latch backoff distance may be reached. This should not happen - check your latch backoff setting if the switch does not open.

I checked the xlb and ylb settings and they seem ok (8.0 mm). I also changes all other settings to be same as the settings that Juha uses... Also updated the fw to see if it made a difference, but no. There is just no latch backoff move on the X-axis

Code: Select all

[kvide@tunnan tmp]$ diff Goodsettings.txt mine.txt
2c2
< [fb]  firmware build            438.02
---
> [fb]  firmware build            440.20
6c6
< [id]  TinyG ID                    1H4973-HTS
---
> [id]  TinyG ID                    3X2204-RJK
31c31
< [1tr] m1 travel per revolution   39.9830 mm
---
> [1tr] m1 travel per revolution   40.0000 mm
37c37
< [2tr] m2 travel per revolution   39.9540 mm
---
> [2tr] m2 travel per revolution   40.0000 mm

[JuKu]

Something is different than it should be. Please send command $$ and show me the results. The command dumps all settings to the log window. Klick in the window, ctrl+A selects all, copy and paste. Send it to here or by email to me. I'll have a look.

[kvide]

When all things are checked, one should start over by rechecking the wiring.

Mea culpa. I rerouted the limit switch cables and accidentally crossed Xmin with Xmax.


But it if of course a bit strange that hitting Xmax while homing to Xmin does not trigger an error state.

Christian