Filter wheel switching failure

[Phillip]

This problem occurred when I used the ZWO EFW filter wheel in NINA beta 2.0:

1. At first, the filter cannot be switched normally when sequence is running. The common case is that the G filter is set in sequencer, and the R exposure is actually used.
2. Switch to image tab, manually switch the filter in the order of LRGB. When switching to G, it shows that the filter is R and the filter does not move, and then continue to switch to B. everything is normal. The same is true for reverse switching.
3. We got about 20 sets of devices using the same item, including cameras, filter wheels, PCs and even operating systems, about 3~4 sets got this problem.

‌

[Phillip]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Stefan B]

Are your filters in options->equipment->filterwheel out of sync with the filters in your ascom setup?

[Phillip]

We checked both SDK and Ascom. When using SDK, the filters are name in Nina and ascom is imported via ascom drivers in options tab, so the filters are sync I suppose.

[Stefan B]

Also double check on the Positions shown inside Nina and that there are no duplicates there too.

If no movement error on the device itself happens, there must be something misaligned in that list, otherwise this error will not happen.

[Sean Chan]

I would like to echo this problem. I recently dismantled my imaging train to clean my filters, etc. I have the 2”x7 setup (in LRGBHaOiiiSii position, where L starts off at 0). I’ve noticed that whenever I use NINA to control the FW irrespective of the ZWO native driver or ASCOM ZWO FilterWheel (1) (Version 6.0) it doesn’t seem to differentiate between Position 0 (Lum) or Position 1 (Red). Instead as per logs, it thinks Position 1 is Green (and it forwards physically rotates 2 positions forward) :-

2022-01-19T20:54:59.9263|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Oiii at Position 4
2022-01-19T20:55:10.4508|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Lum at Position 0
2022-01-19T20:55:34.4618|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Green at Position 1
2022-01-19T20:55:40.0529|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Blue at Position 2
2022-01-19T20:55:46.0910|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Lum at Position 0
2022-01-19T20:56:01.8656|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Sii at Position 5
2022-01-19T20:56:08.4525|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Oiii at Position 4
2022-01-19T20:56:14.1441|INFO|FilterWheelVM.cs|ChangeFilter|102|Moving to Filter Ha at Position 3

One thing to note is that in the actual ZWO ASCOM driver itself (where you can ask it to recalibrate, etc), that recognises all positions properly. i.e. it seems NINA is somehow confusing Position 0 & Position 1 when sending the command to the ZWO driver.

Edit: I found a potential issue. I’ve got 2 installations of NINA on two separate PCs and 1 installation exhibits the issue mentioned above, and the 2nd installation does not. The 2nd installation is still on ASCOM 6.5 whilst the 1st installation has been upgraded to 6.6. This issue may be specific to ASCOM 6.6. But why it’s happening to ZWO native drivers, I’m not certain.

[George Hilios]

Just a note that once the filter wheel positions and names are stored in NINA, we will no longer resync from ASCOM. If you want that to happen, delete all of them and then reconnect with ASCOM.

[Stefan B]

Removing version: 2.0 Beta (automated comment)