I’m just following the example that seeedstudio gave. The commands above are the entirety of the configuration.
Their instructions were
Note down DevEui and AppEUi
+ Add end device|
Click Manually , to enter the registration credentials manually
Select the Frequency plan according to your region. Also make sure you use the same frequency as the gateway in which you will connect this device to. Select MAC V1.0.2 as the LoRaWAN® version and PHY V1.0.2 REV B as the Regional Parameters version . These settings are according to the LoraWAN® stack of Wio-E5.
Copy and paste the previously obtained information from step 8 into DevEUI and AppEUI fields. For AppKey field, use: 2B7E151628AED2A6ABF7158809CF4F3C.
Yep that is for where registering a device that isnt covered by the TTN Device repository…
Dont see anything there where ist says effectively
When using OTAA the LNS recognises the DevEui and AppEui as being ones that matach the registration details you have provided if copied and entered correctly, then as part of the join process the LNS provides the DevAddr over the air (its in the name ) as part of the authenticated ‘activation’ process… There is no hardcoding involved.
Freq Plan AU FSB 8 → does that match that of either of the two Uni GW’s? Note TTN generally uses FSB 2 on AU915 per dropdown on selector. As advised above you need to check device is on same plan as GW’s…As advised there are also two AS923 options in AU - 920-923 and 923-925 with secondary channels.
If device and GW are not fully aligned they wont talk/hear on aligned channels and so join process will fail…
yes, i have tried all the australian plans from FSB 1 to 8, including FSB 2. none of them are connecting. I tried the AS ones too but they seem to give errors
Invalid value of field mac_settings.desired_rx2_data_rate_index.value
As I noted in the original question, I’m going through the documentation but they are very confusing and dont provide a clear a way of translating the parameters into AT commands.
Theres probably some configuration i need to do for the channels and stuff right?
Edit:
trying to read the documents and understand the commands. Ive double checked the commands and the DR command with the AU915 plan seems correct. ive checked ADR is on, class A should be correct. not sure if port is an issue.
i reread the section on ch command and made changes.
its now AT+CH=NUM,0-71 based on the Regional Parameters doc saying au915 has 72 channels from 0 to 71.
that still didn’t fix it though.
Am i supposed to create the channel data structure for each of the 72 channels and define the frequency and datarates? How does that work as the Regional Parameters document separately defines uplink and downlink but the AT command sheet doesnt differentiate between that
also tried
AT+JOIN=DR2
and
AT+JOIN=DR6
for the join request, also based on what the Regional Parameters doc said.
But that stopped messages from appearing in the live feed all together
I keep getting errors like
Specified version PHY_V1_0_2_REV_B of band AS_923_2 does not exist
Invalid value of field mac_settings.desired_rx2_data_rate_index.value
for all of the AS plans.
I can register a new device with ‘Asia 920-923 MHz (used by TTN Australia)’ without any issue. May-be you need to delete your existing one and add it new with the right settings?
Thank you, recreating the application and reregistering the device worked. I could select 1.0.2 with the AS923 plan without any issue, and the device finally connected to TTN.
Thank you so much to every one here who helped!
If i may ask though, how do you check the configuration of a gateway and determine the plan it’s using? This would be very useful to know
If you have the gw id or eui there are several queries you can make against the TTN database, even looking back at old V2 systems where they may still be available.
In your case I quickly checked and at least one of the two GW’s you call out is runnng on Meshed - the TTN Partner infrastructure provider in AU, with Andrew Maj (one of the founders) as the nominated user id:
(Note here v2 references v2 of the api not V2 of TTN! (‘Off’ since Dec 21))
There are similar search structures that can be used on PacketBroker to similar ends. (As TTN traffic is routed theough PB to facilitate sharing and peering with TTN and any associated networks ) Forum search may/will reveal some of the url’s/queries used by others over the years…