Hi Greg, we think the problem can still occur on a "long move" where it goes through many positions, and are going to review the firmware to see if we can clean up this odd situation. A long move like e.g slot 2 to slot 7, slot 2 to slot 1, slot 7 to slot 6. If it goes 1 or two slots, it may work ok. Keep an eye out.
Thanks for the heads up. I did a few of those since I use the Lum filter to do focus and centering every 30 minutes with ACP. I had transitions from slot 2,3,4,6 to 1 (and back) last night. I’ll put the other slots in my test runs to keep checking.
Well, I was wrong. Since my ACP run concluded normally (and not with a hang) I assumed it was all OK. But I see that my FW slot 6 subs did not acquire and checking the ACP logs, the image failed to start acquisition and ACP failed over to just complete the script. I just made a Maxim DL AutoSave script taking images in order 1,2,1,3,1,4,1,5,1,6,1,7,1. It failed at slot 5 and was waiting for Filter Wheel for a while and then changed the message to Waiting for trigger. I will restore Firmware 8 and reverify but this firmware has never given me these issues. Sorry to change my good news to bad.
FWIW, the hang was not a hard hang, which required cycling power. after exiting the script, I asked for a single Lum exposure and the filter wheel moved to Lum and acquired the image.
OK, so went back to Firmware rev 8 and 15 runs of taking images in order FW position 1,2,1,3,1,4,1,5,1,6,1,7,1. No issues. So wherever the problem is, it was introduced after firmware 8.