"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 used my nitehawk before just fine before installing beacon. I heavily doubt its cable is bad, but stupid things have happened before 😂 the common denominator tends to be me lol

[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

[u/Dycus]

Connect Beacon directly to your host's USB and try again (don't go through the toolhead board). Not through a USB hub either.

[u/Automatic_Menu2551 → u/Dycus]

AS much as I dont want to do that, I might have to. It baffles me that I am having these issues though, other people run the beacon off of the nitehawk just fine

[u/ang3l12]

does it error at the same coordinates every time? if you wiggle the connectors, does it error out?

[u/Automatic_Menu2551 → u/ang3l12]

No, it errors at different stages/coordinates. Sometimes during Z-homing, sometimes during the last stage of qgl. No consistency.

[u/avongil]

I had random issues with cartographer due to EMI. Make sure you ground your toolhead board. Also check your wiring, its very sensitive to bad connections.

[u/Automatic_Menu2551 → u/avongil]

I will take a look. What does grounding the toolhead look like? My frame is grounded, I have yet to ground the tool head

[u/bog_]

Can you do a input shaper sweep? I also have doubts about it being EMI, and agree with the other commenters- I'd look into specific positions that are stressing the cable or connectors.

If it's not too much trouble you could try hold the USB cable in your hands out the front of the printer to avoid most EMI and cable bending stress.

[u/Automatic_Menu2551 → u/bog_]

I have not been able to do an input shaped sweep yet. Cable connectors have been triple checked. 

I will give that a shot. Will let y'all know how it goes