Centiloc Service Documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Configuration Token

In case the Board cannot connect anywhere (Wi-Fi connection issue, Platform Host misconfigured…), the Board will enter recovery mode.

In this mode, you can force new configuration to the Board. They will be applied after a hard reboot.

Configuration Token stands for a NFC tag that contains specific content, allowing configuring a Board in recovery mode.

  • A Centiloc Board with version v4.7.1 or later
  • NFC Tag you can write in
  • Tool to write NDEF data in the NFC Tag
    • NFC Tools can be downloaded on any smartphone from application store
The NFC tag used as Configuration Token must be scanned by the Board. It must then match the NFC Type configuration of the Board.
Only Board v4.7.1 and v5 support these tokens. v6 boards use configuration mode.

1. NFC Tag preparation

We first show how to use NFC Tools to program a Configuration Token.

1.1. NFC Tools for writing

Open NFC Tools, and press Write (or Ecrire) button.

1.2. Add Records

Click on Add Record (or Ajouer un enregistrement) button. Select the Text (or Texte) format, to finally enter some information.

Repeat the Add Record operation for every field required by the Configuration Token.

1
2
3
4

1.3. Write to the Tag

Once you have entered all the fields of your Configuration Token, you can press Write (or Ecrire) into the NFC tag.

You will need to approach your NFC tag close to the smartphone antenna and wait for the operation status.

5
6
7

1.4. Troubleshooting

Usually, if you cannot write into the NFC tag, this is because there is a format protection, or even the tag is not prepared for the operation.

You can go back to the Home menu, press Other (or Autre), then use either or both:

  • Tag Erase (or Effacer un tag)
  • Memory Format (or Formater la mémoire)
This will erase the NFC tag memory. This requires approval on the NFC Tool, that you can agree or not.
8
9

2. Configuration Fields

Keep the order of the record!

Pay attention on case sensitivity, the : separation!

Moreover, all the caracters of the fields are taken and analyzed, including spaces or carriage returns

2.1. WiFi Network

See example above

Record number Key Value expected
1 Centiloc:WiFi:Credentials none
2 ssid: WiFi network SSID
3 pwd: Password for this network

For instance, you must have the field below:

  1. Centiloc:WiFi:Credentials
  2. ssid:CentiWifi
  3. pwd:Default01

2.2. MQTT Host

Record number Key Value expected
1 Centiloc:MQTT:Credentials none
2 host: MQTT broker address
3 port: MQTT broker port
4 transport: Transport layer indication (see below)
5 user: User for MQTT authentication
6 pwd: Password for MQTT authentication

2.2.1. Transport Layer

This values depends on firmware version:

The value of this field must be a number:

  • 1: for plain TCP
  • 2: for TLS
  • 3: for Trusted TLS (no server certificate verification)

The value can be:

  • tcp: for plain TCP
  • ssl: for TLS connection (with certification verification)

2.2.2. Example

  1. Centiloc:MQTT:Credentials
  2. host:192.168.1.5 or host:mqtt.centiloc.com
  3. port:8883
  4. transport:3 for TLS without certification verification
  5. user:johndoe
  6. pwd:ChangeMe123*

2.3. Serial Enrolment

Record number Key Value expected
1 Centiloc:RS485:Setup none