RatOS Alpha bug?
Running the latest RatOS Alpha. V-Core 3.1 500. EBB36 toolboard with Super Pinda
Everything works great. No issues with homing, z tilt or running a PAM mesh for prints, but when I try to do a full bed mesh run the probe goes to the front left and off the build plate, causing the nozzle to crash into the bed. Works fine in stable release.
(Also out of curiosity, why has the prime blob been moved to the right side of the bed VS left?)
Thanks!
44 Replies
Are you using sensorless homing?
The prime blob was moved because of stowable probes.
I am not using sensorless homing
Please post your printer.cfg.
You're missing #[include config/printers/v-core-3/physical-endstop-x.cfg] on line 97
But that wouldn't fix your problem. Have you tried disabling PAM?
As in, don't include it, don't include the parameters in START_PRINT either
I'm asking since the bed_mesh hasn't changed for a year: https://github.com/Rat-OS/RatOS-configuration/blame/v2.x/printers/v-core-3/500.cfg#L16
GitHub
RatOS-configuration/printers/v-core-3/500.cfg at v2.x · Rat-OS/RatO...
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
So it's some of your extras
Is your probe offset right?
https://github.com/Rat-OS/RatOS-configuration/blob/v2.x/z-probe/probe.cfg#L7
GitHub
RatOS-configuration/probe.cfg at v2.x · Rat-OS/RatOS-configuration
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
You also have skew correction but nothing defined under it
the skew correction settings are in the klipper config section
Ok, well disregard that then
I have an toolboard connected, so it's on line 259/260. Do I need both?
I'll disable addons one by one and see if it makes any difference and report back
It's a stock EVA setup but I'll doublecheck all the measurements just to be safe
Yes, but it'll work without it, but it would be good practice using both, the toolboard part only overrides the pin.
Checked the offset and it's close enough (off by about a MM to the middle of the probe), and uncommented X end just because and no change. I'll install a fresh copy and see what happens
Update: full fresh install with any addons commented out and it’s still giving the same issue. Saw a comment on the video asking what I was pressing. It’s configuration, bed mesh, add profile, and save. Same thing happens when using the web ui to make a full bed mesh (heightmap, calibrate, calibrate) Here’s another video https://youtu.be/sVuSMCaaWhA
Huh? Why are you adding a bed mesh, that is done as part of the start print macro isn't it?
To check to see how flat the bed is and if the frame needs adjusted at all
I am not used to that front screen, but in mainsail you just do
BED_MESH_CALIBRATE
in the consoleSame error. The probe goes off the bed and the nozzle crashes into the bed.
Wonder if it has anything to do with changing to a toolboard, as it worked fine previously and with the stable branch
I'm also noticing that the Super PINDA probe only probes the bed once when doing any tilt correction/meshing vs collecting multiple samples when connected directly to the board on stable branch.
Only on leveling Z it does it twice (as shown in the video)
Mikel can correct me if I am wrong but I don't think it has anything to do with the tool board stuff. He did rewrite a bunch of the macros so maybe something in there. It seems like it isn't applying the correct offset for the probe or has the wrong points defined or something
If you home just X and then manually move your hotend all the way to X max, what is the number you get? I am trying to see if maybe the endstop is in the wrong place and so X=0 is in reality a negative number for you
One moment
It maxes at 500 but it looks as there’s still a bit of room
After moving all the way to the right, 0 on X looks correct
I also see no visual difference in regards of “nozzle to bed” location between having the nozzle at X0 Y0 and X0 Y500, just to rule out an insanely skewed frame lol. (Hope that makes sense). Also, just for the hell of it, here’s a video of Z home vs tilt https://youtu.be/7j2c8QB7cHA
What happens if you add this to your config?
Can you show me where the nozzle is on the bed when you go to 0,0?
Hmm, this fixed it. Mesh ran fine with this added to the config file.
Well that is good in that it is actually obeying the config. But curious that other people aren't having problems. @miklschmidt I noticed the min is 20,20 - but the X offset for Eva 3 is like 28mm. So maybe the default should be like 40,20?
It may that be the active installs of alpha and those who are trying to run a full bed mesh is pretty low. I'd guess people who are running it already have a pretty well tuned machine, so a full bed mesh wouldn't necessarily be needed. Only reason I was running it was to make sure the changes I made to the frame earlier this week didn't throw everything out of whack.....and looking at my mesh it badly did lol
bed_mesh takes probe offset into account.
I'd guess people who are running it already have a pretty well tuned machine, so a full bed mesh wouldn't necessarily be needed.Not the case here. I always test the vanilla release and i can't reproduce it. Also find it strange because it hasn't changed. Can't see the nozzle here, can you take pics from the front and sides? omg.. I know what your problem is now. You never uncommented a z-probe. So you have no offset. Uncomment that and your problem is solved 🙂 line 87
Ah shit that did it! Wow. lol I guess I skipped past it when I was setting up the tool board. I am so sorry for wasting everyone’s time >.<
No worries, support is what we're here for! I missed it too 😂
Yeah I missed it too. I really need to get a app for my phone that does syntax highlighting
Thank you both. I massively appreciate it
Thanks for bearing with us as we made you troubleshoot everything
No no not at all! Thank you for helping so much!
running into same issue..
post a new thread please
https://discord.com/channels/582187371529764864/1047085604808167424/1047085604808167424
make your own postplease don't reuse this one, make a new post
sry i was reading it checking if any in it would help, seems identical issue