Lost communication with MCU while printing
Hello I started a 20 hours print and after maybe 5 hours I got a communication error with mcu.
Why ?
65 Replies
@miklschmidt @Helge Keck maybe you can help
first 3 tags are free, every new one costs 5€ each
Haha okay so now I knew it so now it starts 🤣
you already used your free tags
:kekw:
so, printers are moving and shaking all the time. i would start to make sure your USB cables are secured and bulletproof
will try to find something in the logs
Okay yes now after a restart everything works fine
And I don’t do anything with the cables
uhh, havent see this before
not sure how to interprete it
maybe mikl does know more
Okay I hope so 🥺
Maybe it was a problem that the endstop of the toolhead was triggered while printing
In the morning today I saw that the endstop switch was stuck in so it was triggered
Could this be a problem ?
i dont think so
Okay then I will wait for mikl
Could you try this code
M83
G1 E-120 F60
M83
G1 E120 F600
M83
G1 E-120 F600
M83
G1 E120 F60
M83
G1 E-120 F0.6
This causes the error I think
Klipper
Error in stepcompress
I suspect the error is in the iterative solver; I don’t think changing anything in stepcompress will change anything. I can reproduce this locally in batch mode: python ../../klippy/klippy.py -i test.gcode -o output -d dict/samd51p20.dict test.cfg With a test.gcode of: M83 G1 E-120 F60 M83 G1 E120 F600 M83 G1 E-120 F600 M83 G1 E120 F60 M83 G1...
Got this message after the code above
No matter if t0 or t1 tried 2 times on each head
Just Now I see that this seems to be exactly my problem here (there is the same error code as you @Helge Keck found in the debug file)
@miklschmidt you are my last hope at the moment don’t know what do else
Internet don’t have more information 😁
From what i can tell your main MCU is disconnecting.
ie. your control board
But it isn’t
What helge here found is 100% identical with this one
Here
And if I test the code that makes an error from the Klipper group
Then I got an error too
Do you have any ideas what I can do
Because it is really annoying that I can’t print or even if I print that I don’t know if it gets ready or any error again 😕
I checked it already but everything seams good and also after restart the pi everything is okay again without doing anything
Could this be a problem ? (That my mem is so high ?)
I only have one gcode on the sd card
Okay so the problem also comes on a voron with Klipper so this can’t be the problem why my MCU lost communication
What else can cause this problem ?
@Helge Keck @miklschmidt
Have again an error while printing
Where in the ratos debug file can i see the latest errors ?
Again
there is a ratos update on its way that could fix that
Okay do you know when it comes ? Today or in a week ?
@Helge Keck Because at the moment I can’t print and this is really annoying 😕
Sorry for the spam @Helge Keck but I am sitting here in front of my printer and don’t know what I can do or test anymore
Also I am struggling if I have to search the internet for solutions or if I just have to wait for the update 🥲😁
we are testing this internally atm
you can do one thing to rule the post processor bug out
1. upload the file
2. run
TEST_PROCESS_GCODE_FILE FILENAME=your filename
3. restart klipper
4. print the file
one sec, is this a idex?Yes it’s Idex
perfectz
then this workarround should work
it basically post processes the file wihtout printing it
if you still have this issue afterwards we know it must be something else
Okay so if it Runs 20 hours (which takes for the print then your update helps or ?)
likely
Okay will run it now
TEST_PROCESS_GCODE_FILE FILENAME= chonk_base_plate_V04_20240730_0.2mm_ABS_23h7m.gcode
So like this ?
TEST_PROCESS_GCODE_FILE FILENAME='"chonk_base_plate_V04_20240730_0.2mm_ABS_23h7m.gcode"'Okay
And then I start the print normally in the g code files click on the file and start or ?
And yes becirce I restart Klipper
yes
Bevor *
Okay
not from the slicer, print from the frontend
From here
yes
Okay
maybe better to restart the pi instead of klipper, just to be sure
TEST_PROCESS_GCODE_FILE FILENAME='"chonk_base_plate_V04_20240730_0.2mm_ABS_23h7m.gcode"'
Okay
Sorry just copied it
Got an error
do you have another RatOS printer with a PI with more memory?
Yes I can change the rasp in the evening
With 4gb
no need to change
just upload the file to the other printer, post process it, download it, upload it to idex and print
Ah okay but the other is a v minion does this matter ?
doesnt matter
Okay then I will write you later if I am in front of the other pi
@Helge Keck same error on the pi with 4gb
Okay I think I got it
ups
Now downloaded it and uploaded it on the other rasp
Reboot the rasp and then start from the mainsail
Is it right that everything heats up ?
Or how can I see that it was a success (to convert the file)
this means it worked
Yes this was on rasp with 4gb
Then downloaded and uploaded and reboot the pi then start the print on the pi with 1GB
And what does this do with the file ?
I'm gonna post this here too. Make sure there's no jumper here on any of your toolboards.
Then afterwards, go over your toolboard power wiring. I suspect there could be issues with the gnd wire.
have you connected your 4028s to the toolboards?
or the MCU
MCU
Okay those are removed and I measured again
And with the external power supply I have 5.24V on the power pins
excellent
That's right where you want it to be
Okay now this is the 4gb ram pi and an external power supply will see if this works now
Tomorrow I knew it 😁
So till now it is printing never get so far 🤣
Fingers crossed it gets till the end in the evening today