Hi Mike
I really, really think you should fix the step losing. If this is really impossible, then you can follow this conversation to do visual homing in a script.
https://groups.google.com/g/openpnp/c/cZSn8Tmvsm0/m/HqW6WyZfAgAJ
_Mark
--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/318172b1-e1f0-49e2-b8bb-00b5a6b5258bn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/17faa96e-cd4c-4f92-a3b6-f66f328ad469n%40googlegroups.com.
I'm busy/away, so I won't be online much.
According to the log it does not find the actuator.
2023-09-28 14:48:47.180 SystemLogger INFO: ### Actuator not found ###
I don't know why. Maybe a space after the name?
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/4924e53a-84be-4e45-8a2f-878029ef4c08n%40googlegroups.com.
This is impossible to debug from afar, using just the log.
Things to check:
endstop.minz.release_first true
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/b1507d54-ceb4-4772-93c5-01fab38a13abn%40googlegroups.com.
This is impossible to debug from afar, using just the log.
Things to check:
- Have you loaded my firmware for sure?
Go to driver / Driver Settings and press Detect Firmware. Send string.
- Have you configured the release_first options in the config.txt? (you would have two entries)
endstop.minz.release_first true
The you need to add
endstop.maxz.release_first true
endstop.maxa.release_first true
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/9ec05a5e-7fc5-4ba7-8630-64808e914f81n%40googlegroups.com.
The only thing that comes to mind is the acceleration.
In regular homing you set the acceleration explicitly to 1000mm/s²
In actuator homing you don't set the acceleration. So it takes the last set acceleration, which according to the log was a mere 38mm/s²
This might mean that after hitting the end-stops, it decelerates
very slowly and therefore goes way too far until it really
stops.
For Smoothie, the feed-rate seems to be set by the fast_rate and slow_rate settings in the config.txt but it seems not the acceleration. If true, this might be seen as a bug, since homing should work the same way every time.
To solve this, I guess you also need to set the same acceleration
in the actuator G-code, exactly the same as in home.
_Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/4f4845e1-b3bd-43ec-a7ce-5623436d0212n%40googlegroups.com.