Resin pump system with From 3L

We are having some similar (very much blocking) issues. Copying from Form 3L + Resin Pumping System issues · Issue #96 · AccelerationConsortium/ac-training-lab · GitHub

First print made it to ~200 layers (out of ~1300, and a 1.3 L print), and then the Form 3L froze.

We replaced the tank. Second print uploaded, and it says filling the tank. No resin is being deposited into the tank. The peristaltic pump wasn’t moving, and there appears to be some kind of debris in there:

At one point, the pump was removed entirely and there was no “complaint” from the software side (still showed as being inserted apparently, which is perhaps more concerning than the reverse issue of it not being recognized as inserted).

We followed everything step by step from https://youtu.be/6OQqgcRhVGs?si=cP-k6RmEtPDycPAF&t=98 (removing drip cap, adding card to it, correct insertion orientation, etc.). We tried rebooting, with and without the cartridge being inserted. Apparently, the resin pump wasn’t being recognized when it was already inserted during the time of reboot, but could sometimes be recognized when inserted after the full reboot.

Towards the end, we tried to print a 1 cm^3 cube when we finally had everything being recognized as inserted (“quick, don’t touch it - let’s try a print”), and this is when no resin was being deposited into the tank (waited maybe 30-60 min) and the peristaltic pump wasn’t moving.

We’re also considering trying to roll back the firmware. This was our first time using the resin pump with the Form 3L.

Some additional thoughts we had:

We could try rolling back the firmware and the preform versions as one of the troubleshooting steps. Maybe back to the last time the prints were successful on the 3L.

customer_v2

customer_v2

It’s possible that sensors on the 3L could be damaged or misaligned from the move to the new lab.

Unsure if the original unresponsiveness is now “resolved” with the manual switching off and on, or if it’s likely to recur. Could be firmware or hardware (if hardware, maybe overheating, but seems less likely).

@Lantech50 did you find any resolution to your issue?