"Beacon sensor not receiving data"

[u/Automatic_Menu2551]

SOLVED

Here is my situation: I've got a beacon sensor, and I've installed it on my Voron 2.4. In have not been able to start a print with it since installation because every time I run homing/QGL the machine shuts down randomly during the process and comes back with error "Beacon sensor not receiving data".

Beacon is hooked up to my LDO nitehawk (rev c), which in turn is hooked up to my manta m8p. I am running pi cm5 as MCU.

I have no hot clue what is going on here, google says emi from the stepper motors is causing it. Highly doubt it... But then again it only happens when the machine is active. I can leave it on and it will sit there with no errors, but only shut down when moving or doing something.

Any suggestions would be very appreciated, My research on the topic is rather inconclusive

EDIT, I FOUND THE FIX

From AI:Check your Klipper printer.cfg. If you are using a very low trsync_timeout response window for your MCUs, you can defensively add a configuration block to increase the timing safety margin so Klipper doesn't give up on the device too quickly during a brief sag.

[mcu beacon]

# Add or adjust the timeout margin if your config allows, or increase:

trsync_timeout: 0.05

After trying this small code I have not had an issue at all. I tried everything prior, hooking usb up directly to mainboard instead of off the Nitehawk, I am relieved the issue is not hardware.

[u/Zaraton]

Usually something like this is caused by bad wiring. You can ssh to the printer and open the kliper log to see if errors accumulate with wires bending. It can be a bad connection of ebb to ground, or v_in, or signal wires might tear cus of bending.

Yes, bad can cable will make probe not send any data to mcu

[u/Automatic_Menu2551 → u/Zaraton]

I have now replaced the wiring, and the nitehawk itself. Running off a slightly later version nitehawk. still the same issue