¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. QSI-CCD
  2. Topics

Qsi6162 sensor size wrong in Ascom

 

Hi all. I bought the 6162 to replace my 683. Hooked it up and connected right away but the images seemed square even though sensor is 4500x3600. I received the updated ascom and install package from the previous owner which were the Atik files. Now ascom reports sensor as 4250x3600 and image has a grey band on the right. I've tried deleting and installing orig package, deleting all drivers, updating ascom, deleting QSI from registry. Actually after I did that and reinstalled the orig installer, I could not get camera to connect. I had to use the newer Atik installer to connect, deleted that again and installed orig package but still having same issues. Any ideas??
?
Thanks, Jeff

1.jpg

 

Sorry, grey band on the left..


On Wed, Apr 30, 2025 at 10:59?AM Jeff Forsyth via <teamforsyth=[email protected]> wrote:
Hi all. I bought the 6162 to replace my 683. Hooked it up and connected right away but the images seemed square even though sensor is 4500x3600. I received the updated ascom and install package from the previous owner which were the Atik files. Now ascom reports sensor as 4250x3600 and image has a grey band on the right. I've tried deleting and installing orig package, deleting all drivers, updating ascom, deleting QSI from registry. Actually after I did that and reinstalled the orig installer, I could not get camera to connect. I had to use the newer Atik installer to connect, deleted that again and installed orig package but still having same issues. Any ideas??
?
Thanks, Jeff
 
Edited

After un-installing the older QSI package you might find that the old ASCOM drivers are not removed.
?
With the camera unplugged, remove all QSI installed packages via the usual Windows Add/Remove dialogue in Windows Settings.
?
Reboot the PC then from the Installed Apps menu, ASCOM, open the ASCOM Profile Explorer, expand the tree/branch for Camera Drivers and mouse-right-click on any entries for QSI camera and select "Delete key". Repeat the same steps for any entries for QSI under the FilterWheel Drivers branch.
?
Install the most recent QSI series 600 drivers from the QSI website, the older driver packages might not include the necessary code for the later 600 cameras.
?
The installer package you need is found on the QSI support page with the driver package for 600 series cameras v23.06.16.
?
Install the drivers with the camera disconnected and don't attempt to connect the camera until you have performed one more reboot after installing the v23.06.16 package.
?
Lastly, if you still have problems connecting to the camera and downloading images with the correct size in MaxIm using the ASCOM driver you can try the QSI MaxIm DL 6 Plug-In instead, which should be installed automatically with the v23.06.16 driver package and should be found in the main cameras drop-down chooser menu (not under the ASCOM chooser menu).
?
The QSI-MaxIm Plug-In was was being used with MaxIm DL 6 for my 683, 583 and 532 cameras in preference to the ASCOM driver because the ASCOM driver would not allow zero time Bias frames to be taken in MaxIm, and that issue was never resolved before MaxIm DL 6 was retired.
The QSI-MaxIm Plug-in does allow zero time Bias frames to be taken and was very stable but I have no experience of using that Plug-In with the 6120.
?
HTH
?
Will.
 

Hi Will, that is basically what I was doing but I started all over again and followed your directions but no help. I tried the ascom and straight QSI camera ID's . Tonight I used new cable, power supply and installed the drivers on another computer but same issues. On the gray part of the image, it looks like it is part of the exposure but exposed different?? Does the camera ID itself as the size of the sensor? Is there a firmware file somewhere for it? I don't see it on either QSI or the Atik site.?
 

Hi Jeff.
?
From the steps you¡¯ve tried and the description of the problem it points to a camera FPGA or firmware issue and Atik/QSI don¡¯t provide those for your 6162 camera publicly, you¡¯d have to contact support directly via the QSI contact page .
?
I don¡¯t know what level of support is now provided for the obsolete series 600 cameras. Atik closed all UK based QSI support operations just a few weeks ago and moved QSI support entirely to the Atik site in Portugal with the main UK support engineers made redundant AFAIK.
?
The Kodak KAF16200 sensor in your 6162 does have extra un-illuminated pixels at both sides of the active area, so called ¡°overscan pixels¡±, but QSI have never unlocked those in their Kodak chipped camera drivers that I know of.

Overscan access is normally enabled through a checkbox on the driver setup page for cameras from other manufacturers that do provide that feature and would be switched on-off via the FPGA and firmware if the camera designer implemented the function, that your camera appears to be showing the dark overscan pixels on the left side points to an issue with the FPGA or firmware, or some other hardware fault.
?
Since you are using MaxIm DL5, which I think went out of support before the the 6162 was released, you could just run a sanity check and try connecting to the camera via ASCOM in N.I.N.A. which at least is an up-to-date (and free) acquisition application. If the image size and overscan region is still incorrect in N.I.N.A. that would point back again to the camera hardware or FPGA/firmware being faulty.
The home page for N.I.N.A. is .
?
One last test you could try is to connect to the camera via ASCOM ConformU and run the camera tests in both 32bit and 64bit modes. The run log would tell you what sensor array sizes the camera is reporting as supported via the ASCOM interface but ConformU itself won¡¯t be able to find discrepancies between what the sensor size should be and what the camera driver is delivering, nevertheless ConformU can be a useful tool for hardware testing. You can download ConformU from the ASCOM GitHub page
?
For specific help with ConformU you would need to be on the ASCOM support forum, I doubt that many QSI owners here will have had much exposure to it and have only used it myself to resolve problems with an ASCOM dome driver and while working with the developer.
?
Will.
 

Thanks for the help Will. I mainly use Voyager. Maxim was just to try to see if Voyager was the issue. I've written to I guess the Atik support and have received automated responses back. I have also written to your link. I was watching shutter action last night. It seems confused, opening when should be closing, filter wheel stopping mid filter. Hopefully they will respond soon with firmware files since seemed to happen when trying to update.?
?
Jeff

1 - 6 of 6