×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

QHY5 not found by Ekos

1 year 1 month ago
crw4096
Expert Boarder
Expert Boarder
Posts: 94
More
Topic Author
QHY5 not found by Ekos #40293
I grep'd through the rules under /etc/udev/rules.d. There are only 3-4 files there, one of which I put there to assign fixed serial port names to my focuser and telescope.

I did a "sudo find / -name '*.rules' -print" to make sure there weren't unexpected places where rules files were lurking. This correctly found all the rules files under /etc/udev and /lib/udev, as well as under the INDI git repo clone, and no other places.

I've reading about the "udevadm monitor" command this morning. Might this be useful to seeing what's going on when the camera is plugged in? "udevadm test" might be useful, too...

Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite

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

1 year 1 month ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
QHY5 not found by Ekos #40294
Hello CRW4096,

Yes. Udevadmin looks like a good place to find DEVPATH. The device path is needed with the rules. This tool is the way to get it.

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

1 year 1 month ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
QHY5 not found by Ekos #40296
Hello,

Success! I have both QHY5L-II and PoleMaster recognized by EKOS. I created custom rules from 85-QHYCCD.RULES and 85-QHY-CAMERAS.RULES. I preserved the original files in a specific folder. I updated the rules and rebooted the PI. EKOS picked both devices up using Device Manager.
The following user(s) said Thank You knro

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

1 year 1 month ago
knro
Administrator
Administrator
Posts: 8213
Karma: 51
QHY5 not found by Ekos #40297
What are the contents of the 2nd file?

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

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

1 year 1 month ago
Odiug
Senior Boarder
Senior Boarder
Posts: 45
More
QHY5 not found by Ekos #40300
@AradoSKYindi:
Where are the INDI-QHYCCDcamera.rule and INDI- QHYCCD.rule coming from? The original INDI 3rdparty drivers come with a QHYCCD rule file called "85-qhyccd.rules".
In this file both pairs 1618:0920 and 1618:0921 can be found. For the first pair the firmware is loaded with the help of "fxload". Then the QHYCCD device renumerates and comes back as 1618:0921, which triggers the second rule which just sets the permission to read/write for everybody.
Same holds for 1618:0940 and 1618:0941.

Ideally there should not be any tinkering necessary with the rules files. I was suspecting that maybe another package or manual editing interfered with the original rules files.

Also a -D without an argument does not make sense. Something must be wrong there.

CS
Guido

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

1 year 1 month ago
Odiug
Senior Boarder
Senior Boarder
Posts: 45
More
QHY5 not found by Ekos #40301
@AradoSKYindi:
You have both 85-QHYCCD.RULES and 85-QHY-CAMERAS.RULES?
Maybe one is a leftover from an older install or different package.

Ah, I see, Jasem also wonders what is in the second file...

CS
Guido

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

1 year 1 month ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
QHY5 not found by Ekos #40304
Hello,

I downloaded AstroBerry from this site. Whatever is in the default package is what I have. I have since upgraded to Ubuntu-Mate 18.04.

The following are my two QHYCCD components that EKOS could not see after a KSTARS update. 1618:0921 is the QHY5L-II. 1618:0941 is the PoleMaster. I looked in /etc/udev/rules.d and found 85-QHYCCD.rules and 85-QHY-CAMERAS.rules. I searched both files for my hardware. I found older revisions 1 digit off.

I did notice a large section of Vendor provided stuff commented out. I looked for QHY5II entries. The family resemblance was 1 digit off. So, I decided to save off the originals, then pare down the file to put the Action and ATTR for both models. I also included turn off MTP check and and check not related to the devices.

I created an 85-QHYCCD-local.rules and an 85-QHY-CAMERAS-local.rules. This will keep my specific needs from being overwritten. I installed the rules , rebooted, and KSTARS worked. In fact, both products appeared under QHYCCD.

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

1 year 1 month ago 1 year 1 month ago by AradoSKYindi.
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
QHY5 not found by Ekos #40306
Hello Oduig,

My version of both original rules files did have 0920 and 0940. The lone 0921 was commented off. No ACTION commands to FXLoad anything were attributed to 0921 or 0941.

I added/changed my files to focus exclusively on my two QHYCCD products. Both files are needed. One contains code. The other contains configuration settings. This worked.

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

1 year 1 month ago
Odiug
Senior Boarder
Senior Boarder
Posts: 45
More
QHY5 not found by Ekos #40310
Be aware that udev executes ALL rules that match. Not only the first one.

However if the same rules filename exists in /etc/udev/rules.d and /lib/udev/rules.d only the one in /etc is used.
That allows you to disable rules files from /lib by creating symlinks to /dev/null under the same name in /etc, without interfering with the rules files installed by packages under /lib, who are subject to being updated.

Guido

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

1 year 1 month ago
crw4096
Expert Boarder
Expert Boarder
Posts: 94
More
Topic Author
QHY5 not found by Ekos #40314
Hi,

I played around with "udevadm monitor" while plugging in the QHY5-II-M. I don't know what to make of it. It does seem to follow Guido's description of what happens when one of these cameras is plugged in, except for the fxload error. I'm including various logs for your scrutiny.

This is the syslog as I plugged in the device:
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: new high-speed USB device number 14 using dwc_otg
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: New USB device found, idVendor=1618, idProduct=0920, bcdDevice= 0.00
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 18 21:55:27 indi-pi mtp-probe[890]: checking bus 1, device 14: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4"
Jun 18 21:55:27 indi-pi mtp-probe[890]: bus: 1, device: 14 was not an MTP device
Jun 18 21:55:27 indi-pi systemd-udevd[889]: Process '/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D ' failed with exit code 255.
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: USB disconnect, device number 14
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: new high-speed USB device number 15 using dwc_otg
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: New USB device found, idVendor=1618, idProduct=0921, bcdDevice= 0.00
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: Product: QHY5-II          
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: Manufacturer: QHY-CCD  
Jun 18 21:55:30 indi-pi mtp-probe[896]: checking bus 1, device 15: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4"
Jun 18 21:55:30 indi-pi mtp-probe[896]: bus: 1, device: 15 was not an MTP device

This is the brief output from udevadm:
udevadm monitor -k -u
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[10242.584954] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
KERNEL[10242.587013] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
UDEV  [10242.716144] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
UDEV  [10242.737332] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
KERNEL[10242.902631] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
KERNEL[10242.903221] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
UDEV  [10242.912296] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
UDEV  [10242.917210] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
KERNEL[10244.879284] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
KERNEL[10244.881772] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
UDEV  [10245.000575] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
UDEV  [10245.013969] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)

I plugged in a second time with more extensive logging (udevadm -k -u -p). That output is in the attached file. From above, it looks like the device attaches, removes, then reattaches. In the attached log, it looks like the first group of ADD events have something to do with the product ID "0920" and the second bunch of ADD events are related to product ID "0921".

Mind you, the camera works in Ekos. I am happy to provide any other info if you think it will help figure out why there's an fxload error in the syslog. Otherwise, I'm calling this "fixed"...

Thanks for all the help,

Charles

Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
Attachments:

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

1 year 1 month ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
QHY5 not found by Ekos #40319
Hello CRW4096,

The two rule files for QHYCCD are out of sync with the QHY5LII. The driver cannot load because other configuration steps are missing. The -D has this string {env(DEVNAME)}.

This session variable is setup in 85-QHY-Cameras.rules. The 85-QHYCCD.rules has the device parameters. Check the Cameras rule first. Then, check the QHYCCD rule next. Only search in QHY and enable only QHY5II 1618 and 0921 lines. This should help you get this running.

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

1 year 1 month ago
Odiug
Senior Boarder
Senior Boarder
Posts: 45
More
QHY5 not found by Ekos #40326
@CRW4096:
BTW, thanks for the pictures, but I would actually need to get close up shots of all PCBs from both sides, so I can see the traces.

Anybody else who has a QHY5-II and could make detailled PCB pictures? Maybe I should post this as a seperate topic...
I am interested in the differences in wiring between QHY5 and QHY5-II.

Regards
Guido

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

Time to create page: 0.916 seconds