@T_Joseph_Nkansah_Mah, I’m glad you asked about the communications channels. Internally in the development of the Form 2, they were particularly useful: Before we had developed the three-motor system that drives the Form 2, we used a Form 1+ to drive the hardware. It went something like this: To trigger the wiper, the flp stream included a
SerialPrintCommand("wipe") command followed by a
WaitOnPinCommand. A separate computer ran a Python script listening to the serial line and used Phidgets to drive the wiper motor, wait for the wiper to return to its limit switch, and trigger the Form 1+ to continue.
You can tap the serial line and listen. A regular print won’t say much. The printer says a few things on boot but otherwise it is quiet. I will point out
SerialPrintClockCommand, which I found useful in doing metrology on prints. You see, the Form 1+'s system clock isn’t super precise, so over a multi-hour print, I found it drifting by a fraction of a second. We added
SerialPrintClockCommand to allow us to synchronize our metrology with the progress of the print.
There are no other pins. Between
SerialPrintClockCommand, I think you can do just about anything. You can use your own electronics to listen to the serial line and send a pin high or low if you have other electronics that wants that as input.