Erik Persson
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 6/8/2024 in #ratos-support
Invalid option pullup_resistor
Hi,
I just upgraded to RatOS 2.1RC from having previously had a 2.0 configuration (and ran 1.x before that). Early on I also upgraded from a regular Rapido to one with a PT1000 thermistor but I had issues getting that to work on the regular thermistor connector. That problem was solved by using the MAX31865 port and setting sensor type accordingly. I have configured accordingly (or so I hope) with overrides in the extruder section of printer.cfg but since the default RatOS toolboard + PT1000 config template sets the sensor type to PT1000 and also sets pullup_resistor klipper will bork in pullup_resistor being invalid for the sensor type.
Anyone who as a tip on how to solve this in a reasonably elegant way? Can you unset paramaters in klipper overrides these days? I realise that if my original issues with the thermistor port was with my configuration and not the board I could rewire but I'd rather print that starting to mess with the config again. Right now I am coping by commenting out the option in RatOS.cfg on each boot which is not exactly ideal.
5 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
Hi,
Having been a very happy camper running buster-based RatOS 2 alpha I proceeded and reinstalled with the alpha 5 bullseye image and merged my old conf into the new one. Everything was fine until sometime after I applied updates which included klipper to v0.11.0-86-g6026a99a and sometime after that the board would no longer show up on the USB bus following a firmware restart.
I have found myself in the position of having an inaccessible MCU and so far I have been able to dig myself out of that particular hole by setting the board to DFU mode and flashing klipper with 'make flash...' but now there seems to be something wrong with the build environment. The steps I have been following to build and flash is to:
# set octopus to DFU mode, and reset. lsusb shows:
# Bus 001 Device 003: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
cd klipper
../printer_data/config/RatOS/boards/btt-octopus-11/firmware.config .config
make clean
make flash FLASH_DEVICE="0483:df11"
The flashing part bails however with:
Flashing out/klipper.bin to 0483:df11
Usage: flash_usb.py [options] -t <type> -d <device> <klipper.bin>
flash_usb.py: error: option -s: invalid integer value: ''
make: *** [src/stm32/Makefile:98: flash] Error 2
As far as I can tell it fails because no valid argument is set for -s. Making the Makefile echo the flash command shows:
@python3 ./scripts/flash_usb.py -t stm32f446xx -d 0483:df11 -s out/klipper.bin
In the same Makefile it appears that -s is set to "$(CONFIG_FLASH_APPLICATION_ADDRESS)" but I cannot see where that variable is supposed to come from.
Any ideas?
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 12/3/2022 in #ratos-support
Print job gets paused waiting for filament
My RatOS 2 V-Core3 har suddenly started with this annoying habit of going though all the motions when starting a print, including homing, tilt, mesh prime blob and then it parks itself at X250 Y500 and prompts me to load filament despite me already having done so. If I oblige and then resume the job it proceeds normally.
It did not do this before. I may very well have changed something while working with the printer without realising it would affect this.
I typically select the PETG heater profile and then "Load filament" with a suitable temperature.
Any ideas what I am doing wrong?
5 replies