Move exceeds maximum extrusion (at primeblob)
I get above error (4 times) while doing a primeblob. Printer (slicer and RatOS) is set for 0.6mm (CHT). I know how to correct this (add max_extrude_cross_section: 5 in [extruder]) but I was curious why this happens. If RatOS is Nozzle Aware...
IDEX config has T0 for both heads?
I'm not sure if I did something wrong or there's a problem with the configuration
Random Pauses? Please Help!
I am having issues with this print randomly pausing partway through the print. It never stops in the same place and never shows anything in the console. Any ideas what’s causing this? I’m so confused. I re-sliced it and again pauses random places. I have an orbiter filament sensor and a broken sensor that’s wired in, but I have yet to add anything to the configuration.
'gcode' in section 'gcode_macro RatOS' must be specified
Hello, I was trying to get my adxl working and this has come up. I havent changed any settings so im not sure why its suddendly decided to happen, anyone know how to fix it, cant seem tofind the mentioned item in config.
Solution:
follow the "how to recover from a hard reset" in https://discord.com/channels/582187371529764864/1233461645167169576
In consistent Z-Height when using bed mesh compensation. Temperature compensation not used
I re-did all my calibrations of Beacon as per Helge's manual from 1 to 5 https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/beacon_contact.md#6-first-print-and-fine-tuning.
At part 6 the nozzle is approx. 0.5mm to high, so I babystep to a proper first layer squisch. Enter SAVE_Z_OFFSET in the console. stop the print. Save_config. I see that the output now says:
Beacon model offset has been updated, new value is -0.46781
after restart, the next print is again approx. 0.5 to high and I can repeat this all night. I thought it should report nozzle_expansion_coefficient_multiplier which was then stored in ratos-variables.cfg?...
Solution:
So, Only thing that I can think of is that my reference Contact mesh somehow was erroneous.... or something in the other refference files was off. anyway, now I need to redo all the bed meshes But I think I solved it (by accident, that is)
Octopus V1.1 doesn't want to flash / get recognized by RatOS 2.1.X
Hi, earlier during my V-Core 4 build I accidentally installed RatOS 2.0.X. Now I reflashed the SD-Card with 2.1.X, and am trying to configure it. But for some reason no matter what I try, flashing the octopus doesn't seem to work in the configuration wizard.
Automatic flashing says there is no board detected.
In the DFU overview I can get it to detect it with the BIOS0 header, and then half a minute or so after pressing flash it simply shows the same, initial, DFU screen, as if it did nothing and can't detect it.
Pressing "Check Board Status" in the SD-Card section doesn't do anything, when in 2.0.X it did work for me....
still cant get first layers to be consistent
i'm at my wits end with this printer. im 10 days in and still dont have a first print done. i've been tryin to get my first layer issues sorted out. multiple beacon calibrations later, i'm still getting inconsistencies and non-sticking portions of prints. it's not the build plate, it's clean. the printer is not putting the plastic down close enough to the bed to smush on the external walls, it's constantly all over the place. it's exceedingly frustrating. this printer was supposed to be u...
Solution:
The only conclusion I came to was "maybe my x-rail was not mounted correctly or something"
