Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- TinyTrak
- Messages
Search
|
Re: New GPS units additional NMEA prefixes
True, but? WHY??
toggle quoted message
Show quoted text
Why reduce the GPS unit's capability for a single character difference? The messages with different Talker IDs could be used by the TT3 & TT4.? They have valid information and are the same format - except the second character of the Talker ID.?? ? ? $GN - provides data calculated from GLONASS and GPS satellites. This is the default message sent by the M8N and many other new GPS modules with updated firmware.
|
|
Re: New GPS units additional NMEA prefixes
Hi Guys, ? OK, some info. The u-blox r8 receivers are capable of receiving GPS, WAAS, Galileo, Glonass, and BeDou. Since there are only 2 RF frontends, Glonass and BeDou are mutually excluded. With all enabled except BeDou, a receiver sitting on my kitchen table routinely receives 25-28 satellites in lock. The U-Blox chip is capable of utilizing all this info to arrive at a location solution. It is obvious that 28 sats will give a better location than 7 or 8 from GPS. If you just want GP messages, go to the u-blox website, download u-center and disable everything but? the GPS sats. You can also find a detailed manual on the chip's operation at the u-blox site. ?? JimK? N8PXW https://www.u-blox.com/en/product/u-center
On Thursday, May 7, 2020, 9:47:13 PM EDT, Rob Giuliano via groups.io <kb8rco@...> wrote:
If you are really interested, you can read the NMEA 0183 documnetation.? I used The short answer is that the TT3 and TT4 devices look at 2 NMEA 0183 sentences to sent position reports: 123519 Fix taken at 12:35:19 UTC 4807.038,N Latitude 48 deg 07.038' N 01131.000,E Longitude 11 deg 31.000' E 1 Fix quality: 0 = invalid 1 = GPS fix (SPS) 2 = DGPS fix 3 = PPS fix 4 = Real Time Kinematic 5 = Float RTK 6 = estimated (dead reckoning) (2.3 feature) 7 = Manual input mode 8 = Simulation mode 08 Number of satellites being tracked 0.9 Horizontal dilution of position 545.4,M Altitude, Meters, above mean sea level 46.9,M Height of geoid (mean sea level) above WGS84 ellipsoid (empty field) time in seconds since last DGPS update (empty field) DGPS station ID number *47 the checksum data, always begins with * RMC Recommended Minimum sentence C 123519 Fix taken at 12:35:19 UTC A Status A=active or V=Void. 4807.038,N Latitude 48 deg 07.038' N 01131.000,E Longitude 11 deg 31.000' E 022.4 Speed over the ground in knots 084.4 Track angle in degrees True 230394 Date - 23rd of March 1994 003.1,W Magnetic Variation *6A The checksum data, always begins with * The standard provides that each message be prefixed (talker ID) with $G? where the ? indicates where the data originalted: GP-GPS GL-GLONASS GN-Combined receiver GA-Galileo GB-BeDou So if the message $GPRMC would be a recommended Minimum sentence C from GPS satellites $GLRMC would be a recommended Minimum sentence C from GLONASS satellites $GNRMC would be a recommended Minimum sentence C from combination of satellites Same with GGA.? So you see that by ignoring the prefix, and just looking at the 3-character message ID and following Data, the tracker would send the proper data.? At least for $GP, $GL, and $GN, but I don't see why the others would be ignored. At least that is what I have been reading on the NMEA standard, again mainly: . KB8RCO On Thursday, May 7, 2020, 05:53:29 PM EDT, weatherspotting <weather@...> wrote: So who wants to explain all this to me? No clue what GL, GN, GA GB and why we would need different settings for GPS. David On 5/7/2020 11:47 AM, Rob Giuliano via groups.io wrote: Yes. Seems more and more GPS units are including GLONASS. Many include others. The prefix I gave correspond to: GP-GPS GL-GLONASS GN-Combined receiver GA-Galileo GB-BeDou From what I have looked at, many current GPS units are now using GN - Combined receiver It appears the messages are the same, just the second letter changes - at least for GN vs GP with respect to GGA and RMC. These come out as GNGGA and GNRMC insterad ofg GPGGA and GPRMC. I assume the GN means it could be calculated from either GLONASS or GPS satellites, or both. Robert Giuliano KB8RCO On Thursday, May 7, 2020, 12:20:03 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote: Robert, Is this a dual-band (NMEA+GLONASS) GPS receiver? 73, Allen AF6OF -----Original Message----- From: Rob Giuliano via groups.io <kb8rco@...>
To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module. ? Settings: 10Hz update with output at 19200,n,8,1 I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid. I plugged in my older GPS, and everything is fine. ? Settings: 10Hz update with output at 19200,n,8,1 Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.? Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options? Current prefixes are: GP, GL, GN, GA, and GB. Robert Giuliano KB8RCO |
|
Re: New GPS units additional NMEA prefixes
Hi Guys, ? OK, some info. The u-blox r8 receivers are capable of receiving GPS, WAAS, Galileo, Glonass, and BeDou. Since there are only 2 RF frontends, Glonass and BeDou are mutually excluded. With all enabled except BeDou, a receiver sitting on my kitchen table routinely receives 25-28 satellites in lock. The U-Blox chip is capable of utilizing all this info to arrive at a location solution. It is obvious that 28 sats will give a better location than 7 or 8 from GPS. If you just want GP messages, go to the u-blox website, download u-center and disable everything but? the GPS sats. You can also find a detailed manual on the chip's operation at the u-blox site. ?? JimK? N8PXW https://www.u-blox.com/en/product/u-center
On Thursday, May 7, 2020, 5:53:30 PM EDT, weatherspotting <weather@...> wrote:
So who wants to explain all this to me? No clue what GL, GN, GA GB and why we would need different settings for GPS. David On 5/7/2020 11:47 AM, Rob Giuliano via
groups.io wrote:
Yes.
Seems more and more GPS units are including GLONASS. Many include others. The prefix I gave correspond to: GP-GPS GL-GLONASS GN-Combined receiver GA-Galileo GB-BeDou From what I have looked at, many current GPS units are now using GN - Combined receiver It appears the messages are the same, just the second letter changes - at least for GN vs GP with respect to GGA and RMC. These come out as GNGGA and GNRMC insterad ofg GPGGA and GPRMC. I assume the GN means it could be calculated from either GLONASS or GPS satellites, or both. Robert Giuliano KB8RCO On Thursday, May 7, 2020, 12:20:03 PM EDT, vhsproducts
via groups.io <vhsproducts@...> wrote:
Robert,
Is this a dual-band (NMEA+GLONASS) GPS receiver?
73,
Allen AF6OF -----Original
Message----- From: Rob Giuliano via groups.io
<kb8rco@...>
To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B
out again and connected it to a new
uBlox M8N GPS module.
? Settings: 10Hz update
with output at 19200,n,8,1
I see the GPS sentences
in a terminal, but the Green LED never
flashes or comes on solid.
I plugged in my older
GPS, and everything is fine.
? Settings: 10Hz
update with output at 19200,n,8,1
Then I realized the
NMEA sentences all started with 'GN'
instead of 'GP'.? Digging deeper, I
found that uBlox configuration
(u-center) allows you to change the
"main talker" to 1-GPS (default is
3-Combined).? Don't forget to go to
the CFG option to permanently set
this value, or it will reset on
power up.?
Only difference
appears to be the second letter.?
Any chance of a future firmware update
to handle more options?
Current prefixes are: GP,
GL, GN, GA, and GB.
Robert
Giuliano
KB8RCO |
|
Re: New GPS units additional NMEA prefixes
If you are really interested, you can read the NMEA 0183 documnetation.? I used The short answer is that the TT3 and TT4 devices look at 2 NMEA 0183 sentences to sent position reports: 123519 Fix taken at 12:35:19 UTC 4807.038,N Latitude 48 deg 07.038' N 01131.000,E Longitude 11 deg 31.000' E 1 Fix quality: 0 = invalid 1 = GPS fix (SPS) 2 = DGPS fix 3 = PPS fix 4 = Real Time Kinematic 5 = Float RTK 6 = estimated (dead reckoning) (2.3 feature) 7 = Manual input mode 8 = Simulation mode 08 Number of satellites being tracked 0.9 Horizontal dilution of position 545.4,M Altitude, Meters, above mean sea level 46.9,M Height of geoid (mean sea level) above WGS84 ellipsoid (empty field) time in seconds since last DGPS update (empty field) DGPS station ID number *47 the checksum data, always begins with * RMC Recommended Minimum sentence C 123519 Fix taken at 12:35:19 UTC A Status A=active or V=Void. 4807.038,N Latitude 48 deg 07.038' N 01131.000,E Longitude 11 deg 31.000' E 022.4 Speed over the ground in knots 084.4 Track angle in degrees True 230394 Date - 23rd of March 1994 003.1,W Magnetic Variation *6A The checksum data, always begins with * The standard provides that each message be prefixed (talker ID) with $G? where the ? indicates where the data originalted: GP-GPS GL-GLONASS GN-Combined receiver GA-Galileo GB-BeDou So if the message $GPRMC would be a recommended Minimum sentence C from GPS satellites $GLRMC would be a recommended Minimum sentence C from GLONASS satellites $GNRMC would be a recommended Minimum sentence C from combination of satellites Same with GGA.? So you see that by ignoring the prefix, and just looking at the 3-character message ID and following Data, the tracker would send the proper data.? At least for $GP, $GL, and $GN, but I don't see why the others would be ignored. At least that is what I have been reading on the NMEA standard, again mainly: . KB8RCO On Thursday, May 7, 2020, 05:53:29 PM EDT, weatherspotting <weather@...> wrote: So who wants to explain all this to me? No clue what GL, GN, GA GB and why we would need different settings for GPS. David On 5/7/2020 11:47 AM, Rob Giuliano via groups.io wrote: Yes. Seems more and more GPS units are including GLONASS. Many include others. The prefix I gave correspond to: GP-GPS GL-GLONASS GN-Combined receiver GA-Galileo GB-BeDou From what I have looked at, many current GPS units are now using GN - Combined receiver It appears the messages are the same, just the second letter changes - at least for GN vs GP with respect to GGA and RMC. These come out as GNGGA and GNRMC insterad ofg GPGGA and GPRMC. I assume the GN means it could be calculated from either GLONASS or GPS satellites, or both. Robert Giuliano KB8RCO On Thursday, May 7, 2020, 12:20:03 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote: Robert, Is this a dual-band (NMEA+GLONASS) GPS receiver? 73, Allen AF6OF -----Original Message----- From: Rob Giuliano via groups.io <kb8rco@...>
To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module. ? Settings: 10Hz update with output at 19200,n,8,1 I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid. I plugged in my older GPS, and everything is fine. ? Settings: 10Hz update with output at 19200,n,8,1 Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.? Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options? Current prefixes are: GP, GL, GN, GA, and GB. Robert Giuliano KB8RCO |
|
Re: New GPS units additional NMEA prefixes
¿ªÔÆÌåÓýSo who wants to explain all this to me? No clue what GL, GN, GA GB and why we would need different settings for GPS. David On 5/7/2020 11:47 AM, Rob Giuliano via
groups.io wrote:
|
|
Re: New GPS units additional NMEA prefixes
I don't think a translator is necessary for many of the newer GPS receivers. The output difference for NMEA sentences "we are interested in"? is just the second letter: uBlox M8N $GNRMC,140843.000,A,4209.3513,N,08346.2741,W,0.08,,070520,,,A*7C $GNVTG,,T,,M,0.08,N,0.1,K,A*04 $GNGGA,140843.000,4209.3513,N,08346.2741,W,1,12,0.8,237.9,M,-34.6,M,,0000*70 $GNGSA,A,3,04,09,27,16,08,07,26,,,,,,1.7,0.8,1.5*22 $GNGSA,A,3,80,71,73,82,70,81,72,,,,,,1.7,0.8,1.5*2D $GPGSV,3,1,10,04,59,198,35,07,30,299,28,08,44,167,32,09,58,276,31*74 $GNDTM,W84,,0.0,N,0.0,E,0.0,W84*71 Older GPS: $GPRMC,141055.00,A,4209.34960,N,08346.27475,W,0.078,,070520,,,A*64 $GPVTG,,T,,M,0.078,N,0.144,K,A*2D $GPGGA,141055.00,4209.34960,N,08346.27475,W,1,08,1.00,232.5,M,-34.6,M,,*64 $GPRMC,141055.10,A,4209.34960,N,08346.27476,W,0.072,,070520,,,A*6C $GPGGA,141055.10,4209.34960,N,08346.27476,W,1,08,1.00,232.5,M,-34.6,M,,*66 $GPGSA,A,3,04,09,27,16,08,07,26,11,,,,,1.75,1.00,1.43*02 $GPVTG,,T,,M,0.024,N,0.045,K,A*24 So, direct comparison:? (uBlox then Old) $GNRMC,140843.000,A,4209.3513,N,08346.2741,W,0.08,,070520,,,A*7C $GPRMC,141055.00,A,4209.34960,N,08346.27475,W,0.078,,070520,,,A*64 $GNGGA,140843.000,4209.3513,N,08346.2741,W,1,12,0.8,237.9,M,-34.6,M,,0000*70 $GPGGA,141055.00,4209.34960,N,08346.27475,W,1,08,1.00,232.5,M,-34.6,M,,*64 If you import them to a spreadsheet and put them in columns, they all match up. Seems like a simple split of the $GsMSG and ignore the second character would provide all the data, no matter source - at least for the RMC and GGA.? Doesn't sound like that big of a change KB8RCO On Thursday, May 7, 2020, 02:06:35 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote: I would be happy if the TT3 just ignored the GLONASS sentences, and just accepted the NMEA sentences. It does not appear that the plethora of inexpensive GPS receivers out there can let you deactivate the GLONASS ( Damned Commie sentences!) and the multiple format coming from these will not work with the TT3. Its a shame, because these GPS receivers tend to be very cheap, especially in Europe. ( Cheap by EU standards at any rate)? The tendency is also to produce GPS receivers with lower supply and output voltages. This can be a problem for any equipment that has relied upon TTL voltage level serial ( Not RS-232) Many of these new receivers are insanely small! Unfortunately, almost none of the new generation of GPS receivers will violate the COCOM altitude limitations, no matter how much you scream at the manufacturers that it is a minor and perfectly legal code change. The Byonics GPS receivers, both the "Hockey Puck" and the OEM unit, are available in a high altitude version for all the HAB people ( High Altitude in the minds of the people who keep us from building our own cruise missiles is 60,000 feet) The OEM unit has "true" serial ( I don't even know for sure what that means anymore...) and 5 Volt TTL, both of which are fully TT3 and TT4 compatible.? I am going to assume that someone out there in code-land is going to produce a sentence translator as a PIC for these weird GPS receivers. I have been disappointed in making such assumptions before...Like hoping we would find a MAC genius who would build an Apple configuration program for us out of the goodness of their hearts! ( Damned Apple Commies!) 73, Allen AF6OF -----Original Message----- From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 9:53 am Subject: Re: [TinyTrak] New GPS units additional NMEA prefixes I have to admit. I haven't used a TT3 since getting the MTT4B. So only really concerned about the TT4. So I have 2 (or maybe 3) TT4s and the MTT4B (used most). What I am unsure of, is what impact the change from Combined to GPS has. Does it ignore the GLONASS infomration, or still use it and just put out the message as GP. Best guess is that it doesn't use the GLONASS information - kind of a waste. Robert Giuliano KB8RCO On Thursday, May 7, 2020, 12:33:29 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote: Robert, Never mind, I just Googled it. You will have to convince Byon to do an upgrade for the TT4. I don't think it is even possible with the TT3.? 73, Allen AF6OF -----Original Message----- From: vhsproducts via groups.io <vhsproducts@...> To: kb8rco@... <kb8rco@...>; [email protected] <[email protected]> Sent: Thu, May 7, 2020 9:18 am Subject: Re: [TinyTrak] New GPS units additional NMEA prefixes Robert, Is this a dual-band (NMEA+GLONASS) GPS receiver? 73, Allen AF6OF -----Original Message----- From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module. ? Settings: 10Hz update with output at 19200,n,8,1 I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid. I plugged in my older GPS, and everything is fine. ? Settings: 10Hz update with output at 19200,n,8,1 Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.? Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options? Current prefixes are: GP, GL, GN, GA, and GB. Robert Giuliano KB8RCO |
|
Re: New GPS units additional NMEA prefixes
I would be happy if the TT3 just ignored the GLONASS sentences, and just accepted the NMEA sentences. It does not appear that the plethora of inexpensive GPS receivers out there can let you deactivate the GLONASS ( Damned Commie sentences!) and the multiple format coming from these will not work with the TT3. Its a shame, because these GPS receivers tend to be very cheap, especially in Europe. ( Cheap by EU standards at any rate)?
The tendency is also to produce GPS receivers with lower supply and output voltages. This can be a problem for any equipment that has relied upon TTL voltage level serial ( Not RS-232) Many of these new receivers are insanely small! Unfortunately, almost none of the new generation of GPS receivers will violate the COCOM altitude limitations, no matter how much you scream at the manufacturers that it is a minor and perfectly legal code change. The Byonics GPS receivers, both the "Hockey Puck" and the OEM unit, are available in a high altitude version for all the HAB people ( High Altitude in the minds of the people who keep us from building our own cruise missiles is 60,000 feet) The OEM unit has "true" serial ( I don't even know for sure what that means anymore...) and 5 Volt TTL, both of which are fully TT3 and TT4 compatible.?
I am going to assume that someone out there in code-land is going to produce a sentence translator as a PIC for these weird GPS receivers. I have been disappointed in making such assumptions before...Like hoping we would find a MAC genius who would build an Apple configuration program for us out of the goodness of their hearts! ( Damned Apple Commies!)
73,
Allen AF6OF -----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 9:53 am Subject: Re: [TinyTrak] New GPS units additional NMEA prefixes I have to admit. I haven't used a TT3 since getting the MTT4B. So only really concerned about the TT4. So I have 2 (or maybe 3) TT4s and the MTT4B (used most). What I am unsure of, is what impact the change from Combined to GPS has. Does it ignore the GLONASS infomration, or still use it and just put out the message as GP. Best guess is that it doesn't use the GLONASS information - kind of a waste. Robert Giuliano KB8RCO On Thursday, May 7, 2020, 12:33:29 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote:
Robert,
Never mind, I just Googled it. You will have to convince Byon to do an upgrade for the TT4. I don't think it is even possible with the TT3.?
73,
Allen AF6OF
-----Original Message-----
From: vhsproducts via groups.io <vhsproducts@...> To: kb8rco@... <kb8rco@...>; [email protected] <[email protected]> Sent: Thu, May 7, 2020 9:18 am Subject: Re: [TinyTrak] New GPS units additional NMEA prefixes Robert,
Is this a dual-band (NMEA+GLONASS) GPS receiver?
73,
Allen AF6OF
-----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module.
? Settings: 10Hz update with output at 19200,n,8,1
I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid.
I plugged in my older GPS, and everything is fine.
? Settings: 10Hz update with output at 19200,n,8,1
Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.?
Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options?
Current prefixes are: GP, GL, GN, GA, and GB.
Robert Giuliano
KB8RCO |
|
Re: New GPS units additional NMEA prefixes
I have to admit. I haven't used a TT3 since getting the MTT4B. So only really concerned about the TT4. So I have 2 (or maybe 3) TT4s and the MTT4B (used most). What I am unsure of, is what impact the change from Combined to GPS has. Does it ignore the GLONASS infomration, or still use it and just put out the message as GP. Best guess is that it doesn't use the GLONASS information - kind of a waste. Robert Giuliano KB8RCO On Thursday, May 7, 2020, 12:33:29 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote: Robert, Never mind, I just Googled it. You will have to convince Byon to do an upgrade for the TT4. I don't think it is even possible with the TT3.? 73, Allen AF6OF -----Original Message----- From: vhsproducts via groups.io <vhsproducts@...> To: kb8rco@... <kb8rco@...>; [email protected] <[email protected]> Sent: Thu, May 7, 2020 9:18 am Subject: Re: [TinyTrak] New GPS units additional NMEA prefixes Robert, Is this a dual-band (NMEA+GLONASS) GPS receiver? 73, Allen AF6OF -----Original Message----- From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module. ? Settings: 10Hz update with output at 19200,n,8,1 I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid. I plugged in my older GPS, and everything is fine. ? Settings: 10Hz update with output at 19200,n,8,1 Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.? Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options? Current prefixes are: GP, GL, GN, GA, and GB. Robert Giuliano KB8RCO |
|
Re: New GPS units additional NMEA prefixes
Yes. Seems more and more GPS units are including GLONASS. Many include others. The prefix I gave correspond to: GP-GPS GL-GLONASS GN-Combined receiver GA-Galileo GB-BeDou From what I have looked at, many current GPS units are now using GN - Combined receiver It appears the messages are the same, just the second letter changes - at least for GN vs GP with respect to GGA and RMC. These come out as GNGGA and GNRMC insterad ofg GPGGA and GPRMC. I assume the GN means it could be calculated from either GLONASS or GPS satellites, or both. Robert Giuliano KB8RCO On Thursday, May 7, 2020, 12:20:03 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote: Robert, Is this a dual-band (NMEA+GLONASS) GPS receiver? 73, Allen AF6OF -----Original Message----- From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module. ? Settings: 10Hz update with output at 19200,n,8,1 I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid. I plugged in my older GPS, and everything is fine. ? Settings: 10Hz update with output at 19200,n,8,1 Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.? Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options? Current prefixes are: GP, GL, GN, GA, and GB. Robert Giuliano KB8RCO |
|
Re: New GPS units additional NMEA prefixes
Robert,
Never mind, I just Googled it. You will have to convince Byon to do an upgrade for the TT4. I don't think it is even possible with the TT3.?
73,
Allen AF6OF -----Original Message-----
From: vhsproducts via groups.io <vhsproducts@...> To: kb8rco@... <kb8rco@...>; [email protected] <[email protected]> Sent: Thu, May 7, 2020 9:18 am Subject: Re: [TinyTrak] New GPS units additional NMEA prefixes Robert,
Is this a dual-band (NMEA+GLONASS) GPS receiver?
73,
Allen AF6OF
-----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module.
? Settings: 10Hz update with output at 19200,n,8,1
I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid.
I plugged in my older GPS, and everything is fine.
? Settings: 10Hz update with output at 19200,n,8,1
Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.?
Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options?
Current prefixes are: GP, GL, GN, GA, and GB.
Robert Giuliano
KB8RCO |
|
Re: New GPS units additional NMEA prefixes
Robert,
Is this a dual-band (NMEA+GLONASS) GPS receiver?
73,
Allen AF6OF -----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...> To: [email protected] Sent: Thu, May 7, 2020 7:53 am Subject: [TinyTrak] New GPS units additional NMEA prefixes I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module.
? Settings: 10Hz update with output at 19200,n,8,1
I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid.
I plugged in my older GPS, and everything is fine.
? Settings: 10Hz update with output at 19200,n,8,1
Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.?
Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options?
Current prefixes are: GP, GL, GN, GA, and GB.
Robert Giuliano
KB8RCO |
|
New GPS units additional NMEA prefixes
I just pulled my MTT4B out again and connected it to a new uBlox M8N GPS module. ? Settings: 10Hz update with output at 19200,n,8,1 I see the GPS sentences in a terminal, but the Green LED never flashes or comes on solid. I plugged in my older GPS, and everything is fine. ? Settings: 10Hz update with output at 19200,n,8,1 Then I realized the NMEA sentences all started with 'GN' instead of 'GP'.? Digging deeper, I found that uBlox configuration (u-center) allows you to change the "main talker" to 1-GPS (default is 3-Combined).? Don't forget to go to the CFG option to permanently set this value, or it will reset on power up.? Only difference appears to be the second letter.? Any chance of a future firmware update to handle more options? Current prefixes are: GP, GL, GN, GA, and GB. Robert Giuliano |
|
Re: Slightly OT: favorite arm microcontrollers
I am not THE moderator, but I am a?moderator, and I find your posts very interesting. Of course, I fully support your rights to keep and bear ARM's!? 73, Allen AF6OF VHS/BYONICS On Sun, May 3, 2020 at 2:16 PM Hank Riley via <n1ltv=[email protected]> wrote: Gil, |
|
Re: Slightly OT: favorite arm microcontrollers
Hank Riley
Gil,
Yours (ST Arm offerings) is one of the best replies I've seen on any group, forum, or old-fashioned email list.?? Since it's OT, I did not know really what kind of response there'd be to my question, especially such a well written and so information packed one as yours.? So thank you. Rob also had a favorite Arm family of devices: "If you are asking the general group - I kind of like the Teensy line." And yes, I'd certainly like to hear from anyone else about how they've done with arm devices.? ?I don't think there will be a problem with a ton of posts to this thread, but should the moderators feel it's getting too long, it can shift to private email. Hank |
|
Re: Slightly OT: favorite arm microcontrollers
Robert: I will second that -- the teensy parts are great price/perf computing gizmos in friendly dip formats.? Paul S. has done an amazing job not only bringing great hardware to life but writing oodles of code to extend the arduino ide, adding high-perf extensions to take advantage of his hardware. Also a big shout out to Limor Fried who has developed heaps of cool arduino-compatible boards and other fun stuff, and written a bunch of great code to support all her adafruit wonderfulness. gil
|
|
Re: Slightly OT: favorite arm microcontrollers
Hi Hank: Well, I have only used arms from ST, so can't give a complete perspective.? While the core (M0/M3/M4...) is the same for all manufacturers, they add their own peripheral complement, and provide programming APIs and libraries.? It is a big time-sink to learn an ecosystem, and I don't know what is available from TI, NXP... For programming I do everything in gcc.? I've used the eclipse IDE for java stuff in the past, but for c I just use notepad++.? For loading into the board I use a jlink jtag pod (or, for st's development boards, they include an stlink section on-board, and just need a usb cable).? All my arms are 3.3V systems. I use ST's standard-peripheral libraries, not their oddball hal stuff, or the bloated Cube code generator.? I should just start coding registers directly and skip it all, but the SPL libs have worked well for me. The 32-bit arm cortex family includes a pretty-low-power M0 core, a faster M3 core which includes hardware divide, the M4 core which adds a floating point unit and dsp instructions, and higher-perf cores like the M7.? There are some others. The st ecosystem looks kinda like: ? - STM32F0xx? 48MHz M0? (great parts -- have used many) ? - STM32F1xx? 72MHz M3? (have used the ancient F103 before, but this family is quite old) ? - STM32F2xx? 120MHz M3 (never used) ? - STM32F3xx? 72MHz M4? (love this family) ? - STM32F4xx? 180MHz M4? (on my to-do list) ? - STM32F7xx? 216MHz M7?(never used) ? - STM32L4xx? 80-to-120MHz low-power-M4?(never used;? looks great;? no SPL avail) On the low-power end I use an M0-core STM32F071CB by the thousands (128K/16K for $2.63, in qty 100 at mouser).? It has been a nice little chip.? The 051 is much the same with less memory and I have used those in high-altitude balloons.? These Cx parts are 48-pin quad flat packs with a 0.5mm (20 mil) pitch.??I finally mastered soldering this tiny stuff, which used to be scary, but now is no big deal.? And I say that as an old guy with bad eyes and shaky hands :)? I tack two corners, ensure pins and pads line up, solder all pins on each side as a big blob, then use solder wick to finish.? I have done hundreds this way and it only takes me a few minutes per chip.? There are also Kx packages which are 32-pin quad flat packs with a 0.8mm (32 mil) pitch, and much easier to solder.? There are also larger packages with 64 and 100 pins when you need that much i/o. For applications where I want a usb interface, I have used the 072CB and 042C6.? I also like the little tssop-20 042FG. My main go-to part for lots of stuff is?STM32F303CC (256/40K for $4.65, in qty 100), or the 128K?CB.? There is a 373 which adds a 16-bit delta-sig adc, but I generally use spi-connected 24-bit adcs from ti. I'd like to start playing with faster parts like the 405 or 433, but have not found the time yet. ST has a lot of development boards, many of which are dirt-cheap, like the?STM32F3DISCOVERY for 16 bucks, or the?NUCLEO-F303K8 (little dip-30) for 11 bucks, which include the jtag loader circuitry and just needs a usb cable to program. Anyway, that is a quick overview from my st-focused perspective. gil
|
|
Re: Slightly OT: favorite arm microcontrollers
If you are asking the general group - I kind of like the Teensy line. * Lots of IO, including DAC.? * High clock rate, low power.? Many of the 3.3V are 5V tolerant. * Good variety of options for different projects (including CAN-FD on some models).? * Lots of available accessories (breakouts, etc.). * Arduino IDE interface I've always wanted to interface with my vehicle's GPS, and some day (when I have time <grin>) I'll use one of these to read the GPS off CAN and send the NMEA strings to my MTT4 (maybe over Bluetooth).? Now that would be a nice mobile configuration!? However, you may have been specifically asking Byon and Allen - well, you got another opinion. Robert Giuliano
On Saturday, May 2, 2020, 7:29:54 AM EDT, Hank Riley via groups.io <n1ltv@...> wrote:
Gil, Which arms do you favor presently?? Just a few of your faves please, together with the main reasons why. ?Hank __________________________________________________________________ Gil Smith mentioned: I have migrated most everything from pic to arm these days, ... |
|
Slightly OT: favorite arm microcontrollers
Hank Riley
Gil,
Which arms do you favor presently?? Just a few of your faves please, together with the main reasons why. ?Hank __________________________________________________________________ Gil Smith mentioned: I have migrated most everything from pic to arm these days, ... |
|
Re: Tinytrak power supply low voltage from a single LiPo cell?
Gil, It is great to hear from you! I am playing with a slight revision to the MT-AIO, and it uses a switching (5 Volt) regulator, so I expect the new unit to be somewhat more energy efficient. I need 12 to 15 Volts or so for the power amplifier?stage of the MT-AIO, so I would have to do a pretty?big chain of series/parallel batteries to get the power I need from three of the little batteries, which Byon also sources from the land of bat virii.? Three 1865 batteries just happen to fit perfectly in the 1 X 3 battery cartridge, which happily?just fits inside the Pelican case?interior width dimension. I have not found a 2 X2 holder for 18650 batteries yet, but with four 18650's the MT-AIO will put out as much as 20 Watts! This may explode the amplifier eventually, as it is way past its happy thermodynamic envelope, but I am hoping that with transmission?nominally 300 to 500 ms long, the problem won't be heat building up and melting the MOSFETS.? The AIO was designed originally to hold a 8 X AA battery holder. The new design will hold a 10 X AA battery holder, so even though I start off with a nice high Voltage and good power output, the Voltage decay of an alkaline battery slopes and the power output follows the Voltage decay. The Lithium batteries, even the primary batteries, just run with a minor voltage decay, but supply a very?stabile current due to their high ESR. They just run until they give up and die. I like that! Even the 3X AA LiPo ( 14500?) will run the MT-AIO and not fall below 10 Watts power output over their entire discharge time, about 24 hours, and this is a very lightweight option! 73, Allen On Fri, May 1, 2020 at 2:21 PM Gil Smith <tinytrak@...> wrote:
|
to navigate to use esc to dismiss