Robee
Robee
RRCRat Rig Community [Unofficial]
Created by Robee on 3/9/2025 in #ratos-support
Set heat soak time in the slicer?
With that exact line in my Gcode I get the following console error Unknown gcode_macro variable 'bed_heat_soak_time'
16 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 3/9/2025 in #ratos-support
Set heat soak time in the slicer?
ah I need to remove the variable_ prefix, thank you!
16 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 3/9/2025 in #ratos-support
Set heat soak time in the slicer?
I feel like I am doing something wrong, I can't seem to set this in my slicer Gcode. 😦 If I use SET_GCODE_VARIABLE it throws an error Unknown gcode_macro variable 'variable_bed_heat_soak_time', and if I just put the line in on its own, it throws Unknown command:"VARIABLE_BED_HEAT_SOAK_TIME=1"
16 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 3/9/2025 in #ratos-support
Set heat soak time in the slicer?
Thank you, I'll try that!
16 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 3/9/2025 in #ratos-support
Set heat soak time in the slicer?
Do you mean the variable? variable_bed_heat_soak_time
16 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 10/4/2024 in #ratos-support
Prime Line instead of Blob?
Thanks Helge! I thought it would be doing the opposite, maybe my snot is coming from somewhere else...
10 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 10/4/2024 in #ratos-support
Prime Line instead of Blob?
It does stick to the bed, but the nozzle drags through it and I'm sure there is residue that gets stuck to the nozzle and burns 😦
10 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/29/2024 in #fix-my-print
Under extrusion on retractions
Managed to fix this by adjusting my pressure advance using Ellis' Print Tuning guide and test print rather than the Klipper docs
5 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/29/2024 in #fix-my-print
Under extrusion on retractions
No description
5 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/25/2024 in #fix-my-resonance
V-Core 3.0 500 Belt Tension
Cool, as long as tension is okay, I think the other bits are just the wires to the toolhead which aren't tied down and can wobble about a bunch. Thank you!
7 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/25/2024 in #fix-my-resonance
V-Core 3.0 500 Belt Tension
And which belt does this mean I need to tighten or loosen? 🙂
7 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/25/2024 in #fix-my-resonance
V-Core 3.0 500 Belt Tension
Yes, I'm running RatOS 2.1, just wondering what does it look like if my belts are tensioned correctly?
7 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
Z-Tilt scared the hell out of me when my 500x500 bed started flying towards my nozzle, I emergency stopped that right away since I'd not even tested z homing
30 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
I have done a few things, so I'm not sure what has helped, and I won't count my chickens until they hatch, but I reformatted the octopus SD card to be blank FAT, reimaged the Pi SD card with the 2.1.0-RC2 image, made sure I updated everything in update manager before going further, began the whole setup again reflashing both the octopus board and EBB36 without any version mismatch warnings this time (it's interesting klipper version seems older in RC2 to what I had?), and so far I can move all the axis without any errors. 🤷‍♀️
30 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
I think it is up to date already 😦 RatOS v2.0.2-36-g230929e3
30 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
I have an SD card in the Octopus board if that matters? It was blank FAT32 formatted when I put it in there tho
30 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
I've reflashed klipper on the octopus and despite this confusing message "Version mismatch The board is running version v0.12.0-296-gcc4ad667 but you your pi is on version v0.12.0-296-gcc4ad6670. If you want to update your board click 'flash again' below" Nothing's better :/
30 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
yes, pretty sure, checked the STM32 chip is an F446, the board is marked bigtreetech octopus, and dmesg shows: [ 2.451445] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd [ 2.563571] usb 1-1.2: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00 [ 2.563645] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.563675] usb 1-1.2: Product: stm32f446xx [ 2.563698] usb 1-1.2: Manufacturer: Klipper [ 2.563721] usb 1-1.2: SerialNumber: btt-octopus-11 Plus /dev/btt-octopus-11 exists I removed modemmanager which fixed that error from appearing in the logs but otherwise has had no effect.
30 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
30 replies
RRCRat Rig Community [Unofficial]
Created by Robee on 9/20/2024 in #fix-my-printer
Timer too close on V-Core 3.0 500 with Klipper
I think I spoke too soon, I can buzz all the steppers but the moment I try to home any axis it reoccurs 😦
30 replies