jambouk Posted August 10, 2015 Share Posted August 10, 2015 Has anyone else encountered a ZWO camera just stop working?I was using it earlier to have a go at all sky imaging tonight and all was fine in SharpCap. I then tried using an active extension lead and it has stopped working and can't seem to be resurrected.I've uninstalled drivers, software, reinstalled, used no extension leads and tried different USB leads (and tested these on other kit), tried USB 2 and 3 ports, rebooted countless times. tried two other laptops and a desktop.In device manager it just appears as an unknown device and I can't update the driver from there as the drivers on the website are just a setup utility (http://astronomy-imaging-camera.com/software/ASI120MC_Setup.exe). Tried connecting without drivers installed and it fails to automatically identify the device.I think this is what happened with my previous ZWO!Has anyone else encountered this?Thanks for any ideas.JamesZWO ASI120MC (I've tried the -S version of the drivers too and the MM version, no joy). Link to comment Share on other sites More sharing options...
JamesF Posted August 10, 2015 Share Posted August 10, 2015 What does device manager give as the USB vendor id and product id?James Link to comment Share on other sites More sharing options...
ChrisLX200 Posted August 10, 2015 Share Posted August 10, 2015 Not with ZWO but I have 3 dead QHY5s in a draw here... Unrecognised device.ChrisH Link to comment Share on other sites More sharing options...
johnno Posted August 11, 2015 Share Posted August 11, 2015 Funny enough, I just bought a asi178mc and it lasted about 1 minute and the preview screen went blank, but my pc see's the camera in device manager and the software see's the camera but it shows 0 fps.Tried it on 3 different pc's with different OS's. I was using Firecapture at the time and was playing around with the settings when it threw a wobbler also tried it with Sharpcap and Amcap. I've also uninstalled and reinstalled everything and still the same, just waiting for a replacement to come, not a happy bunny Link to comment Share on other sites More sharing options...
jambouk Posted August 11, 2015 Author Share Posted August 11, 2015 Details from Device Manager attached; I couldn't see the vendor ID option:Broken ZWO.pdf Link to comment Share on other sites More sharing options...
JamesF Posted August 11, 2015 Share Posted August 11, 2015 I think it should be under the details tab. I'll see if I can find a machine to boot into Windows and check.James Link to comment Share on other sites More sharing options...
JamesF Posted August 11, 2015 Share Posted August 11, 2015 Yup. If you select the "details" tab and then "hardware ids" from the dropdown.James Link to comment Share on other sites More sharing options...
jambouk Posted August 11, 2015 Author Share Posted August 11, 2015 Hardware IDs:USB\VID_D282&PID_5303&REV_>?91USB\VID_D282&PID_5303James Link to comment Share on other sites More sharing options...
JamesF Posted August 11, 2015 Share Posted August 11, 2015 Well that doesn't look good. The ZWO cameras all have vendor IDs of 03c3 and I think the 120MC should be 03c3:120b, not d282:5303.I wonder if the firmware has got mangled somehow. Could be worth contacting ZWO and asking if there's any way you might be able to restore the firmware.James Link to comment Share on other sites More sharing options...
jambouk Posted August 12, 2015 Author Share Posted August 12, 2015 I've sent Sam an email and a link to this thread. I'll report back what he says.James Link to comment Share on other sites More sharing options...
jambouk Posted August 15, 2015 Author Share Posted August 15, 2015 Sam from ZWO tapped into my laptop over the internet from China and couldn't work out why it won't work, so it is going back to him for him to have a look at and hopefully fix.James Link to comment Share on other sites More sharing options...
JamesF Posted August 15, 2015 Share Posted August 15, 2015 That's positive news.James Link to comment Share on other sites More sharing options...
JamesF Posted August 17, 2015 Share Posted August 17, 2015 Not with ZWO but I have 3 dead QHY5s in a draw here... Unrecognised device.ChrisHI meant to add a comment to this earlier.QHY use the Cypress USB chipset for their cameras (I think it actually combines a USB interface and a microcontroller to manage any peripheral that you'd like it to), as do ZWO. The system can store a copy of firmware on-board, but it's also possible to download new firmware to the device to update the on-board firmware or just to run from RAM instead of the on-board system. ZWO use on-board firmware as far as I'm aware (at least most of the time) whilst QHY upload firmware to RAM each time the device is connected.I wonder if there's some way that the default firmware on these devices can get corrupted and that's what's happened in these cases. I have a vague recollection of a posting on QHY's forums (I can't check at the moment as they've been down for several months because of hacking) suggesting that it might be possible to reprogram the on-board firmware to recover the camera when this happens, but I can't remember much else at the moment.James Link to comment Share on other sites More sharing options...
JamesF Posted August 17, 2015 Share Posted August 17, 2015 Oooh, now here's a thought... (just for the QHY cameras)The way the QHY cameras work is that when initially connect the driver recognises the camera, downloads the new firmware into RAM and then the camera resets itself, reconnecting to the USB bus with a new vendor ID and product ID which the driver recognises as the "real" camera.However, there's a separate utility that can be used to load firmware into these Cypress-based devices. It doesn't have to be done by the driver. The software is called "fxload" and it's part of the libusb package which I believe has been ported to Windows. I use it with oaCapture for exactly this purpose on both OSX and Linux. It can recognise which device to download the firmware to by using the VID and PID, so it doesn't matter if they're wrong.I wonder if it might be possible to load the firmware into the camera manually using fxload and have it start working again?James Link to comment Share on other sites More sharing options...
ChrisLX200 Posted August 17, 2015 Share Posted August 17, 2015 I meant to add a comment to this earlier.QHY use the Cypress USB chipset for their cameras (I think it actually combines a USB interface and a microcontroller to manage any peripheral that you'd like it to), as do ZWO. The system can store a copy of firmware on-board, but it's also possible to download new firmware to the device to update the on-board firmware or just to run from RAM instead of the on-board system. ZWO use on-board firmware as far as I'm aware (at least most of the time) whilst QHY upload firmware to RAM each time the device is connected.I wonder if there's some way that the default firmware on these devices can get corrupted and that's what's happened in these cases. I have a vague recollection of a posting on QHY's forums (I can't check at the moment as they've been down for several months because of hacking) suggesting that it might be possible to reprogram the on-board firmware to recover the camera when this happens, but I can't remember much else at the moment.JamesJames, if you want one to play with I'll mail it to you :-)Cheers,Chris Link to comment Share on other sites More sharing options...
JamesF Posted August 17, 2015 Share Posted August 17, 2015 If you're happy to do that Chris I'd be more than willing to spend a bit of time on it to see if it might provide a way forward for those with QHY cameras that are no longer recognised. I'll PM you.James Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.