Problem with Beacon RevD after upgrading to ratOS 2.0.2
I upgraded RATOS to 2.0.2 from version 1.0xxx I have been running a Beacon RevD probe for around 6 months with no issue.
All went fine with the upgrade - they appear to have streamlined and intergrated the beacon setup .
my issue is that the z probe always shows as triggered, when I know it's not. If I manually trigger it the indicator light comes on as expected.
Anyone else had this issue?
If I setup for my superpinda it works fine.
It was not disconnected during the setup so I don't feel any damage occured there, I have also commented out the call to include Beacon.cfg and used the manual method as per my RATOS V1.0 printer.cfg but have the same issue.
So at a bit of a loss at the mo
I have ordered the latest Beacon Version (Did this a week ago as they were on sale) that will hopefully get to me soon - I will see what that one gives me,
I have attached my printer.cfg and Klippy log.
I appreciate any guidance given!
Regards
Ian
All went fine with the upgrade - they appear to have streamlined and intergrated the beacon setup .
my issue is that the z probe always shows as triggered, when I know it's not. If I manually trigger it the indicator light comes on as expected.
Anyone else had this issue?
If I setup for my superpinda it works fine.
It was not disconnected during the setup so I don't feel any damage occured there, I have also commented out the call to include Beacon.cfg and used the manual method as per my RATOS V1.0 printer.cfg but have the same issue.
So at a bit of a loss at the mo
I have ordered the latest Beacon Version (Did this a week ago as they were on sale) that will hopefully get to me soon - I will see what that one gives me,
I have attached my printer.cfg and Klippy log.
I appreciate any guidance given!
Regards
Ian
Solution
Well it turned out that I was an dumb idiot, - I ignored the instruction in printer.cfg that simply said " just connect it and run BEACON_CALIBRATE" - I was afraid to do the Beacon_Calibrate before checking it's operation to make sure I did not crash the head into the bed, run the macro and like magic all worked. - Sorry to waste anyones time!