Configuring Multitech MDOT for TTN

2 Replies

I have a Multitech MDOT-BOX for testing. Configuring it for TTN requires the following connection to a computer, after which AT commands can be used to probe and set parameters. The following resets the MDOT to factory defaults and shows the configuration overview.

AT&F
AT&V

Firmware: 		2.0.0
Library : 		0.0.9-14-g4845711
Device ID:		00:80:00:00:00:00:b3:76
Frequency Band:		FB_868
Public Network:		off
Network Address:	00000000
Network ID:		6c:4e:ef:66:f4:79:86:a6
Network ID Passphrase:	MultiTech
Network Key:		1f.33.a1.70.a5.f1.fd.a0.ab.69.7a.ae.2b.95.91.6b
Network Key Passphrase:	MultiTech
Network Session Key:	00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
Data Session Key:	00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
Network Join Mode:	OTA
Tx Data Rate:		SF_7
Tx Power:		11
Log Level:		6
Maximum Size:		242
Minimum Size:		11
Maximum Power:		20
Minimum Power:		2
Data:			0

After adding a device to application page on the TTN console with OTA activation, the following identifiers/keys are listed on the TTN console page for the device

Device EUI
Application EUI
App Key
Device Address
Network Session Key
App Session Key

From the Multitech documentation: In OTA mode, the device only needs to be configured with a network name (+NI=1,name) and network passphrase (+NK=1,passphrase). The network session key, data session key, and network address are all automatically configured.

With ABP activation, the following identifiers/keys are listed on the TTN console page for the device. 

Device EUI
Application EUI
Device Address
Network Session Key
App Session Key

From the Multitech documentation: In Manual mode, there is no join request sent and the device must be manually configured with a network address (+NA), a network session key (+NSK), and a data session key (+DSK). The device must be provisioned with the network server as well.

Mapping between TTN and MDOT keys/identifiers

The Device EUI is hardware dependent and should therefore be copied from the MDOT device to the TTN console. The other keys/identifiers are application dependent and should be copied from the TTN console to the device.

For OTA the following settings need to be updated:

AT+PN=1
AT+NJM=1
AT+NI=0,70B3D57EF000451B
AT+NK=0,5108008928062F42980E42C20AC1E4E1
AT&W

TTN direction MDOT
Device EUI <- Device ID
Application EUI -> Network ID
App Key (only in OTA) -> Network Key

I could not get ABP to work.

TTN direction MDOT
Device EUI <- Device ID
Application EUI -> xxx
App Key (only in OTA) -> xxx
Device Address -> xxx
Network Session Key -> xxx
App Session Key -> xxx