×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

QHY5 - alccd5 mono distorted images

  • Posts: 53
  • Thank you received: 0
Hi All,

My first post here..
I've some problems with my QHY5v Mono guidecam.

I've have a RPI 3 with Ubuntu Mate and indi-full and or indi-bleeding (not yet familiour with all the terms).
I also have PHD2.

After installing everything, I managed to connect my iEQ45 GTN 8407 and Canon 60D.
But my QHY5v wasn't available. After searching the forum I found out that my VID wasn't in the list of devices in the udev rules.
I added and extra line there with my VID and after a reboot it was recognized by Ekos and PHD2.

But when turning on the cam in PHD2 or taking an image in Ekos.. I only get distorted images instead of a clear view. I already changed the gain value, but that doesn't affected the distrortion.

Does anyone have a clue?
Hope so, because I can't wait to use this setup for real.

Kind regards,
Chris.
SW Quattro CF 8" F4 - Canon 60DAW -Canon FD200mm F2.8 - allccd5v mono - Datyson T7M - iEQ45 8407 & iEQ45 8406 - RPi 3b ekos+kstars - LattePanda W10
7 years 2 months ago #14085

Please Log in or Create an account to join the conversation.

There are just so many varieties of QHY5s in the wild. Is it identical to the stock QHY5? The closest one to it (productID wise) is the mini QHY5.. could it be that one? It's possible you're loading the wrong firmware into it.
7 years 2 months ago #14091

Please Log in or Create an account to join the conversation.

  • Posts: 53
  • Thank you received: 0
unfortunately I can't upload any image.
But it's a grey black cam with the following desciption on the backside between the st4 and USB port:

ALccd5V CMOS-Kamera
serienr: 010211
Astrolumnia
Optische und digitale Systeme

The output of lsusb in the terminal before I added the line to the udevrules was:
T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=1618 ProdID=0932 Rev=00.00
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)

Current udevrule is:
ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0932", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
SW Quattro CF 8" F4 - Canon 60DAW -Canon FD200mm F2.8 - allccd5v mono - Datyson T7M - iEQ45 8407 & iEQ45 8406 - RPi 3b ekos+kstars - LattePanda W10
Last edit: 7 years 2 months ago by Chris.
7 years 2 months ago #14101

Please Log in or Create an account to join the conversation.

  • Posts: 151
  • Thank you received: 27
hi!
can you give a link to an image from the Alccd5 ???
yours
wolfi
7 years 2 months ago #14111

Please Log in or Create an account to join the conversation.

  • Posts: 53
  • Thank you received: 0
SW Quattro CF 8" F4 - Canon 60DAW -Canon FD200mm F2.8 - allccd5v mono - Datyson T7M - iEQ45 8407 & iEQ45 8406 - RPi 3b ekos+kstars - LattePanda W10
7 years 2 months ago #14140
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 151
  • Thank you received: 27
hi!
i was speaking of the images you get :D
can you send an image (not a screenshot)??
yours
wolfi
Last edit: 7 years 2 months ago by Wolfgang Birkfellner.
7 years 2 months ago #14141

Please Log in or Create an account to join the conversation.

  • Posts: 53
  • Thank you received: 0
Hi Wolfi, attached a fits file of the image created by the cam in Ekos :) hope that's wat you wanted?
SW Quattro CF 8" F4 - Canon 60DAW -Canon FD200mm F2.8 - allccd5v mono - Datyson T7M - iEQ45 8407 & iEQ45 8406 - RPi 3b ekos+kstars - LattePanda W10
7 years 1 month ago #14154
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 151
  • Thank you received: 27
hi!
accroding to the AstroLumina homepage, the AlCCD 5v mono has 752 x 480 pixel, whereas the AlCCD 5 (which i have) has 1280*1024 pixels. your FITS also has 1280x1024 pixels. apparently, this is the wrong driver.

is there something supposed to be seen on that image?
yours
wolfi
7 years 1 month ago #14157

Please Log in or Create an account to join the conversation.

  • Posts: 53
  • Thank you received: 0
Hmm not sure, but I always thought iT was 1280x1024 when I used before with Windows.
Nothing should be visible, its pointing at a white wall. But with cap on, it makes no difference.

In Windows with phd2 it just works, but the driver used there is signed by Van Ooijen Technische Informatica.
Searching for that I found this page: 07102649639700250278.googlegroups.com/at...AwQprenRYNn37L7JZXNc

Need to dive into this, but maybe you have an idea?

Thanks,
Chris
SW Quattro CF 8" F4 - Canon 60DAW -Canon FD200mm F2.8 - allccd5v mono - Datyson T7M - iEQ45 8407 & iEQ45 8406 - RPi 3b ekos+kstars - LattePanda W10
7 years 1 month ago #14169

Please Log in or Create an account to join the conversation.

  • Posts: 151
  • Thank you received: 27
hi!
"Hmm not sure, but I always thought iT was 1280x1024 when I used before with Windows.
Nothing should be visible, its pointing at a white wall. But with cap on, it makes no difference.!"

astro lumina homepage says:
www.astrolumina.de/kamerasysteme/alccd-q...pen/alccd-qhy-5v.php

"In Windows with phd2 it just works, but the driver used there is signed by Van Ooijen Technische Informatica.
Need to dive into this, but maybe you have an idea?"

it is possible to do a hack - if you can provide a FITS with something (anything) on it, it can try to reconstruct it, but the problem persists in my opinion ....
yours
wolfi
7 years 1 month ago #14173

Please Log in or Create an account to join the conversation.

  • Posts: 53
  • Thank you received: 0
Will make an image of something.
Another thing I noticed is that PID and VID the first time before I added an extra line to the udev rules was VID:1608 and PID:0932.

The current udev rule I created is:
ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0932", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"

But looking at the output of dmesg, the VID and PID are changed. Is this because a mapping in the udev rules?
[ 7.748015] usb 1-1.5: New USB device found, idVendor=16c0, idProduct=296d
[ 7.748031] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7.748044] usb 1-1.5: Product: QHY5-CMOS
[ 7.748057] usb 1-1.5: Manufacturer: QHY_CAMS
SW Quattro CF 8" F4 - Canon 60DAW -Canon FD200mm F2.8 - allccd5v mono - Datyson T7M - iEQ45 8407 & iEQ45 8406 - RPi 3b ekos+kstars - LattePanda W10
7 years 1 month ago #14176

Please Log in or Create an account to join the conversation.

That's a different vendor. I edited the 85-qhy.rules file and added this:
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="296d", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME}"

Remove the rules you had and try this, maybe this would work. If not try this:
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="296d", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"

After making each change, unplug the QHY from USB and restart the computer to make sure the rule is loaded correctly.
Last edit: 7 years 1 month ago by Jasem Mutlaq.
7 years 1 month ago #14177

Please Log in or Create an account to join the conversation.

Time to create page: 0.717 seconds