New gateway from Laird: Sentrius RG1XX


(Adolfo Brandao) #105

Hello @brocaar, @kersing and everybody else,

I’ve managed to get the rxPacketsReceivedOK to be greater then 0 and most of the times equal to the rxPacketsReceived. I believe the gateway is now receiving correct messages from the end node, which can be seen below:

mosquitto_sub -t “#” -d
Client mosqsub|13908-iotrix-pi sending CONNECT
Client mosqsub|13908-iotrix-pi received CONNACK
Client mosqsub|13908-iotrix-pi sending SUBSCRIBE (Mid: 1, Topic: #, QoS: 0)
Client mosqsub|13908-iotrix-pi received SUBACK
Subscribed (mid: 1): 0
Client mosqsub|13908-iotrix-pi received PUBLISH (d0, q0, r0, m0, ‘gateway/c0ee40ffff2938c6/stats’, … (163 bytes))
{“mac”:“c0ee40ffff2938c6”,“time”:“2017-12-19T13:03:20Z”,“rxPacketsReceived”:4,“rxPacketsReceivedOK”:4,“txPacketsReceived”:0,“txPacketsEmitted”:0,“customData”:null}
Client mosqsub|13908-iotrix-pi received PUBLISH (d0, q0, r0, m0, ‘gateway/c0ee40ffff2938c6/stats’, … (163 bytes))
{“mac”:“c0ee40ffff2938c6”,“time”:“2017-12-19T13:03:50Z”,“rxPacketsReceived”:6,“rxPacketsReceivedOK”:6,“txPacketsReceived”:0,“txPacketsEmitted”:0,“customData”:null}
Client mosqsub|13908-iotrix-pi sending PINGREQ
Client mosqsub|13908-iotrix-pi received PINGRESP

The problem is I am not seeing any messages from the “gateway/mac/rx” topic, which can be seen above and below:

mosquitto_sub -t “gateway/c0ee40ffff2938c6/rx” -d
Client mosqsub|13590-iotrix-pi sending CONNECT
Client mosqsub|13590-iotrix-pi received CONNACK
Client mosqsub|13590-iotrix-pi sending SUBSCRIBE (Mid: 1, Topic: gateway/c0ee40ffff2938c6/rx, QoS: 0)
Client mosqsub|13590-iotrix-pi received SUBACK
Subscribed (mid: 1): 0
Client mosqsub|13590-iotrix-pi sending PINGREQ
Client mosqsub|13590-iotrix-pi received PINGRESP
Client mosqsub|13590-iotrix-pi sending PINGREQ
Client mosqsub|13590-iotrix-pi received PINGRESP

I can aso see these messages on the gateway log:

RG1xx2938C6 php-cgi user.info Dec 19 13:38:00 lrd-sdk: LRD_WF_GetSSID():2976 returned SDCERR_FAIL
RG1xx2938C6 php-cgi user.info Dec 19 13:37:55 lrd-sdk: LRD_WF_GetSSID():2976 returned SDCERR_FAIL
RG1xx2938C6 php-cgi user.info Dec 19 13:37:50 lrd-sdk: LRD_WF_GetSSID():2976 returned SDCERR_FAIL
RG1xx2938C6 lora user.notice Dec 19 02:12:34 src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty
RG1xx2938C6 lora user.notice Dec 19 02:12:34 ### [JIT] ###
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # BEACON rejected: 0
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # BEACON sent so far: 0
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # BEACON queued: 0
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # TX errors: 0
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # RF packets sent to concentrator: 0 (0 bytes)
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # PULL_RESP(onse) datagrams received: 0 (0 bytes)
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # PULL_DATA sent: 3 (100.00% acknowledged)
RG1xx2938C6 lora user.notice Dec 19 02:12:34 ### [DOWNSTREAM] ###
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # PUSH_DATA acknowledged: 100.00%
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # PUSH_DATA datagrams sent: 1 (113 bytes)
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # RF packets forwarded: 0 (0 bytes)
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
RG1xx2938C6 lora user.notice Dec 19 02:12:34 # RF packets received by concentrator: 1
RG1xx2938C6 lora user.notice Dec 19 02:12:34 ### [UPSTREAM] ###
RG1xx2938C6 lora user.notice Dec 19 02:12:34 ##### 2017-12-19 13:36:20 GMT #####
RG1xx2938C6 lora user.notice Dec 19 02:12:34 INFO: [up] PUSH_ACK received in 1 ms
**RG1xx2938C6 lora user.notice Dec 19 02:12:34 JSON up: {“rxpk”:[{“tmst”:2339877916,“chan”:7,“rfch”:1,“freq”:914.800000,“stat”:-1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:-12.2,“rssi”:-108,“size”:65,“data”:“rzMQTaO90wK4nm2NtbW4TKvFHF6zfz2jCUc8i0jR9cuF9Ldj6uws5IDPVmhveme2JXrie+D2CslxPqKMp/nSZ6A=”}]} **
RG1xx2938C6 lora user.notice Dec 19 02:12:34 INFO: [down] PULL_ACK received in 1 ms
RG1xx2938C6 lora user.notice Dec 19 02:12:34 INFO: Enabling GPS mode for concentrator’s counter.
RG1xx2938C6 lora user.notice Dec 19 02:12:34 INFO: host/sx1301 time offset=(1513688210s:274970µs) - drift=-35µs
RG1xx2938C6 lora user.notice Dec 19 02:12:34 INFO: Disabling GPS mode for concentrator’s counter…
RG1xx2938C6 lora user.notice Dec 19 02:12:34 INFO: [up] PUSH_ACK received in 3 ms
RG1xx2938C6 lora user.notice Dec 19 02:12:34 JSON up: {“rxpk”:[{“tmst”:2331543619,“chan”:0,“rfch”:0,“freq”:914.000000,“stat”:-1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/6”,“lsnr”:-12.8,“rssi”:-71,“size”:110,“data”:“YtMqaOzbwKxQh5UO1nueV9V9CZfJFP7oLQ1wLToiT7g1JzVlc06myjk0BBZW/xcGcxACvKm+5EcBkvuEVUZ6azYuIe3CeckBCuP/ZVWCJvfmo3Q6yGgFaK70Xfz+huRuzat2ioKrR5O935yNVSU=”}]}

This is my gateway’s dashboard:

Do you have any idea why I am not getting messages from the “gateway/mac/rx” topic?

Thanks in advance!


#106
 {“rxpk”:[{“tmst”:2331543619,“chan”:0,“rfch”:0,“freq”:914.000000,“stat”:-1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/6”,“lsnr”:-12.8,“rssi”:-71,“size”:110,“data”:“YtMqaOzbwKxQh5UO1nueV9V9CZfJFP7oLQ1wLToiT7g1JzVlc06myjk0BBZW/xcGcxACvKm+5EcBkvuEVUZ6azYuIe3CeckBCuP/ZVWCJvfmo3Q6yGgFaK70Xfz+huRuzat2ioKrR5O935yNVSU=”}]}

See "stat": -1, this indicates that the CRC of the frame is invalid. I suspect your gateway in configured to ignore these frames.


(Adolfo Brandao) #107

This is my config:

And another piece of the gateway log:

|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# BEACON queued: 0|
|—|---|—|---|—|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# TX errors: 0|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# RF packets sent to concentrator: 0 (0 bytes)|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# PULL_RESP(onse) datagrams received: 0 (0 bytes)|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# PULL_DATA sent: 3 (100.00% acknowledged)|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |### [DOWNSTREAM] ###|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# PUSH_DATA acknowledged: 100.00%|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# PUSH_DATA datagrams sent: 1 (113 bytes)|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# RF packets forwarded: 0 (0 bytes)|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%|
|RG1xx2938C6 |lora |user.notice |Dec 19 13:54:40 |# RF packets received by concentrator: 9|

What config you think I should use?

Thank you very much!


(Adolfo Brandao) #108

Hello @brocaar,

Just wanted to let you know that I received a message on the “…/rx” topic:

Client mosqsub|17406-iotrix-pi received PUBLISH (d0, q0, r0, m0, ‘gateway/c0ee40ffff2938c6/rx’, … (333 bytes))
{“rxInfo”:{“mac”:“c0ee40ffff2938c6”,“time”:“0001-01-01T00:00:00Z”,“timestamp”:43965292,“frequency”:914400000,“channel”:5,“rfChain”:1,“crcStatus”:1,“codeRate”:“4/5”,“rssi”:-5,“loRaSNR”:9,“size”:24,“dataRate”:{“modulation”:“LORA”,“spreadFactor”:7,“bandwidth”:125},“board”:0,“antenna”:0},“phyPayload”:"//8AAEhlbGxvIFdvcmxkICM1MDU2ACAA"}

Using this configuration:

Thank you very much!


#109

new version announced - IP67


(Carlberg) #110

Hi @jmarcelino,

Please share how you where able to get the root password so I can enable SSH.


#111

I received the manual with the details. Please let me know if anyone needs it.


(Joao P Taveira) #112

I do :slight_smile:


#113

It’a publicly available I just noticed ! Happy reading.


(Espyjpny) #114

Hi All,

I am having issue with update RG1XX gateway. Current version is “Laird Linux gatwick-laird-93.7.1.13” and I would like to update to “Laird Linux gatwick-laird-93.7.2.9” as It supported MQTT and loraserver. The URL i used is as shown in manual. Below is error log. It seem some issue with wget. Any suggestion will be much appreciated. Thanks.

Downloading ‘fw.txt’ from www.lairdtech.com to /tmp/fw.txt
Processing firmware-update-list *
Checking Bootstrap - update n/a
Checking Bootloader - update n/a
Checking Linux Kernel - overwriting
Updating kernel-b
(1s) erasing/writing_^OK
Checking Root Filesystem
Updating rootfs-b (ubi)
(10s) erasing/writing_______ …image download/flash interrupted
WARNING: cannot verify www.lairdtech.com’s certificate, issued by ‘CN=COMODO RSA Domain Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB’:
Self-signed certificate encountered.


(Espyjpny) #115

The URL i used is “https://www.lairdtech.com/products/rg1xx-lora-gateway/firmware/latest/fw.txt


(Espyjpny) #116

After a few tries, I am able to update it. Thanks all.


(Derchris) #117

noob question but I’m looking for a start: will the Sentrius be able to do Multicast? I understand that this might be (software-side) in responsibility of the LoRa server implementation, but I just want to make sure


(Nikosp) #118

Hello everyone. As i can see, Sentrius RG1XX looks functional using it with TTN.
If anyone knows, may i have any compatibility problem alongside with IMST iM880B as end-node device?

Thanks in advance,
Nikos.


(Goran Mahovlic) #119

It should work as any other gateway…


(Luis-I3led) #120

Hi,everyone!

I have the Gateway Sentrius RG1XX, North American version

I just updated the driver to its most current version from the control panel of the Gateway.
The installation finished successfully, then I reboot the device.
After this the gateway does not work, the lights blink and go off, in blucle.
The reset button does nothing and I can not access the Gateway control panel.

I would like to know if there is a way, no matter how complicated it is to solve the problem.

I would appreciate your help it very much.


#121

Hey,

Can you contact Laird support, https://www.lairdtech.com/support
They will be able to help you with this.

Thanks!


(Jeff Uk) #125

I use several Laird and as @Borroz says they perform well and I find them very stable and quick to set-up/configure - just rehoused one for outdoor use in N.West UK and 1st day tests showed immediate coverage out to >9.75km (probably much more but that was as far as I drove!). Several deployments are indoors and like you I use roof space for cover/deployment. You have to be careful going that route and once you have eliminated bad sensor end node as issue per suggestion then check that antenna isnt near metallic objects (if close to roof they can contain metal stud work or even have foil backed sheeting) as this can de-tune Ant. Also if foil or similar insulation used this can severely limit signal reception (LoRa is v good but…) also if sheet plastic or any form of water proof/breathable membrane used check for RF transparency as have seen many instances where the material has high metal/carbon/contaminant content which again screens. One suggestion on forums if take sample and place in microwave - if it heats up independently of other content in oven then may not be good - ok uWave @2.4Ghz but gives indication. Even a UV/K-Glass/IR reflective roof lite/window can filter by >10db as they are usually metal (silver?) oxide coated. As you say height, fresh air and outdoor ant always best cure for poor indoor reception. Can you keep GW indoors for shelter & back-haul connection but then run a short 1-5m feed cable (ultra low loss not just low loss) to external Ant mount?

One last tip, though mounting high in roof seems logical because of the materials issues mentioned above I’ve sometimes found that mounting low down/at floor level in the roof space with ant low or even hanging out of roof eves and falling below can give very much improved signal as you are then clear of such filters/attenuators though your building will itself then cause possibly asymmetric reach.


(Jeff Uk) #131

ok :sunny:


(Jeff Uk) #132

Quick check on range using a Laird RG186 re-housed in Outdoor/IP rated case and mounted on 7+m mast Warrington WA4 area planned to cover Warrington South & Central :slight_smile:
image