Seestar connectivity on a Linux box

[Matt Considine]

Hi,

I have a question as to how to get Stellarium on a Linux box to talk to a Seestar telescope.  I've checked this list's archives, the github discussion and issues sections as well as google and am getting no where.

On a phone with SkySafari, I can identify the telescope as an LX200 Classic listening to port 4030 and SkySafari will track where it is pointed.  There is no need to run indiserver on the unit - the port is getting straight LX200 commands like :GD#, etc.

I thought that I could do the same thing with Stellarium on the Linux box, but it appears that the only way to identify the ip address and port is via the indiserver.

Has anyone gotten comms with a Seestar to work in this kind of situation and if so can you describe how I can accomplish this or point me to some resource I have missed?

Thanks in advance and, as well, apologies in advance if I have overlooked something or am misdirecting my question here.

Regards,

Matt Considine

[Georg Zotti]

An LX200 "classic" should be connected over serial port as LX200, so the mention of an IP address surprises me. The User Guide describes what we know.

[Matt Considine]

Hi,

Thanks.  Yes, I agree.  I have an Lx200 and I need a serial connection that.  In this case, there's a program listening on port 4030 and it's just raw lx200 compatible commands it takes.  I've sniffed this with Wireshark.  I tried setting up a virtual comm port using socat on the Linux box, to tie /dev/ttyS0 to that port.  But for some reason I'm not able to pull that off.

Matt

Sent from allegedly smart phone

--
You received this message because you are subscribed to a topic in the Google Groups "Stellarium" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/stellarium/peqBIeWP1aY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to stellarium+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/stellarium/7283077c-cd00-4009-8998-138a14d88346n%40googlegroups.com.

[ha...@lambermont.dyndns.org]

Hi Matt,

You can probably do this via INDI as Stellarium supports that and INDI can talk
to LX200 mounts over TCP/IP. But you have to run a local INDI server with an
LX200 driver for that. I suspect the generic driver indi_lx200generic suffices.

I do not have your mount so cannot test it, but it will be like this for a
GM2000HPS mount: indiserver -v indi_lx200_10micron

I did not see an easy way to configure INDI from Stellarium but when the
appropriate config file that instructs the driver to connect to your scope over
TCP is found in ~/.indi/ it will get used automatically. (For the 10Micron this
config file is 10micron_config.xml which has ao.

<oneSwitch name="CONNECTION_TCP">
On
</oneSwitch>

and

<newTextVector device="10micron" name="DEVICE_ADDRESS">
<oneText name="ADDRESS">
some-ip-address
</oneText>
<oneText name="PORT">
3492
</oneText>
</newTextVector>

This config file was created with KStars/EKOS, but can be used from Stellarium
just fine)

I hope this gets you going. Do let us know your progress.

-- Hans Lambermont

[Matt Considine]

Hello Hans,

Thank you very much for this insight.  Can you tell me: should I read the port setting of 3492 to mean that you changed it from the default of 7624?  I'm thinking that I need to make sure the driver on the xml definition in ~/.indi need to be synchronized.  So far, I haven't been able to get stellarium to see the new definition, it seems.

Regards,

Matt

[ha...@lambermont.dyndns.org]

Hi Matt,

Matt Considine wrote on 20240405:
> Thank you very much for this insight. Can you tell me:
> should I read the port setting of 3492 to mean that you
> changed it from the default of 7624?

Ah I see some confusion here. The port 3492 is the listening
port of the 10micron mount. So the INDI server listens at
its port 7624 and this particular INDI device driver
connects to a physical device (my mount) at port 3492.

> I'm thinking that I need to make sure the driver on the
> xml definition in ~/.indi need to be synchronized. So
> far, I haven't been able to get stellarium to see the new
> definition, it seems.

If you can talk to the Seestar via some INDI client that can
generate the needed xml config (like KStars/EKOS can) then
Stellarium should be able to re-use that config.

I hope this explains it. If not just let me know.

-- Hans

> On Tuesday, April 2, 2024 at 7:37:45 AM UTC-4

[Hamza Gaming]

I understand. I can assist with that.

--
You received this message because you are subscribed to the Google Groups "Stellarium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stellarium+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/stellarium/ZhAWkGgZqULnLPLC%40rey.speckle.red.