ArcWelderPlugin icon indicating copy to clipboard operation
ArcWelderPlugin copied to clipboard

Klipper crashes with converted file

Open DroneMang opened this issue 3 years ago • 9 comments

Hi,

I have been using arcwelder for some time and overall I would say I have had no issues, this converted file crashes the printer, causing Klipper to give an MCU shutdown, timer too close.

Here is the unconverted file and converted.

I use SolidWorks for my CAD, and when I export I use the very highest resolution settings, makes large STL/3MF files, but works well usually, perhaps I need a more coarse file? I am using Simplify3D for the slicer.

Also, I have this set in Klipper:

[gcode_arcs] resolution: 0.05 # 1.0 default

File.zip

DroneMang avatar Jan 17 '21 18:01 DroneMang

I will take a look. Whay version are you running?

FormerLurker avatar Jan 17 '21 22:01 FormerLurker

Of arcwelder? Whatever the newest that octoprint updates to, looks like 1.0.0+u.bb71e8f? I have arcwelder set to the stable release channel, I'll try dev later and recompile.

I just looked at the .aw file in S3D, I didn't see any issues. The crash happens right at the start of the print, Klipper says timer too close.

Thanks!

DroneMang avatar Jan 18 '21 18:01 DroneMang

Ok, so I've been researching the error you observed, and it seems like it's typically a communication problem. Obviously you're not having this trouble on other files, so perhaps something else is going on? Can you take a look at the terminal output when you are trying to print that file? Maybe that will be illuminating.

FormerLurker avatar Jan 18 '21 19:01 FormerLurker

If I select dev from within octoprint, will it use the 1.0.1rc1.dev2 version or do I need to manually install that?

DroneMang avatar Jan 18 '21 23:01 DroneMang

You would have to paste in an archive url. I can send the most recent link when i get back.

However, if you have time, see if you can replicate the error and capture the terminal output (the octoprint terminal tab). 100 lines or so should be plenty

FormerLurker avatar Jan 18 '21 23:01 FormerLurker

Changing monitoring state from "Operational" to "Starting" Send: N0 M110 N0125 Recv: ok Changing monitoring state from "Starting" to "Printing" Send: N1 G9017 Recv: ok Send: N2 M8326 Recv: ok Send: N3 M106 S4181 Recv: ok Send: N4 M140 S6087 Recv: ok Send: N5 M190 S6091 Recv: ok Send: N6 M104 S240 T033 Recv: ok Send: N7 M104 S240 T133 Recv: ok Send: N8 M109 S240 T034 Recv: ok Send: N9 M109 S240 T134 Recv: ok Send: START_PRINT Recv: ok Send: N10 M10522 Recv: ok B:59.7 /60.0 T0:238.9 /240.0 Send: N11 T010 Recv: // Extruder extruder already active Recv: ok Send: N12 G1 Z0.200 F48023 Recv: ok Send: N13 G1 X38.161 Y6.781 F21000123 Recv: ok Send: N14 G1144 Recv: ok Send: N15 G3 X42.308 Y3.013 I4.339 J0.611 E0.26249 F660013 Recv: ok Send: N16 G1 X48.514 Y3.010 E0.268384 Recv: ok Send: N17 G3 X49.029 Y11.737 I-0.032 J4.381 E0.56980112 Recv: ok Send: N18 G1 X48.310 Y11.790 E0.0312107 Recv: ok Send: N19 G2 X75.971 Y136.701 I336.760 J-9.057 E5.5640979 Recv: ok Send: N20 G2 X148.399 Y242.460 I309.032 J-133.957 E5.57479121 Recv: ok Send: N21 G2 X255.093 Y313.5 I236.616 J-239.731 E5.57479118 Recv: ok Send: N22 G2 X380.603 Y339.531 I129.907 J-310.762 E5.57479119 Recv: ok Send: N23 M10522 Recv: ok B:59.5 /60.0 T0:237.5 /240.0 Send: N24 G2 X506.75 Y316.785 I4.395 J-336.796 E5.5747978 Recv: ok Send: N25 G2 X615.263 Y248.555 I-121.771 J-314.070 E5.5747984 Recv: ok Send: N26 M10519 Recv: // Klipper state: Shutdown Recv: ok B:59.6 /60.0 T0:237.5 /240.0 Send: N27 G2 X690.424 Y144.723 I-230.278 J-245.814 E5.5747982 Recv: // MCU 'mcu' shutdown: Timer too close Recv: // This is generally indicative of an intermittent Recv: // communication failure between micro-controller and host. Recv: // Once the underlying issue is corrected, use the Recv: // "FIRMWARE_RESTART" command to reset the firmware, reload the Recv: // config, and restart the host software. Recv: // Printer is shutdown

Also, the printhead never moves from where it homes, it seems like the print starts, the START_PRINT script runs and then whatever those few commands are what make it fail.

DroneMang avatar Jan 19 '21 00:01 DroneMang

Where should I install python 3 from? I have your command from your documentation, but there is an Octoprint link as well: https://octoprint.org/blog/2020/09/10/upgrade-to-py3/

I think I am going to install the new OctoPi image 0.18.0 RC2, which should have python 3 on it, will this be sufficient for ArcWelder?

DroneMang avatar Jan 20 '21 02:01 DroneMang

I think you will still need to upgrade to python 3. You can use the script you linked to. Best to run that befort installing any plugins (less to go wrong then). The command I gave installs the development tools, but the script may install that too (i suspect it does). If you can install arc welder after the upgrade, then you don't have to run the command i gave.

Also, I still need to look into your terminal log. Not been able to work on this at all since my last message, but will have time Friday at the latest. I also forgot to send you the latest install url, so here it is:

https://github.com/FormerLurker/ArcWelderPlugin/archive/cb5e62706269bce0333017d095ace93ba815535e.zip

Install via the plugin manager (get more->from url...)

FormerLurker avatar Jan 20 '21 03:01 FormerLurker

I can't seem to figure this out. Looking at some other klipper issues now, so maybe it will help. Just wanted to let you know it hasn't fallen off my radar.

FormerLurker avatar Feb 06 '21 19:02 FormerLurker