Device and Gateway Debugging

Hi There,

I have tried to search forum for specific help on this topic, and have not been successful, so please let me know if it can be found elsewhere.

I am new to Chirpstack, and have set up vis Docker-Compose on a Centos 7 VM a server.
I am using a Tektelik Kona Micro gateway and an Agri sensor.
I have been able to connect the gateway, but am getting some errors see below:

time="2020-10-15T08:28:42Z" level=error msg="finished client unary call" ctx_id="<nil>" error="rpc error: code = Unknown desc = lorawan/band: invalid data-rate" grpc.code=Unknown grpc.ctx_id=44a48ad2-b8f0-4e1e-8da3-5195ac171447 grpc.duration=1.188453ms grpc.method=SendProprietaryPayload grpc.service=ns.NetworkServerService span.kind=client system=grpc
time="2020-10-15T08:28:42Z" level=error msg="send gateway ping error: send ping error: send proprietary payload error: rpc error: code = Unknown desc = lorawan/band: invalid data-rate"
time="2020-10-15T08:28:43Z" level=info msg="gateway ping created" ctx_id=d9604ba5-660e-4467-ab1d-2afbf174fb32 dr=5 frequency=902300000 gateway_mac=647fdafffe00864d id=19648
time="2020-10-15T08:28:43Z" level=error msg="finished client unary call" ctx_id="<nil>" error="rpc error: code = Unknown desc = lorawan/band: invalid data-rate" grpc.code=Unknown grpc.ctx_id=706c8587-90e6-42b1-ad37-fb2520eb63d6 grpc.duration="983.84µs" grpc.method=SendProprietaryPayload grpc.service=ns.NetworkServerService span.kind=client system=grpc
time="2020-10-15T08:28:43Z" level=error msg="send gateway ping error: send ping error: send proprietary payload error: rpc error: code = Unknown desc = lorawan/band: invalid data-rate"
time="2020-10-15T08:28:44Z" level=info msg="gateway ping created" ctx_id=dca67645-ddb0-4019-a000-3c8f2564fe97 dr=5 frequency=902300000 gateway_mac=647fdafffe00864d id=19649
time="2020-10-15T08:28:44Z" level=error msg="finished client unary call" ctx_id="<nil>" error="rpc error: code = Unknown desc = lorawan/band: invalid data-rate" grpc.code=Unknown grpc.ctx_id=809e3930-b5e9-43b8-a43d-0b262a0d3b19 grpc.duration=1.197633ms grpc.method=SendProprietaryPayload grpc.service=ns.NetworkServerService span.kind=client system=grpc
time="2020-10-15T08:28:44Z" level=error msg="send gateway ping error: send ping error: send proprietary payload error: rpc error: code = Unknown desc = lorawan/band: invalid data-rate"
time="2020-10-15T08:28:45Z" level=info msg="gateway ping created" ctx_id=3905089a-2c63-4241-bba2-622ec065a82b dr=5 frequency=902300000 gateway_mac=647fdafffe00864d id=19650^C

This gateway and sensor was previously working on another instance, but now I have not been able to get the sensor to reconnect, and the gateway location is also not working any longer.

See Device Downlink Data:

Again, any help in regards to debugging and getting this connected would be greatly appreciated

R

Hi,

my 2 cents…

Double check your channel definitions on your GW and your node… DR5 not valid for 902.3 Mhz.

https://lora-alliance.org/resource-hub/rp2-101-lorawanr-regional-parameters-0

2.5.2 US902-928 Channel Frequencies

• Upstream – 64 channels numbered 0 to 63 utilizing LoRa 125 kHz BW varying from DR0 to DR3, using coding rate 4/5, starting at 902.3 MHz and incrementing linearly by 200 kHz to 914.9 MHz

Regards

Thanks Ric,

So this would be via the gateway config file?

This has not changed since it last worked on a separate instance see below for gateway config:

"chip_enable": true,
        "chan_multiSF_0": {"chan_rx_freq": 902300000, "spread_factor": "7-12" },
        "chan_multiSF_1": {"chan_rx_freq": 902500000, "spread_factor": "7-12" },
        "chan_multiSF_2": {"chan_rx_freq": 902700000, "spread_factor": "7-12" },
        "chan_multiSF_3": {"chan_rx_freq": 902900000, "spread_factor": "7-12" },
        "chan_multiSF_4": {"chan_rx_freq": 903100000, "spread_factor": "7-12" },
        "chan_multiSF_5": {"chan_rx_freq": 903300000, "spread_factor": "7-12" },
        "chan_multiSF_6": {"chan_rx_freq": 903500000, "spread_factor": "7-12" },
        "chan_multiSF_7": {"chan_rx_freq": 903700000, "spread_factor": "7-12" },
        "chan_LoRa_std" : {"chan_rx_freq": 903000000, "bandwidth": 500000, "spread_factor": 8 },
        "chan_FSK"      : {"chan_rx_freq": 903000000, "bandwidth": 250000, "bit_rate": 100000 }

The Network-server.toml looks like:

# This file is for the US915 band. See the examples/ folder for more
# configuration examples.

[postgresql]
dsn="postgres://chirpstack_ns:chirpstack_ns@postgresql/chirpstack_ns?sslmode=disable"

[redis]
url="redis://redis:6379"

[network_server]
net_id="000000"

[network_server.band]
name="US915"

  [network_server.network_settings]
  enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]

[network_server.gateway.backend.mqtt]
server="tcp://mosquitto:1883"

[join_server.default]
server="http://chirpstack-application-server:8003"

[geolocation_server]
server="chirpstack-geolocation-server:8005"

Again, thank you for any guidance or support it is greatly appreciated,

R

  1. on your GW side it looks good.

  2. update your NS.toml file with this:
    enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7, 64]

  3. It looks on the node side… do you have more details

Hi Ric,

Please see attached for details of Device (I have managed to get one Vibe xmitter connected but cannot get any of the agri-sensors connected).

I’m sorry, what do you mean by …cannot get any of the agri-sensors connected…

Can you add more details about these sensors… model, type, provider, etc.

Hi Ric,

They are a Tektelic sensor Agriculture sensor, on the previous instance they worked fine.
(see link to spec sheet: https://tektelic.com/wp-content/uploads/Agriculture-Sensor.pdf)

The vibe which is connected is and Advantec Wise 2410 - which is connected.

Still having some Network Service Errors. Again, I appreciate the help and responsiveness.

-R

error log tells you “Invalid data rate”.
check this in your device configuration/profile sections

Thanks Eugene,

Is there a simple way to know what the data rate should be?

Can you paste your device profile ?

allowed and existed in your regional band.

Hi Ric,

See below for device and service profile. I appreciate the help very much.

R