MCU reporting incorrect temps
hello, Im not sure if this is a firmware issue but ive had an issue with my control board mcu reporting very high temps. is there a firmware fix or have i fried something?
Initial beacon calibration fails constantly...
I´m now trying since some hours with calibrating my beacon h.
I don´t get something.
Beacon screws are tight...
I don´t know how to get this beast working on my VC4/300.
Any help is appreciated....
How do I create a new printer configuration?
Hello. I want to create my own configuration in RatOS for my printer, which is not supported by the system as standard. Is there an instruction or short instructions for this? At the moment, the main problem is a misunderstanding of the overall picture of the dependence of some files on others (many parameters are specified several times in different files). When trying to create a completely new printer and specifying "template": "vostok-printer.template.cfg" in printer-definition.The error "Ca...
RatOS initial setup and configuration
I followed the steps for initial configuration and after that, I am getting an error. Since there isn’t much information about the troubleshooting, I hope to find the solution here. Where do I start?
RatOS 2.1 Manta M5P Missing motor configuration in RatOS Configurator
I am trying to install RatOS 2.1 on a Manta M5P board and at the very last step in the configurator I get errors because stepper configuration is missing. In the previous step I can choose the motors and then in the last step I cannot Confirm and Save since config for the Z1 and Z2 motors are missing.
Error...
BEACON_INITIAL_CALIBRATION moves the head to incorrect place, crashing head
Vc4 400. v2.1.0-RC2-106-g8614d79e.
Most of the time the BEACON_INITIAL_CALIBRATION works ok. However on two occasions it (or BEACON_RATOS_CALIBRATE) has now moved the head to x=400 before doing initial approach. First time was as part of BEACON_RATOS_CALIBRATE. The second time was when running it explicitly. The first time this happenend, I believe the y was also set to 400, since the head moved to the very back right corner. In that position there is nothing that beacon would detect, so the head crashed with the bed during the initial approach.
The second time y was at 200, so perhaps beacon would have stopped, but i switched off the printer rather than wait and see.
What might cause this? An uninitialized variable somewhere? ...
What might cause this? An uninitialized variable somewhere? ...
Solution:
Missing G90. You're in relative positioning, so you've already homed and have moved the axis around with the mainsail toolhead dialog (which sets relative positioning)
