Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - glatiak

Pages: [1]
Dont recall seeing this before, but when I was testing a new cabling arrangement I noticed that when I changed filters the LED would always flash 'green'. But when I changed to position number 3 on the wheel it flashed 'red' instead. I removed the camera and observed the filter changes and other then the colour of the LED being different, there was no difference in the apparent behaviour of the filter wheel. Does this colour difference have a meaning? If so, what? And what, if anything, should i do about it?

greg latiak

Thank you for the process explanation. That is what I wanted to know. There is still a problem with this device but sounds like the actual reason is different than what Pegasus was asserting. In any event, my QHY cameras work just fine on a different USB hub and I have found a way to make it work with the Pegasus -- which is still useful as a dew strap and DC toggle switch. Now all I need to do is find a better way of marshalling the pile of cables... and of course, more nighttime clear skies.

Thanks again,

Please do. Pegasus Astro has asserted that QHY cameras will not work with their USB 3 ports (#1 particularly) on their Powerbox Advanced because they say you do a USB2 connection first then switch to a USB 3 for operations. I was unable to get two cameras to work on their device but did work fine on a separate USB 3 hub. So there is an issue there someplace.

I had already come to that conclusion -- as I have two devices that are USB2 only and the two QHY183s. So I am going to connect the computer to the new powered USB3 hub and use a short cable to connect the Pegasus device to it. So there is still only one USB cable wrapped around the mount.

But what you did not say was whether the Pegasus assertion of how your cameras connect was correct -- I will assume from your response that they are correct. It might be helpful to mention this in the documentation for any affected cameras -- just as it would have if Pegasus mentioned their hardware peculiarity in theirs before problems emerged.

A note has appeared on the PegasusAstro product page for the Powerbox Advanced that one of their ports is not USB 2.0 compatible and they say QHY cameras do an initial USB 2.0 setup before switching to USB 3. The device has four ports - three of which will do usb 3/2 and one usb 3. Maybe this is the real issue -- I have to use this port and one other to connect my cameras as I need usb 2 ports for my QHYFW3 and another device. Your thoughts?

Thank you. I was surprised (and pleased) that the cameras showed up in a separate category of their own, unlike my guide camera. And the problem turned out to be with the new Power Hub that I had implemented -- the USB3 ports had issues. When connected through a known good hub, both cameras were displayed.

I have a pair of telescopes in use -- a 6" RC with QHY183M+filter wheel and a 360mm APO refractor with QHY183C. Previously I have disconnected one camera to use the other, but this made automation less convenient. So I installed a Pegasus Astro hub to connect and power both cameras simultaneously. My first test was strange -- Sharpcap would only see one camera as native -- the QHY183M. Both cameras were present as ASCOM but for some reason, Sharpcap persisted in seeing the 183C as a mono camera. Clearly there is some sort of collision here. Is there anything I should know about potential and known issues of a two camera configuration?

The QHY Ascom picker clearly does not see the second camera -- it only sees the 183M. This is different than when I was manually disconnecting and reconnecting the camera. Previously, I setup Capture as the 183M and Capture2 as the 183C. Now both of them show as 183M. This is with (Anycpu) SDK and Ascom I am assuming from the Capture and Capture2 drivers it was not supposed to work this way... but it does. Please advise.

Greg Latiak

Mechanical Q&A / Re: QHY183c TEC cooling
« on: February 12, 2019, 08:58:42 AM »
Thanks, Qui.

But that is not how it behaves. Just got the camera back from California after the TEC stopped responding (and no fan). Power is connected to the camera and I notice that whether the software has connected to it or not, when there is external power the fan runs. But there seems to be a delay before the TEC indicates that its working. Meanwhile, camera temperature as indicated by software, climbs. So it did make me wonder if there is a startup process that must complete before the TEC is operational. So the reliability and stability of the TEC continues to be a concern.


Mechanical Q&A / QHY183c TEC cooling
« on: February 04, 2019, 02:52:14 PM »
Am curious about the startup cycle for this camera as I am sometimes operating it remotely. How long is the startup cycle -- and at what point should the TEC engage if it has been turned on through software -- like EZ_Cap? Should it be immediate or is there some delay inherent in the design?


greg latiak

QHYCCD Standard Software Q&A / Re: QHY183C binning
« on: January 02, 2019, 04:59:12 PM »
Thank you for clearing that up.


QHYCCD Standard Software Q&A / QHY183C binning
« on: December 30, 2018, 09:36:26 AM »
I am curious as to whether the QHY183c supports binning? And if so, through which software? Would be convenient for focusing and framing. Notice that a number of the configuration dialogs have a provision for this but I have not explored it.


greg latiak

Ah, a feature...

OK, when I get my replacement QHY183c back I will give it another try -- ensuring that only a single gain setting is selected. Thank you.


That is correct -- I selected a set of dark frame exposures reasonable for my style of observing, when I hit 'capture' the program exited. Machine is an HP Elitedesk 705 G3 Mini with AMD Pro A10-9700E processor, 16gb ram, 3.0ghz cpu clock, Windows 10 pro v1803 build 17134.407. Domain member connected to Server 2012r2 essentials. DEP is enabled by default for windows services only. This is what was in the EZCAP log:
2018-12-08 11:20:57.400 LOG_ALARM -----------------  log4z thread started!   ----------------------------
And I did find this on a more careful search of the Windows Event log:
Faulting application name: EZCAP.exe, version:, time stamp: 0x03ad0788
Faulting module name: EZCAP.exe, version:, time stamp: 0x03ad0788
Exception code: 0xc0000005
Fault offset: 0x0002a369
Faulting process id: 0x218
Faulting application start time: 0x01d48c0f8a9f1fdb
Faulting application path: C:\Program Files (x86)\QHYCCD\EZCAP_QT\EZCAP_Qt\EZCAP.exe
Faulting module path: C:\Program Files (x86)\QHYCCD\EZCAP_QT\EZCAP_Qt\EZCAP.exe
Report Id: afd8bcb5-9c68-47bd-9a20-6ccb1a7e5a7d
Faulting package full name:
Faulting package-relative application ID:

Have been attempting to use the dark frame wizard to build up a dark library for my new QHY183c, but after opening the dark wizard with the camera connected, specifying the exposures wanted -- the program crashes with no error message or event logged in the windows error log. Execution environment is HP 705 mini with an AMD processor, Win10 pro. Looked like a nice tool -- be even nicer if I could use it.


greg latiak

Pages: [1]