Csaba Kertesz replied to the topic 'Synscan coordinates differ from those of the solver' in the forum. 3 weeks ago

Ok. So the syncing does not work by some magical reason.

I would like to ask to test some things without clear sky:
1. Start your system.
2. Sync your handset inside KStars _without plate solving_. In KStars, go to a sky position, open a context menu, inside Synscan submenu, there is the Sync option. Select it and verify if the Synscan points to the new synced location.
3. Try the previous step in different parts of the sky.

Let us know if this kinda manual syncing works well or if it is does not work for some kind a RA or DEC coordinates. I am pretty sure now what is the problem, my current bet is that syncing does not work with negative RA and DEC values, but it works fine with positive RA/DEC values. My location and sky visibility does not have negative RA/DEC values therefore they were not tested. Let me know if my guess is right!

Read More...

Csaba Kertesz replied to the topic 'Synscan coordinates differ from those of the solver' in the forum. 3 weeks ago

Oh then it should work. Let us know if the firmware update fixed the problem.

Read More...

Csaba Kertesz replied to the topic 'Synscan coordinates differ from those of the solver' in the forum. 3 weeks ago

1. Are you on negative GMT offset (timezone)?
2. Are you on Northern or Southern hemisphere?

Read More...

Csaba Kertesz replied to the topic 'Synscan coordinates differ from those of the solver' in the forum. 3 weeks ago

Ok. Can you check the KStars version exactly on your Mac? The link what you linked shows 2.8.8 what is more than a year old version.

Read More...

Csaba Kertesz replied to the topic 'Synscan coordinates differ from those of the solver' in the forum. 4 weeks ago

Yes, something is completely wrong in your use case.

First of all, if you don't plan to control your mount with hand (hand controller), your setup can be simplified by using a direct cable (EQDir) to the mount, ditch the Synscan handset and use EQMod INDI driver what is much more feature-rich.

Regarding your problems, the screenshot is not so important, the most important things to answer:
- What is your INDI version on your laptop?
- What is the Synscan handset firmware version?
- After you connect the handset to the laptop with INDI. Does the handset show the correct time and timezone (GMT)?

Read More...

Csaba Kertesz replied to the topic 'Synscan coordinates differ from those of the solver' in the forum. 4 weeks ago

Which version of INDI do you use? Official Ubuntu, Jasem PPA or built from source? If the answer is the first, update your system with Jasem PPA or built from source. The Synscan driver was completely broken, I fixed it some months ago.

Do you use your mount directly from your laptop or remotely via Raspberry Pi? At least there was a serious bug what I fixed a week ago. If you use your mount with Raspberry Pi (or similar arm minicomputer) in a place with negative timezone (GMT offset), the Synscan driver was broken. This fix is in git (source repo) and only landed in the nightly PPA:
launchpad.net/~mutlaqja/+archive/ubuntu/indinightly

Read More...

Greg Beaton thanked Csaba Kertesz in topic HEQ5 support 1 month ago
Csaba Kertesz replied to the topic 'HEQ5 support' in the forum. 1 month ago

I think you are the first user of this driver on an arm device with negative GMT offset. Anyway, I fixed the problem:

github.com/indilib/indi/pull/543

Read More...

Csaba Kertesz replied to the topic 'HEQ5 support' in the forum. 1 month ago

Ok. The problem can be on the Stellarmate. There is a certain code line in the driver which can be a problem on other architectures. I will also retest with my RaspPi setup on my balcony.

Read More...

Csaba Kertesz replied to the topic 'HEQ5 support' in the forum. 1 month ago

@gbeaton: I have a bad news for you. I can't reproduce your problem, everything works as expected, I can sync negative GMT offset to my handset and the time+GMT match between KStars and the handset. I have also a V3 handset, the only difference that I have the latest firmware installed: v3.39.05 or the problem is the macOS environment. When you connect and sync the time, check the following before disconnecting from KStars:
- Is the GMT offset good in the handset inside the manual menu?
- Is the GMT offset good in INDI/Synscan/Site Management tab?

The daylight saving is never set on the handset, it is included in the GMT offset on the handset.

Guiding: Yes, synscan does not support guiding, it must go though the camera.

Read More...

Csaba Kertesz replied to the topic 'HEQ5 support' in the forum. 1 month ago

Thanks for the testing. I am almost completely sure what is the problem. I checked the documentation and the negative GMT offsets need special handling that is why I did not experience this problem here at GMT+2. The driver had this kinda huge bugs in every corner before my refactoring. This time handling is an earlier implementation and it seemed to work hence I did not touch. I will check today after work at home.

Read More...

Csaba Kertesz thanked Greg Beaton in topic HEQ5 support 1 month ago
Csaba Kertesz replied to the topic 'HEQ5 support' in the forum. 1 month ago

You mentioned that

Time: 18:45:54 (correct)

The handset will use these numbers and the latitude/longitude, it does not care about if the timezone is incorrectly set, if the local time is correct.

Read More...

Csaba Kertesz replied to the topic 'HEQ5 support' in the forum. 1 month ago

Time zone+daylight savings: I think the handset does not care about these settings, the time itself what matters. The driver worked without any problem for me.
Elevation: There is no way to set the elevation via serial protocol. It is most likely reset by the handset when longitude/latitude are set.

If you find these settings crucial for you, disable the handset update in KStars.

Read More...

Jasem Mutlaq thanked Csaba Kertesz in topic HEQ5 support 1 month ago
Csaba Kertesz replied to the topic 'HEQ5 support' in the forum. 1 month ago

Regarding the GPhoto. I was also surprised that e.g. the Canon M-series cameras were not supported at all a few years ago and I could just dig some discussions when some preliminary support was added a year ago. The GPhoto-compatibility must be checked always for the camera.

I also point people to EQMod driver if it is feasible, but there are use cases when synscan driver is needed, I admit. Did you check this page?

indilib.org/devices/telescopes/synscan-telescope.html

I think the most important to update the firmware of the handset. When I refactored the Synscan driver some months ago, it was completely broken in some aspects. V3.37/V4.37 and up should be okay, but earlier versions can have missing support in the communication protocol, I don't support them at all. On the other hand, please check your setting in "KStars Configure/INDI/Time & Location". If "KStars Updates All Devices" is selected, your Mac will sync its time and the location in KStars to the handset. If this setting is not selected, KStars gets the location from the handset. Please report your progress, there can be some nuances on Mac what we can look into if macOS works specially in this matter compared to Linux.

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!