Chris Kuethe wrote: > On Thu, Jun 12, 2008 at 8:05 PM, Tim Cwik <[EMAIL PROTECTED]> wrote: > >> Is there a way to have gpsd use 8N1 for TSIP? The manual says teh >> thunderbolt uses 8N1, the windows support program says it and the >> thunderbolt are using 8N1. I can not find a way to tell the thunderbolt >> to use 8O1. >> > > If you're compiling it yourself, cut out the parity change from line > 66 of tsip.c. I seem to have been eerily prophetic when I put the XXX > comment in... > > I have changed line 66 to: gpsd_set_speed(session, session->gpsdata.baudrate, 'N', 1);
This results in: ]# gpsd -N -D4 /dev/ttyS1 gpsd: launching (Version 2.37) gpsd: listening on port gpsd gpsd: shmat(0,0,0) succeeded gpsd: shmat(0,0,0) succeeded gpsd: shmat(0,0,0) succeeded gpsd: shmat(0,0,0) succeeded gpsd: running with effective group ID 0 gpsd: running with effective user ID 0 gpsd: opening GPS data source at '/dev/ttyS1' gpsd: speed 9600, 8N1 gpsd: => GPS: $PASHQ,RID*28\x0d gpsd: => GPS: 0299661c0800040200001203 gpsd: Navcom: sent command 0x1c (Test Support Block) gpsd: Navcom: command 0x1c mode = 02, length = 0 gpsd: => GPS: 029966200e000001ae02000071000000f203 gpsd: Navcom: sent command 0x20 (Data Request) - data block id = ae at rate 00 gpsd: => GPS: 029966200e00000186020a0071000000d003 gpsd: Navcom: sent command 0x20 (Data Request) - data block id = 86 at rate 0a gpsd: garmin_gps not active. gpsd: no probe matched... gpsd: gpsd_activate(0): opened GPS (4) gpsd: switch_driver(Trimble TSIP) called... gpsd: selecting Trimble TSIP driver... gpsd: ntpd_link_activate: 0 gpsd: speed 9600, 8N1 gpsd: Sent TSIP packet id 0x1f: gpsd: Sent TSIP packet id 0x21: gpsd: Sent TSIP packet id 0x28: gpsd: Sent TSIP packet id 0x8e: 15 gpsd: Sent TSIP packet id 0xbb: 03 gpsd: TSIP packet id 0x8f length 68: ac0700640000002b0000004000000000bfc7da19bb8becd3000861a03e7410004224b0683fe5d1609572ff6bbff4e1debfbb572cc03aa9d2acdc00000000000000000001 gpsd: Unhandled TSIP superpacket type 0xac gpsd: Sent TSIP packet id 0x21: gpsd: Sent TSIP packet id 0x24: gpsd: Sent TSIP packet id 0x3c: 00 gpsd: Sent TSIP packet id 0x26: gpsd: speed 9600, 8N1 gpsd: closing GPS=/dev/ttyS1 (4) gpsd: Received terminating signal 2. Exiting... I hope this is progress, but I am not sure why gpsd closes the port and who sends signal 2. Is anyone using the thunderbolt with gpsd or are we breaking new ground? Thanks, Tim _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
