-
Posts
-
Sorry if this is a bit naive. How do you get the DEVEUI from a MiniUltraLoRaWAN so that you can input this into the TTN application?
I’ve tried the TTN DeviceInfo sketch, but it isn’t connecting to the gateway so its just printing a blank Device Information listing..
I’m using the RS CH340E USB-Serial adapter to communicate and power the board.
TIA
If you load the example code here (which you must also add your own AppEui), the debug messages on the serial at 115200 bps will print out the DevEui.
I’m not getting a join. I’m pretty sure I’ve got the freqPlan, appEUI and appKey set right. Should I try a reset on the RN2903?
Please provide a screenshot of the TTN dashboard setup of the device and the AppEui added in your unit code. You can blur the private and confidential field.
Also as the RN2903 only supports US band officially, are you using a US915 gateway in Australia?
// Set your AppEUI and AppKey const char *appEui = "70B3D57ED001BD78"; const char *appKey = "86E112B5E0D1B1FDEF2849E2B1AA8645"; #define SLEEP_PERIOD 60000 #define BAUD_RATE_LORA 19200 #define BAUD_RATE_DEBUG 115200 #define debugSerial Serial // Replace REPLACE_ME with TTN_FP_EU868 or TTN_FP_US915 #define freqPlan TTN_FP_US915Yes I’m using the US915 plan in Australia. I have been connecting successfully with a SodaqOne that uses a RN2903 with TheThingsNetwork.h library. Code looks the same.
I’ve just remembered that I had to do a firmware update on the SodaqOne RN2903. Sodaq have provided a hex image routine which I used successfully (https://github.com/SodaqMoja/RN2483FirmwareUpdater). Do I need to do this for the MiniUltraLoRaWAN and would this sketch work on the ATMega328?
What is the output from the debug serial?
I have customer getting this work on 1.0.3 straight out of the box on US frequency on TTN. Let’s check the debug serial output before making a decision on the upgrade. All I know is, 1.0.4 is okay but the newer 1.0.5 has issue to work properly on TTN.
To upgrade on the Mini Ultra LoRaWAN is simpler, follow the instruction here. Then you could use the Microchip upgrade tool to upgrade the RN2903A firmware to 1.0.4.
-- STATUS Model: RN2903 Version: 1.0.3 Sending: mac set deveui 0004A30B00262DDE Sending: mac set adr on EUI: 0004A30B00262DDE Battery: 3036 AppEUI: 70B3D57ED001BD78 DevEUI: 0004A30B00262DDE Data Rate: 0 RX Delay 1: 1000 RX Delay 2: 2000 -- JOIN Model: RN2903 Version: 1.0.3 Sending: mac set deveui 0004A30B00262DDE Sending: mac set adr on Sending: mac set deveui 0004A30B00262DDE Sending: mac set appeui 70B3D57ED001BD78 Sending: mac set appkey 86E112B5E0D1B1FDEF2849E2B1AA8645 Sending: mac save Sending: mac set ch status 0 off Sending: mac set ch status 1 off Sending: mac set ch status 2 off Sending: mac set ch status 3 off Sending: mac set ch status 4 off Sending: mac set ch status 5 off Sending: mac set ch status 6 off Sending: mac set ch status 7 off Sending: mac set ch status 8 on Sending: mac set ch drrange 8 0 3 Sending: mac set ch status 9 on Sending: mac set ch drrange 9 0 3 Sending: mac set ch status 10 on Sending: mac set ch drrange 10 0 3 Sending: mac set ch status 11 on Sending: mac set ch drrange 11 0 3 Sending: mac set ch status 12 on Sending: mac set ch drrange 12 0 3 Sending: mac set ch status 13 on Sending: mac set ch drrange 13 0 3 Sending: mac set ch status 14 on Sending: mac set ch drrange 14 0 3 Sending: mac set ch status 15 on Sending: mac set ch drrange 15 0 3 Sending: mac set ch status 16 off Sending: mac set ch status 17 off Sending: mac set ch status 18 off Sending: mac set ch status 19 off Sending: mac set ch status 20 off Sending: mac set ch status 21 off Sending: mac set ch status 22 off Sending: mac set ch status 23 off Sending: mac set ch status 24 off Sending: mac set ch status 25 off Sending: mac set ch status 26 off Sending: mac set ch status 27 off Sending: mac set ch status 28 off Sending: mac set ch status 29 off Sending: mac set ch status 30 off Sending: mac set ch status 31 off Sending: mac set ch status 32 off Sending: mac set ch status 33 off Sending: mac set ch status 34 off Sending: mac set ch status 35 off Sending: mac set ch status 36 off Sending: mac set ch status 37 off Sending: mac set ch status 38 off Sending: mac set ch status 39 off Sending: mac set ch status 40 off Sending: mac set ch status 41 off Sending: mac set ch status 42 off Sending: mac set ch status 43 off Sending: mac set ch status 44 off Sending: mac set ch status 45 off Sending: mac set ch status 46 off Sending: mac set ch status 47 off Sending: mac set ch status 48 off Sending: mac set ch status 49 off Sending: mac set ch status 50 off Sending: mac set ch status 51 off Sending: mac set ch status 52 off Sending: mac set ch status 53 off Sending: mac set ch status 54 off Sending: mac set ch status 55 off Sending: mac set ch status 56 off Sending: mac set ch status 57 off Sending: mac set ch status 58 off Sending: mac set ch status 59 off Sending: mac set ch status 60 off Sending: mac set ch status 61 off Sending: mac set ch status 62 off Sending: mac set ch status 63 off Sending: mac set ch status 64 off Sending: mac set ch status 65 on Sending: mac set ch status 66 off Sending: mac set ch status 67 off Sending: mac set ch status 68 off Sending: mac set ch status 69 off Sending: mac set ch status 70 off Sending: mac set ch status 71 off Sending: mac set pwridx 5 Sending: mac set retx 7 Sending: mac set dr 3 Sending: mac join otaa Join not accepted: denied Check your coverage, keys and backend status. Sending: mac join otaa Join not accepted: denied Check your coverage, keys and backend status. Sending: mac join otaa Join not accepted: deniedThe output suggest nothing is wrong on the device side. Both the TTN dashboard setting also tallies with the one on the node.
I can see you are using the USB adapter to power the board. Can you try powering the board by supplying maybe 2xAA to the VBAT pin? And de-solder the solder blob underneath the CH340E USB-Serial adapter so no power is being supplied from the adapter to the Mini Ultra LoRaWAN. Sometimes, the USB port output current is not enough especially from side port of computer or older motherboards.
Also, do you have access to the debugging messages on the gateway as well? You should be able to see any LoRa packages even if the TTN setting is incorrect. Also, make sure the device and the gateway distance is not too near each other if they are in the same room.
The gateway you are using is not a single channel gateway right? And if it is a typical 8 channel gateway, just make sure the uplink channel tallies with the ones shown by your device debug messages as above (channel 8-15).
Then only, we try the 1.0.4 as a last resort although I doubt this is the issue.
OK thanks for this.
I have jumpered the CH340E to the MULWAN leaving out the 3.3V pin. Supplied power via a new CR123 in battery holder. Same output, join not accepted: denied.
I’m not sure about the gateway debug messages, I’m using a “uGateway” from Core Electronics and I don’t know how to get at debug. It is a full 8 channel gateway. I may be able to get hold of another gateway in a week or so. I’ve tried moving to another room.
I’ll try and get some output from the RN2903 on the SodaqOne to see if there’s any difference.
Your help and support is much appreciated.OK here is the output from the SodaqOne using the RN2903 (successful join). I think the problem for the RocketMULWAN is that we need to reflash the RN2903 so it will work with the AU915 frequencies (just as I did before with the SodaqOne). The details are here http://forum.sodaq.com/t/channel-frequency-in-australia/421. Please could you confirm that the SodaqMoja/RN2483FirmwareUpdater will work with the MULWAN.
-- STATUS EUI: 0004A30B001A8219 Battery: 3273 AppEUI: 70B3D57ED00145B2 DevEUI: 0004A30B001A8219 Data Rate: 3 RX Delay 1: 1000 RX Delay 2: 2000 -- JOIN Model: RN2903AU Version: 0.9.7rc7 Sending: mac set deveui 0004A30B001A8219 Sending: mac set adr off Sending: mac set deveui 0004A30B001A8219 Sending: mac set appeui 70B3D57ED001BF52 Sending: mac set appkey AFEABCB0B6A25FE0A924A22BCA08AF8D Sending: mac save Sending: mac set ch status 0 off Sending: mac set ch status 1 off Sending: mac set ch status 2 off Sending: mac set ch status 3 off Sending: mac set ch status 4 off Sending: mac set ch status 5 off Sending: mac set ch status 6 off Sending: mac set ch status 7 off Sending: mac set ch status 8 on Sending: mac set ch drrange 8 0 3 Sending: mac set ch status 9 on Sending: mac set ch drrange 9 0 3 Sending: mac set ch status 10 on Sending: mac set ch drrange 10 0 3 Sending: mac set ch status 11 on Sending: mac set ch drrange 11 0 3 Sending: mac set ch status 12 on Sending: mac set ch drrange 12 0 3 Sending: mac set ch status 13 on Sending: mac set ch drrange 13 0 3 Sending: mac set ch status 14 on Sending: mac set ch drrange 14 0 3 Sending: mac set ch status 15 on Sending: mac set ch drrange 15 0 3 Sending: mac set ch status 16 off Sending: mac set ch status 17 off Sending: mac set ch status 18 off Sending: mac set ch status 19 off Sending: mac set ch status 20 off Sending: mac set ch status 21 off Sending: mac set ch status 22 off Sending: mac set ch status 23 off Sending: mac set ch status 24 off Sending: mac set ch status 25 off Sending: mac set ch status 26 off Sending: mac set ch status 27 off Sending: mac set ch status 28 off Sending: mac set ch status 29 off Sending: mac set ch status 30 off Sending: mac set ch status 31 off Sending: mac set ch status 32 off Sending: mac set ch status 33 off Sending: mac set ch status 34 off Sending: mac set ch status 35 off Sending: mac set ch status 36 off Sending: mac set ch status 37 off Sending: mac set ch status 38 off Sending: mac set ch status 39 off Sending: mac set ch status 40 off Sending: mac set ch status 41 off Sending: mac set ch status 42 off Sending: mac set ch status 43 off Sending: mac set ch status 44 off Sending: mac set ch status 45 off Sending: mac set ch status 46 off Sending: mac set ch status 47 off Sending: mac set ch status 48 off Sending: mac set ch status 49 off Sending: mac set ch status 50 off Sending: mac set ch status 51 off Sending: mac set ch status 52 off Sending: mac set ch status 53 off Sending: mac set ch status 54 off Sending: mac set ch status 55 off Sending: mac set ch status 56 off Sending: mac set ch status 57 off Sending: mac set ch status 58 off Sending: mac set ch status 59 off Sending: mac set ch status 60 off Sending: mac set ch status 61 off Sending: mac set ch status 62 off Sending: mac set ch status 63 off Sending: mac set ch status 64 off Sending: mac set ch status 65 on Sending: mac set ch status 66 off Sending: mac set ch status 67 off Sending: mac set ch status 68 off Sending: mac set ch status 69 off Sending: mac set ch status 70 off Sending: mac set ch status 71 off Sending: mac set pwridx 5 Sending: mac set retx 7 Sending: mac set dr 3 Sending: mac join otaa Join not accepted: denied Check your coverage, keys and backend status. Sending: mac join otaa Join not accepted: denied Check your coverage, keys and backend status. Sending: mac join otaa Join not accepted: denied Check your coverage, keys and backend status. Sending: mac join otaa Join accepted. Status: 00000001 DevAddr: 26042961 -- LOOP Blue Led ON Battery Volts = 4083 Temperature = 18.00 nofix Red Led ON Sending: mac tx uncnf 1 016700AA02739F7E03880000000000000000C8 Successful transmission All Led's OFF -- LOOPAfter reading your review on the uGateway’s product page, I noticed you are running Australia AU915 and not North America’s US915. Although they are similar, but there are differences. Unless on 1.0.4 has some patch that takes care of this, I’m pretty sure it won’t work.
Also from the debug messages of your Sodaq unit, it stated the unit as having a RN2903AU module (only RN2903A exist). It means it is clearly having an AU915 firmware which is not released to public before and the firmware revision is stated as 0.9.7rc7. It means it is still a release candidate. So it is not a 1.0.4 as you have mentioned earlier.So, I guess we can maybe try the 1.0.4 (or the Australian 0.9.7rc7 that you have access to). Please reread this message on the firmware upgrade.
I think we should go with the Australian 0.9.7rc7 since we know this works. My question is, will the SodaqMoja/RN2483FirmwareUpdater work OK with the MULWAN? I’m a bit loath to go down the Microchip LoRa Development Suite path as it looks complicated and others have struggled.
CheersI have been updating the RN2483A that was previously on 1.0.3 as the 1.0.4 was publicly available faster than the RN2903A’s. I have no issue updating them using the Microchip tool for a big batch of the modules. With Mini Ultra LoRaWAN, we are not using the ATMega328 MCU in between the PC and RN2903A, it is direct connection. Those who have issue are due to using SoftwareSerial or having the MCU acting as a bridge.
- You must be logged in to reply to this topic.
