This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
wiki:loraloc_spf-3.3.1 [2017/07/07 16:25] dqu created |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== iBTS Packet Forwarder v3.3.1 and lower - Instructions ====== | ||
- | |||
- | ===== Configuring the packet forwarder ===== | ||
- | |||
- | * Pick the config.json file from the [[resources:resources_spfv2_v3.3.1|resource page]] that fits with your platform, region and feature need. | ||
- | * Update the JSON configuration file, as explained below. | ||
- | * The way the program takes configuration files into account is the following: | ||
- | - if there is a config.json parse it, look for the next file | ||
- | - if there is a local.json parse it. If some parameters are defined in both config and local configuration files, the local definition overwrites the global config definition. | ||
- | - in our case the local.conf is automatically generated at boot time. It contains antenna configuration. Do not change this file. | ||
- | | ||
- | * In each configuration file, the program looks for a JSON object named: | ||
- | - "SX1301_array_conf" that should contain the parameters for the Lora concentrator board (RF channels definition, modem parameters, etc) | ||
- | - "gateway_conf" that should contain the gateway parameters (gateway MAC address, IP address of the server, keep-alive time, etc). | ||
- | - "gps_conf" | ||
- | |||
- | There are many configuration fields among these files, but most of them are by default correctly filled. The configuration you might want to change are the following: | ||
- | |||
- | \\ | ||
- | ==== Radio Frequencies configurations ==== | ||
- | |||
- | Each LoRaLoc module contains two SX1301. Each SX1301 can be configured to use 10 different frequencies. However, these channels needs to be contained within a 2 Mhz bandwidth. | ||
- | |||
- | * "chip_enable" enable/disable SX1301 | ||
- | * "chip_center_freq" is used to define the center frequency of the SX1301. All 10 channels will be around this particular frequency (+/- 1Mhz). | ||
- | * "chan_rx_freq" are used to define each channel frequencies. | ||
- | * "chip_rf_chain": define the rf chain used by the SX1301. The front-end board integrates two duplicated TX and Rx paths (RF1 path and RF2 path). Each TX/RX path is connected to one SMB antenna port, referenced as RF1 and RF2 (Installation manual 1.5.4.4 Front-end boards). | ||
- | |||
- | <code> | ||
- | "SX1301_conf":[ | ||
- | { | ||
- | "chip_enable": true, | ||
- | "chip_center_freq": 907800000, | ||
- | "chip_rf_chain": 0, | ||
- | "chan_multiSF_0": { "chan_rx_freq": 907100000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_1": { "chan_rx_freq": 907300000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_2": { "chan_rx_freq": 907500000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_3": { "chan_rx_freq": 907700000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_4": { "chan_rx_freq": 907900000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_5": { "chan_rx_freq": 908100000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_6": { "chan_rx_freq": 908300000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_7": { "chan_rx_freq": 908500000 , "spread_factor": "7-10" }, | ||
- | "chan_LoRa_std" : { "chan_rx_freq": 907800000 , "bandwidth": 500000, "spread_factor": 8 }, | ||
- | "chan_FSK" : { "chan_rx_freq": 907800000 , "bandwidth": 125000, "bit_rate": 50000 } | ||
- | },{ | ||
- | "chip_enable": true, | ||
- | "chip_center_freq": 909400000, | ||
- | "chip_rf_chain": 0, | ||
- | "chan_multiSF_0": { "chan_rx_freq": 908700000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_1": { "chan_rx_freq": 908900000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_2": { "chan_rx_freq": 909100000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_3": { "chan_rx_freq": 909300000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_4": { "chan_rx_freq": 909500000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_5": { "chan_rx_freq": 909700000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_6": { "chan_rx_freq": 909900000 , "spread_factor": "7-10" }, | ||
- | "chan_multiSF_7": { "chan_rx_freq": 910100000 , "spread_factor": "7-10" }, | ||
- | "chan_LoRa_std" : { "chan_rx_freq": 909400000 , "bandwidth": 500000, "spread_factor": 8 }, | ||
- | "chan_FSK" : { "chan_rx_freq": 909400000 , "bandwidth": 125000, "bit_rate": 50000 } | ||
- | }], | ||
- | </code> | ||
- | |||
- | \\ | ||
- | ==== Antennas configuration ==== | ||
- | |||
- | To understand all antennas configuration possibilities read the chapter 4.6.2.4 of the Installation manual. | ||
- | |||
- | * “tx_lut”, "rssi_offset", "rssi_offset_coeff_a" and "rssi_offset_coeff_b" fields are used to calibrate the antennas. These values are overwritten by the local.json. No need to change them. | ||
- | * "rx_enable" and "tx_enable" are used to enable or disable emission and reception of the antennas. In case you only have one antenna, disable both these values for one antenna. | ||
- | |||
- | <code> | ||
- | "rf_chain_conf":[ | ||
- | { | ||
- | "rx_enable": true, | ||
- | "tx_enable": true, | ||
- | "rssi_offset": -202.5, | ||
- | "rssi_offset_coeff_a": 20, | ||
- | "rssi_offset_coeff_b": 2925, | ||
- | "tx_lut":[ | ||
- | { "rf_power": 2, "fpga_dig_ ... | ||
- | ... | ||
- | ... }] | ||
- | },{ | ||
- | "rx_enable": true, | ||
- | "tx_enable": true, | ||
- | "rssi_offset": -202.5, | ||
- | "rssi_offset_coeff_a": 20, | ||
- | "rssi_offset_coeff_b": 2925, | ||
- | "tx_lut":[ | ||
- | { "rf_power": ... | ||
- | ... | ||
- | ... }] | ||
- | }], | ||
- | </code> | ||
- | |||
- | \\ | ||
- | ==== Gateway Configuration ==== | ||
- | |||
- | * “server_address” is the address of the server to which the packets will be forwarded | ||
- | * “serv_port_up” and “serv_port_down” are the ports used by the packet forwarder to communicate with the LoRa server | ||
- | * “stat_interval” is the period (in second) at which the statistics of the packet forwarder are logged. | ||
- | * "forward_crc_valid", "forward_crc_error" and "forward_crc_disabled" are Boolean that defines whether invalids packets should be forwarded to the server or not. | ||
- | * "keepalive_interval" is the period (in second) at which the packet forwarder will send a PUSH_DATA frame to the server | ||
- | |||
- | <code> | ||
- | "gateway_conf": { | ||
- | "gateway_ID": "00AEAEFFFE000000", | ||
- | "server_address": "iotbeta.semtech.com", | ||
- | "serv_port_up": 1690, | ||
- | "serv_port_down": 1690, | ||
- | "keepalive_interval": 10, | ||
- | "stat_interval": 30, | ||
- | "push_timeout_ms": 100, | ||
- | "forward_crc_valid": true, | ||
- | "forward_crc_error": false, | ||
- | "forward_crc_disabled": false, | ||
- | "link_mote": "00CC01AF" | ||
- | }, | ||
- | </code> | ||
- | |||
- | |||