help "from GPS" is in Red and not able to be selected

[Gregg Lind]

I am trying to get the 64bit mode windows 7 to work with roverlog my new GS puck

did some changes to the tck script now the GPS is reading and sending to the roverlog but I get a "RED GPS" and cannot enable reading from GPS

2013-09-23 13:02: Popup_Debug: Debug log enabled

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

2013-09-23 13:02: Read_GPS: Got a $GPRMC line

2013-09-23 13:02: Read_GPS: Time difference abs(tgps-tpc) = 2

2013-09-23 13:02: Read_GPS: Machine time and GPS time agree.

2013-09-23 13:02: To_Grid: lat lon = 42.017293 -91.694477

2013-09-23 13:02: Read_GPS: Cancelling after job.

2013-09-23 13:02: Read_GPS: Scheduling after job.

[Tom Mayo]

Looks like the GPS module is never getting requests from the main RoverLog program. Since you have hacked the code, it's hard to help you unless you provide the code you modified. Check the IP settings between the GPS module and RoverLog to see if there is a mismatch on port number or IP address. 

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "RoverLog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to roverlog+u...@googlegroups.com.
To post to this group, send email to rove...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/roverlog/7e6a22de-b674-4f31-a62e-25ee8fe8070d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[W7QQ]

I too am having the same problem:  GPS info is getting into the GPS module but the main screen shows the GPS data in red, as though the info is blacklisted. Cannot seem to correct this after reading the manual and applying everything therein. Background: I'm not as adventurous as Gregg so I have not attempted to change anything in the program.

I previously used this package with an older XP machine with the GPS directly connected to the serial port. It worked fine with that older XP machine. In a move to conserve volume at the op position I am trying to use a smaller HP Mini. This later machine is also an XP machine but having no serial port, I struggled to find a working serial to USB adapter.  Having finally done that (and learning things I didn't want to know about counterfeit chips, FLDI and related issues) I arrived at a point where the Roverlog GPS module reads GPS data and updates correctly when there has been a change to grid info but does not make this updated info available on the main screen where the GPS display remains red.

Anyone have ideas about how to solve this Roverlog failure to show and log current GPS info?

73, Bill

W7QQ DM65sb 

[Gregg Lind]

My problem is that the new GPS sends new data strings also that the software tries to interpret. but also I modified the code to fix the parsing of the time see below...

I was wondering if I could get some help on roverlog using my GPS, the GPS module blanks the gps data as I believe the script cannot handle the other data sent from the gps. I believe the problem is read gps routine and at the bottom of the function it. Runs the section "if we don't have core information, something is screwed up and resets all the fields"

I need to use a logging program since last contest my log was so screwed up that I submitted so I am going to use computer logging when mobile roving.. I had rover log working on my old laptop and it died so I got this new setup and I cannot get rover log to work. I changed the two places to fix the time of day issue, but the program still blanks the data.

      set utc [ lindex $parsed 1 ]

with
      set utc [ lindex [ split [ lindex $parsed 1 ] "." ] 0 ]


This GPS works with all other app on my Windows 7 Machine.

--
You received this message because you are subscribed to a topic in the Google Groups "RoverLog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/roverlog/9oMSCWGmG6c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to roverlog+u...@googlegroups.com.

To post to this group, send email to rove...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/roverlog/81ca0ae9-f0d7-4b1d-8d64-1ff2359cc12f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Thomas]

On Thu, Apr 17, 2014 at 7:28 PM, Gregg Lind <gr...@thelinds.net> wrote:

I changed the two places to fix the time of day issue, but the program still blanks the data.

      set utc [ lindex $parsed 1 ]

with
      set utc [ lindex [ split [ lindex $parsed 1 ] "." ] 0 ]

I had a similar problem.  It's because my GPS is including a subsecond in its reports - it supports multiple readings per second.  Roverlog doesn't like the decimal in the time at all, and I found it necessary to do the time split trick you've mentioned.  Just be sure that you apply it to all sections where Roverlog deals with the GPS timestamp, and you should be fine.

--
-Thomas AC9BJ
Mount Horeb, WI  EN53da

[Tom Mayo]

Folks,

I may have fixed this in the most recent release. If not, it would help me if you'd send some NMEA data I can use to reproduce the issue. 

Tom

Sent from my mobile phone

--

You received this message because you are subscribed to the Google Groups "RoverLog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to roverlog+u...@googlegroups.com.

To post to this group, send email to rove...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/roverlog/CAFe52LXYJoAcsXbB-_4shjLdy8tBUVJy02X-y7EeDQuA52XTYg%40mail.gmail.com.