3.2.21 on Hillstar
Started this morning with a fresh cache
3 instances running
3 machines configured each to a different port (not on AUTO)
Machine 1: ACM0
Machine 2: ACM1
Machine 3: ACM2
Started a print from all 3 without issues
Then began a SD print on Machine 3
Disconnected Machine 1 to perform an adjustment
Attempted to reconnect to Machine 1
CuraLE decided to try to connect to Machine 3 on ACM2 instead of Machine 1 on ACM0 as specified, and killed the SD print running.
Why would CuraLE attempt to connect to a port other than the one clearly specified under machine settings?
Also, connecting takes too long because although the baud rate is specified in machine settings, CuraLE takes extra time to "Autodetect baudrate" even though it is specified. I don't think this should be occurring.