silent iron
Hello everyone, I'm currently in the process of installing and testing Turtle for the first time, and I've encountered a strange issue. The front sensor seems to keep changing its state automatically without any operation. Could this be a software configuration issue or a problem with the hardware PCB? I'm completely clueless...
I have already tried turning off all additional feature configurations (such as the TMC's stallguard function) and also replaced the PCB.
I measured the sensor signal, and the sensor side is stable with no loose connections. However, on the PCB side, the measurement results fluctuate between 1.0V ~ 0.1V.
silver copper
<@&1304550334839918672>
silent iron
I think I have identified the issue—it's related to a mismatch between the normally open/normally closed connection of the sensor and the pull-up/pull-down configuration of the circuit.
hallow pond
You are running HH, HH is not supported by AT team. HH offer there own support, if you want proper support and to get the best from the BT you should look at switching to the fully supported AFC software.
merry stag
while that' strue
i suspect your issue is that you need a pullup on the switch pin (^)
so instead of defining the pin as e.g. AFC:HUB it should be ^AFC:HUB
if you have a negated pin (e.g. !AFC:HUB - you would want it to be ^!AFC_HUB' (Klipper cares very much about the order here)
@silent iron
I don't believe a pull-up is needed on the AFC-Lite PCB's endstop ports, but may be needed if you are using some alternative board like a BTT MMB.
silent iron
while that' strue
Now I have adjusted the wiring of the micro switch, using the normally open + ^AFC:HUB configuration, it can work normally。
merry stag
so can we mark this as resolved?
rapid phoenix
Hi, if this is solved, please mark is at [Solved] in the title!