Albuqshutterbug Loc: Albuquerque NM

I had issues with the software that came with the camera and went to the Celestron site. There is a new version that works very well. I bounce between color and mono and the new version has a camera selection box that opens up telling me which camera I have connected if its not the same as the previous session.
I also had issues with the camera driver and sent windows 10 out to look for a better version. It found one and I haven't had issues capturing since.
I do however have issues reading files that I generate in 16 bit with some of the file reader programs.. I don't have problems opening them in AutoStakkert! however, so I load and preview them there.
Quirks of the game I guess..
I hope this helps.

Albuqshutterbug Loc: Albuquerque NM

Is the USB port on your laptop powered?
Some are and some just aint.
I have 2 USB3 ports and only one has extra power, my cameras seem to prefer the unpowered port but not since I upgraded drivers and capture program.
Now it doesn't matter which I plug into but I figure if it works in the unpowered why feed it more of my battery?
;)

raymondt3 Loc: Chicago Heights

Thanks for the suggestion. I'll certainly give it a try. That's more help than I've gotten from Celestron on this issue. I'm still awaiting their ideas on this matter.

SonnyE Loc: Communist California, USA

I got the same bewildered answers from Orion. They had no answers as to why the program crashed.
But everything improved (Speed and crashing resolved) when the laptop was acting as a data solver, and not trying to be a power supply as well.

When the laptop gets busy with Mount Control, Stellarium, PHD2 Guidance, and is running the main camera (Orion Camera Studio), it is easy to see it could get taxing.
For example, if I am running PHD2 at 0.5 seconds, and run the main camera down at say 1 second exposures in a looping mode for focusing, the data can collide and one has to wait on the other. It shows the most as PHD2 will pause and then resume. (It actually shows "PHD Paused")
So I know they can effect each other. But broaden the time rate on the main camera to 5 seconds, or 10 seconds, and PHD runs happily.

Before Matthew recommended the powered hub, on top of the stalling between the different programs was the inevitable crashing of the main camera's program.
At first, I suspected buggy program software. So I tried working with that by removing and reinstalling the program in hopes of getting a "clean" download, and a good install.
But since the laptop is acting as a computer, and not trying to be all that and the power supply too... things have run noticeably better for me.
And I attribute the overall performance increase to the one simple change of plugging my 16' USB cables into the powered hub right behind my laptop. Where the non-powered (or computer port powered) hub was.

My reasoning to try that configuration was because it was the simplest change to make for me. Rather than to reconfigure my entire harness. And to my logic, having a short tail from the hub to the laptop might cause less data collisions from that bottleneck in the route.

And finally, if you are still with me, the powered hub is a 12 volt DC supply primary. That also appealed to me so I could do what I am currently working on doing, powering the hub with my huge 12 volt battery. And not trying to run it with my inverter I use for the laptop.

Clear as mud, huh?