Unknown Pin Chip Name: Probe
Hello there. I opened my printer.cfg to increase the speed of my bed mesh with a Beacon. I then started getting this error. printer.cfg attached.
60 Replies
Thank you for taking a look @miklschmidt This line was added when I did the beacon set up from the picture. Do I need it?
I guess for reference, when removing the line, I still get the same error.
No, like it says in the template, all you need to do is enable the include and run BEACON_CALIBRATE
I don't think that is what I will want to do as the x and y offset that are within that part of RatOS are different than what I have.
I have y offset of 16. And this doesn't have the serial.
the beacon include has offsets for the beacon mod made by fabreeko speedy, obviously if you're using custom stuff you should deal with that in an override in the user override section like with everything else.
/dev/beacon is the correct serial. RatOS maps the beacon device for you.
If you follow the instructions, everything is a lot easier. If you need to modify the y_offset, then add
To user overrides. That's it.
So you would recommend deleting all of the other beacon things I have?
I'm not sure what you mean by "all the other beacon things", how much did you change?
Here is what I had added for the beacon. I'm not sure what I need to remove to fix the Probe error
ah.. Yes delete everything under [beacon] except y_offset.
And delete the two yellow lines from your last pic
Oh you need to delete the safe_z_home section too
That's not a thing in RatOS.
Really you should pay attention to the comment at the beacon include:
That's literally all that should be done
What do you think about the bed mesh section? I wanted to make sure I had the correct size, speed, and increase the number of probe points?
I use maybe more points myself with beacon. 50x50
i believe at 600 mm/s
But make sure your mesh is scanned first.
If you're limiting your Y (because of the mod you're using and the rear leadscrew for example) or using a different mod etc, you may need to adjust your bed mesh min/max and change your y_offset.
But that is it.
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
This is what I am using to attach.
Yeah the config is made for that
I will remove the y offset part.
Only it cannot adjust your bed mesh. So make sure you set your Y endstop so that your beacon won't hit the rear leadscrew.
This is probably why you get 16mm and not 27.
So y_offset is fine
What do you mean adjust your bed mesh? Also I have made sure the y endstop is triggered before it hits the rear leadscrew
bed mesh min/max. If you limit your Y position_max, you'll get an error when the bed mesh attempts to scan outside your defined boundaries.
Also I have made sure the y endstop is triggered before it hits the rear leadscrewPerfect. This is what i'm talking about. When you do that you move the physical position of the virtual dimensions. Y=0 will have moved forward.
Gotcha. So I should delete this section as well? For yours how do you edit the speed or the number of points?
You need to adjust your [stepper_y]
position_min and position_max. Verify that 0,0 and 400,400 is within your print sheet.
No, you can change those to your liking. However you should delete horizontal_move_z.I have a 500, so I should ensure that 0,0 and 500,500 are within the print sheet? If this is correct, should the mesh min and max be 0,0 and 500,500?
Yes, sorry. 🙂
And no, bed_mesh is confusing and subtracts the probe offsets.
Attempting to scan up to 500 would put your toolhead at 516.
(causing an error)
Oh, so I could do 0,16 and 500,484 if I wanted to.
Potentially, you'll have to experiment and make sure everything is set correctly if you want to min/max it like that.
Do you have any recommendations? Like is 20mm a good buffer on both x and y?
The mapping between virtual coordinates and physical space is important to get right.
The defaults are my recommendation. That's why i made it. 😂
Okay, so how about I just get rid of those lines for right now!!
Yes, just remember your repositioned your endstop and thus moved the entire virtual space in physical space.
So just make sure that's set up correctly.
Do you mind if I save and restart my firmware, then turn off and on my printer, and then see if the error is still there?
No, but i have to go, i'll check in on you later.
You don't need to turn it off and on to check the error. Save and restart is enough.
Thank you! I am still getting the error, so maybe we can talk later. I really appreciate your help so far. I was supposed to run my printer for the first time today as I just finished making the cabinet that it sits on. Thank you again!
Post your klippy.log (download from machine tab) and i'll take a look when i'm back
Also adding in that my things are up to date!!
Can't find any issues ... try deleting this part from your printer.cfg
Hmm, still getting the error.
Do I just need to reset my printer config or Pi or something?
You can try resetting your printer.cfg, but i fail to see anything wrong with it, honestly not sure what's going on.
you can replace it with the v-core-3 template found in
RatOS/templates/v-core-3-printer.template.cfgSo copy in that template save and restart? Then go back in and change the values I need?
pretty much yeah
Should I just copy paste it into the current printer.cfg, or delete that and make a new one?
I just don't know what to do. I have never even printed with this machine and it feels like all I do is run into problems. This error didn't occur yesterday. It only showed up when I started the printer today.
Looking at the boards, everything is plugged in correctly. My toolboard, pi, and mainboard all have lights. I can't check to see if the beacon is working as I can't do anything with the printer homing with this error.
Is it a RatOS thing? Should I uninstall it, wipe my boards and go with a different operating system?
Looking at the boards, everything is plugged in correctly. My toolboard, pi, and mainboard all have lights. I can't check to see if the beacon is working as I can't do anything with the printer homing with this error.
Is it a RatOS thing? Should I uninstall it, wipe my boards and go with a different operating system?
Is it a RatOS thing?No Like i said, i'm running Beacon no issues. Multiple people are. You can try reinstalling, but i have no idea what's going wrong with your setup. Could be because the beacon isn't connected actually. Send me a screenshot of the machine page in mainsail The "System Loads" tab specifically I would just assume you'd get an error about the beacon MCU and not that the virtual probe pin alias wasn't registered, it's very odd.
You should see this
Wait a minute.. You should have info messages about untracked files in here..
I think you done goofed something
If that's not there, that means all the plugins are missing. Did you hard reset klipper?
I updated it this morning.
How do I get the plugins back?
This is what I have for system loads.
Go to http://ratos.local/configure and click the "Actions" dropdown on the top right of the page, then click "Symlink klipper extensions"
Right it's not connected to anything whatsoever because the config never loaded.. nevermind.
Go to the configurator and restore the extensions from there.
Everyting is now connected. I feel like a complete idiot. I am sorry for wasting your time today.
Finally, thank you for all the help on this.
Just to be absolutely sure everything is restored to it's proper working order please do this:
That'll fix everything RatOS need to keep itself running when you update.
No worries
So I just put that in the console?
Oh, no you run that from the commandline of your computer
Assuming you're on windows, press WIN + R, enter "cmd" and hit enter
Then put in those lines. one at a time. First line will connect to your raspberry pi. User is
pi password is raspberry
Next line will run a script that fixes everything that needs to be fixed.Done!
Thank you so much!!
It is up and working! Thank goodness!