MM002-xx-EU Personalization - Revision history

Lcs at 11:30, 30 January 2018

2018-01-30T11:30:23Z

← Older revision		Revision as of 11:30, 30 January 2018
Line 77:		Line 77:

	dev_uid=70B3D53260000000&app_key=0123456789ABCDEF0123456789ABCDEF&sfx_id=000FFFFF&sfx_pac=524579AAAA0B47DA		dev_uid=70B3D53260000000&app_key=0123456789ABCDEF0123456789ABCDEF&sfx_id=000FFFFF&sfx_pac=524579AAAA0B47DA


			== Personalization Files ==

			Following files could also be requested on volumes (check with your ressellers)

			Nemeus Yaml File

			---
			xx752:
			:dev_uid: 70B3D532xxxxxxxx
			:app_uid: 70B3D532yyyyyyyy
			:app_key: 8AEAAAAAAAAAAAAAAAAA9574509FB12A
			:dev_addr: 'AAAAAAAA'
			:nwk_skey: 6F49D79EAAAAAAAAAAAAAAAA52E59DD5
			:app_skey: 611B8E7AAAAAAAAAAAAAAAAA4120E4A1
			:sfx_id: 00xxxxxx
			:sfx_pac: AAAAAAAAAAAAAAAA

			...

			xx753:
			:dev_uid: 70B3D532xxxxxxxx
			:app_uid: 70B3D532yyyyyyyy
			:app_key: 1C01E9DAAAAAAAAAAAAAAAA55E74CBDD
			:dev_addr: 'AAAAAAAA'
			:nwk_skey: 156AAAAAAAAAAAAAAAAAC25EE31C8F54
			:app_skey: 544AAAAAAAAAAAAAAAA7069E3FB7B708
			:sfx_id: 00xxxxxx
			:sfx_pac: AAAAAAAAAAAAAAAA



			Nemeus CSV file

			id,dev_uid,app_uid,app_key,dev_addr,nwk_skey,app_skey,sfx_id,sfx_pac
			xxx752,70B3D5326yyyyyyy,70B3D53260yyyyyyy,8AEAFCE6AAAAAAAAAAAAAAAA56899888,6yyyyyyy,6F49D79AAAAAAAAAAAAAAAAF52E59DD5,611B8AAAAAAAAAAAAAAAA29B4120E4A1,00zzzz92,AAAAAAAAAAAAAAAA

			...
			xxx758,70B3D5326yyyyyyy,70B3D53260yyyyyyy,092EB6A4AAAAAAAAAAAAAAAA8292E791,6yyyyyyy,70D5847AAAAAAAAAAAAAAAAA9DF6E55E,BB82A9AAAAAAAAAAAAAAAA488C0E0D71,00zzzz98,AAAAAAAAAAAAAAAA

Lcs at 14:22, 21 June 2017

2017-06-21T14:22:14Z

← Older revision		Revision as of 14:22, 21 June 2017
Line 62:		Line 62:


	== Get personalization Information		== Get personalization Information ==

	As much as possible identifier should be read from module; Nemeus Product may have also simple and full Qrcode		As much as possible identifier should be read from module; Nemeus Product may have also simple and full Qrcode
Line 73:		Line 73:

	[[File:Qr-ls-example-full.jpg\|300px\|Full Qr code]]		[[File:Qr-ls-example-full.jpg\|300px\|Full Qr code]]

			Information are decoded like this:

			dev_uid=70B3D53260000000&app_key=0123456789ABCDEF0123456789ABCDEF&sfx_id=000FFFFF&sfx_pac=524579AAAA0B47DA

Lcs at 10:45, 16 June 2017

2017-06-16T10:45:32Z

← Older revision		Revision as of 10:45, 16 June 2017
Line 60:		Line 60:
	The activation of Platinium Evaluation Kit (MK002-LS-EU, SIS_LS_EU, ...) can be done directly through SigFox Backend		The activation of Platinium Evaluation Kit (MK002-LS-EU, SIS_LS_EU, ...) can be done directly through SigFox Backend
	https://backend.sigfox.com/activate/Nemeus		https://backend.sigfox.com/activate/Nemeus


			== Get personalization Information

			As much as possible identifier should be read from module; Nemeus Product may have also simple and full Qrcode

			Simple Qr code Contains only Nemeus Identification

			[[File:Qr-ls-example-simple.jpg\|300px\|Simple Qr code]]

			Full Qr code contains information for OTAA activation (defaul APPUID=70B3D53260000100) and Sigfox Activation

			[[File:Qr-ls-example-full.jpg\|300px\|Full Qr code]]

Lcs at 17:45, 15 March 2017

2017-03-15T17:45:10Z

← Older revision		Revision as of 17:45, 15 March 2017
Line 1:		Line 1:
			[[Category:MM002]]
			[[Category:Modules]]

	The module MM002 is pesonalized as follows:		The module MM002 is pesonalized as follows:

	== ABP personalization ==		== LoRaWAN™ ABP personalization ==

	* Device address can be read with AT+MAC=RDEVADDR can be modified with AT+MAC=SDEVADDR,<devaddr> (new value is persistent, it is saved in file system)		* Device address can be read with AT+MAC=RDEVADDR can be modified with AT+MAC=SDEVADDR,<devaddr> (new value is persistent, it is saved in file system)
Line 19:		Line 22:
	OK		OK

	== OTAA personalization ==		== LoRaWAN™ OTAA personalization ==

	* Device EUI can be read with AT+MAC=RDEVUID it is read only		* Device EUI can be read with AT+MAC=RDEVUID it is read only
Line 38:		Line 41:


	== SigFox Personalization ==		== SigFox™ Personalization ==


Line 53:		Line 56:
	Warning: PAC ID given by the command <span style="color: red;">is only valid for First Activation</span>. If the device has already been activated in the past you should get the new PAC which is available from SigFox Backend linked to the previous activation.		Warning: PAC ID given by the command <span style="color: red;">is only valid for First Activation</span>. If the device has already been activated in the past you should get the new PAC which is available from SigFox Backend linked to the previous activation.

	== ~~Sigfox~~ Activation (Platinium Evaluation Kit) ==		== SigFox™ Activation (Platinium Evaluation Kit) ==

	The activation of Platinium Evaluation Kit (MK002-LS-EU, SIS_LS_EU, ...) can be done directly through SigFox Backend		The activation of Platinium Evaluation Kit (MK002-LS-EU, SIS_LS_EU, ...) can be done directly through SigFox Backend
	https://backend.sigfox.com/activate/Nemeus		https://backend.sigfox.com/activate/Nemeus

Lcs: Activation of MM002 devices

2017-03-15T17:31:06Z

Activation of MM002 devices

New page

The module MM002 is pesonalized as follows:

== ABP personalization ==

* Device address can be read with AT+MAC=RDEVADDR can be modified with AT+MAC=SDEVADDR,<devaddr> (new value is persistent, it is saved in file system)
* Network security key can be read with AT+MAC=RNSKEY it is read only
* Application security key can be read with AT+MAC=RAPPSKEY it is read only

Before reading the ABP security keys you must send AT+MAC=ON,,A,0 to switch the module in ABP mode

If you modify the device address you must perform MAC OFF and MAC ON to take into account the new device address (you can also reset the module):

AT+MAC=OFF

OK

AT+MAC=ON,,A,0

OK

== OTAA personalization ==

* Device EUI can be read with AT+MAC=RDEVUID it is read only
* Application key can be read with AT+MAC=RAPPKEY can be modified with AT+MAC=SAPPKEY,<AppKey>
* Application EUI can be read with AT+MAC=RAPPUID can be modified with AT+MAC=SAPPUID,<AppEUI>

If you modify the AppKey and/or the AppEUI you must perform MAC OFF and MAC ON to take into account the new values.

To trigger the join procedure in OTAA mode, you must send AT+MAC=ON,,A,1

Then you can send AT+MAC=? to check that MAC is ON

When the join procedure is finished you will receive the following unsolicited AT response:

+MAC: RDEVADDR,<devAddr>,<NwkId>

You can also poll the module with AT+MAC=RDEVADDR until the device address is not null.

== SigFox Personalization ==

To get SigFox Activation information you can send the following command

AT+SF= ?

+SF: OFF,NMS-SFX-LIB-1.2,UDL1-1.6.0,xxxxxxxx,yyyyyyyyyyyyyyyyyyy,1

The response indicate:
* xxxxxxxx => ID sigfox
* yyyyyyyyyyyyyyyyyyy => PAC ID

Warning: PAC ID given by the command <span style="color: red;">is only valid for First Activation</span>. If the device has already been activated in the past you should get the new PAC which is available from SigFox Backend linked to the previous activation.

== Sigfox Activation (Platinium Evaluation Kit) ==

The activation of Platinium Evaluation Kit (MK002-LS-EU, SIS_LS_EU, ...) can be done directly through SigFox Backend
https://backend.sigfox.com/activate/Nemeus