RatOS 2.0 upgraded to v2.1.x - Custom V-Core 3.1 with Etched Foil bed heater w/ 3 combined sensors.
Hi everyone,
I'm running a modded V-Core 3.1 AWD that was working great on RatOS 2.0. But after upgrading to 2.1.0-RC2-106-g8614d79, my custom bed heater setup stopped working because of a conflict with an existing parameter.
The Etched Foil heater has double thermistors (named as "bottom_x") and the 12mm alumium plate has another one in the top. As the whole bed system/ arms are metal I am able to heat the heater to 180C (on the bottom) without problems, so that allows me to get the desired temperature in the top much faster than usual (usually 105C).
The issue is that the sensor_pin: heater_bed_sensor_pin parameter is predefined in /RatOS/printers/v-core-3/v-core-3.cfg (v2.1) under [heater_bed], which clashes with my custom setup using sensor_type: temperature_combined in printer.cfg. This parameter didn't exist in v2.0, so it's causing the error: "Option 'sensor_pin' is not valid in section 'heater_bed'".
Since these parameters don't play nice together, is there any way to 'unset' the pre-existing sensor_pin config to avoid this clash?
I'd really appreciate any help with this!
Thanks in advance!
5 Replies
This is basically the configuration I need to set:
[heater_bed]
heater_pin: PF5
max_power: 1
min_temp: 0
max_temp: 130
sensor_type: temperature_combined
sensor_list: temperature_sensor bed_bottom_1, temperature_sensor bed_bottom_2, temperature_sensor bed_top_1,
combination_method: min
maximum_deviation: 100
pwm_cycle_time: 0.02
[verify_heater heater_bed]
check_gain_time: 300 # Increased to allow more time for heat transfer
hysteresis: 10
max_error: 25 # Increased to allow for larger temperature differentials
[temperature_sensor bed_bottom_1]
sensor_type: ATC Semitec 104NT-4-R025H42G
sensor_pin: PB0
min_temp: 0
max_temp: 175
[temperature_sensor bed_bottom_2]
sensor_type: ATC Semitec 104NT-4-R025H42G
sensor_pin: PB1
min_temp: 0
max_temp: 175
[temperature_sensor bed_top_1]
sensor_type: ATC Semitec 104NT-4-R025H42G
sensor_pin: PC4
min_temp: 0
max_temp: 130
copy the ratos.cfg to another file and change what you need. Then include that custom file instead of ratos.cfg
Thank you very much @blacksmithforlife, it worked perfect.
[heater_bed] has had sensor_pin defined since the very first release of RatOS. That's not new.
Did you just not include the default v-core-3 configs in 2.0?
Seems like i should implement a "section blacklist" feature, so that the configurator omits the blacklisted sections for custom implementations.
That’s a good point, and you’re right, I probably completely forgot about that part.
Thanks for the clarification @miklschmidt