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

Hello,

Look for the red light on the device. When first plugged in, the light is red. For me, when I select record, the light goes out. With the light out, the messages of “No QHY product found. Is it powered on?”

I am going to attempt the fxload update. Something is shutting the QHY5LII-C to off. Under Windows the same power off happens when recording. I am fast coming to the conclusion the QHY5LII model is abandoned to Windows 7. EOL hardware is the result.

Read More...

John Robison created a new topic ' Distinct camera for guidance and polar alignment' in the forum. 2 weeks ago

Hello,

I apologize if this has been discussed. In building an AstroBerry RPI3B+, I had two QHYCCD cameras, PoleMaster and QHY5LII-C. With EKOS and powered, telescope has the guide scope selection. Going to polar align and the guide scope is there. The option to change to a different scope is not offered. Should guide and polar scopes be more flexible?

Read More...

John Robison created a new topic ' Path out of State of broken' in the forum. 2 weeks ago

Hello,

I seem to be in a repeatable cyclical pattern of diminishing returns with RPI3B+ and AstroBerry.

The troubles that are mounting are OS related. The first area is Swap File. The AstroBerry GUI doesn’t have a path to set it to any other device. Command line does work. A GUI front end to troubleshoot issues would be nice. Warnings about the swap file on the same partition as the OS are valid.

The second is sudo. Sudo has stopped displaying its output. Hmm... Did an update kill echo out?

The third is DEB files. I am getting repeated error messages attempting to install any DEB file. Software Index is broken. Check that 1) for broken packages = none, 2) the rights to some directory/file is corrupted = Chmod 777 = no change, 3) or the file /etc/apt/sources.lists is corrupt. Every suggested remedy does not work. With a dead sudo, any sudo apt-get install -f returns to command line. Any errors should show up in some OS log. None are found to justify the error message.

The fourth is boot console. Raspi-config changes to look for Left Shift are ignored to get to boot repair console.

I am going to start with deleting the swap file. I have a spare USB drive to place the swap file.

The start of these troubles is attempting to get a brain dead QHYCCD QHY5LII to work in EKOS. Bought new, The QHYCCD device shuts down when asked to SNAP or RECORD any object. EKOS sees the device, gets its details, and connected. Ask it to live stream or record and nothing is placed in the SER files. The QHY5LII light goes out. This looks like a mismatched Firmware. Nope. Under Windows 10 and RUN AS administrator, every QHYCCD tool causes the light to go out.

OaCapture was claimed by the OS to be an installed app without a resource. Sudo apt-get update does not find oaCapture. Running gdebi to uninstall yields the Software Index is broken.

Supposedly, QHYCCD and the vendor are working the QHY5LII issue. Getting AstroBerry stable now is my focus. What options are available to turn of AstroBerry to back to Ubuntu-Mate for troubleshooting? The reverse should get me back to AstroBerry. Thank you.

Read More...

John Robison replied to the topic 'INDI QHY GetQHYCCDSingleFrame error (-1). Logs included' in the forum. 3 weeks ago

Hello.

I have two QHY products. QHY5L-II-C and Polemaster are attached to my Ubuntu-Mate for RPI3B+. I looked at the DEBUG for INDI_QHY_CCD and am seeing some problems.

The DEBUG file is filled with this.

DEBUG 169.822986 sec : [QHY CCD POLEMASTER-00d7] QHYCCD|QHY5LIIBASE.CPP|GetLiveFrame|GetLiveFrame pW=1280 pH=960 pBpp=8 pChannels=1

This says that the QHY5LII is attempting to setup the PoleMaster as a QHY5LII. Nope. This explains why my QHY5LIIC is not working. It should be pointing to (QHY CCD QHY5L-II-C]. I am puzzled if I have a missmatch somewhere.

Read More...

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

Hello CRW4096,

Read More...

John Robison replied to the topic 'QHY5 not found by Ekos' in the forum. 4 weeks 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. 1 month 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. 1 month 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. 1 month 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. 1 month 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. 1 month 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 month 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. 1 month 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. 3 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...