John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 4 days ago

Hello CRW4096,

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 6 days ago

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.

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 7 days ago

Hello Oduig,

My version of both original rules files did had 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.

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 7 days ago

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.

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 7 days ago

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.

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 7 days ago

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.

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 7 days ago

Hello Oduig,

After looking at several non related issues, I have learned a few things about rules and Ubuntu-Mate. As for the QHYCCD brand of devices, I think I will create a distinct QHY5L-II rule. This prevent the blow out of any KSTARS rule overwrites.

The rules for QHYCCD are INDI-QHYCCDcamera.rule and INDI- QHYCCD.rule. A # is a comment field. The QHYCCD rule has many lines commented out. After reviewing the models, 1618:0921 is not listed. 1618:0920 is listed.

1618:0941 is the PoleMaster. 1618:0940 has a rule. None exist for 1618:0941.

If wildcard is used, then like families of devices would be working. I used a wildcard in getting another USB device to work. That was assigning a TTY port.

I added rules to the default QHYCCD rule files for the missing products that I have. Only one problem exists. The fxload and the -D (devpath) is pretty important. The OS refuses to load QHY5II.hex. This is fx3load being called out.

I will create a custom QHYCCD rule for the two newer devices not supported yet. This should cover me. I would like to know why the -D option is required for UBUNTU- MATE. Usbfs is an old distro of linux. All other QHYCCD models have -D blank.

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 1 week ago

Hello Guido,

Thank you for your suggestion. When I get back to my house, I will investigate oaCapture. Everything worked fine before the update. I am not adverse to updates. The QHYCCD company did not indicate or I failed to notice the drop of support of QYH5 in EKOS.

I had a nice 3.0 USB 4 port hub. I added the QHYCCD PoleMaster. It was not working. I thought not enough power. I got a powered hub. I had 4 USB devices. Now, I had 5. More power was needed.

Come to find out, libraries needed to be copied to other areas not mentioned in the excellent RPI installation documentation. I thought the PATH changes took care of needing special replication. The PoleMaster works . But, guide camera, QHY5-II-C, was not working. QHYCCD does not provide any RPI tools.

This thread claims that the developers SDK from QHYCCD did not contain the QHY5 model. KSTARS device manager and QHYCCD says, No QHYCCD product found. So, the QHY5 family is discontinued within KSTARS and EKOS. Developers can only code to what is provided from hardware vendors.

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 2 weeks ago

Hello,

I have a QHY-5LII-C. This was working fine. An update to Astroberry and 18.04 occured. Now, I have been chasing my tail thinking BAD USB hubs or worse a dead camera.

QHY-CCD does not see the camera. LSUSB -V enumerate the camera just fine. I have the PoleMaster and that was working fine until the updates. I found that key fines specific to the QHYCCD RPI install were overwritten. The PoleMaster PI version works.

The QHY-CCD QHY5L-II-C does not . EKOS says no cameras found. This thread has identified the source. No chance of EKOS having this back from the looks of this thread. What a waste.

I never did see a completed thread on how to integrate PoleMaster into EKOS. The claim is there. But EKOS is not listing it as an option and QHY for PI is not itegrating the QHY driver into EKOS. Hmm.... To me, EKOS has illiminated the QHY5L-II-CThis suggests dead product line. Not even Windows 10 ASCOM likes the product. Oh well.

Read More...

John Robison replied to the topic 'Under-Voltage error' in the forum. 2 months ago

Hello,

Fantastic. The 5V 4amp switching power and Adrino MicroUSB dongle are powering up the PI successfully. Now, I must wait for clear skies. Thunderstorms are coming.

Best regards

Read More...

John Robison replied to the topic 'Under-Voltage error' in the forum. 2 months ago

Hello,

Thank you these options to power these RPI 3B+ models. Supposedly, RC models are claimed to not need heaters. None are in my plans.

The USB standard for pins supplying power is 2. Running is parallel increases the amps and keeps the voltage the same. The 3.0 standard uses two connections (micro USB and USB-C) in parallel to give increased current.

Most MicroUSB cables are just 1.2 amp. Finding 2.5 amp cables (parallel) is not on any manufacturers’ minds.

Looks like a 5V 4 amp switching power with a micro USB port is the answer. These don’t exist on Amazon.

Read More...

John Robison created a new topic ' Under-Voltage error' in the forum. 2 months ago

Hello,

In a Raspberry PI forum galaxy far far away, a claim was made the this error was an OS problem and just update. Well, today is year 2019 and updates a well past this problem.

I am attempting to create a personal portable solution. I looked at the PSU and it says 5V @2.5amps. USB 3.0 is the same. The PI PSU is too short. So, a long USB was purchased and the appropriate USB 3.0 USB. Length of cable can degrade power. But 5’ shouldn’t degrade that much.

Current USB 3.0 is a two plug setup. So, the supplied PSU works. Any replacement (USB battery, plug battery, or USB 3.0 base with standard USB 2.0) generates this error.

Are there any other options for power of the Raspberry PI 3 B+ ?

Read More...

John Robison replied to the topic 'INDI Remote Server fails to start' in the forum. 2 months ago

Hello.

I figured it out. I must of inadvertently clicked off INDI Server. Live and learn. Enjoy.

Read More...

John Robison created a new topic ' INDI Remote Server fails to start' in the forum. 2 months ago

Hello,

I am setting up for a new event. However, EKOS is not starting INDI server. The message is cryptic and logs do not appear in the LOGS directory. I have deleted Profiles.db. Where else should I be considering?

Thank you.

Read More...