- miran March 20, 2018 at 1:09 pm
Please can you send me one example of RMC sentence.
I try to connect my GPS Receiver without success. I attempt with RMC protocol.
After first connection my GPS send a few sentence and they are not $GNRMC. Is that the problem?
The first few sentence You can see below.
19:42:03 $GNTXT,01,01,02,u-blox AG – http://www.u-blox.com*4E
19:42:03 $GNTXT,01,01,02,HW UBX-M8030 00080000*60
19:42:03 $GNTXT,01,01,02,ROM CORE 3.01 (107888)*2B
19:42:03 $GNTXT,01,01,02,FWVER=SPG 3.01*46
19:42:03 $GNTXT,01,01,02,GNSS OTP=GPS;GLO*37
19:42:03 $GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*3E
and so one
Please help me. This is really a great improvement of practical use of yours spectrum analyzers.
Regards, MiranAndrew March 21, 2018 at 10:17 am
Are you seeing the “CommErr” message in the Spike application?
If you haven’t already, verify the baud rate is correct.
It looks like after a few seconds, only the RMC string is being transmitted? It only transmits the other NMEA sentences on the first second? I believe in my code I pattern match everything between the string “RMC” and a newline, which means if the RMC sentence was the only sentence in the message it wouldn’t parse properly. I will need to account for this case for the next release.
AndrewAndrew March 21, 2018 at 10:51 am
Here is an RMC string from our shop GPS. If I match it successfully (as per my previous post) I only look for the first 7 comma separated values, and ignore the rest.
$GPRMC,174641.000,A,4552.763046,N,12235.011607,W,0.011,142.26,210318,,,A*47miran March 21, 2018 at 1:33 pm
After setting the correct Port number (13) and correct speed (I tray all standard speed) and pressing the button Connect I receive
immediately the message: “Unable to Connect GPS”
I Also change RMC format from $GPRMC (neutral-all satellite not only GPS) to $GPRMC and add some extra sentences. Without success
20:16:01 $GPTXT,01,01,02,u-blox AG – http://www.u-blox.com*50
20:16:01 $GPTXT,01,01,02,HW UBX-M8030 00080000*7E
20:16:01 $GPTXT,01,01,02,ROM CORE 3.01 (107888)*35
20:16:01 $GPTXT,01,01,02,FWVER=SPG 3.01*58
20:16:01 $GPTXT,01,01,02,GNSS OTP=GPS;GLO*29
20:16:01 $GPTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*20
Please send me all NMEA sentences that are used in the program.
thank you for helping me!
Regards, Miranmiran March 21, 2018 at 1:59 pm
I just change the port number; from 13 to 2 without any other changes from the last GPS settings and now I get position. “GPS Connectect”.
I dont have Altitude, Sat. in View and SNR.
If you send my all NMEA sentences that are used in the program I can fix that.
Many new GPS receiver received also other satellite. For this reason i recommend also to use also $GNxxx sentences.
Regards MiranAndrew March 21, 2018 at 2:13 pm
If you are seeing the “Unable to Connect GPS” then this is not an issue with the NMEA data, it is an issue with attempting to open a file handle with the GPS. We use the CreateFile() function to open the GPS with a fileName of “COM#” where # is the COM port number you provided. Can you think of a reason why the GPS would be unable to open this way? Is it being interfaced in another application?
To answer your question, we only look at the RMC, GSV, and GGA sentences, but we only require the RMC to be present, if the others aren’t present then we ignore those values, but these sentences are only going to be looked at if the GPS is successfully connected, which it doesn’t sound like it is.
RegardsAndrew March 21, 2018 at 2:50 pm
It doesn’t look like your GSV sentence contains the SNR value, so it will stay empty.
Also I used this sentence format for the GGA string.
It looks like your message contains the data when it is emitted. Is it possible it is not emitting the GGA sentence in it’s current configuration?miran March 21, 2018 at 2:57 pm
Thank you for the very quick response.
Now I get all GPS information.
The solution: I just change the port from 13 to 2. Is there any limitation for port number (except max 255)?
I also switch in GPS receiver: GSV, and GGA sentences.
RegardsAndrew March 22, 2018 at 9:27 am
I’m not sure of the limitation. You can determine the COM port number of a device in the device manager.
JasonSParticipantJasonS May 10, 2018 at 8:11 pm
Seems like there is more too this. I also struggled to get the GPS comms going.
My GPS created a COM35 port. This was the first available COM port. No connection in Spike.
I changed it to COM2 manually in Device Manager and all was good!
So there is a limitation somewhere …
Justin Crooks May 11, 2018 at 10:44 am
- This reply was modified 1 week, 4 days ago by Justin Crooks.
I remember running into this before. I think this is the bug fix:
https://support.microsoft.com/en-us/help/115831/howto-specify-serial-ports-larger-than-com9Andrew May 14, 2018 at 9:35 am
Hello Jason and Miran,
It looks like Justin is correct. There is something additional I needed to do to get port numbers above 9 to work properly. I can now get Spike to connect to higher port number devices properly. You should see this in the next version of Spike (no timeframe yet). Apologies for the difficulties and thanks for the feedback so we could get this fixed.
You must be logged in to reply to this topic.