Hello,

Thank you for the screen shots. I was able to compare my selections. I do not have CCD camera yet. I am casually observing and working kinks out. I confirm that I have selected the same settings for GPS guidance of KSTARS and the use of EKOS equipment management.

I have my RA issues fixed. I have the 19.04 issues fixed. Now for a clear night get Astrometry working. As I stated, Observation GPS Location, is where my site was not selected. Next clear night I will try again. I am under 19.04 now. For a while, Ubuntu-mate was complaining about a partial upgrade. Those problems are now fixed under 19.04.

Are you testing this indoors? If so you may just be having issues getting a fix. You can monitor the gps status with gpsmon or cgps or xgps. Plus from within the indi driver. All things being equal when the indi driver receives a fix everything should update. And UTC offset is actually taken from the operating system's settings.

Hello Ihoujin,

I can and have. I test with a long USB extension and place the device in the window sill. It does get a lock there. I prefer testing outdoors. I like seeing tech working together for a specific goal.

Hello,

I have had several clear nights. I used PoleMaster software to get me aligned first. It works.

Last night, I opened KSTARS and EKOS. GPSD is working. PoleMaster is working. I was determined to see Astrometry working. I tested Astrometry. Nope. Resolver quite after 0 secs. I resorted to PoleMaster software. I connected to the device.

No image shows up in Astrometry. When using Observation List, I clicked on the GPS button. This took me to a blank city and no GPS coordinates. I searched for my saved coordinates by city. I am now in a time zone.

To me, something isn’t talking between Indi Control panel and KSTARS. KSTARS never gets a feed from EKOS with the GPSD position. And EKOS does know where it is to match a PoleMaster image to the GPSD coordinates.

I spend too much time watching Astrometry time-out and show a blank screen. I don’t have all night to wait. I have a wish list that I would like to see.


Tomorrow, I will set everything up outside and look at the logs to see if GPSD is stumped on communicating with KSTARS. I want this to work.

There is an issue with GPS dongle together with chrony/ntpd.
I wonder whether you have met such issue or not
indilib.org/forum/development/5231-indi-...from-gpsd.html#40677

Hello,

ecloud, I appreciated the link. I followed it to another link. The child link provided a Stellermate tool called Serial Port Mapper. No tool like this is included with Astroberry. This should be a similar tool with AstroBerry. The Vendor ID and Product ID with SIMLINK+ = "Mount" should work but the parser wants the full text. I am seeking a solution for USB devices.

I attempted to use Rules to setup the GPSD and AstroEQ. SIMLINK failed miserablely. I seem to be on the correct path as KSTARS now shows the GPSD coordinates. However, Observation Planner still does not know where it is at. I have my coordinates tied to a city. So, I help it. This looks like an absolute match for the GPS and CITY to match. Clicking on the GPS button pulls up a blank city. The good news is the GPSD is functioning.

There is an issue with GPS dongle together with chrony/ntpd.
see: bluestacks.vip/ , kodi.software/ & ​​​​​​​https://luckypatcher.pro/​​​​​​​

Hello,

I am happy to report the SYMLINK issue is resolved. Loose nut behind the keyboard is a good analogy. I am seeking a clear night to have everything working as design. AstroEQ and GPSD are now on more solid footing. I am interested in what Astrometry will provide.

What about sharing the solution with others? Might be useful if anybody faces similar issue

Hello,

Thank you the challenge. I stated in another of my quests that devices powering motors cannot depend on USB power. USB is for control. When setting up EKOS devices, ensure all devices are properly powered.

Use RULES.D to SYMLINK devices to specific use of limited OS resources. On a RPI 3b+, without modification, two RS232 capable devices are available. The OS can play leapfrog with serial ports. RULES.D allows control need for INDI and EKOS.

With the configuration settled, the next step is to test the implementation. Clear nights are needed for these actions.

Hello.

With the SYMLINK solution in place, I was able to test this configuration and see if Astrometry was operational on October 1. I always consider the first issue as operator error. The night was very clear. I captured the Astrometry sequence. This is included in the images and in the TXT file. Unfortunately, I did not capture the QHY errors which mirrored the errors in the TXT file. Every abort had a corresponding QHY error of -1. What was puzzling was the image in the 37.png. The abort messages must refer to something else. The last line is this section of my INDI log showed purple in INDI. Here, it looks innocuous. Every -1 event is directly linked to an Astrometry abort event.

[2019-10-01T00:54:05.827 EDT DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5LII-C-61f7e : "[DEBUG] QHYCCD|QHY5LIIBASE.CPP|GetLiveFrame|GetLiveFrame pW=0 pH=0 pBpp=8 pChannels=1 "
[2019-10-01T00:54:05.830 EDT DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5LII-C-61f7e : "[DEBUG] QHYCCD|QHY5LIIBASE.CPP|GetLiveFrame|GetLiveFrame pW=0 pH=0 pBpp=8 pChannels=1 "
[2019-10-01T00:54:05.837 EDT DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5LII-C-61f7e : "[DEBUG] QHYCCDRD|CMOSDLL.CPP|QCamImageParsing|RawDataLen = -1 frameLen = -1 l = 76800 "

Of particular concern was PHD. The 56.png image shows that PHD could not see the QHY 5LDII device in INDI. The PoleMaster is not in an OTA device. Both the ZWO 120 and QHY 5LII are each installed in an OTA. I would like to focus them with EKOS. But, errors between INDI and PHD say not that night.

As I see it, INDI shows all devices working. None show errors or conflicts. Why Astrometry is aborting does not make sense. My goal is to have the ZWO 120 to capture, the QHY 5L-II to guide and the PoleMaster to align KSTARS. I am reviewing any configuration steps which could be causing these errors.

Hello,

I went back to the FOV calculator and looked up my equipment for to calculate some FOV values. The PoleMaster is always 11 x 8. The ZWO and QHY 5L-IIC are roughly the same in between the QHY Mini scope and the ZWO 60mm F/4.,6. I will try these values next clear night.