MCU connection lost.
Hello people. I'm close to despair with my fully assembled VCore 4 IDEX 400, which haven't made a single print yet.
When the printer is idling, at some point a message pops, that MCU hast lost connection. At first (when I started with commissioning 5 days ago), it was showing as a culprit T0, T1, Beacon, randomly. The last two days I disconnected and checked all the wiring, and put in order all the cables in the electronic's compartment. Bought 2 new USB cables and replaced the one from the kit. Now the error popping up is mentioning only the Beacon. Strangely, right after the rewiring a new issue started to appear and maybe both are related. When I power the printer, I manage to go through a Heightnap calibration ones and on any attempt afterwards, a red error says the meshing failed. Until the next restart. I've wiggled all the cables and connectors both toward the toolheads and inside the black box, but no error appeared. Did that 3 times to be sure. All the connectors look fine.
No idea what to try next. And I'm still waiting to receive new VAOC camera (under warranty) as mine appears to be faulty. Quite a lot of disappointment and frustration at this point. The Voron was more complicated on assembling, but I'm having harder time starting printing with the RatRig....
Any hints, ideas or tips are greatly appreciated or this big junk of metal and plastic will be searching for a new owner...
15 Replies
can you share ratos-debug.zip?
How do you have all the USB plugs connected?
the mesh issue, it it trying to make it with kms long...
T0, T1 and Beacon are plugged in the Pi. The rest (monitor, camera) is on the hub. The error shows even without the extra accessories.
any chance you have the zip ties too tight?
Nope. This time I intentionally left them more loose.
how do I create the ratos-debug zip - ... got it
can you send _VAOC_RESET on your console, do VAOC again and retry the bed mesh?
you are missing some data on variables
starting on BEACON_RATOS_CALIBRATE
My VAOC is not working. Some of its components are faulty. I wrote to the support team and now I'm waiting for them to send me a new camera kit.
(Spent a who day with tha one, assembling, disassembling 15 times, tried it on the laptop, different combinations of the band cable and to no avail. Just dead.)
In the meantime I wanted to start using it at least as a non IDEX
ok
probably not the best idea to use before calibration...
endstop positions is set with the aid of the VAOC system.
Oh, you mean the missing/dead VAOC might be part of the problem... Haven't thought of that. The thing is it's connected and led could be lit too. Only the camera provides no signal...
yes. Doing the calibration with the VAOC cam and then sending CALCULATE_DC_ENDSTOP will save the endstop positions on variables. That data is "read" when doing the mesh
but you need the cam for that
Interesring. I've managed to create my hight mesh a few times before (with no error before... or only once). Anyway it doesn't explain the mcu connection loss when idling.
Try unplugging the monitor
Klipper screen has caused issues before
First I've tried without unneeded accessories, just the basics, but the issue was there. Afterwards attached the monitor and a logitech camera and it's the same.