Beacon Help

Ok, so I have the Beacon installed and running to the PI , the red light comes on the board when triggered , I just don't know what to do in printer config or where to start as I don't see the Beacon as a option in printer config to be selected, just further in the Ratos file under z-probes, sorry don't know what I am doing on this one TIA!!!!
80 Replies
blacksmithforlife
GitHub
RatOS-configuration/templates/v-core-3-printer.template.cfg at v2.x...
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
Silver Raider US
Silver Raider US16mo ago
Yeah I don't have line 96 in my config and am running RatOS v2.x: v2.0.2-10-g7e4431a with nothing else to update
miklschmidt
miklschmidt16mo ago
add it. Make sure everything [probe] and [bltouch] is commented out. Then run beacon calibration and you're good to go 🙂
Silver Raider US
Silver Raider US16mo ago
Do I add it right there or further down where I have always been told to save changes? Thanks
miklschmidt
miklschmidt16mo ago
Either will work, but i'd stick to the same place as the original template 🙂
Silver Raider US
Silver Raider US16mo ago
Thanks that is working, now I realized though I need different screws to mount the beacon as the cap heads are to big and drop below the nozzle, so hoping my work has some low profile m3's So now I get Move out of range: 20.000 -7.000 2.000 [0.000] when doing mesh calibrate. I saw where you mentioned to someone else that had the same thing happen to put [bed_mesh] mesh_min: 20,30 mesh_max:365,330 But where do I put this, I put it in user area nothing happens , I put it right under the beacon probe part on line 96, still nothing , I also have a 400
miklschmidt
miklschmidt16mo ago
it should be in useroverrides Post your printer.cfg
miklschmidt
miklschmidt16mo ago
[beacon]
serial: /dev/beacon
x_offset: 0
y_offset: 27
mesh_main_direction: x
mesh_runs: 2
speed: 15.
lift_speed: 80.
[beacon]
serial: /dev/beacon
x_offset: 0
y_offset: 27
mesh_main_direction: x
mesh_runs: 2
speed: 15.
lift_speed: 80.
should be [include RatOS/z-probe/beacon.cfg]. Besides that, this looks correct to me, please make sure you're not getting a different error from the one you posted.
Silver Raider US
Silver Raider US16mo ago
Yeah thats what it looks like in the read only file, and every time I run BEACON MESH_CALIBRATE it comes up with above error still
miklschmidt
miklschmidt16mo ago
I don't understand what you mean by this. Don't copy paste the contents, include the file. That makes no sense, are you sure you're doing a firmware_restart after saving the config? And are you sure you're not editing a printer.cfg backup?
Silver Raider US
Silver Raider US16mo ago
The only thing I have altered is on line 96 where you said to add the Beacon option earlier yesterday. I just rebooted but going to shut it down and restart it again and see if that does anything as my printer config that I showed you is the only thing I have altered.
miklschmidt
miklschmidt16mo ago
Aah i see it, delete this then:
[beacon]
serial: /dev/beacon
x_offset: 0
y_offset: 27
mesh_main_direction: x
mesh_runs: 2
speed: 15.
lift_speed: 80.
[beacon]
serial: /dev/beacon
x_offset: 0
y_offset: 27
mesh_main_direction: x
mesh_runs: 2
speed: 15.
lift_speed: 80.
Silver Raider US
Silver Raider US16mo ago
So deleted saved restarted and still same error
miklschmidt
miklschmidt16mo ago
During BED_MESH_CALIBRATE ? Send your klippy.log (the actual file, don't copy paste 😄 )
Silver Raider US
Silver Raider US16mo ago
This right and thank you so much for your time and help
miklschmidt
miklschmidt16mo ago
So according to your log you either didn't save your printer.cfg with the bed mesh changes, you didn't edit the correct file or you didn't restart klipper yet. It has been running forever according to that log No FIRMWARE_RESTART.
Silver Raider US
Silver Raider US16mo ago
Thats weird as I have restarted it multiple times this past half hour 5:57 PM Move out of range: 20.000 -7.000 2.000 [0.000] 5:57 PM BED_MESH_CALIBRATE 5:57 PM echo: Homing Z 5:57 PM G28 5:56 PM Klipper state: Disconnect 5:56 PM FIRMWARE_RESTART 5:56 PM Move out of range: 20.000 -7.000 2.000 [0.000] 5:56 PM BED_MESH_CALIBRATE 5:56 PM echo: Homing Z 5:56 PM G28 5:55 PM FIRMWARE_RESTART 5:55 PM Klipper state: Disconnect 5:55 PM FIRMWARE_RESTART 5:49 PM Move out of range: 20.000 -7.000 2.000 [0.000] 5:49 PM BED_MESH_CALIBRATE 5:48 PM Move out of range: 20.000 -7.000 2.000 [0.000] 5:48 PM BED_MESH_CALIBRATE 5:47 PM Move out of range: 20.000 -7.000 2.000 [0.000] 5:47 PM BED_MESH_CALIBRATE 5:47 PM echo: Homing Z 5:46 PM G28 5:46 PM Klipper state: Disconnect 5:46 PM FIRMWARE_RESTART 5:46 PM Move out of range: 20.000 -7.000 2.000 [0.000] 5:46 PM BED_MESH_CALIBRATE 5:46 PM echo: Homing Z 5:46 PM G28 5:45 PM Klipper state: Disconnect 5:45 PM FIRMWARE_RESTART 5:44 PM Move out of range: 20.000 -7.000 2.000 [0.000] 5:44 PM BED_MESH_CALIBRATE 5:44 PM echo: Homing Z 5:44 PM G28 Even did a complete power down
miklschmidt
miklschmidt16mo ago
Sorry, i had word wrapping on thats why it looked like forever. In either case, your printer.cfg is not saved Send me the actual printer.cfg file Because it's not containing what you pasted earlier This is your current compiled bed mesh config:
[bed_mesh]
speed = 200
horizontal_move_z = 5
mesh_min = 20,20
mesh_max = 365,360
probe_count = 7,7
fade_start = 1.0
fade_end = 10.0
mesh_pps = 2,2
algorithm = bicubic
bicubic_tension = .2
[bed_mesh]
speed = 200
horizontal_move_z = 5
mesh_min = 20,20
mesh_max = 365,360
probe_count = 7,7
fade_start = 1.0
fade_end = 10.0
mesh_pps = 2,2
algorithm = bicubic
bicubic_tension = .2
Notice mesh_min = 20,20. That's why you're getting that error ( 20 - 27 = -7). 27 is the beacon's Y offset.
Silver Raider US
Silver Raider US16mo ago
So I saved it agin restarted and it is working I dont know what was going on but thank you it developed a heght map and all Thank you but it does rack the front left corner a bit
miklschmidt
miklschmidt16mo ago
excellent How so?
Silver Raider US
Silver Raider US16mo ago
I might have my new Y endstop a little too forward but sounds like it rams to the front left at the begging of the mesh and skips the belt a little
miklschmidt
miklschmidt16mo ago
Yeah you prolly need to adjust your [stepper_y] position_max and position_endstop if you've adjust it so it doesn't hit the leadscrew. Like set it to 390 or 380 or however much you moved it forward so that G1 X0 Y0 takes the nozzle to the front left corner of your build plate.
Silver Raider US
Silver Raider US16mo ago
Guessing thats it and sorry tried looking but dont see where the above adjustment is made, I did the extra 10mm endstop but just can not find where I set it too 390 I belive I found it So I set it to 395 and it stops right at the corner perfect now, but the cordinates read X 20.00 / Y 3.00 Also doesnt seem to scan the back 3 inches of the bed
miklschmidt
miklschmidt16mo ago
As expected. X min is 20 and 30 - 27 = 3. This has nothing to do with position_max and endstop though Fix that by adjusting bed_mesh mesh_max
Silver Raider US
Silver Raider US16mo ago
So its at 365/330 and goes right up to the front but just not the back bit, how would you adjust ? I feel if I go to 390 its going to rack the front again but could just be over thinking it
miklschmidt
miklschmidt16mo ago
You’re confusing kinematic boundaries with bed mesh boundaries
Silver Raider US
Silver Raider US16mo ago
thought so thanks again for all your help , I am sure its kinda late where you are at 🙏
miklschmidt
miklschmidt16mo ago
Bed mesh is specified in probe coordinates, so 390 would be 390-27 = 363 3AM 😅
Silver Raider US
Silver Raider US16mo ago
Well thank you
miklschmidt
miklschmidt16mo ago
You need to do two things: 1) make sure your kinematic space matches the physical space. You do this by adjusting stepper position_min/max/endstop 2) define bed mesh parameters that cover what you want. Test 1) by moving the toolhead to the extremes. Ie x0 y0 and x400 y395
Silver Raider US
Silver Raider US16mo ago
So front left I have X 0.50 / Y 0.10 and at the back right I have X 400 / Y 394.9
miklschmidt
miklschmidt16mo ago
Do you mean you can’t go to x0 / y0?
Silver Raider US
Silver Raider US16mo ago
No the machine says out of range if i try to move it beyond that
miklschmidt
miklschmidt16mo ago
Type “G1 X0 Y0” in the console
Silver Raider US
Silver Raider US16mo ago
Does nothing when entered
miklschmidt
miklschmidt16mo ago
Much easier to just tell it where to go using gcode Without the quotes
Silver Raider US
Silver Raider US16mo ago
correct
miklschmidt
miklschmidt16mo ago
What does the toolhead panel say?
Silver Raider US
Silver Raider US16mo ago
Right now its coordinates are the top right corner ones I wrote
miklschmidt
miklschmidt16mo ago
🤨
Silver Raider US
Silver Raider US16mo ago
X400 Y394.9 Z 15
miklschmidt
miklschmidt16mo ago
G90 G1 X0 Y0 F30000
Silver Raider US
Silver Raider US16mo ago
Homed it now did that g1 code and it put it front left X 0.0 Y 0.0
miklschmidt
miklschmidt16mo ago
Good Now G1 X400 Y395
Silver Raider US
Silver Raider US16mo ago
It moved it to the stated coordinates
miklschmidt
miklschmidt16mo ago
Good, and you’re sure X200 Y395 won’t collide with the rear leadscrew?
Silver Raider US
Silver Raider US16mo ago
barely rubs the wire for the beacon
miklschmidt
miklschmidt16mo ago
Okay, if you’re comfortable with that, move on to 2)
Silver Raider US
Silver Raider US16mo ago
Yeah I set it to 390/390 and seems to cover it well Thank you again for helping me and building this great interface for us , this is only my second printer and my third is the minion, the first was a creality as was most peoples!
audiorazor
audiorazor16mo ago
which duct are you using that its mounted to?
Silver Raider US
Silver Raider US16mo ago
Printables.com
EVA 3 Beacon Probe UHF / Volcano Ducts by Fabreeko Speedy | Downloa...
EVA 3 UHF / Volcano Ducts with a mount for Beacon Probe. Same as the volcano length ducts. | Download free 3D printable STL models
audiorazor
audiorazor16mo ago
I remixed that duct and raised it so you have more clearance. I found that was too tight and I was actually hitting my prints
audiorazor
audiorazor16mo ago
Printables.com
EVA Volcano/Rapido UHF Duct with mount for beacon - 1mm extra clear...
I raised the beacon mount up an additional 1mm to reduce the issue I was having with the screwheads knocking into prints | Download free 3D printable STL models
miklschmidt
miklschmidt16mo ago
I've been running this for a while, it's exactly where it needs to be? ah maybe your screws were different It's supposed to be at 2mm from the nozzle according to the docs.
audiorazor
audiorazor16mo ago
I talked to the beacon people and they said it only came with 1 type of screws
miklschmidt
miklschmidt16mo ago
i have no issues with mine, strange.
audiorazor
audiorazor16mo ago
yea but matt has said it can be further away with no negative impact yea mine were knocking into the prints 1mm made all the difference within reason of course.
miklschmidt
miklschmidt16mo ago
my ducts are lower than the screws, so confusing
audiorazor
audiorazor16mo ago
agreed
Silver Raider US
Silver Raider US16mo ago
I just got some low profile head m3 screws from work and it works great I am loving this beacon, keep being confused why my prints are starting so quick then remember the beacon😂
VisualTech48
VisualTech4816mo ago
@miklschmidt Or anyone else how does one mesure the beacon y offset, as I think its messing up my bed mesh due to the wrong offset.
miklschmidt
miklschmidt16mo ago
If you're using the mount by Speedy, the Y offset is already set when using the RatOS beacon include. It's measured from the nozzle to the center of the coil.
VisualTech48
VisualTech4816mo ago
I put my ruller and got 18.2, but I could be wrong... Yes I'm using the UHF Rapido beacon probe by Speedy...
VisualTech48
VisualTech4816mo ago
@miklschmidt
No description
miklschmidt
miklschmidt16mo ago
Hmm yeah i can see that.. Well you can change it and try it.
[beacon]
y_offset: 18.2
[beacon]
y_offset: 18.2
Looking at it, i actually don't know where i got the Y offset from 🤔 You may very well be right that it's wrong
VisualTech48
VisualTech4816mo ago
Yeah I was wondering why I was getting some odd behaviour so I tested it out myself, and it seemed less than 27, so went to check. I'll roll with 18.2 then. Thanks. Perhaps put it into the default Beacon config as well?
miklschmidt
miklschmidt16mo ago
Yes, either submit a PR with the change when you've verified it or let me know then i'll make the change 🙂
VisualTech48
VisualTech4816mo ago
I'll do some more testing prior. Will do. Thanks again! Yeah works like a charm so far. @miklschmidt At least for that mount, is 18.2
miklschmidt
miklschmidt16mo ago
Will get this fixed
QUINX
QUINX16mo ago
@miklschmidt , do z-tilt points need to be adjusted for Beacon Probe?
miklschmidt
miklschmidt16mo ago
Shouldn't need to adjust z_tilt points, no.
QUINX
QUINX16mo ago
Wouldn't the probe location be at the wrong points? Since the default points have X-offset
miklschmidt
miklschmidt16mo ago
No such thing as wrong points 🙂 z_tilt can probe whatever points your want. The important part is the z_positions which are defined in nozzle coordinates, those don't change.
plain-purple
plain-purple16mo ago
Im having the exact same problem as OP (Move out of range: 20.000 -7.000 2.000 [0.000]) Ive checked my cfg file and removed all traces of bed mesh, then rebooted host and firmware restart of MCU but no joy have included my cfg if anyone would be able to tell me where I am going wrong?
miklschmidt
miklschmidt16mo ago
That's because you need to fix your bed mesh min/max, read the rest of the thread. Specifically this part is why you're getting the error: https://discord.com/channels/582187371529764864/1129607596123357265/1129925736002756618
genetic-orange
genetic-orange15mo ago
Sorry for my ignorance, but where exactly is it that you would write that in the printer config, so that it changes the read only beacon.cfg?
miklschmidt
miklschmidt15mo ago
Includes & Overrides | RatOS
RatOS uses a modular configuration that heavily takes advantage of the config file include and merge logic in Klipper. For this reason, the order of includes and overrides are very important, do not change the order of the configuration unless you know what you're doing.
Want results from more Discord servers?
Add your server