Well, it took significantly longer than a few weeks to get back to printing. But I’ve been doing lots of homing and probing operations today and had no issues so far.
1 Like
Which of al the previous issues was the problem do you think?
It was quite a read but super interesting, since I am planning to move to canbus soon and if I would have these issues without knowing about your previous thread I would probably faint while screaming.
If it was the updates together with upping the bitrates, I think all sounds well. I am already running 32 bit on the pi, since I heard that 64 bit can cause trouble. Not running can yet, taking it step by step after solving lots of wiring problems on my second hand V2.4
But running umbillical instead of those nasty cable chains for about 6 months now and seems stable so soon I will take the dive to canbus. I will be using a special can cable from IGUS for this, just to eliminate wiring trouble.
Would love to hear what it was according to you?
Kees
No idea really. Haven’t gotten too far into it. You are right it is quite a long read, and trip down memory lane for myself. But I have in my notes that over a full qql and bed mesh, the printer would fail to start a print about 50% of the time. That seems to be fixed now. I didn’t do anything to the electronics. In fact I’m surprised I had very little to do to get the printer up to date and printing again. Git took care of updates for the past year, apt got all the packages, and I had to rebuild the MCU firmware. And there was a minor config update with some deprecated macros.
Moving house clearly helped 
Maybe your previous place was ful of 3d printing gremlins.
Joking aside it is always good to hear things are solved.
Also promising news is that it probably was a combination of updates and software conflicts.
We will see once I dive into that rabbit hole.
Thanks for the update!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.