This file contains the configuration of the gateway (except the fleet configuration).
When this file is uploaded, the station parses it and replaces the configuration of the gateway with the one described in the file. If the syntax or one field of the file is not correct, then the entire file is ignored.
It is not necessary to use every fields in the file at once.

The following example shows a fully functioning file that only configure the received data backup parameters.

XXXXXX_data.json

{
  "body": {
    "public": {
      "csvlo": {
        "rotation_time": "hour",
        "rotation_count": 50
      }
    }
  }
}                         

The configuration file can be downloaded/uploaded thanks to:

• The web interface.
• The USB service.
• The Local FTP service.
• The HTTP REST API service.

• db_max_entries: integer. Not managed in v1.1.1. Do not use this field.

• enable: boolean. Local FTP activation.

• rotation_time: string “hour” or “day” or “week” or “month”. Rotation time of CSV rx data files.
• rotation_count: integer from 1 to 100. Maximum number of files saved.

• enable: boolean. Remote HTTP activation.
• secure: boolean. False: http / True: https.
• host: string. Hostname or IP address.
• port: integer. Port used.
• path: string. Path (must start and end with “/”).

• enable: boolean. Remote FTP activation.
• user: string. User.
• password: string. Password.
• host: string. Hostname or IP address.
• port: integer. Port used.
• path: string. Path (must start and end with “/”).

From SPN firmware 2.0.3

• “enable”: boolean. SMS interface activation.

• enable: boolean. Spectral scan activation. Not managed in v1.1.1. Do not use this field.
• freq_min: integer. Frequency min in Hz. Not managed in v1.1.1. Do not use this field.
• freq_max: integer. Frequency max in Hz. Not managed in v1.1.1. Do not use this field.

• region: integer.
  • 0: none
  • 1: Europe
  • 2: America
  • 3: Australia
  • 4: Asia
  • 5: Korea

• nwk_id: integer from 0 to 127. LoRa Network ID.

The RX frequencies configuration is explained here.

• enable: boolean. Radio 0 frontend activation (in blue on the picture).
• freq: integer. Central radio 0 frequency in Hz.

• enable: boolean. Radio 1 frontend activation (in blue on the picture).
• freq: integer. Central radio 1 frequency in Hz.

• enable: boolean. Multi SF channel X activation (in yellow on the picture).
• radio: integer 0 or 1. Identifier of the radio frontend used.
• if: integer from -400000 to 400000. Relative frequency in Hz. The relative frequency is the difference between the channel central frequency and the radio central frequency.

Example:

"radio_0": {
  "enable": true,   // Radio 0 is enabled
  "freq": 868500000 // Radio 0 central frequency is 868500000
  },
 
"chan_multisf_0": {
  "enable": true,   // Channel 0 is enabled
  "radio": 0,       // Channel 0 works with radio 0
  "if": -400000     // Channel 0 desired channel frequency is 868100000
                    // Channel 0 relative frequency = desired channel frequency - radio 0 central frequency
                    // Channel 0 relative frequency = 868100000 - 868500000 
                    // Channel 0 relative frequency = -400000
},

• enable: boolean. Mono SF channel activation.
• radio: integer 0 or 1. Identifier of the radio frontend used.
• if: integer from -400000 to 400000. Relative frequency in Hz.
• bandwidth: integer 125000 or 250000 or 500000. Channel bandwidth.
• spread_factor: integer from 7 to 12. Channel spreading factor.

• enable: boolean. FSK channel activation. Not managed in v1.1.1. Do not use this field.
• radio: integer 0 or 1. Identifier of the radio frontend used. Not managed in v1.1.1. Do not use this field.
• if: integer from -400000 to 400000. Relative frequency in Hz. Not managed in v1.1.1. Do not use this field.
• bandwidth: integer. Channel bandwidth. Not managed in v1.1.1. Do not use this field.
• datarate: integer. Channel data rate. Not managed in v1.1.1. Do not use this field.

• tx_power: integer from 5 to 29. TX power in dBm (EIRP).
• antenna_gain: integer from 0 to 20. Antenna gain (in dBi)

From SPN firmware 2.0.3

• “enable”: boolean. Packets forwarding activation.
• “host”: String. IPv4 address, name, or URL. Address of the gateway that will receive the packets.

• type: string “dhcp”, “static” or “off”. LAN type.
• address: string. IPv4 address if static selected.
• netmask: string. IPv4 netmask if static selected.
• gateway: string. IPv4 gateway if static selected.

• network_name: string. Wi-Fi network name.
• passphrase: string. Wi-Fi passphrase.
• type: string “dhcp”, “static” or “off”. LAN type.
• address: string. IPv4 address if static selected
• netmask: string. IPv4 netmask if static selected.
• gateway: string. IPv4 gateway if static selected.

• enable: boolean. GSM activation.
• operator
  • mcc: string. Operator MCC (Mobile Country Code).
  • mnc: string. Operator MNC (Mobile Network Code).
• pin_code: string. PIN code.
• apn: string. Operator APN (Access Point Name).
• user: string. User.
• password: string. Password.

• enable: boolean. OpenVPN activation.

• timezone: string. Timezone
• ntp: string.
  • polling: string. NTP polling period.
  • address_1: string. Address 1.
  • address_2: string. Address 2.

• password: string. Login password.

Depending on the version of the firmware, the template to use changes. Templates can be downloaded from the resources page. Make sure to use the template that suits your gateway.