ST-10XE unknown device

Discussion in 'STF Series CCD Cameras' started by Jaroslaw Smolar, Oct 16, 2016.

  1. Jaroslaw Smolar

    Jaroslaw Smolar Standard User

    Joined:
    Apr 8, 2015
    Messages:
    8
    Hi,

    I've strange problem - my camera is always "unknown device"
    and I can't do anything
    just simply stop under working (I mean doing astrophoto) and I can't simply connect it
    no firmware - because is not recognized
    I have tried different power source, USB cables + ports
    and allready reinstalled system on notebook - tried Windows XP Prof and (right now) Windows 7 32bit

    below
    - Windows device manager
    device identificator = USB\UNKNOWN

    all info from Debug Log (newest DriverChecker)

    Log file created : Sun Oct 16 22:30:47 2016

    =======================================================
    Computer : ASTRONOTEK
    Processor type : 586
    Number of processors : 2
    Operating system : Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 32-bit
    System directory : C:\Windows\system32
    Windows directory : C:\Windows
    User : von Tadeoooo
    =======================================================
    Driver Name Version Date Current
    =======================================================
    sbigudrv.dll 4.95 Build 1 09-16-16 Yes
    sbigu32.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
    =======================================================

    AND

    USB Device Tree Viewwer

    =========================== USB Port1 ===========================

    Connection Status : 0x02 (Device failed enumeration)
    Port Chain : 1-1

    ======================== USB Device ========================

    +++++++++++++++++ Device Information ++++++++++++++++++
    Device Description : Unknown Device
    Device Path : \\.\usb#vid_0000&pid_0000#5&2010edaf&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    Device ID : USB\VID_0000&PID_0000\5&2010EDAF&0&1
    Driver KeyName : {36fc9e60-c465-11cf-8056-444553540000}\0014 (GUID_DEVCLASS_USB)
    Driver Inf : C:\Windows\inf\usb.inf
    Legacy BusType : PNPBus
    Class : USB
    Class GUID : {36fc9e60-c465-11cf-8056-444553540000} (GUID_DEVCLASS_USB)
    Interface GUID : {a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE)
    Enumerator : USB
    Location Info : Port_#0001.Hub_#0004
    Manufacturer Info : (Standardowy kontroler hosta USB)
    Capabilities : 0x44 (Removable, RawDeviceOK)
    Status : 0x01806400 (DN_HAS_PROBLEM, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
    Problem Code : 43 (CM_PROB_FAILED_POST_START)
    Address : 1
    Power State : D3 (supported: D0, D2, D3, wake from D0, wake from D2)

    ---------------- Connection Information ---------------
    Connection Index : 0x01 (1)
    Connection Status : 0x02 (DeviceFailedEnumeration)
    Current Config Value : 0x00
    Device Address : 0x00 (0)
    Is Hub : 0x00 (no)
    Number Of Open Pipes : 0x00 (0)
    Device Bus Speed : 0x00 (Low-Speed)

    ------------------ Device Descriptor ------------------
    bLength : 0x00 (0 bytes)



    HELP :)
     
  2. Tim

    Tim Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    1,841
    What happens if you manually select the driver in the device manager?
     
  3. Jaroslaw Smolar

    Jaroslaw Smolar Standard User

    Joined:
    Apr 8, 2015
    Messages:
    8
    I have "tell to Windows" to use SBIG drivers from download directory or windows drivers,
    even replace and rename usb.inf - with sbigu....inf
    no matter what I do - still Windows report back - that unknown device driver (windows driver) is better than anything
    or
    directory doesn't contains driver for that device ...... or not for 32bit Windows (from both directory - pro or classic / 32 or 64 bit)
    :(
     
  4. Jaroslaw Smolar

    Jaroslaw Smolar Standard User

    Joined:
    Apr 8, 2015
    Messages:
    8
    Linux also tell nothing ...
    usb 2-1.3: new full speed USB device number 8 using ehci_hcd
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: new full speed USB device number 9 using ehci_hcd
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: new full speed USB device number 10 using ehci_hcd
    usb 2-1.3: device not accepting address 10, error -32
    hub 2-1:1.0: unable to enumerate USB device on port 3
    mppe_decompress[0]: FLUSHED bit not set in stateless mode!
    usb 2-1.3: new full speed USB device number 12 using ehci_hcd
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: new full speed USB device number 13 using ehci_hcd
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: device descriptor read/64, error -32
    usb 2-1.3: new full speed USB device number 14 using ehci_hcd
    usb 2-1.3: device not accepting address 14, error -32
    usb 2-1.3: new full speed USB device number 15 using ehci_hcd
    usb 2-1.3: device not accepting address 15, error -32
    hub 2-1:1.0: unable to enumerate USB device on port 3
    [vonTadeooooo@vonTadeo Pulpit]$
     
  5. Tim

    Tim Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    1,841
    In Windows Device Manager, if you select the unknown device and select "Update", the "Browse my computer for driver software", does it give you the option to "Let me pick from a list of device drivers on my computer"? If it does, it should show a list of available SBIG drivers.
     
  6. Tim

    Tim Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    1,841
    The fact that Linux does not detect the USB connection either hints at a hardware issue. You should contact Bill Lynch for repair service:

    Bill Lynch - SBIG Service & Repair Center

    3769 Constellation Road, Unit D
    Lompoc, CA 93436

    Bill Lynch - bill@sbig.com
    Phone: (805) 308-6979

    Note: Please contact our authorized service & repair center for an RMA number prior to returning your equipment.
     
  7. Jaroslaw Smolar

    Jaroslaw Smolar Standard User

    Joined:
    Apr 8, 2015
    Messages:
    8
    If it does, it should show a list of available SBIG drivers...

    It does - but give me back this kind of message

    directory doesn't contains driver for that device ...... or not for 32bit Windows (from both directory - pro or classic / 32 or 64 bit)


    You should contact Bill Lynch for repair service: ...

    anything but that- I have received camera after major repair (almost 1000 $ ) few months before - april this year :(
     
  8. Doug

    Doug Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    9,932
    Look in Device Manager Properties and see if it displays a VID and PID. If the values are 0 then it has to go in for service.
     
  9. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,378
    Location:
    Earth
    It was mentioned above:
    Device Path : \\.\usb#vid_0000&pid_0000#5&2010edaf&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    VID and PID both 0.
     
  10. Doug

    Doug Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    9,932
    Ah, so it was. It looks like the EEPROM for the USB processor needs to be reprogrammed.
     
  11. Jaroslaw Smolar

    Jaroslaw Smolar Standard User

    Joined:
    Apr 8, 2015
    Messages:
    8
    EEPROM for the USB processor needs to be reprogrammed


    Can it be done without sending camera "behind Big Water" ?
     
  12. Doug

    Doug Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    9,932
    Please contact Bill @ Service.
     

Share This Page