MCU protocol error, 4028 fan going full blast, 4 pin doesn't work.
Yeah I'm getting a mess going on for some reason. I just upgraded a fan and put a beacon on and now I'm getting errors all over the place.
I commented the pin for the fan to !PD15 cuz apparently J55 doesn't work.
Then the 4-pin fans part cooling is declared "not a valid pin name" after I just commented the line....
Unknown command:"BEACON_RATOS_CALIBRATE" and 4028 fan not working
When I run BEACON_RATOS_CALIBRATE it gives me this error, I can also not update anything even after clicking check for updates multiple times.
My 4028 fan is also not working, the connection is fine and I have set the voltage correct on the right fan connector. I did accidentally connect the tacho to the pwm pin on the toolboard for a while though, did I kill it?...
Solution:
I'm out of town, so ability to help is greatly reduced. Did you follow the update procedure as outlined elsewhere? Search posts by me and you'll probably find it, it's about 15 steps long.
Heater Fan Soft PWM issue
Hello all, I got a new hotend fan and its lower voltage so I wanted to add a 'Max_Power' section to the hotend fan config, this apparently isn't allowed, is there a way of getting around this soft PWM issue.
"Webcam stream not available" despite service running, logs good (?)
I had VAOC working before, no physical changes were made, but I did a fresh RatOS install and now I'm getting these errors. I have SSH'd into the Pi and checked log files. Crowsnest looks good afaict:
```
[05/25/25 06:32:03] crowsnest: zoom_absolute 0x009a090d (int) : min=0 max=60 step=1 default=0 value=0
[05/25/25 06:32:03] crowsnest: iris_relative 0x009a0912 (int) : min=0 max=0 step=0 default=0 value=0 flags=write-only...
Solution:
OKAY, this was 100% my fault. I didn't realize how much stuff is NOT covered in the printer.cfg. When I reinstalled RatOS to the SD card and copied in the printer.cfg, I didn't realize I still had to go through the commissioning guide, which included modifications to crowsnest.cfg.
I updated crowsnest.cfg, restarted and all is fine now. Whoops. Not sure if this should be deleted, or maybe a good lesson for someone else who makes the same mistake....
Manta M8p 2.0 configuration only allows to set one 4 pin fan header
In both 4 pin fan headers are used in the configuration for part cooling fans, it sets both the fans with same pins, causing an error unless overwritten in printer.cfg manually.
Expected behavior would be the configurator setting pins for the second fan to be that of the second 4 pin header....
RatOS configuration sets wrong pins for 2240 drivers
RatOS 2.1, board: Manta M8P + pi CM4 compute module with eMMC, BIGTREETECH TMC2240 V1.0 steppers.
The SPI pins set by the RatOS configurator are wrong and cause error when attempting to move any axis. The makeshift solution is to overwrite the pins in printer.cfg
The order of changes that got me this problem was as follows:
Change board to Manta M8p 2.0 with standard 2209 steppers -> change steppers to 2240 and bridge the correct SPI pins on the board -> go to configuration and change the steppers there....
Nozzle Diameter settings not updating.
RatOS configuration HARDWARE SELECTION step, Firefox browser.
When changing the nozzle size by clicking up or down the settings does not update, instead it is necessary to either write the number manually or after changing it with the arrows put the cursor in and press enter.
This is most likely unintended behavior and could cause confusion (it did for me at first), probably caused by the arrows not automatically confirming the value with each press, only changing the displayed value....
Getting an error
Getting this error think it’s because the tool head I use does not use a hot end fan this is on a v2.4 and also I don’t know where in ratos to change the gear ratio for the z drives
Problem with updating RatOS configuration trying to install ratos
I have been to update ratos configuration but it’s been stuck for 2 hours with no change when I refresh the webpage I need to reflash my sdcard to log into ratos.local
New Box Turtle Setup - First one works great, second one fails as soon as print starts with error
So I've got 2 box turtle units hooked up to my VC3.1 (single extruder, multi-material), and boy has it been less than smooth sailing with RatRig's built-in T0 macro colliding with AFC and the slicer's T0/lane1 load command. Finally sorta worked around all that, added a filament cutter/purge/wiper system and got my first box turtle unit working quite well now.
So now I'm moving on to stress testing the second unit, but when I start a print with it everything acts like it's working perfectly fine until the nozzle finally arrives where it would start printing. The second it arrives this error is thrown in the console.
Anyone here who happens to be knowledgeable in both RatOS and AFC/BT, and might have any idea where I would look to figure out why my first box turtle works great, but the second one throws this error? I've found the macro and what I believe could be the specific line causing the error...but I'm super confused as to why it is doing this, when the first unit works perfectly fine. Both box turtles are configured identically 😦...
Help with Beacon Calibration
Since first assembly, beacon hasn't responded properly. Just tried re-flashing with an sd card rather than usb-stick and am running into a similar issue. Anyone know what the issue could be?
Rpi runs hot @ Ratos 2.0
Hello. I recently connected an Rpi v1 camera to my Minion and set everything up according to the Crowsnest instructions, and it's working. I didn't even have any problems for days, but suddenly the Pi started overheating in standby mode, reaching between 52 and 60 degrees Celsius. I read in htop that Crowsnest is using a lot of power. Is something wrong since an update or is it configured incorrectly, or is the Rpi1 camera using so many resources?
