-
Notifications
You must be signed in to change notification settings - Fork 15
Add Option to Disable Serial Output During Rover to Reduce Radio Traffic #604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Ryan (@ryanmurray ), Please post a link to your Serial Modem project. Thanks! Best wishes, |
https://tinkerbugrobotics.com/how-to-send-rtk-corrections/ Paul I am using sparkfuns Lora serial radios. I believe this may be an issue of the postcard being very noisy. Reading the manual a little more last night is there guidance (I tried low bandwidth defaults) on maybe what minimal nmea messages are needed (maybe none?). Also am I understanding I could turn the frequency of the rtcm messages down? Finally my idea was to adjust the Lora airspeed. Basically I'm just trying to get Lora to work with the postcard (I've also tried with the facet as a base) since espnow works great I'm assuming that the link is just way too noisy. So maybe some guidance on messages for rinex conversion, rtcm messages needed to the rover for RTK, minimal nmea messages. I was going to try to play around a little more but where others gave up on the Loraserial I believe it probably can work. |
Think I found a better solution in rover mode disable uart3 transmit. Once I disconnected the jst wire the Lora worked fine from base to rover. I used 19200 airspeed I am going to retest decreasing that. |
Thanks for the update Ryan (@ryanmurray ), We haven't yet had time to look into this. Please keep the updates coming - and thank you for spending time on this. Best, |
I believe what you are asking is for the ability to disable serial transmission on the RADIO port, during rover, correct?
|
Exactly Nathan and since rtk postcards just have the one port for uart 3 that's what I've been connecting loras to, as soon as I disconnected the transmit wire on the rover postcard I got corrections. It was a moment of glory. On the base I disabled nmea and only broadcast 1005, and the msm7 messages for glo, gal, and gps. I obtained an instant 8mm by 11mm fix. Basically the rover back feeding over serial (I'm in multipoint mode btw) overwhelms the link. I was using the jst cables. as you stated the facet I own does not behave this way. And would make sense why 2 torches can do it fine also. The only issue I could see ( I use corrections on my phone when using state network) is that you need gga on that but my application does that versus the rover itself. But maybe if someone was using onboard ntrip that would break? |
I had suggested removing the Radio RX pin connectivity on the Rover side to basically prove/demonstrate in a hard fashion whether the traffic there was an issue or not. |
Ok this Comment has me thinking I do not really understand the "Configure Ports" Serial Menu for the RTK Postcard: My thinking was that option 1 was to set the Baud Rate for the internal ESP-NOW radio and option 2 set the baud rate for the "4-pin locking JST-GH connector" which I now see listed on the Schematic as the RADIO Port 🤯. Please Confirm? also what then is the "Data Port" ? (My guess: not functional item for the RTK Postcard?) |
RADIO port is the JST-GH connector. DATA is USB (C connector) port B on the CH342. |
Trying to find a way to get Lora to work with postcard since it's quite noisy. Maybe I need to disable much of the nmea on the base. But I also noted for another project using rp2040
Our system uses the Raspberry Pi RP2040 processor on the main board to interact with the GPS receiver and the radio. The software is written for the Arduino IDE and is available, at our Serial Modem project on GitHub. For the base station the RP2040 receives the RTCM formatted correction data from the GNSS receiver and then sends it out in packets over the LoRa radio. LoRa packets are restricted to 256 bytes by the protocol, so the RP2040 breaks up the messages into that sized packets. On the rover, the RP2040 receives the packets from the LoRa radio, parses them into messages (including data spread across packets), and then sends them to the RXD2 port on the rover’s GNSS receiver. The GNSS receiver uses these RTCM messages to produce an an RTK solution with centimeter level accuracy.
Is there a way to break up packets?
I haven't found a definitive guide to what rtcm opus needs but my goal is to set up a base logging while providing corrections over Loraserial and have my rover do work and correct my base later. Espnow works fantastic so I believe I'm overload lora.
The text was updated successfully, but these errors were encountered: