Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

The Sigfox protocol is similar to LoRaWAN, and it uses different frequency bands. It uses the infrastructure built by Sigfox and its partners and messages (with a maximum payload size of 12 bytes, and a maximum frequency of 140 messages a per day) are transmitted to the cloud (backend.sigfox.com) from which they can be obtained through the REST API.

The communication was tested between sensors and the Sigfox cloud using curl utility to retrieve data via https.

...

  • Configuration of File/IO line:
    • Input file: name of the directory where data (JSON files) downloaded from the Sigfox cloud will be located. A symbolic constant #APPDIR#, which specifies application directory, may be used, e.g. #APPDIR#/Sigfox_input (valid syntax for Windows and Linux).
    • Archive: name of the directory where data files will be moved after being processed. The KOM process will move the data files after processing to the subdirectories of this directory, which will be named according to respective stations (e.g B.Sigfox_1) and it will adds a time stamp indicating the processing time (e.g. a file msg_21FDA7.txt) may be archived as msg_21FDA7_2018-10-26 -06-26-08.txt).
      Similarly to the input file, a symbolic constant #APPDIR# may be used, e.g. #APPDIR#\/Sigfox_archiv
      Note 1: Invalid files or files for which no station has been identified will be moved to the subdirectory BAD after processing.
      Note 2: If the archive directory is not specified, all files will be deleted after processing.

...

  • Communication protocol "IoT over LoRaWAN/Sigfox".
  • Station address: the address of the station is the identifier of the specific device (mote) that is in the Mote Field Name field.
    • for Connection Type=Kerlink IoT Station SPN address is a text representation of 8 byte LoRaWAN address (e.g. 00-00-00-00-21-1a-e3-c8)
    • for Connection Type=MQTT Client the address may be a text representation of 8 byte LoRaWAN address (e.g. 0018B2000000147D) or a symbolic address defined within MQTT server (e.g. fieldtestdevice)
    • for Connection Type=Sigfox Client (JSON via HTTPS) address is a device identifier (e.g. 21FDA5)

...

ParameterDescriptionUnitDefault Value
Kotva
dt
dt
Device Type
LoRaWAN type Type of device. Each device type may have its own structure of transmitted data (payload). The list of supported devices will gradually increase.
Currently supported devices are:
  • None - no device
  • OEM device - payload parsing is performed by an external dll library
  • Adeunis RF Field Test Device - test device sending GPS position data and temperature data
  • SolidusTech IndoorUNI Sensor - indoor temperature and humidity meter
  • SolidusTech miniUNI DS18B20 Sensor - temperature meter for outdoor use
  • Adeunis RF LoRaWAN TEMP (ARF8180BA) - temperature meter for outdoor use with two independent temperature sensors
  • Codea WZU-SG (Landis+Gyr Ultraheat T550) - radiomodule WZU-SG by Codea for heat meter Landis+Gyr UH50/UC50/T550
-None
Kotva
ed
ed
External Dll Name
Name of external DLL library with code for payload parsing for Device Type=OEM device.- 
Kotva
nd
nd
No Data Timeout
Timeout after which the station goes into communicatoin communication error state if no data has been received.hh:mi:ss01:00:00

Kotva
mt
mt
MQTT Topic (for writing)

Topic used when writing the value (for Connection Type=MQTT client).
Note: for ipesoft-test user and fieldtestdevice device writing was tested towards TheThings.network writing with MQTT_TOPIC=ipesoft-test/devices/fieldtestdevice/down.
- 

Kotva
dc
dc
Sigfox Download Command File

For Sigfox: path to the file for downloading data from the Sigfox cloud to the input directory (specified by parameter Input file of the File I/O line) together with possible parameters. The path may contain (like the Input File parameter) the symbolic constant #APPDIR# (application directory) as well as #ADDR# (station address) so that a single file can be used to handle multiple stations.
Example for Windows: #APPDIR#/Sigfox_cmd/get.bat #ADDR#
Example for Linux: /bin/sh #APPDIR#/Sigfox_cmd/get.sh #ADDR#
Note: this parameter does not have to be entered if an independent mechanism is used to download the data.

The download itself can use the curl utility to perform a HTTPS GET query against the sigfox web server.

Example for Windows platform - file get.bat (download is via proxy server, server identity verification is disabled, xxx:yyy is user name and password for Sigfox cloud):

rem default count=1, possible to download upto 100 values
set count=1
rem ID of device is 1st parameter
set id=%1
c:\utils\curl.exe  --proxy http://proxy:3128 --insecure -u xxx:yyy -o msg_%id%.txt https://backend.sigfox.com/api/devices/%id%/messages?limit=%count%

Example for Linux platform - file get.sh (it is necessary to explicitly specify that files are downloaded e.g. to Sigfox_input directory):

#/bin/sh# default count=1, possible to download upto 100 values
count=1
base=$(dirname "$0")
#ID of device is 1st parameter
id=$1
#name of downloaded data file (including directory)
datafile=$base/../Sigfox_input/msg_$id.txt
/usr/bin/curl --proxy http://proxy:3128 --insecure -u xxx:yyy -o $datafile $datafile https://backend.sigfox.com/api/devices/$id/messages?limit=$count


Note: if command files are edited prior to running KOM process, parameter count can be increased upto 100, resulting in downloading not only the latest value, but also previous (upto 99) historical values. Then, after the first polling, parameter count can be decreased to 1.



Kotva
t
t
Sigfox Download Timeout

For Sigfox: timeout for downloading data via Sigfox Download Command File. If downloading takes longer, station will go to error.sec30

...