allow_unknown_gcode_generator
Just completed a and yeah I read the warning.
However I now see this error "allow_unknown_gcode_generator"
and on refreshing the Update Manager I now see that the "RatOS Configuration repository" is invalid
I'm assuming this isn't supposed to happed and what steps do I need to take to fix this?
15 Replies
So re-ran the Configurator hoping this would solove the issue. However now I see this after restarting the firmware... 'Internal error during connect: module 'extras.resonance_tester' has no attribute 'SweepingVibrationsTestGenerator'Rebooted the PI and now I see a Klipper Update in Update Manager.... Currently Installing this update. So far the Klipper update has the printer booted and back online... So far all seems to be working. Edited my printer.cfg and about to run a test print 🤞 Spoke too soon..... Uploading. atest print from PrusaSlicer crashes the printer..... 17:04:21 Unhandled exception during run 17:04:21 Unhandled exception during run 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 17:04:21 Unhandled exception during run 17:04:21 Unhandled exception during run 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 17:04:21 Unhandled exception during run 17:04:21 Unhandled exception during run 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 17:04:21 Unhandled exception during run 17:04:21 Unhandled exception during run 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 17:04:21 File selected 17:04:21 File opened:RatCube_M_III_ABSx_RATRIG QUALITY SPEED 0.25mm 0.4 nozzle_21m.gcode Size:1386181 Printer working as expected using PrusaSlicer 2.8.1. Crashes with PS 2.9.0-rc1.
seems like i may have broke the error reporting. 2.9.0-rc1 is not supported.
if you want to try it anyways (not recommended, no guarantees) you can add
Can you please show me what happens before this line: File opened:RatCube_M_III_ABSx_RATRIG QUALITY SPEED 0.25mm 0.4 nozzle_21m.gcode Size:1386181
It should've reported exactly why it's shutting down.
I didn't get much further last night as shortly after starting the test print there was a power outage, the joys of living in a small village in France.
I have checked but the klippy log has no mention (assuming of course thats where I need to look).
Klippy log....
The klippy log for yesterday
I have the same with Superslicer (alpha release). Can I go back to Pre-repo- merger? I really do not want any post processing stuff or somebody to controle which Slicers I am allowed to use ... This way RatOs is going a direction I really do not want to join.
I'll reiterate in here. No you can't go back, however you can simply bypass the postprocessor (you'll need it, if you're running IDEX, IDEX support in slicers is terrible).
IDEX won't work without the post processor.
On non-idex machines you'll get an extra move when moving to the print area.
@malcinator Better error handling and messaging is live in 5 minutes.
Ok, so today testing the Release version of PS 2.9.0 crashed the printer again.... I did capture this from the console as asked in a post above..
11:42:04 Klipper state: Disconnect 11:41:41 Unhandled exception during run 11:41:41 Unhandled exception during run 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 11:41:41 Unhandled exception during run 11:41:41 Unhandled exception during run 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 11:41:41 Unhandled exception during run 11:41:41 Unhandled exception during run 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 11:41:41 Unhandled exception during run 11:41:41 Unhandled exception during run 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 11:41:41 File selected 11:41:41 File opened:SpoolHolder_A - 2x - Accent - V1.0_ABS_RATRIG QUALITY 0.20mm 0.4 nozzle - POSITRON ABS_11m.gcode Size:1006912 11:41:41 Klipper state: Shutdown 11:41:41 Post-processing unsuccessful File is not supported, aborting... 11:41:38 Post-processing started Processing SpoolHolder_A - 2x - Accent - V1.0_ABS_RATRIG QUALITY 0.20mm 0.4 nozzle - POSITRON ABS_11m.gcode (0.96 mb)... 11:11:56 BED_MESH_PROFILE LOAD="default" 11:11:31 BED_MESH_PROFILE LOAD="ratos"Prior to this the printer was powered on and therewas only the RATOS logo displayed in the console. Yeah, just updated and now I see the warning. Is there any time set for campatability with the latest PS release?
Not yet, but did you try it with
allow_unknown_slicer_versions as prompted?I haven't tried as I felt that I should only be using 2.8.1, I will see what happens tomorrow. I find it strange that the 2.9.0 alpha & beta worked just fine until the update landed. Anyway yes I will give test tomorrow. Thanks.
ok, so..... I have just started a print with 2.9.0. Fingers crossed now power outage today.
14:49:50
File opened:Positron/Primary Colour Parts pt1_ABSx_RATRIG QUALITY 0.20mm 0.4 nozzle - POSITRON ABS_4h2m.gcode Size:21399699
14:49:50
Post-processing completed
Slicer: PrusaSlicer v2.9.0
Used tools: T0
14:49:50
Warning: Unsupported slicer version
Only versions 2.8.0 and 2.8.1 of PrusaSlicer are supported. Version 2.9.0 is not supported. This may result in print defects and incorrect operation of the printer.
14:49:47
Post-processing started
Processing Positron/Primary Colour Parts pt1_ABSx_RATRIG QUALITY 0.20mm 0.4 nozzle - POSITRON ABS_4h2m.gcode (20.41 mb)...
14:45:39
Welcome to RatOS v2.1.0
you saved my night, adding both lines of code fixes the issue for me
add this to printer.cfg:
[ratos]
allow_unsupported_slicer_versions: True
bypass_post_processing: True
Question:
IDEX machine, but printing with just T0, PrusaSlicer 2.9.0
Is that going to be an issue with
allow_unsupported_slicer_versions and bypass_post_processing?Should be fine 🙂
allow_unsupported_slicer_versions is enough though 🙂jsut for the records, bypassing post processing idex in single toolhead mode will create an issue in the start print macro
we can fix this by using the total_toolchange parameter from the slcier in the start_print macro
the TOTAL_TOOLSHIFTS variable would be missing and couöd create a problem
Fortunately they don't need to bypass the processor, just allowing unsupported versions is enough (to use PS 2.9)