QHY268C SDK Error V4.1.10700

[cairomike]

Started Sharpcap 4.1.107 with the Capture area set to 2300x2000 and all was fine. The exception happened when I tried to set the Capture Area to full scale 6280x4210.

If I start 4.0.9562 and change the capture area to full scale then try to start 4.1.107 it crashes immediately.

This doesn't happen on version 4.0.9562, but does on 4.1.10700 up.

Regards
Mike Cuffe

[admin]

Hi Mike,

sounds as though some setting that is being set on the camera by 4.0 is being remembered by the camera and is upsetting 4.1 (something not being re-read/reset properly). I expect if you unplug and replug the camera between the two it should be OK.

It looks very like the QHY code is over-filling the memory that SharpCap sets up for the image - causing it to write to unallocated memory and hence the crash. I will look into the details of this when I get back from my current holiday to see if anything can be done to avoid the issue. For now, try the unplug/replug of the camera and also try putting the camera into RAW8 or RAW16 mode rather than RGB mode.

cheers,

Robin

[cairomike]

Hi Robin

Power cycling the Camera doesn't solve the issue. However, I've just run the 64bit version 4.1.107 and it doesn't crash, so maybe it's a memory issue as you suspect.

Regards
Mike

[cairomike]

Hi Robin

A bit more detail.

V4.1.10700 32bit doesn't crash in Raw8 mode, but does in Raw16 or RGB24. V4.1.10700 64bit doesn't crash.

I've just installed V4.1.10872 32bit and 64bit.

The 32bit version doesn't crash when in Raw8 mode, but does in either Raw16 or RGB24 same as 4.1.10700. The 64bit version doesn't crash no matter what colour space or capture area I set, again same as 4.1.10700 64bit.

Regards
Mike

[admin]

Hi Mike,

it sounds dreadfully like a bug in the QHY code that happens in 32 bit and not in 64 bit. To be honest, I'd suggest just going with the 64 bit version anyway, since it is much more resilient to out-of-memory issues when you are working with high resolution cameras. In 4.1 I am recommending the 64-bit as the default version and only keeping the 32-bit version for compatibility with 'problem' devices like ASCOM drivers that do not have a 64-bit version.

cheers,

Robin

[cairomike]

Hi Robin

Okay, thanks for the advice, I'll use the 64bit version from now on.

Regards
Mike