Hi, I just upgraded my v core 4 with an octopus pro v1.1, and 56v psu for motors, everything works (motors, hotend etc...) I do the commissioning guide from start and ratos crash when the beacon initial calibration start to heat de bed, but no problem when I heat it manually. Only the motors power is on 56v by the board. Board and bed is always on 24v psu. any idea ?
#RatOs crash with 56v upgrade
6 messages · Page 1 of 1 (latest)
What does "ratos crash" mean? Are you on 2.1RC4?
I don’t have any error message, ratos restart after the beacon_initial_calibration try to heat the bed, I’m on 2.1RC3 right now
What does ratos restart mean? Do you mean that klipper restarted, and you were greeted at the console with the
```
Welcome to RatOS 0c1b392d
Base image: RatOS v2.1.0-RC4 (bullseye)
Updated to: 0c1b392d
What does you mainsail console have?
IIRC, beacon_initial_calibration does not heat the bed, it just homes and sets leds etc, and then runs BEACON_AUTO_CALIBRATE :
```
[gcode_macro BEACON_INITIAL_CALIBRATION]
gcode:
# parameters
{% set automated = true if params._AUTOMATED|default(false)|lower == 'true' else false %}
# config
{% set speed = printer["gcode_macro RatOS"].macro_travel_speed * 60 %}
# home x and y axis if not homed already
MAYBE_HOME X=True Y=True
# visual feedback
_LED_BEACON_CALIBRATION_START
# Absolute positioning
G90
# Go to safe home
_MOVE_TO_SAFE_Z_HOME
# auto calibrate beacon
BEACON_AUTO_CALIBRATE
# raise toolhead to safe z-height
_Z_HOP
# echo
RATOS_ECHO MSG="Initial beacon contact calibration finished!"
{% if not automated %}
_CONSOLE_SAVE_CONFIG
{% endif %}
# visual feedback
{% if not automated %}
_LED_BEACON_CALIBRATION_END
{% endif %}
```
It would sound like the issue is somewhere else than bed heating. What prompts you to think it is the bed?
It’s when the script start thermal compensation, so the bed heat to do that (by memory because it’s was last week and I’m not at home)