×

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

Bi-monthly release with minor bug fixes and improvements

Help with GPSD

  • Posts: 45
  • Thank you received: 1

Replied by Dana Tousley on topic Help with GPSD

I'll try. I already edited the .inf file with the Windows drivers and it still didn't work - but it's real common for the Prolific driver to not work in Windows as it is.
7 years 1 week ago #15162

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

  • Posts: 45
  • Thank you received: 1

Replied by Dana Tousley on topic Help with GPSD

I'm giving up. I've tried modifying both the Windows and Linux drivers - spent two hours under crystal clear skies last night trying to fix the Linux driver because it wouldn't see the mount either.

That GPS puck is permanently hosed and needs replacing. Lesson: if you don't know what you're doing, don't #$&# with it.

I'll get a new one and start over.
Last edit: 7 years 5 days ago by Dana Tousley.
7 years 5 days ago #15545

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

  • Posts: 200
  • Thank you received: 57

Replied by Paweł on topic Help with GPSD

What was the problem with Linux driver? It should just talk to the device you tell it to. Unfortunately it may be that writing broke some assumptions in the firmware and that will be difficult to fix.
7 years 5 days ago #15547

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

  • Posts: 45
  • Thank you received: 1

Replied by Dana Tousley on topic Help with GPSD

I changed an existing Vendor / Product ID (total of 4 bytes) to the one I had written into the GPS and the next time I tried connecting to mount - nothing. reloaded old driver - mount works again. Problem is I am extremely inexperienced with Linux and it takes me far longer than it should to look up even the simplest stuff.
7 years 4 days ago #15590

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

  • Posts: 200
  • Thank you received: 57

Replied by Paweł on topic Help with GPSD

So it works now? Or just the mount?
7 years 4 days ago #15592

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

Replied by Jasem Mutlaq on topic Help with GPSD

Dana, you read Serial Port Mapping tutorial I presume? This is not suppose to take a lot of time, unless there is no information at all to distinguish between devices. In this case, I'd probably use "Auto-Search" and let it find the devices automatically.
7 years 4 days ago #15594

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

  • Posts: 45
  • Thank you received: 1

Replied by Dana Tousley on topic Help with GPSD

Just the mount works. GPS is in the trash. I will have to buy another one. When that arrives I will not plug it into my USB hub, I will have to plug it in to the USB on the other side of the laptop, so UDEV can differentiate between it and my mount by USB bus. Previously they were on the same bus and it was random as to which got recognized and given a name first. It's a Linux problem that windows somewhat shared. With Windows I had to be careful to always plug the same device into the same port to assign the same COM port.
7 years 4 days ago #15595

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

  • Posts: 200
  • Thank you received: 57

Replied by Paweł on topic Help with GPSD

Maybe you was too quick with the GPS. It is up to you but you can try to debug it a bit more. I simply doubt that it is totally toasted. Did it show up on the lsusb list? If it does the kernel and the core USB driver is *talking* to it and it is *responding*. Otherwise, if it is not there you are right - it is probably toasted.
7 years 4 days ago #15596

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

  • Posts: 45
  • Thank you received: 1

Replied by Dana Tousley on topic Help with GPSD

New gps puck
New udev rule to bind it to dev/globalsat (too many identical Prolific PL2303 serial thingamagigs)
Set gpsd device to dev/globalsat

Joy
┌───────────────────────────────────────────┐┌─────────────────────────────────┐
│ Time: 2017-04-16T02:00:10.000Z ││PRN: Elev: Azim: SNR: Used: │
│ Latitude: 42.xxxxxx N ││ 12 35 312 41 Y │
│ Longitude: 83.xxxxxx W ││ 6 82 280 34 Y │
│ Altitude: 1011.0 ft ││ 17 52 079 31 Y │
│ Speed: 0.6 mph ││ 19 69 049 31 Y │
│ Heading: 3.1 deg (true) ││ 2 39 243 28 Y │
│ Climb: 15.4 ft/min ││ 3 20 043 24 Y │
│ Status: 3D FIX (15 secs) ││ 24 18 268 25 Y │
│ Longitude Err: +/- 40 ft ││ 28 16 151 00 N │
│ Latitude Err: +/- 52 ft ││ 4 20 238 00 N │
│ Altitude Err: +/- 143 ft ││ 23 02 081 00 N │
│ Course Err: n/a ││ 135 21 237 00 N │
│ Speed Err: +/- 71 mph ││ │
│ Time offset: -0.737 ││ │
│ Grid Square: EN82ir ││ │
└───────────────────────────────────────────┘└─────────────────────────────────┘
,"epy":16.028,"epv":43.700,"track":274.5550,"speed":0.125,"climb":-0.011,"eps":3
2.06,"epc":87.40}
{"class":"TPV","device":"dev/globalsat","mode":3,"time":"2017-04-16T02:00:10.000
Z","ept":0.005,"lat":42.725089456,"lon":-83.302931171,"alt":308.160,"epx":12.345
,"epy":16.028,"epv":43.700,"track":3.1148,"speed":0.268,"climb":0.078,"eps":32.0
6,"epc":87.40}
6 years 11 months ago #16214

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

  • Posts: 535
  • Thank you received: 109

Replied by Jim on topic Help with GPSD

Is anyone noticing a problem with indi_gpsd where the timezone offset is not respecting daylight savings time? The UTC time is fine, but now our offset is 5, and indi_gpsd says offset 6. This is really confusing my mount on go-to.

Thanks
Jim
6 years 10 months ago #16715

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

  • Posts: 200
  • Thank you received: 57

Replied by Paweł on topic Help with GPSD

It uses standard system/libc functions to establish local time. Are you sure you have current timezone data installed?
Is your computer showing proper UTC/Local times? What is gpsmon saying?
6 years 10 months ago #16722

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

  • Posts: 535
  • Thank you received: 109

Replied by Jim on topic Help with GPSD

All of the timezone data is up to date. The GPS is reporting the accurate time in UTC. The system clocks are also reporting the correct time at the OS level. All computer clocks are in sync with ntp/chrony.

gpsmon:
Time: 2017-05-13T14:12:40.000Z Leap: ??
Fix:  9 = 26 16  3 23 22 31 14 29  9

sudo hwclock -r;date;date -u
2017-05-13 09:16:06.389065-6:00 {!!}
Sat May 13 09:16:07 CDT 2017
Sat May 13 14:16:07 UTC 2017

As you can see, the hardware clock does show a -6, does indi use the hw clock and not the system clock?

edit:

I found another command datetimectl. This command shows the offset correctly from all clocks. The hwclock command still lists an offset of -6 even though it has the right time. Now I am really confused. All times are correct in both local and UTC time, but the -0600 offset reported by hwclock seems to be the culprit. Will keep digging.

timedatectl
timedatectl status
      Local time: Sat 2017-05-13 10:44:39 CDT
  Universal time: Sat 2017-05-13 15:44:39 UTC
        RTC time: Sat 2017-05-13 15:44:39
       Time zone: America/Chicago (CDT, -0500)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no
[root@neptune ~]# timedatectl
      Local time: Sat 2017-05-13 10:46:12 CDT
  Universal time: Sat 2017-05-13 15:46:12 UTC
        RTC time: Sat 2017-05-13 15:46:12
       Time zone: America/Chicago (CDT, -0500)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

hwclock:
hwclock --debug
hwclock from util-linux 2.28.2
Using the /dev interface to the clock.
Last drift adjustment done at 1494689370 seconds after 1969
Last calibration done at 1494689370 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2017/05/13 15:48:22
Hw clock time : 2017/05/13 15:48:22 = 1494690502 seconds since 1969
Time since last adjustment is 1132 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2017-05-13 10:48:21.092867-6:00
Last edit: 6 years 10 months ago by Jim. Reason: more info from hwclock and datetimectl
6 years 10 months ago #16736
Attachments:

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

Time to create page: 1.141 seconds