Chirpstack application server - error:"status:TX_FREQ " on gateway - ERROR: Packet REJECTED, unsupported frequency - 0 (min:863000000,max:870000000)

Hi! I have problem with downlink with device C class (ABP). My command is
mosquitto_pub -t ‘application/1/device/313135385e377e18/tx’ -m ‘{“confirmed”: true, “fPort”: 1, “data”: “aGk=”}’
Here screen from gateway

My global_conf.json on gateway
{
“SX1301_conf”: {
“lorawan_public”: true,
“clksrc”: 1, /* radio_1 provides clock to concentrator /
“antenna_gain”: 0, /
antenna gain, in dBi /
“radio_0”: {
“enable”: true,
“type”: “SX1257”,
“freq”: 864500000,
“rssi_offset”: -166.0,
“tx_enable”: true,
“tx_freq_min”: 863000000,
“tx_freq_max”: 870000000
},
“radio_1”: {
“enable”: true,
“type”: “SX1257”,
“freq”: 869000000,
“rssi_offset”: -166.0,
“tx_enable”: false
},
“chan_multiSF_0”: {
/
Lora MAC channel, 125kHz, all SF, 864.1 MHz /
“enable”: true,
“radio”: 0,
“if”: -400000
},
“chan_multiSF_1”: {
/
Lora MAC channel, 125kHz, all SF, 864.3 MHz /
“enable”: true,
“radio”: 0,
“if”: -200000
},
“chan_multiSF_2”: {
/
Lora MAC channel, 125kHz, all SF, 864.5 MHz /
“enable”: true,
“radio”: 0,
“if”: 0
},
“chan_multiSF_3”: {
/
Lora MAC channel, 125kHz, all SF, 864.7 MHz /
“enable”: true,
“radio”: 0,
“if”: 200000
},
“chan_multiSF_4”: {
/
Lora MAC channel, 125kHz, all SF, 864.9 MHz /
“enable”: true,
“radio”: 0,
“if”: 400000
},
“chan_multiSF_5”: {
/
Lora MAC channel, 125kHz, all SF, 869.1 MHz /
“enable”: true,
“radio”: 1,
“if”: 100000
},
“chan_multiSF_6”: {
/
Lora MAC channel, 125kHz, all SF, 868.9 MHz /
“enable”: true,
“radio”: 1,
“if”: -100000
},
“chan_multiSF_7”: {
/
Lora MAC channel, 125kHz, all SF, 867.9 MHz /
“enable”: false,
“radio”: 1,
“if”: 0
},
“chan_Lora_std”: {
/
Lora MAC channel, 250kHz, SF7, 868.3 MHz /
“enable”: false,
“radio”: 1,
“if”: -200000,
“bandwidth”: 250000,
“spread_factor”: 7
},
“chan_FSK”: {
/
FSK 50kbps channel, 868.8 MHz /
“enable”: false,
“radio”: 1,
“if”: 300000,
“bandwidth”: 125000,
“datarate”: 50000
},
“tx_lut_0”: {
/
TX gain table, index 0 /
“pa_gain”: 0,
“mix_gain”: 8,
“rf_power”: -6,
“dig_gain”: 0
},
“tx_lut_1”: {
/
TX gain table, index 1 /
“pa_gain”: 0,
“mix_gain”: 10,
“rf_power”: -3,
“dig_gain”: 0
},
“tx_lut_2”: {
/
TX gain table, index 2 /
“pa_gain”: 0,
“mix_gain”: 12,
“rf_power”: 0,
“dig_gain”: 0
},
“tx_lut_3”: {
/
TX gain table, index 3 /
“pa_gain”: 1,
“mix_gain”: 8,
“rf_power”: 3,
“dig_gain”: 0
},
“tx_lut_4”: {
/
TX gain table, index 4 /
“pa_gain”: 1,
“mix_gain”: 10,
“rf_power”: 6,
“dig_gain”: 0
},
“tx_lut_5”: {
/
TX gain table, index 5 /
“pa_gain”: 1,
“mix_gain”: 12,
“rf_power”: 10,
“dig_gain”: 0
},
“tx_lut_6”: {
/
TX gain table, index 6 /
“pa_gain”: 1,
“mix_gain”: 13,
“rf_power”: 11,
“dig_gain”: 0
},
“tx_lut_7”: {
/
TX gain table, index 7 /
“pa_gain”: 2,
“mix_gain”: 9,
“rf_power”: 12,
“dig_gain”: 0
},
“tx_lut_8”: {
/
TX gain table, index 8 /
“pa_gain”: 1,
“mix_gain”: 15,
“rf_power”: 13,
“dig_gain”: 0
},
“tx_lut_9”: {
/
TX gain table, index 9 /
“pa_gain”: 2,
“mix_gain”: 10,
“rf_power”: 14,
“dig_gain”: 0
},
“tx_lut_10”: {
/
TX gain table, index 10 /
“pa_gain”: 2,
“mix_gain”: 11,
“rf_power”: 16,
“dig_gain”: 0
},
“tx_lut_11”: {
/
TX gain table, index 11 */
“pa_gain”: 3,
“mix_gain”: 9,
“rf_power”: 20,
“dig_gain”: 0
}
},

"gateway_conf": {
    "gateway_ID": "00006cc3743f0870",
    /* change with default server address/ports, or overwrite in local_conf.json */
    "server_address": "192.168.1.220",
    "serv_port_up": 1700,
    "serv_port_down": 1700,
    /* adjust the following parameters for your network */
    "keepalive_interval": 10,
    "stat_interval": 30,
    "push_timeout_ms": 100,
    "autoquit_threshold": 10,
    /* forward only valid packets */
    "forward_crc_valid": true,
    "forward_crc_error": false,
    "forward_crc_disabled": false,
    /* GPS configuration */
    "gps_tty_path": "/dev/ttyO1",
    "ubx_timegps_control_enable": true,
    /* GPS reference coordinates */
    "ref_latitude": 0.0,
    "ref_longitude": 0.0,
    "ref_altitude": 0
}

}
my chirpstack-networr-server.toml
log_level=4
log_to_syslog=true
[postgresql]
dsn=“postgres://chirpstack_ns:dbpassword@localhost/chirpstack_ns?sslmode=disable”
[redis]
url=“redis://localhost:6379”
[network_server]
net_id=“010203”
[network_server.band]
name=“RU_864_870”
[network_server.network_settings]

[[network_server.network_settings.extra_channels]]

frequency=864100000
min_dr=0
max_dr=5

[[network_server.network_settings.extra_channels]]
frequency=864300000
min_dr=0
max_dr=5

[[network_server.network_settings.extra_channels]]
frequency=864500000
min_dr=0
max_dr=5

[[network_server.network_settings.extra_channels]]
frequency=864700000
min_dr=0
max_dr=5

[[network_server.network_settings.extra_channels]]
frequency=864900000
min_dr=0
max_dr=5

[network_server.api]

ip:port to bind the api server

bind=“0.0.0.0:8000”

[network_server.gateway.backend]

Backend

type=“mqtt”
[network_server.gateway.backend.mqtt]
event_topic=“gateway/+/event/+”
command_topic_template=“gateway/{{ .GatewayID }}/command/{{ .CommandType }}”
server=“tcp://localhost:1883”
username=""
password=""
[metrics]
timezone=“Local”
[join_server]
[join_server.default]
server=“http://localhost:8003

my chirpstack-gateway-server.toml
[general]
log_level=4
log_to_syslog=true

[backend]
type=“semtech_udp”

Semtech UDP packet-forwarder backend.

[backend.semtech_udp]

udp_bind = “0.0.0.0:1700”

[backend.basic_station]
region=“RU864”
frequency_min=863000000
frequency_max=870000000
[integration]
marshaler=“protobuf”
[integration.mqtt]
event_topic_template=“gateway/{{ .GatewayID }}/event/{{ .EventType }}”
command_topic_template=“gateway/{{ .GatewayID }}/command/#”

[integration.mqtt.auth]
type=“generic”
[integration.mqtt.auth.generic]
server=“tcp://127.0.0.1:1883”
username=""
password=""

Here my parameters on web interface

After making modifications to the device-profile, did you re-activate your device? As soon as you activate a device, the parameters are copied from the device-profile. If you change the device-profile at a later point, then the device is not updated (as using mac-commands, the state of the device might already have changed).

You’re right, after re - activation it’s working, thanks!

1 Like