Arthur_C
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 2/10/2025 in #fix-my-printer
Rapido 2 thermistor not reading correctly (pt1000 on EBB42-with max31865)
After a full rebuild of my RR vc3.1 300, my thermistor now reads -237,5-ish (MINUS). I think it is caused by my own doing and am looking for some advise on how to proceed:
I am running a 3-wire hot end fan to monitor the functioning of this fan (curtesy of Andrew Ellis: https://ellis3dp.com/Print-Tuning-Guide/articles/useful_macros/hotend_fan_monitoring.html).
With the rebuild, I accidently put the fan's tachometer_pin wire in a 5V (probe) output of the ebb42 i.s.o. PB9. At first it all worked as before the rebuild. I heated the hot-end and got warnings for fan stoppage (as now is clear to me, as I did not wire it in correctly). I extruded some plastic and got a shutdown due to the hot-end fan not working (all as it should work!).
When I did a firmware restart I got a warning for the extruder being out of range. I lowered my min_temp and after that it started up but shows my extruder temp at high negatives.
I wired in a spare (identical) thermistor and that showed the same value.
I checked all the wiring and all seems fine.
So, I think I blew up something on the ebb42...?
- What are my options? (other than ordering a new EBB42-non Max31865, which I already did but needs to come from far-far-away)
- Can I wire the thermistor to other pins?
Appreciate all your thoughts and suggestions!
(to avoid the first reply being a ref to https://discord.com/channels/582187371529764864/1047086745415594044 I added the logs)
Full setup (I think this is all):
- Ratrig VC3.1-300 enclosed
- Manta M8P (1.0)
- EBB42 Max 31865 V1.1
- Orbiter 2.0 with Orbiter sensor
- Phaetus Rapido 2.0 UHF
- Ratos 2.1 RC3
15 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 1/27/2025 in #ratos-support
Error during accelerometer data streaming
24 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 1/21/2025 in #ratos-support
Wrong skew profile tries to load
I previously had a skew_profile made up (in printer.cfg) with the name "tuurke_skew". This worked fine and did not give me any errors.
I recently rebuild the printer. I removed the skew profile as well as the reference in the variables from printer.cfg. I re-calibrated the skew, stored it in the printer.cfg as "borg01" (as per klipper refference) and made reference to that profile in the RATOS variable to load it.
Now, with every new print, at the start of the print, my klipperscreen warns me that it can not find "tuurke_skew" profile.
(I can not find that warning at the Mainsail interface, but it shows up in klipperscreen).
I have checked printer.cfg and any other *.cfg file I think has something to do with this. Also, I checked the .gcode files for the "tuurke_skew" reference and I checked the slicer (print, printer and filament) custom-gcode's but have not been able to find any such references, leading me to believe it has something to do with Ratos / Klipper.
Does anybody have an idea where to find any more references?
As I am battling some over-dampening issues with the printer, I really need to be sure of the loaded skew profile. Now, I need to check at every start of the print what the actual skew is.
Any help is appreciated
23 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 12/31/2024 in #fix-my-resonance
Dampening issue on Y-axis (VC3.1 - 300 enclosed)
69 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 12/4/2024 in #ratos-support
variable_hotend_heat_soak_time as slicer variable?
Would it be possible to have
variable_hotend_heat_soak_time change depending (for instance) a variable in the slicer?
As I often print quite some stuff, consecutively, it happens a lot that i have the hotend heater on (as a result of a filament change) or that I just finished one print and want to redo or start another and as such would like to have a lower variable_hotend_heat_soak_time.14 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 11/1/2024 in #ratos-support
_USER_END_PRINT_PARK Macro misbehaving
29 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 10/12/2024 in #ratos-support
Move exceeds maximum extrusion (at primeblob)
44 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 10/11/2024 in #ratos-support
BEACON COMPENSATION_MESH higher on POA then PEI and Powder coated
I created 9 Bed compensation meshes;
-3 build plates (Smooth PEI, Powder coated PEI and POA)
-3 temperature ranges
The 3 temperature ranges of the POA-plate are all "higher" then the other 6. Is this normal?
57 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 10/6/2024 in #ratos-support
In consistent Z-Height when using bed mesh compensation. Temperature compensation not used
44 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 9/6/2024 in #fix-my-printer
bed temp fluctuation
11 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 8/16/2024 in #ratos-support
How to use adaptive mesh with multiple profiles
I have created 5 meshes (different build plates and different plate temps). How do I now enable the right profile in the slicer? I do NOT have a profile called Contact so the RATOS variable beacon_scan_compensation_profile: "Contact" throws an error. I thought I could add this to my printer Start G-code
SET_GCODE_VARIABLE MACRO="RatOS" variable="beacon_scan_compensation_profile" VALUE="PEI_110_40"
but this gives me:
Unable to parse 'PEI_110_40' as a literal: malformed node or string:
7 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 6/22/2024 in #fix-my-printer
After a Pause & Resume MCU 'mcu' shutdown: Rescheduled timer in the past
During a print, I have pressed pause (on my klipperscreen), did some maintainance on the printed part (removed a blob of filament) and pressed resume (on my klipper screen). the toolhead starts to move to the proper location, however in the middle of the move, I get a MCU shutdown error.
Specs:
Ratrig V-Core 3.1-300 running RatOS 2.1 (latest update as per update manager)
Manta M8P (rev1) with a CM4 (with emmc)
EBB42 rev 1.2
Rapido Plus UHF CFT
Orbiter 2.0 with orbiter sensor
Beacon RevH
logfiles and cfg files attached
As I experienced this prior to upgrading to RatOS 2.1, I do not believe this is the problem (back then I believe it happend multiple times when pressing resume after a filament runout). Any help would be appreciated as now the pause/resume become unreliable...
1 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 6/21/2024 in #fix-my-print
Pressure advance tuning, infill weirdness
4 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 6/11/2024 in #ratos-support
RatOs 2.1 help in setting up (renamed post)
213 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 1/18/2024 in #ratos-support
Orbiter Sensor / Ratos MCU error after loading filament and Resume
I have a orbiter 2 with filament sensor, configured as per attached printer.cfg on a EBB36. This used to operate with the OrbiterSensor.cfg but this is very complex so I changed it acc. to Helge's suggestion in another post (adopting the Pins to the setup with EBB36).
One change that I had to make between the 2 configs is that I had to inverse the functions (remove the exclamation marks) and added the ^ sign as per suggestion of Helge.
- Pressing the unload butten works
- Sensor activates the Park & unload sequence during a print.
2 issues remain however
- Minor issue: When I pull out the last filament-bit out of the extruder, the extruder immediately starts the Load Filament routine. I quickly put the new filament in and it then continues loading and purging and waits for me to press the resume button.
- Bigger issue: after pressing resume, it briefly moves the extruder towards the resume point, the halts and throws an error:
10:11 FIRMWARE_RESTART
10:11 MCU 'mcu' shutdown: Rescheduled timer in the past
10:11 MCU 'mcu' shutdown: Rescheduled timer in the past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
10:11 Klipper state: Shutdown
10:11 Filament loaded!
10:10 Filament unloaded! Please inspect the tip of the filament before reloading.
10:10 SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=1
Printer:
RatRig VCore 3.1 300 (Enclosed)
Manta M8P with CM4 + EBB36
Orbiter 2.0 with filament sensor
Revo Voron
Printer.cfg + klippy.log attached
(I will add @ of Helge later this evening, not to ping him now as per his request)
12 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 1/15/2024 in #fix-my-printer
XY-gantry (to) rigid
10 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 1/10/2024 in #ratos-support
PITFT50 boots into terminal login screen
Hi, I have been running klipperscreen on an old android tablet. Although it works it is not ideal and I have just bought, recieved and connected a pitft50 via the ribbon cable to the Manta M8P board. After some searching here on the forum (and putting in some wget's and blobs in) I have it now showing the Raspberrypi's terminal screen and it halts at the login prompt, wanting me to log in,.... any ideas how I could get it to go to the Klipperscreen?
17 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 1/8/2024 in #fix-my-printer
Internal Error on "G4"
Looking for some assistance on below. I have an Orbiter 2.0 (on a RR3.1-300) with the orbiter filament runout sensor. I have installed, and are running the macro's that go allong with that. It has been working flawlessly for months but now, Since a couple of weeks I get an error.
When I run out of filament, the toolhead is parked in the back and any remaining filament is pushed out the back/up as normal and than it awaits the user (me) to add filament. When the filament is grabbed by the Orbiter, I get an error on screen stating: "Internal Error on command: "G4" "
I then need to do a firmware restart but lost the print. The part of the klippy.log (attached) also shows me another error: FILAMENT_LOAD
Not sure what is going on. I did not alter any of the Macro's. Any help would be appreciated.
2 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 10/29/2023 in #fix-my-printer
Klipper errors after 2nd M600
I am attempting to print a small part with 2 filament/color changes. The part prints the first layer fine. I then have a color change (M600). also works fine. The next two layers are printed (also fine). Then upon M660 the filament change is executed like normal but when I then press Resume, the printer errors. (whereby at the first Resume at the first filament change, I also have pressed Resume and it doesn;t error...))
14:54 MCU 'mcu' shutdown: Rescheduled timer in the past
14:54 MCU 'mcu' shutdown: Rescheduled timer in the past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
14:54 Klipper state: Shutdown
14:54 echo: Filament load complete!
(Ratrig VC3.1-300 with Orbiter 2 and Revo Voron HF)
Reduced [printer] velocity from 1000 (as per performance settings) to 800 and Accel from 15000 to 9000
Any ideas?
8 replies
RRCRat Rig Community [Unofficial]
•Created by Arthur_C on 10/14/2023 in #fix-my-print
Gaps at end of perimeter
6 replies