Hi again,

Just pulled from git the fresh code.
I've enabled parking for StarSense:

if (fwInfo.controllerVersion >= MINSTSENSVER)
{
LOG_INFO("Starsense controller detected.");
cap |= TELESCOPE_CAN_PARK;
}

Then recompiled indi, and made some tests, they went well:

1. started kstars. started indi, mount was unparked, parked ok in the right position. stopped indi, kstars, no errors

2.1 started kstars. geographic was set at a random location.

2.2.1 started indi, mount was found parked:
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] InitPark Axis1 90.0136 Axis2 90.0132 "
org.kde.kstars.indi: < Celestron NexStar >: < Use Pulse Cmd >

2.2.2 date/time updated correctly:
org.kde.kstars.indi: < Celestron NexStar >: < TELESCOPE_TIMED_GUIDE_NS >
org.kde.kstars.indi: < Celestron NexStar >: < TELESCOPE_TIMED_GUIDE_WE >
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <t> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <00 23> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <h> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <0D 3B 0F 09 1C 12 02 01 23> "
org.kde.kstars: Daylight Saving Time active
org.kde.kstars: Next Daylight Savings Time change (Local Time): "Sun Nov 4 02:00:00 2018 GMT"
org.kde.kstars: Next Daylight Savings Time change (UTC): "Sun Nov 4 09:00:00 2018 GMT"

2.2.3 location updated correctly:
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Toggle Debug Level -- Scope Verbose "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Toggle Logging Level -- Messages "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Setting location (24.168,45.853) "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <57 2D 33 0A 00 18 0A 06 00> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <#> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Configuration successfully saved for GEOGRAPHIC_COORD. "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Configuration successfully loaded. "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <E> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <32AE,3FFA#> "
org.kde.kstars.indi: Celestron NexStar : "[SCOPE] RA-DEC ( 4:45:04,89:58:01) "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Configuration successfully saved. "

2.2.4 mount unparked successfully, no errors, mount didn't had any unexpected movement, kstars showed correctly the telescope's center towards NCP

3.1 slew to Polaris:
org.kde.kstars.indi: ISD:Telescope sending coords RA: "02h 56m 06s" ( 2.93508 ) DE: " 89° 20' 19\"" ( 89.3388 )
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Goto RA-DEC( 2:56:06,89:20:20) "

3.2 kstars showed correctly the telescope's center towards Polaris
3.3 smoked a cigarette for 5 minutes

3.4 checked the log:
...
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <E> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <2085,3F84#> "
org.kde.kstars.indi: Celestron NexStar : "[SCOPE] RA-DEC ( 3:02:55,89:19:08) "
org.kde.kstars.indi: ISD:Telescope sending coords RA: "02h 56m 06s" ( 2.93508 ) DE: " 89° 20' 19\"" ( 89.3388 )
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <E> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <2086,3F84#> "
org.kde.kstars.indi: Celestron NexStar : "[SCOPE] RA-DEC ( 3:02:57,89:19:08) "
...
3.5 parked the mount:
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Parking to Az (90:00:49) Alt (90:00:47)... "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Goto AZM-ALT ( 90:00:49,90:00:47) "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <B4002,4002> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <#> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <E> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <205E,3FD5#> "
org.kde.kstars.indi: Celestron NexStar : "[SCOPE] RA-DEC ( 3:02:04,89:45:50) "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <L> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <1#> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <E> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <A446,3EA1#> "
...
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <L> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <0#> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <54 00> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <#> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Mount tracking is off. "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] Configuration successfully saved. "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <E> "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] RES <37FA,3FFA#> "
org.kde.kstars.indi: Celestron NexStar : "[SCOPE] RA-DEC ( 5:14:52,89:58:01) "
org.kde.kstars.indi: Celestron NexStar : "[DEBUG] CMD <E> "
...
3.6 kstars showed correctly the telescope's center towards NCP

3.7 checked mount's indexes, home position acquired correctly

4. disconnected and stopped indi, set logs to regular, restarted indi, repeated the test, all things went as expected

5. rebooted RasPi, repeated the test, all OK


Should I try to test anything else?

Kind regards,
Lucian

Update

Hi,

the previous tests with StarSense were done in this simplified config: celestron_gps + CCD simulator.

Last two hours I tried to test with my actual gear: celestron_gps + Canon DSLR + QHY guider + Pegasus DMFC focuer

The config celestron_gps + Canon DSLR works fine, but when I try to add to the profile the rest of the gear: guider and/or the focuser the situation is becoming ridiculous:

Somehow seems that the geographic becomes corrupted.
Instead of Setting location (24.168,45.853), which is correct, I receive Setting location (0.000,51.468) which is a location in the Indian Ocean.

I've done it again and again, restarted the mount and RasPi several times, same result Setting location (0.000,51.468)
Any idea?...

I will do the same with NexStar HC, and i really hope will be different results.

NexStar+ same situation...

Noticed in log
org.kde.kstars.indi: INDI Server: "2018-09-28T13:36:43: Driver indi_qhy_ccd: No ISwitch 'OGV' in QHY CCD QHY5II-M-1027e9.CCD_STREAM_RECORDER"
org.kde.kstars.indi: INDI Server: "2018-09-28T13:36:44: Driver indi_qhy_ccd: snooping on Celestron GPS.EQUATORIAL_EOD_COORD"
org.kde.kstars.indi: INDI Server: "2018-09-28T13:36:44: Driver indi_qhy_ccd: snooping on Celestron GPS.TELESCOPE_INFO"
org.kde.kstars.indi: INDI Server: "2018-09-28T13:36:44: Driver indi_qhy_ccd: snooping on Celestron GPS.GEOGRAPHIC_COORD
is this OK ?

Lucian, great report!! Thanks a lot!

Suramare: Can you attach the complete debug log? Is KStars set to receive location from mount?

Hi Jasem,

now it works!
Yes, also in previous runs kstars was set to be updated time/location by the mount.

I'm talking now about NexStar. all devices connected to RasPi/StellarMateOS.
KStars was executed on RasPi via ssh connection to my laptop running OpenSuse Linux.

What have I done since my last post:
- manually set up the correct coordinates on the HC
- restarted mount/HC unpluged from RasPi
- waiting for "GPS Linked" message on the HC, done it also when behavior was wrong and after that plugged onto RasPi
- same behaviour.
- set up kstars that it will update the mount
- done a few tests, the mount was correctly updated
- gone to lunch
- received your reply
- restarted kstars with the option to be updated by mount, done the last tests

attached the requested logs:


I really don't understand what's going on.


later edit:
I've also made a fresh "make install", because watching top I've noticed today that apt- update was running. Being paranoyd I wanted to be sure that I'm working with the right binaries...

This may not be relevant to this particular issue but setting the location or time in the mount is a bad idea because changing these will change the local sidereal time and can upset the mount alignment. StarSense will set it's internal isAligned flag to false if this is done.

There is no code in the Celestron driver to read the location from the mount.
BTW I've tried to do a PR with the PierSide changes. It is complaining about conflicts but I don't think I can fix this because I don't have write access to the master.

Chris, thanks for the PR! I fixed the conflicts and it's merged to master. Great work!

I'm still receiving the mount firmware does not support tracking error. in both Stellarmate OS and Desktop versions with latest updates. i am also unable to connect to the gps module on the mount (not a big deal). i tried for several hours to get the internal guider and phd2 to guide but they both could not. in phd the star would just keep drifting and in the internal guider it just gave up i'm not sure of the errors. i do remember an error in ekos about phd2 having to uncheck auto reconfigure calibration data or something of the sort. but i could not find that option in the settings.

What's your KStars version?

my KStars version is 2.9.8

Hello newb here does any of this apply to CGE with skysync GPS not CGE pro.

HC new Nexstar+ usb with
HC GEM: 5.29.7137
MC: 5.20 5.20
Gone through align process site setup shows gps linked.

Can’t get gps to populate in kstars and i have a gps dongle coming in on tuesday. I’ve tried all gos drivers and the the only one i get feed back from is gpsd. Which says gos fiv in progress.

Utilizing stellarmate

I have the Starsense now for one week and see something strange, compared to the normal HC. In KSTARS (nightly branch) the following happens:
- using the "manual" HC in KSTARS a move sometimes does not stop when releasing the soft button
- the mount mark - the red cross - jumps around sporadically or is sometimes not shown, suspect KSTARS is not receiving information at that time

please advice which information you need in case this behaviour is not known to you
Stefan