Another Duplicate Chip name 'probe' error
Hi there, I just installed Beacon H, changed the config (attached), but Klipper returns an error. BLtouch is installed/connected to the board. System is up to date (2nd attachment). I'll will appreciate help with this issue!
Turning the Heated bed off during meshing
Im using a eddy current scanner and im wanting to know if there is a easy way for me to implement turning the heated bed off while it scans, i think the 240v heated bed is causing some interfernce with the mesh and for the 30 - 40seconds it takes to scan the bed it wont make a huge difference from a heat point of view
Klipper reports SHUTDOWN : verify_heater. ##Urgent##
This error is driving me nuts. I have 4-5 models , printed to 10-20%
I have a 6-7 day print that I need urgent.
After 12-36 Hours this error appears.
*...
64-bit v2.0.2?
Is there a reason there is no 64-bit v2.0.2 release on Github? I've tried searching issues there and Discord here but either I'm blind or it hasn't been brought up. With an 8GB Pi4 I'd usually want to install 64-bit, so is there any harm in just installing the v2.0.1 release and updating? Or has 64-bit been discontinued or something?
Solution:
I'll answer here as well - yes there is a reason why it doesn't exist. It used to exist and there were bugs caused by the 64 bit versions. The only advantage is a single process can access more than 4gb of memory, but no single process needs that much in klipper so that argument is moot.
"Timer too close" errors keep occurring.
36 HOURS into a ~48 hour print and I just got another timer too close error. This is on a Pi 4 8GB, after a brand new v30 SD card, and new USB cables connecting both my Octopus and ERCF mcu's. Already tried removing my klipper screen hardware previously and that didn't fix the issue either. What should I try next?? Going to poke though log files now but any advice on what might be worth a test next?
Error message
Just updated software and getting this error message. Option 'max_accel_to_decel' is not valid in section 'printer'. Checked the printer speed cfg and everything looks OK. Anyone else with the same issue?
bad configuration of legit x and y for printing with inductive probe
Hi all,
On bed mesh, the printer tries to mesh according to the location of the hotend, but the inductive probe is a bit to the side, and sometimes doesn’t trigger as it partially above the print bed.
Should I order a bit larger print plate?...
BTT kraken support.
I would love to use RATOS but there is no config file for the BTT Kraken board yet. I have tried to go through the setup saying its a BTT Octopus board while loading the correct Kraken firmware from github onto the sd card. Consequently I have emptied the printer.cfg file and pasted the config.cfg from the BTT Kraken github.
Anybody got a clue on how to get the BTT Kraken working on RATOS?...
Enforced Heat Soak Timer
Is there a parameter somewhere that I can adjust to say wait for 2 minutes after heating the bed but before doing the leveling and bed mesh?
Would like to make sure the heat has settled throughout the bed....
How to restart a failed print?
I had a failure with a "Extrude below minimum temp" error and want to try to finish off the rest of the print before swapping out the ps which I'm guessing is the issue.
So how do I restart the print from where it stopped?
#restart print...
weird error toolboard related
Has anyone had a random crash then ADC out of range? then
MCU 'toolboard' shutdown: Rescheduled timer in the past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of...
Toolhead not connecting
I just got my printer fired up and I am setting up my printer.cfg. Can anyone help me firgure out why my toolhead isn't connecting.
9GAX0412P3S001 40x28 fan - 0 RPM reported through tacho
I know the tacho reporting is quality of life only.
There are two 4-pin PWM fans in my setup; a Noctua 120mm and the Sanyo Denki 9GAX0412P3S001 (part cooling).
Both are configured and working properly, except the tacho wire for the 9GAX0412P3S001.
It is configured in RatOS, the wire continuity is checked, I have triple-checked the pinout, but the reported speed is always 0....
Extra MCU not updated for new version of Klipper
Hi my extra mcu is an SKR mini E3 V3 and for months it has alway updated with new versions of Klipper. But for versions .....154 and now today .....155 the SKR mini has failed to update. What is going on? The printer is working and the skr mini is working as well, but it is still on Klipper 154. I will update via the configurator again but would love for this to stop happening
Flashing EBB42 v1.2 via DFU
Hello,
I just received a usb c/a cable and my ebb42 v1.2.
I connected the ebb42 to my raspberry pi4 via usb.
I connected the ebb42 with CAN(gnd+vin) to my psu with a wago (24v).
But I don't have an LED to turn on, and my DFU not detected...
Problem with z probe - led light works as expected, but the probe doesn't always change state
I've installed the probe which arrived with the ratrig v minion full kit.
Sometimes it shows as "open", and sometimes as "triggered" but not necessarily in correlation with the proximity to the pei sheet.
I re-crimped the connectors twice but no help there.
Important to mention - the led light on the probe does change color as expected....
Setting up adaptive mesh
Saw that i could do an adaptive mesh to avoid probing a whole 500 bed every print but it doesn't work.
do i need to set 'variable_calibrate_bed_mesh: False' to True? is this what's causing my printer to ignore the variable_adaptive_mesh: True ?
read my prusaslicer Gcode and it is spitting out dimensions...
ratos on prusa mini
hi everyone, I have a nice v-minion and a prusa mini and I'm happy with ratos, I wanted to try to convert the prusa mini to ratos, but between the manual and various forums, I don't understand how installing the firmware on the mini works. reference is made to an SD that the mini doesn't have (I imagine you mean USB), the card even in DFU doesn't allow me to install the firmware. Can anyone help me?
klipper reports startup
Hi there, I have updated my printer and since than, I cannot get past then blue anouncement that the klipper is in startup, try later. Sometimes it says cannot connect to MCU. I have restarted the printer and control board several time. I am running RPI and SKR V1.2, I might have accicentally pressed the reset button on it. Anyone experienced something similar? Any help is appreciated