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......
Error after some minutes idling.
Hi. I've just finished the build of my VCore4, but it has strange behaviour. If I leave it idling, after 5-10-15 minutes (haven't noticed how much), a yellow warning appears, saying Klipper lost connection to T0, T1 or Beacon. Each time it's different but mostly it's T0. After selecting Firware Restart, I does not start. I need to select Restart only and then all is good. After the last one the reddish attached image showed up.
Initially I thought there are loose cables or something, but it's not that, as the printer passed all its belt and shaper tests without an issue. If it's doing something (moving, heating, whatever) it's OK. If I leave it idling, then it dyes.
Is it possible to be the Hub?
Any help, hint on advice on that issue would be appreciated....
Faulty VAOC camera (or accessories)
Hello people,
I'm close to finishe my VCore4 IDEX assembly, but got stuck on the VAOC camera.
I believe it's faulty (or some of it's accessories - cables or board) as it not visible from the printer (can'tconnect). Even tried to rotate the band cable in different configurations, but to no avail.
Can't connect at all. Like it's not existing.
I've also tried to connect it to my laptop, but doesn't recognize it either....
VAOC Error
after an idex test i've done, i was doing the vaoc alignment again and this pop up.
I literally did nothing, and was working perfectly.
any suggestions?...
Scan compensation mesh looks wonky
when creating a scan compensation mesh i get this result. my machine is a vcore4 400 idex. I Heatsoaked for 30mins at 85C. How could this be?
Why isn't retraction working?
Since I updated to Ratos 2.1 I had a lot of problems but now the printer is running at least but retraction doesn't work, I've tried different length, speed, different PA-value I even changed extruder and same result so what is the problem?
z-offset constantly triggered VC4 IDEX
Alright, we've got another problem on my IDEX upgrade. My Z-offset switch is showing as constantly triggered. The switch clicks in the housing, the wiring is plugged in to the position shown in the build guide, I've tried querying the probe both pressed and not, even unplugged, with no changes. I've removed the switch, and tested it with a multimeter, and checked the switch out of the housing, and it still does the same thing.
Below is my printer.cfg lines for the probe [z_offset_probe] pin: ^PG10 # probe trigger pin ...
Below is my printer.cfg lines for the probe [z_offset_probe] pin: ^PG10 # probe trigger pin ...
Solution:
Problem has been solved. I re-checked the wiring, and the pin for the endstop came out of the housing, and wasn't making contact with the pin on the board. Thanks for the help, again!
