Beacon not recognized after IDEX upgrade
Sop, After completing the IDEX upgrade, on my Vcore 4 400, RatOS essentially is acting as if it doesn't see the beacon probe. I know its installed, and was working correctly prior to the IDEX upgrade, as the machine was running with it as a Hybrid for awhile. I've tried updating, reinstalling RatOS, verifying connections (the beacon shows up under devices, and lights up when close to the bed), to no avail. Will attach debug zip to comment.
TIA

Solution:
Jump to solution
OK, went through the configurator again. I found where the probe is selected. It defaults to the Superpinda, which is where that came from. Maybe a future revision to have the configurator default to the probe included in the kit, like the rest of the hardware?
Thanks for the help!...

9 Replies
Here's my debug zip
New information: after playing with the ratos and printer cfg files, I was able to get the beacon probe reinstalled. Now every time I restart the printer, ratos.cfg wipes out the [include RatOS/z-probe/beacon.cfg] line and it freaks everything out. it wipes my previous calibration of the beacon as well on every soft restart, to where i have to re-run beacon_initial-calibration in order to get the machine to home
You are not meant to edit ratos.cfg. read the first line
Make any overrides in printer.cfg at the end, but right before the section that says not to edit below.
OK, got it. dont modify the ratos.cfg. So how do I fix my problem? when I run the normal configurator, the beacon doesnt get recognized, and then modifying the printer.cfg is a pointless endeavor.
Dumb question, are you selecting the beacon in the configurator?
looks like you've selected a superpinda
Whatever edits you made to the ratos.cfg to get it to work, you can do in printer.cfg.
I don’t know where the superpinda came from. I never selected it, or had an option to select a probe that I recall
I'd recommend going through the configurator again very carefully.
Solution
OK, went through the configurator again. I found where the probe is selected. It defaults to the Superpinda, which is where that came from. Maybe a future revision to have the configurator default to the probe included in the kit, like the rest of the hardware?
Thanks for the help!

ratos supports many printers and versions so you can't really default to something that then conflicts with another person's kit
you can't even do it based on vcore3, because there were several hardware default changes over the years (like how it used to be LGX lite extruder and now is orbiter)