Hi all,
Beta port of my RAK Wireless RAK811 LoRaWAN(not LoRa) module library to TinyCLR V2 on Fezduino (suitable clicks for Fezportal etc. on the way) is available.
The RAK811 EVB needs some mods with wire cutters detailed here. Beware, I may revisit the removal of 0ohm resistor on reset line.
The library is working reliably in my test rig (compatibility, stress & soak) on a The Things Network node running in my office and on the nationwide network operated by Spark NZ,
The next step will be to build libraries for other LoRaWAN modules (waiting on EVBs from emOne and others) then after 3 or 4 see if there is enough commonality to role them up into one codebase.
@KiwiBryn
4 Likes
Great Byran, I will try to see if I can get your code working in a click LoraWAN!
Hi,
Sorry, the V1 code is RAK811 module specific. Each vendor has slightly different AT commands which is a problem. e.g. one vendor you specify the transmission port each time you send a message, the other you set it for a session. They also appear to handle downlink messages in different ways in class A & class C.
I have an iMAS923 modem due in a couple of days from Thailand which comes in Arduino shield and or Mikroe Click format so i’ll write a driver for that next.
I can’t get Microchip RN290X/RN248X modules (used in some of the Mikroe LoRaWAN clicks) which are certified for use in NZ(AS923) which is a problem.
@KiwiBryn
I have the LoraWan 5 Click, it uses the MIPOT 32001409 Module…
Hi
I had a look at the manual and the MIPOT device uses quite a different approach to the three modems I have.
For example with
USI to get the device version
AT+VER
then the device responds
lrwan_ver>,<fw_ver>,,<bootloader_ver>
OK
RAK811 to get the device version
at+version
Then the device responds with
OK
With the MIPOT Device to get the firmware version
0XAA 0x34 0x00 0x22
Then the device responds with
0XAA 0xB4, 8
The RAK & USI & IM devices use an approach closer the Hayes AT Command which sacrifices some storage as the commands are longer. Where as the MIPOT approach is most probably to minimise the amount of storage used.
I had a quick look at the MIPOT site and they didn’t appear to support AS923 so I can’t test/debug in New Zealand.
@KiwiBryn
