How long is the sentence? Can you post the code that reads the sentence and give me the length of the packet you want to send?
Ok, no more messing with the library.
So here is a NMEA message generated on the transmitter side by the GPS, the is correctly displayed on the serial monitor:
$GPRMC,224553.000,A,1952.6095,S,04355.7367,W,0.34,199.27,160216,,,A*60
All the messages that I want to send start with "$GPRMC," . So that one could be appended on the receiver side in front of the received message before it is Serial.print trough the serial port. That would make the message be 63 byte. But that seems to still be too much.
On the other side I get this:
$GPRMC,230138.000,A,1952.6095,S,04355.7367,W,0.34,199.27,160??
At the end it is truncated and some weird characters added. There are 10 bytes missing.
So I guess 80 bytes would be the maximum ever. If I could split the message in two, that would be enough.
Also, I'm sending radio data with two different payload to two different nodes numbers, but they are the same receiver. The idea is to allow me to use a full 64 bytes of data packet size to try to send the NMEA message. This is required because I'm already sending a data package with the parsed data like altitude and airspeed on a different data package to the same receiver.
Why is this required? Well, I want to make a log of position waypoints on the transmitter SPIFLASH. I can't do it on the receiver side because it is already maxed out on memory size, due to the LCD, menus, buttons, etc, so adding the extra code to allow datalogging is not possible. And since the transmitter was very light on the code, I decided to make the log there.
I'm adding the code I'm using on both the transmitter and the receiver.
This will be, I hope, all part of my next Moteino project, a do all Telemetry System for R/C airplanes/drones, that will allow a fast recovery in case of a fly away. It will also allow the viewing of the model position on a local laptop in real time on Google Maps and to download the position log from the transmitter if no laptop is available.
NMEA message content:
$GPRMC,220516,A,5133.82,N,00042.24,W,173.8,231.8,130694,004.2,W*70
12 coma separated parts:
1 220516 Time Stamp
2 A validity - A-ok, V-invalid
3 5133.82 current Latitude
4 N North/South
5 00042.24 current Longitude
6 W East/West
7 173.8 Speed in knots
8 231.8 True course
9 130694 Date Stamp
10 004.2 Variation
11 W East/West
12 *70 checksum
eg4. $GPRMC,hhmmss.ss,A,llll.ll,a,yyyyy.yy,a,x.x,x.x,ddmmyy,x.x,a*hh
1 = UTC of position fix
2 = Data status (V=navigation receiver warning)
3 = Latitude of fix
4 = N or S
5 = Longitude of fix
6 = E or W
7 = Speed over ground in knots
8 = Track made good in degrees True
9 = UT date
10 = Magnetic variation degrees (Easterly var. subtracts from true course)
11 = E or W
12 = Checksum
Sorry for the long post.
Thank you for your interest.