kasztimate
RRCRat Rig Community [Unofficial]
•Created by kasztimate on 2/19/2024 in #fix-my-printer
Relative_Reference_Index leftover in update blocks Voron to start.
Hi @miklschmidt ,
I have recently updated my Ratos operated voron to the latest and found out that you have left the relative_reference_index entry under bed_mesh and the latest klipper update removed it, so it wont start now. Can you please do a quick modification in the RatOS folder so we can start our printers anytime soon?
If there is a workaround until the official release please do not hesitate to share.
Thanks!
Mate
11 replies
RRCRat Rig Community [Unofficial]
•Created by kasztimate on 11/24/2023 in #fix-my-printer
Timer too close and Lost connection to MCU errors
Dear Community,
I am running a RatRig Vcore 500mm with USB Toolboard.
The specs:
Raspberry Pi4 B+ 2GB (reads 1,6GB RAM only) - 64GB Kigston MicroSDXC card - Active cooled (Mostly 45C all the time)
EBB42 v1.2 without MAX - 3DO 2m USB cable + 2x0,75mm wire for power - 2x1mm Piano wire for umbilical + zipped so the connector does not move
Octopus V1.1 Board
Phaetus Rapido HF hotend
24V Supply
BTT TouchScreen 5” with FCC cable + KlipperScreen
FW versions:
klipper
v0.11.0-303
KlipperScreen
v0.3.6-52
mainsail
v2.8.0
moonraker
v0.8.0-186
RatOS
v2.x: v2.0.2-15
ratos-configurator
v0.0.0-67-gc5b78c02-inferred
RatOSTheme
v2.0.2-0-g515851db
timelapse
v0.0.1-142-g57bec0de
Host Klipper version says dirty at the end: v0.11.0-303-g67499853-dirty
Also sometimes its failed to start up then I have to power cycle it 1-2 times. Also sometimes don’t get the wifi signal and starts as RatOS but the configuration is still good. After a restart it catches up with the Wifi. Signal strength should not be an issue as I have a Voron which is next to it and it starts all good. BTW they both share the same electronics and it never happened on the Voron.
My problem is sometimes I have this error message:
Klipper reports: SHUTDOWN
MCU 'toolboard' shutdown: Timer too close
And sometimes this:
Klipper reports: SHUTDOWN
MCU 'toolboard' shutdown: Lost communication with MCU
What I did already:
Before the umbilical upgrade to 3DO cable and piano wire a lot more error happened.
I lowered the micro stepping to 16
Only Input shaping is enabled ADXL is disabled (its only needed for measurement) - it improved a bit.
Restarted the printer before every print - No change
Speeds are: 350 travel - 150-250 print
Max access is 9000mm/s2
Can someone point me in the right direction?
Thank you guys, I will send virtual beers to all 🙂
Have a nice weekend!
Mate
98 replies
RRCRat Rig Community [Unofficial]
•Created by kasztimate on 11/24/2023 in #ratos-support
Timer too close or Lost communication with MCU errors
Dear Community,
I am running a RatRig Vcore 500mm with USB Toolboard.
The specs:
- Raspberry Pi4 B+ 2GB (reads 1,6GB RAM only) - 64GB Kigston MicroSDXC card - Active cooled (Mostly 45C all the time)
- EBB42 v1.2 without MAX - 3DO 2m USB cable + 2x0,75mm wire for power - 2x1mm Piano wire for umbilical + zipped so the connector does not move
- Octopus V1.1 Board
- Phaetus Rapido HF hotend
- 24V Supply
- BTT TouchScreen 5” with FCC cable + KlipperScreen
FW versions:
klipper
v0.11.0-303
KlipperScreen
v0.3.6-52
mainsail
v2.8.0
moonraker
v0.8.0-186
RatOS
v2.x: v2.0.2-15
ratos-configurator
v0.0.0-67-gc5b78c02-inferred
RatOSTheme
v2.0.2-0-g515851db
timelapse
v0.0.1-142-g57bec0de
Host Klipper version says dirty at the end: v0.11.0-303-g67499853-dirty
Also sometimes its failed to start up then I have to power cycle it 1-2 times. Also sometimes don’t get the wifi signal and starts as RatOS but the configuration is still good. After a restart it catches up with the Wifi. Signal strength should not be an issue as I have a Voron which is next to it and it starts all good. BTW they both share the same electronics and it never happened on the Voron.
My problem is sometimes I have this error message:
Klipper reports: SHUTDOWN
MCU 'toolboard' shutdown: Timer too close
And sometimes this:
Klipper reports: SHUTDOWN
MCU 'toolboard' shutdown: Lost communication with MCU
What I did already:
- Before the umbilical upgrade to 3DO cable and piano wire a lot more error happened.
- I lowered the micro stepping to 16
- Only Input shaping is enabled ADXL is disabled (its only needed for measurement) - it improved a bit.
- Restarted the printer before every print - No change
- Speeds are: 350 travel - 150-250 print
- Max access is 9000mm/s2
Can someone point me in the right direction?
Thank you guys, I will send virtual beers to all 🙂
Have a nice weekend!
Mate
4 replies