I pulled a radio out of the reach and hooked it to a usb serial converter and was receiving the RTK data. This is a bit of good news. it means there is no handshaking required by the user to start receiving correction data. If they are using some version of this MOST protocol, the GlobalSat radios “remember” their previous channel settings. You would need to buy another Reach RS to get the radio preconfigured this way. The good news is that if you have another one laying around, you can pipe the RTCM data directly to a ublox chip and get your RTK that way.
I also tried using a HM TRP radio with the SiK firware running on it to stream data from the Emlid.
Although I was able to pick up RTK corrections there were a few issues with this approach:
The web interface would not load up when the Emlid was booted up with the packet radio installed
If you somehow get the web interface loaded up, and try to change ANY of the “LoRa” settings, the program hangs…forever. I am sure is waiting for a response from what was the Global Sat radio.
There is some good news however, because the Global Sat radio is sending back information about its self and the operational status of the radio, one can interrogate it to reveal the settings it is using to communicate with other Emlids.
The LM-210H doesn’t appear as a current product on GlobalSat’s website. It is listed for sale on a couple of websites for under USD$20, but no stock available. I wonder if it has been superseded?
There is another MOST-link only module listed on the GlobalSat website called the LM-230H, but it does not come in a pin-header style module with the RP-SMA antenna connection, so would require a bit more work to package up into a discrete radio.
The dual mode GlobalSat radios (MOST-link and LoRaWAN) like the LM-110H1 look to be slightly different specification using an AT command set to send
Ultimately what I would like to get to is a fully Reach RS/RS+ compatible and re-configurable LoRa (MOST-link) external radio with RS232 interface.
For the MCU, its hard to read from the picture but I would put my money that being a STM 8L 151G. I have not done much with ST but I do happen to have one of their programmer/debuggers in my desk.
After poking and prodding at it for a few hours I was not able to grab the firmware off of it but I am no expert. Also I am being careful not to destroy my only spare radio, so if anyone out there knows how to do this please speak up.
I sent the interrogation/read command (0xFF 0x4C 0xCF 0x52 0xA1 0x52 0xF0) and got this:
HEX(responce) Meaning
Preamble: 24 None
Model Name: 31 30 31 48 101H
FW version: 31 36 31 30 30 34 31 1610041
LoRa MAC: A3 6C 7D 03 00 39 00 71
Group ID: 00 None (I thought this would have been the propriatary "key")
RF Freq: 0D F6 38 915MHz
RF Tx Rate: 05 18.23Kbps
RF Power: 07 20dBm
UART Baud Rate: 06 57600bps
UART Parity: 00 None
Wakeup Time: 05 1sec
End Word: 21 None
It is curious even though I set the baud rate to 9600bps the radio claims to be talking back at 57600bps.
No, I dont get anything back when I change the baud rate to 57600.
Maybe this is a change in the firmware that did not get documented in the Design Guide.
I don’t know of any configuration software GlobalSat provides. The only way I was able to reconfigure the radio and the way that the Reach RS does it is by pulling pins 6 and 7 high, then issuing the commands that change the properties of the radio.
Here is the example given by the Design Guide:
For example, Module setting is as below:
Group ID is 0. Air rate is 0.81K bps. RF frequency is 915.000MHz. RF power is 20dBm.
UART Baud Rate is 9600bps. UART parity is none. Wakeup time is 1 sec.
You are welcome to look up exactly what is happening here but I can confirm that this method works with with a FTDI USB to serial converter and RealTerm terminal software.
If you know of any GlobalSat configuration software please share the link
For Operation Mode 4(Setup mode) connect FTDI USB to serial converter to LoRa and leave pins 6(P2) & 7(P1) alone do not connect it with ground. read and write after configuration test by operation mode 1 (connect ground to pins 6 & 7).
The software provided is for the InternalSence RTK system. The only way this has a chance of working is if InternalSense and GloabalSat are using the exact same communication protocol when configuring their chips. That may be the case here but I have not gotten their software working either (missing plugin).
If a gui is really of that much, interest, I will hack something together and post it on github but I dont see any flaws configuring using hex commands.
@naratchr@DirtyHarry anyone could receive corrections using LM-210H or LM-230? I’m stating a project with RPI + LoRa TX/RX + NEO-8MT and need to receive my corrections from Emlid Reach RS+ to my RPI rover
You got it. It’s a fairly standard radio in there. Not Lora or anything. Im sure you know the one to which I am referring.
I made it to communicate with another device without having to totally reinvent the wheel. You could use it to communicate to another reach rs but that was not the motivation and I don’t know why one would want to. Lora’s range is just better.
