SBIG CFW8 doesn't report current filter


#1

Hi,

I am running SGP 3.0.2.94 on Win10Pro, and use it to control an ST2000XM with CFW8 filter wheel - the filter wheel is connected directly to the camera (so the camera needs to be connected before the FW, as normal). I’m using the latest SBIG drivers (as per the normal DriverChecker utility)

The current filter is never reported in SGP - it always says “None”, though moving filters works without any issue at all. Is there a way of getting this to work? It reports fine in CCDSoft/APT so it can be done…

Thanks

Graeme


#2

I am having a similar issue with FW8 used with ST 8300. Error log reporting a motor time out, but works fine in Maxim. using latest version of SGP and SBIG drivers


#3

Have you imported the filters into SGP or setup the fitlers in profile/sequence?

image

Thanks,
Jared


#4

Yep - I have the 5 filters setup in the filter setup as follows:

There’s nothing obvious in the log, which looks like this (from connection through to a successful filter change):

[09/17/18 09:35:26.743][DEBUG] [Main Thread] Connecting camera in main thread…
[09/17/18 09:35:26.743][DEBUG] [Main Thread] Connecting SBIG camera…
[09/17/18 09:35:26.746][DEBUG] [Main Thread] SBIG Driver name: SBIGUDrv.DLL Ver 4.99 Build 3
[09/17/18 09:35:26.746][DEBUG] [Main Thread] SBIG Driver version: 4.99
[09/17/18 09:35:26.859][DEBUG] [Main Thread] SBIG Camera Name: SBIG ST-2K Dual CCD Camera
[09/17/18 09:35:26.859][DEBUG] [Main Thread] SBIG Camera Firmware: 2.46
[09/17/18 09:35:26.859][DEBUG] [Main Thread] SBIG Camera Num Readout Modes: 10
[09/17/18 09:35:26.859][DEBUG] [Main Thread] Connecting SBIG guider camera…
[09/17/18 09:35:26.860][DEBUG] [Main Thread] Attempting to connect SBIG guider: Internal
[09/17/18 09:35:26.860][DEBUG] [Main Thread] SBIG Camera has remote guide head
[09/17/18 09:35:26.860][DEBUG] [Main Thread] SBIG Guider Camera Num Readout Modes: 3
[09/17/18 09:35:26.860][DEBUG] [Main Thread] SBIG Camera has onboard guider
[09/17/18 09:35:27.025][DEBUG] [Main Thread] Camera cooler detected…
[09/17/18 09:35:27.026][DEBUG] [Main Thread] Camera cooler is OFF…
[09/17/18 09:35:27.026][DEBUG] [Main Thread] Camera cooldown on connect is selected…
[09/17/18 09:35:27.026][DEBUG] [Main Thread] Camera cooldown is starting…
[09/17/18 09:35:27.036][DEBUG] [TEC Thread] SGM_CHANGE_COOLER_TEMP message received…
[09/17/18 09:35:27.036][DEBUG] [TEC Thread] TEC Change: Starting…
[09/17/18 09:35:27.068][DEBUG] [TEC Thread] TEC Change: After camera connect change, waiting ~5 seconds…
[09/17/18 09:35:30.564][DEBUG] [Main Thread] SBIG CFW Firmware: 0
[09/17/18 09:35:30.564][DEBUG] [Main Thread] SBIG CFW Num Positions: 5
[09/17/18 09:35:32.079][DEBUG] [TEC Thread] TEC Change: Attempting to turn the camera cooler on…
[09/17/18 09:35:32.082][DEBUG] [Main Thread] Turning camera cooler on…
[09/17/18 09:35:32.592][DEBUG] [Main Thread] Turning camera cooler on…
[09/17/18 09:35:34.154][DEBUG] [Filter Wheel Thread] SGM_FW_SET_POSITION message received…
[09/17/18 09:35:36.381][DEBUG] [Filter Wheel Thread] SGM_FW_SET_POSITION complete…


#5

@Jared Any further ideas on this one?


#6

Unfortunately not. It seems working fine with the SBIG Sim when using a ST-2000XM. Their sim is generally pretty accurate. Can you post a full log where you’ve set different filters a couple of times?

I’m guessing you’ve attempted the normal things like updating drivers, etc?

Thanks,
Jared


#7

SBIG Drivers are all up to date - here’s a log with me connecting, then changing the filter manually a few times.

Then a sequence runs, and because “auto focus” on filter change is set, it attempts to refocus after each frame (which destroys the ability to kick off several filters in a run without manual intervention as it thinks it has changed filter after each frame…).

sg_logfile_20181030190729.txt (389.8 KB)


#8

Digging around int he SBIG debug logs gives me this - assuming that cfwPosition shouldn’t be 00, but confirming. It’s not an issue with CCDSoft or APT (they clearly send the requested position but don’t check it afterwards) - I assume SGP does the check and reports “Unknown”, and thus flags the wheel as needing the filter setting.

At t = 617.321: =========================
At t = 617.324: CC_CFW : begin
At t = 617.328: -------------------------
At t = 617.332: CFWCommand Params :
At t = 617.337: cfwCommand : 01 - CFWC_GOTO
At t = 617.341: cfwModel : 06 - CFWSEL_AUTO
At t = 617.345: Attached camera ID : 14 - ST-2K
At t = 617.348: CFW - use cached model : 03 - CFWSEL_CFW8
At t = 617.456: Requested position : 04
At t = 617.462: CFWGoto Results : 00 - No Error
At t = 617.468: CC_CFW : end, err = 00 - No Error
At t = 617.577: =========================
At t = 617.581: CC_CFW : begin
At t = 617.584: -------------------------
At t = 617.588: CFWCommand Params :
At t = 617.592: cfwCommand : 00 - CFWC_QUERY
At t = 617.595: cfwModel : 06 - CFWSEL_AUTO
At t = 617.599: Attached camera ID : 14 - ST-2K
At t = 617.603: CFW - use cached model : 03 - CFWSEL_CFW8
At t = 617.618: CFWQuery Results : 00 - No Error
At t = 617.622: cfwModel : 06 - CFWSEL_AUTO
At t = 617.625: cfwStatus : 02 - CFWS_BUSY
At t = 617.629: cfwError : 00 - CFWE_NONE
At t = 617.633: cfwPosition : 00 - valid only if cfwStatus is CFWS_IDLE, 00=unknown position, otherwise 1,2,…10
At t = 617.637: CC_CFW : end, err = 00 - No Error
At t = 618.657: =========================
At t = 618.668: CC_CFW : begin
At t = 618.677: -------------------------
At t = 618.686: CFWCommand Params :
At t = 618.696: cfwCommand : 00 - CFWC_QUERY
At t = 618.705: cfwModel : 06 - CFWSEL_AUTO
At t = 618.710: Attached camera ID : 14 - ST-2K
At t = 618.716: CFW - use cached model : 03 - CFWSEL_CFW8
At t = 618.732: CFWQuery Results : 00 - No Error
At t = 618.740: cfwModel : 06 - CFWSEL_AUTO
At t = 618.749: cfwStatus : 02 - CFWS_BUSY
At t = 618.755: cfwError : 00 - CFWE_NONE
At t = 618.761: cfwPosition : 00 - valid only if cfwStatus is CFWS_IDLE, 00=unknown position, otherwise 1,2,…10
At t = 618.767: CC_CFW : end, err = 00 - No Error
At t = 619.712: =========================
At t = 619.722: CC_CFW : begin
At t = 619.741: -------------------------
At t = 619.749: CFWCommand Params :
At t = 619.756: cfwCommand : 00 - CFWC_QUERY
At t = 619.761: cfwModel : 06 - CFWSEL_AUTO
At t = 619.765: Attached camera ID : 14 - ST-2K
At t = 619.771: CFW - use cached model : 03 - CFWSEL_CFW8
At t = 619.787: CFWQuery Results : 00 - No Error
At t = 619.790: cfwModel : 06 - CFWSEL_AUTO
At t = 619.794: cfwStatus : 01 - CFWS_IDLE
At t = 619.798: cfwError : 00 - CFWE_NONE
At t = 619.803: cfwPosition : 00 - valid only if cfwStatus is CFWS_IDLE, 00=unknown position, otherwise 1,2,…10
At t = 619.808: CC_CFW : end, err = 00 - No Error
At t = 620.753: =========================


#9

Not only that but we never receive a good position to go off of, so we’d always be assuming that the filterwheel is doing what we’ve asked.

I guess we could add something that does that (very specific to only this filterwheel) but it seems like this should be addressed by SBIG.

Thanks,
Jared


#10

So I raised this issue on the Diffraction Ltd forums here:

http://forum.diffractionlimited.com/threads/cfw8-not-reporting-wheel-position-to-sgpro.5018/

The feedback from them (after using the SBIG driver debug log) is that the old CFW8s don’t ever report their position (but report if they are moving or not). Can some handling be built into SGP to handle these wheels at all?

Many thanks


#11

According to the ASCOM standard the driver is required to report its position so this is not a SGP problem.


#12

Except the SBIG driver isn’t an ASCOM driver.


#13

Yes, we can look into “faking” the position for the CFW8s.

Thanks,
Jared


www.mainsequencesoftware.com