Code Monkey home page Code Monkey logo

gateway-conf's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

gateway-conf's Issues

"serv_port_down"

Shouldn't the "serv_port_down" set to 1700, same as "serv_port_up"?
With the current 1701, the pull data sent keep 0% acknowledged, while 1700 make this reach 100%.

Provide template like config for use with poly forwarder

For those running the poly forwarder it would be nice to have the information in a format that allows easy automatic merging with existing configuration on embedded Linux systems (basic *nix tools like sed/awk, no json parsers)

lbt_cfg prevents some gateways from operating

For AS2, Japan requires LBT. But Taiwan does not.

Currently, the as2 config includes LBT overrides. This means that gateways in Taiwan without LBT support in hardware can't use the as2 config, even though they're otherwise fine.

Please consider further splitting for AS2 with and without LBT.

(I also note that AS1 always enforces LBT, and I'm not sure that this is needed in every country.)

Add KR-global_conf.json

Proposed configuration:

{
"SX1301_conf": {
	"lorawan_public": true,
	"clksrc": 1,
	"clksrc_desc": "radio_1 provides clock to concentrator",
	"radio_0": {
		"enable": true,
		"type": "SX1257",
		"freq": 904200000,
		"rssi_offset": -166.0,
		"tx_enable": true
	},
	"radio_1": {
		"enable": true,
		"type": "SX1257",
		"freq": 905000000,
		"rssi_offset": -166.0,
		"tx_enable": false
	},
	"chan_multiSF_0": {
		"desc": "Lora MAC, 125kHz, all SF, 922.1 MHz",
		"enable": true,
		"radio": 0,
		"if": -300000
	},
	"chan_multiSF_1": {
		"desc": "Lora MAC, 125kHz, all SF, 922.3 MHz",
		"enable": true,
		"radio": 0,
		"if": -100000
	},
	"chan_multiSF_2": {
		"desc": "Lora MAC, 125kHz, all SF, 922.5 MHz",
		"enable": true,
		"radio": 0,
		"if": 100000
	},
	"chan_multiSF_3": {
		"desc": "Lora MAC, 125kHz, all SF, 922.7 MHz",
		"enable": true,
		"radio": 0,
		"if": 300000
	},
	"chan_multiSF_4": {
		"desc": "Lora MAC, 125kHz, all SF, 922.9 MHz",
		"enable": true,
		"radio": 1,
		"if": -300000
	},
	"chan_multiSF_5": {
		"desc": "Lora MAC, 125kHz, all SF, 923.1 MHz",
		"enable": true,
		"radio": 1,
		"if": -100000
	},
	"chan_multiSF_6": {
		"desc": "Lora MAC, 125kHz, all SF, 923.3 MHz",
		"enable": true,
		"radio": 1,
		"if": 100000
	},
	"chan_multiSF_7": {
		"desc": "Lora MAC, 125kHz, all SF, 905.3 MHz",
		"enable": false,
		"radio": 1,
		"if": 300000
	},
	"chan_Lora_std": {
		"desc": "Lora MAC, 500kHz, SF8, 904.6 MHz",
		"enable": false,
		"radio": 0,
		"if": 400000,
		"bandwidth": 500000,
		"spread_factor": 8
	},
	"chan_FSK": {
		"desc": "FSK disabled",
		"enable": false
	},
	 {
		"desc": "TX gain table, index 0",
		"pa_gain": 0,
		"mix_gain": 8,
		"rf_power": -6,
		"dig_gain": 0
	},
	"tx_lut_1": {
		"desc": "TX gain table, index 1",
		"pa_gain": 0,
		"mix_gain": 10,
		"rf_power": -3,
		"dig_gain": 0
	},
	"tx_lut_2": {
		"desc": "TX gain table, index 2",
		"pa_gain": 0,
		"mix_gain": 12,
		"rf_power": 0,
		"dig_gain": 0
	},
	"tx_lut_3": {
		"desc": "TX gain table, index 3",
		"pa_gain": 1,
		"mix_gain": 8,
		"rf_power": 3,
		"dig_gain": 0
	},
	"tx_lut_4": {
		"desc": "TX gain table, index 4",
		"pa_gain": 1,
		"mix_gain": 10,
		"rf_power": 6,
		"dig_gain": 0
	},
	"tx_lut_5": {
		"desc": "TX gain table, index 5",
		"pa_gain": 1,
		"mix_gain": 12,
		"rf_power": 10,
		"dig_gain": 0
	},
	"tx_lut_6": {
		"desc": "TX gain table, index 6",
		"pa_gain": 1,
		"mix_gain": 13,
		"rf_power": 11,
		"dig_gain": 0
	},
	"tx_lut_7": {
		"desc": "TX gain table, index 7",
		"pa_gain": 2,
		"mix_gain": 9,
		"rf_power": 12,
		"dig_gain": 0
	},
	"tx_lut_8": {
		"desc": "TX gain table, index 8",
		"pa_gain": 1,
		"mix_gain": 15,
		"rf_power": 13,
		"dig_gain": 0
	},
	"tx_lut_9": {
		"desc": "TX gain table, index 9",
		"pa_gain": 2,
		"mix_gain": 10,
		"rf_power": 14,
		"dig_gain": 0
	},
	"tx_lut_10": {
		"desc": "TX gain table, index 10",
		"pa_gain": 2,
		"mix_gain": 11,
		"rf_power": 16,
		"dig_gain": 0
	},
	"tx_lut_11": {
		"desc": "TX gain table, index 11",
		"pa_gain": 3,
		"mix_gain": 9,
		"rf_power": 20,
		"dig_gain": 0
	},
	"tx_lut_12": {
		"desc": "TX gain table, index 12",
		"pa_gain": 3,
		"mix_gain": 10,
		"rf_power": 23,
		"dig_gain": 0
	},
	"tx_lut_13": {
		"desc": "TX gain table, index 13",
		"pa_gain": 3,
		"mix_gain": 11,
		"rf_power": 25,
		"dig_gain": 0
	},
	"tx_lut_14": {
		"desc": "TX gain table, index 14",
		"pa_gain": 3,
		"mix_gain": 12,
		"rf_power": 26,
		"dig_gain": 0
	},
	"tx_lut_15": {
		"desc": "TX gain table, index 15",
		"pa_gain": 3,
		"mix_gain": 14,
		"rf_power": 27,
		"dig_gain": 0
	}
},
"gateway_conf": {
	"server_address": "router.us.thethings.network",
	"serv_port_up": 1700,
	"serv_port_down": 1700,
	"servers": [ {
		"server_address": "router.us.thethings.network",
		"serv_port_up": 1700,
		"serv_port_down": 1700,
		"serv_enabled": true
	} ]
  }
}

See

India bandplan doesn't work on Conduit for ul ch#0/1

Testing in India by TTN Chennai/MCCI revealed that the Conduit was not fully functional:

  1. uplink on ch#2 and downlink during the second RX slot worked
  2. uplink on ch#0 and ch#1 didn't work.

Investigation and experimentation led us to believe that the intermediate frequency offsets for channel 0 and 1 were too large (> 400kHz). We contacted Multi-Tech who provided their band plan for India. We swapped their channel 2 and 3 (so that we have 0/1/2 as per the LoRaWAN regional spec) and disabled channels above channel 2. (It would be nice to have the join accept enable these channels; but that's probably a change request; this is just a problem fix).

Will submit a pull request momentarily with the file that works for us.

CN470-510 configuration

In China, there are two bands specified: CN470-510 and CN779-787. The TX power of the latter is limited to 10 dBm, which is too low.

Therefore, we are planning a CN470-510 configuration. Most channels are reserved for China Electric, so we need to select a frequency sub band (FSB) of the channels:

  • 80-87
  • 88-95

We are calling for contributions on defining the channels and testing.

Add a mapping from country to correct frequency plan.

In the console and ttnctl, we currently give people the option to select the frequency plan they want to use.

We do not have a way to check wether or not the frequency plan used is consistent with the location of the gateway.

For this, we'd need to have a mapping between countries and their correct/preferred frequency plan.

Sanity check the Radio freq and channel IFs for all conf files

It has happened a few times that there were configuration issues due to incorrect config files. We need to double check the radio0 and radio1 frequencies, as well as the IF offsets applied to them. According to the sx1257 the radio only has a 800kHz bandwidth, meaning we should use IF offsets of less than +-400. The channel's width should also be taken into account, and the channel, plus it's width should fit inside the sx1257's bandwidth.

KR-global_conf.json

Hi,
in your KR-global_conf.json file, there is IF value 600000 and -600000.
it seems IF value is limited by semtech lora gateway HAL.

how can i fix this value while following KR's channel plan?

Document frequency-plans.yml and v3 indexing

In the v3 frequency plans format, frequency-plans.yml is used as an index for all frequency plans. It would be useful to document that:

  • Document how this translates in a user interface (e.g. WebUI)
  • Document how links frequency plan ID <-> frequency plan content works
  • Document how frequency plans extensions work

"Invalid configuration Std Channel" on AU915-928

I'm trying to run Semtech Packet Forwarder using the AU-global_conf.json file provided (without any changes).
When I start the Packet Forwarder service, all of the multi-SF channels seems to be configured without problems, except for the LoRa Standard Channel, whose the following error appears:

`INFO: Lora std channel> radio 0, IF 400000 Hz, 500000 Hz bw, SF 8

ERROR: invalid configuration for Lora standard channel`

I switched to US-global_conf.json, just for testing purposes, and the PF starts without problems, but using AU-global_conf.json, I can't make it work because the PF initialization breaks after this error.

Am I doing something wrong?

EU433 configuration

There is no configuration file for a gateway with SX1255 transceivers using 433MHz channels. Can anybody provide me a working configuration file? Thanks.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.