×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel

  • Posts: 23
  • Thank you received: 1
I just looked at the root of /home/stellermate/.indi and there actually doesn't appear to be an indi_gpsd.xml file at all. I tried to open that file in geany through the terminal, so it looks like the application thought I wanted to create it.
SkyWatcher HEQ5 > Pegasus Pocket Powerbox > Celestron Nexstar 6se OTA w/ f/6.3 FR > Nikon Z6 imaging camera > Agena StarGuider 50mm guide scope > ZWO ASI290MM Mini guide camera
3 years 8 months ago #57140

Please Log in or Create an account to join the conversation.

  • Posts: 23
  • Thank you received: 1
I found the indi_gpsd.xml file in the following directory: /usr/share/indi

Not sure if that's right, but it's the only file with that name on the system.

This is the contents:

<?xml version="1.0" encoding="UTF-8"?>
<driversList>
<devGroup group="Auxiliary">
<device label="GPSD">
<driver name="GPSD">indi_gpsd</driver>
<version>0.5</version>
</device>
</devGroup>
</driversList>
SkyWatcher HEQ5 > Pegasus Pocket Powerbox > Celestron Nexstar 6se OTA w/ f/6.3 FR > Nikon Z6 imaging camera > Agena StarGuider 50mm guide scope > ZWO ASI290MM Mini guide camera
3 years 8 months ago #57144

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

We may have to look at indi_gpsd.service. This seems to be initiating a second start GPSD. This conflicts with the enabled GPSD service. This is going to take some sleuthing. I will look at this tomorrow.
3 years 8 months ago #57146

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

A fresh look at the data shows the difference between AstroBerry and StellerMate. With StellerMate, GPSD functions are managed by indi_gpsd.

Use: sudo systemctl disable gpsd

Next

Use: sudo geany /lib/systemd/system/gpsd.service

Use: sudo geany /etc/gpsd

The options look funny. The options come from /etc.
Last edit: 3 years 8 months ago by John Robison.
3 years 8 months ago #57155

Please Log in or Create an account to join the conversation.

  • Posts: 23
  • Thank you received: 1
From: sudo geany /lib/systemd/system/gpsd.service

[Unit]
Description=GPS (Global Positioning System) Daemon
Requires=gpsd.socket
# Needed with chrony SOCK refclock
After=chronyd.service

[Service]
Type=forking
EnvironmentFile=-/etc/default/gpsd
ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES

[Install]
WantedBy=multi-user.target
Also=gpsd.socket

When running sudo geany /etc/gpsd, it appears that there is no existing file and geany attempts to create a new blank file. When looking in the /etc directory, there is no reference to gpsd.
SkyWatcher HEQ5 > Pegasus Pocket Powerbox > Celestron Nexstar 6se OTA w/ f/6.3 FR > Nikon Z6 imaging camera > Agena StarGuider 50mm guide scope > ZWO ASI290MM Mini guide camera
3 years 8 months ago #57169

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

Thank you for the first file.

Use: sudo geany /etc/default/gpsd
3 years 8 months ago #57181

Please Log in or Create an account to join the conversation.

  • Posts: 23
  • Thank you received: 1
Hello,

This is the output:

# Default settings for the gpsd init script and the hotplug wrapper.

# Start the gpsd daemon automatically at boot time
START_DAEMON="true"

# Use USB hotplugging to add new USB devices automatically to the daemon
USBAUTO="true"

# Devices gpsd should collect to at boot time.
# They need to be read/writeable, either by user gpsd or the group dialout.
DEVICES="/dev/gps"

# Other options you want to pass to gpsd
GPSD_OPTIONS="-n -b"
GPSD_SOCKET="/var/run/gpsd.sock"
SkyWatcher HEQ5 > Pegasus Pocket Powerbox > Celestron Nexstar 6se OTA w/ f/6.3 FR > Nikon Z6 imaging camera > Agena StarGuider 50mm guide scope > ZWO ASI290MM Mini guide camera
3 years 8 months ago #57184

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

A symlink can be created by a rule. Astroberry does not automatically have the device adder which symlinks drivers. I am seeing what has /dev/ttyACM1. Next is to see who has /dev/ttyACM0.

USE: sudo udevadm test -a add $(udevadm info -q path -n /dev/ttyACM1)

Next

USE: sudo udevadm test -a add $(udevadm info -q path -n /dev/ttyACM0)

Finally

USE: sudo geany /lib/systemd/system/gpsd.service

Change "forking" to "idle". NGINX is the only service I know that needs to be "forking". NGINX explicitly states this.
Last edit: 3 years 8 months ago by John Robison.
3 years 8 months ago #57187

Please Log in or Create an account to join the conversation.

  • Posts: 23
  • Thank you received: 1
Thanks for your efforts to troubleshoot this issue with me. Jasem from StellarMate has been troubleshooting as well over the last two days. I noticed that the stable version of StellarMate 1.5.3 was release this week, so I did a clean installation this morning and everything is working as expected.
SkyWatcher HEQ5 > Pegasus Pocket Powerbox > Celestron Nexstar 6se OTA w/ f/6.3 FR > Nikon Z6 imaging camera > Agena StarGuider 50mm guide scope > ZWO ASI290MM Mini guide camera
3 years 8 months ago #57341

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

Fantastic. You and I use a common GPS device. I discovered my issue with this same problem. The Problem is USB 3.0.

Any USB 2.0 device does not work 100%. What does it not work with? Any Udevadm rule governing an RS233 device stops working 100%.

This doesn’t appear to be INDI. This is an OS issue. Rules don’t work under USB 3.0. A rule with a SYMLINK doesn’t get run. Under 2.0, the SYMLINK gets created.

Running udevadm test cannot find idVendor:idProduct. Moving to USB 2.0 works. I would be interested if chained 3.0 devices work.
3 years 8 months ago #57343

Please Log in or Create an account to join the conversation.

Time to create page: 1.043 seconds