When changing filters I frequently get a CFW Error usually saying "Bad CFW Command". The filter wheel (FW8G-STXL) always seem to go the correct location however. I set up to log the issue and ran the CFW Exerciser and on the 5th move got the error. CFW Error Error occurred in the Query State Bad CFW Command Here is what I believe to be the relevant part of the log showing a successful sequence followed by the error. Any ideas of suggestions would be appreciated. At t = 92.440: CFWCommand Params : At t = 92.445: cfwCommand : 00 - CFWC_QUERY At t = 92.449: cfwModel : 18 - CFWSEL_FW8_STT At t = 92.455: Attached camera ID : 17 - STX At t = 92.460: CFW - use cached model : 18 - CFWSEL_FW8_STT At t = 92.469: ReadComPipe : Ask/Got = 4/4, -> MC = MC_EEPROM At t = 92.473: data : A5, 71, 1F, 00 At t = 92.479: CFWQuery Results : 00 - No Error At t = 92.483: cfwModel : 18 - CFWSEL_FW8_STT At t = 92.488: cfwStatus : 02 - CFWS_BUSY At t = 92.492: cfwError : 01 - CFWE_BUSY At t = 92.497: cfwPosition : 00 - valid only if cfwStatus is CFWS_IDLE, 00=unknown position, otherwise 1,2,...10 At t = 92.502: ------------------------- At t = 92.507: CFWCommand Params : At t = 92.511: cfwCommand : 00 - CFWC_QUERY At t = 92.516: cfwModel : 18 - CFWSEL_FW8_STT At t = 92.520: Attached camera ID : 17 - STX At t = 92.525: CFW - use cached model : 18 - CFWSEL_FW8_STT At t = 92.531: ReadComPipe : Ask/Got = 4/4, -> MC = MC_EEPROM At t = 92.536: data : A5, 71, 9F, 00 At t = 92.541: CFWQuery Results : 35 - CFW Error At t = 92.545: cfwModel : 18 - CFWSEL_FW8_STT At t = 92.550: cfwStatus : 02 - CFWS_BUSY At t = 92.555: cfwError : 02 - CFWE_BAD_COMMAND At t = 92.559: cfwPosition : 00 - valid only if cfwStatus is CFWS_IDLE, 00=unknown position, otherwise 1,2,...10 At t = 93.185: data : A5, 38, 00, 07, B7, 03, 84, 07, C1, 00 At t = 93.198: ReadComPipe : Ask/Got = 10/10, -> MC = MC_SYSTEM At t = 93.204: data : A5, E8, 01, 00, 04, 01, 84, 07, C1, 00 At t = 93.210: ReadComPipe : Ask/Got = 10/10, -> MC = MC_SYSTEM At t = 93.215: data : A5, E8, FA, 4B, 05, 00, 02, 00, 04, 00 At t = 93.220: ReadComPipe : Ask/Got = 10/10, -> MC = MC_SYSTEM At t = 93.225: data : A5, E8, 1B, 04, 00, 00, 00, 00, 00, 00 At t = 93.231: ReadComPipe : Ask/Got = 10/10, -> MC = MC_SYSTEM At t = 93.236: data : A5, E8, 9E, 3B, 05, 00, 02, 00, 03, 00 ======================================================= Log file created : Fri Aug 14 15:46:43 2020 ======================================================= Computer : BB16CORE Processor type : 586 Number of processors : 32 Operating system : Microsoft Professional (build 9200), 64-bit System directory : C:\WINDOWS\system32 Windows directory : C:\WINDOWS User : ballard ======================================================= Driver Name Version Date Current ======================================================= sbigudrv.dll 4.99 Build 7 02-11-19 Yes sbigu64.sys 2.41.0.1338 01-27-15 Yes sbigpcam.hex 2.46 01-27-15 Yes sbiglcam.hex 2.20 01-27-15 Yes sbigfcam.hex 2.25 01-27-15 Yes sbigfga.bin 2004.11.10 01-27-15 Yes =======================================================
So there's a few possibilities. I'm not sure which version of Windows you are running eg Windows 8 64bit or Windows 10 Home 64bit? First thing to check is Windows Power Management - USB Selective Suspend should be turned OFF (Disabled). Then, in Windows Device Manager, go through all the USB devices, USB hubs, USB root hubs, and PCIe devices, and turn off the settings that says: [] Allow the computer to turn off this device to save power. Make sure this is disabled / unchecked. I suspect what is happening is that there is a communication failure, and this is a common cause. You might also try downloading the Demo version of MaxIm DL Pro and testing to see if things behave with it. Go here, and then expand the DEMO section, fill it in, and we will send you a 30day demo license: https://diffractionlimited.com/maxim-dl/ The other possibility is that that position sensor in the FW is not working properly, is loose, or misaligned. This is unlikely, but can happen. I suggest you have a look down the nose toward the filters, and see if they move when commanded and are properly aligned in the centre. e.g. do this on your workbench / kitchen table. Our repair wizard @Bill may have some comments as well.
Hi Collin I changed my USB setting to disable selective suspend and the problem still existed. I then opened up the filter wheel and disconnected all the internal connectors, cleaned the contacts and reseated them and the problem is now gone. Thanks for your quick response to this issue. Note: I'm using windows 10 pro and Microsoft has slightly changed the way to get to the selective suspend . On a none laptop go to Control Panel->Hardware and Sound->Power Options->Change Plan Settings->Change advanced power settings Then you can get to USB settings and disable selective suspend. On a windows 10 pro Laptop it is the same expect that there is a setting for On battery and Plugged in (so you would want to disable both).
I forgot to mention the device management setting of the root hub(s) power management is the same as you showed for windows 10 pro on both the laptop and desktop. Thanks again I will give Maxim-dl a try and see if that will work well for my environment. ( I do want to automatically take a series of images while using the guiding filter wheel, so far it appears that I can only do this one at a time with CCDOps).
