Dragino LPS8 Disconnected

TTN Network and Services The Things Stack v3
1

Hello, I would like to add my Dragino LPS8 Gateway to the new system V3.
I have the latest software on the gateway.
In LoRaWAN I have then selected The Things Network V3 and the correct server eu1…
The gateway was also removed from the old system.
Unfortunately, the new console says Disconnected.
I entered the Gateway Id as the eui and made one up as the ID.
I hope you can help me.

Many greetings Tom!

Here is the log:

    on Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]:
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ################## Report at: 2021-04-19 18:18:06 UTC ##################
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ### [UPSTREAM] ###
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # RF packets received by concentrator: 0
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # RF packets forwarded: 0 (0 bytes)
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PUSH_DATA datagrams sent: 0 (0 bytes)
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PUSH_DATA acknowledged: 0.00%
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ### [DOWNSTREAM] ###
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PULL_DATA sent: 1 (100.00% acknowledged)
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # RF packets sent to concentrator: 0 (0 bytes)
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # TX errors: 0
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # BEACON queued: 0
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # BEACON sent so far: 0
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # BEACON rejected: 0
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ### [PPS] ###
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # SX1301 time (PPS): 1022882956
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: INFO: [jit] queue is empty
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: INFO~ ### [GPS] ###
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: INFO~ # GPS sync is disabled
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: INFO~ ##### END #####
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: RXTX~ {"stat":{"time":"2021-04-19 18:18:06 UTC","rxnb":0,"rxok":0,"rxfw":0,"ackr":0.0,"dwnb":0,"txnb":0}}
    Mon Apr 19 18:18:06 2021 daemon.info lora_pkt_fwd[1928]: INFO~ [up] PUSH_ACK received in 34 ms
    Mon Apr 19 18:18:07 2021 daemon.info lora_pkt_fwd[1928]: INFO~ [down] PULL_ACK received in 32 ms
    Mon Apr 19 18:18:09 2021 user.notice iot_keep_alive: Internet Access OK: via eth1
    Mon Apr 19 18:18:09 2021 user.notice iot_keep_alive: use WAN or WiFi for internet access now
    Mon Apr 19 18:18:24 2021 user.notice iot_keep_alive: Internet Access OK: via eth1
    Mon Apr 19 18:18:24 2021 user.notice iot_keep_alive: use WAN or WiFi for internet access now
    Mon Apr 19 18:18:31 2021 daemon.err uhttpd[1228]: killall: logread: no process killed
    Mon Apr 19 18:18:32 2021 daemon.info lora_pkt_fwd[1928]: PKT_FWD~ DATA_CONF_DOWN<- {"DevAddr": "10C23573", "FCtrl": ["ADR": 1, "RFU": "RFU", "ACK": 1, "FPending" : 0, "FOptsLen": 11], "FCnt": 46916, "FPort": 3, "MIC": "3BD6F540"}
    Mon Apr 19 18:18:33 2021 daemon.err uhttpd[1228]: wc: /tmp/logfile.log: No such file or directory
    Mon Apr 19 18:18:33 2021 daemon.err uhttpd[1228]: sh: 2000000: unknown operand
    Mon Apr 19 18:18:33 2021 daemon.err uhttpd[1228]: killall: logread: no process killed
    Mon Apr 19 18:18:33 2021 daemon.err uhttpd[1228]: killall: logread: no process killed
    Mon Apr 19 18:18:34 2021 daemon.err uhttpd[1228]: sh: write error: Broken pipe
    Mon Apr 19 18:18:34 2021 daemon.err uhttpd[1228]: sh: write error: Broken pipe
    Mon Apr 19 18:18:34 2021 daemon.err uhttpd[1228]: sh: write error: Broken pipe
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]:
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ################## Report at: 2021-04-19 18:18:36 UTC ##################
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ### [UPSTREAM] ###
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # RF packets received by concentrator: 1
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # RF packets forwarded: 0 (0 bytes)
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PUSH_DATA datagrams sent: 0 (0 bytes)
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PUSH_DATA acknowledged: 0.00%
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ### [DOWNSTREAM] ###
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PULL_DATA sent: 1 (100.00% acknowledged)
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # RF packets sent to concentrator: 0 (0 bytes)
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # TX errors: 0
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # BEACON queued: 0
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # BEACON sent so far: 0
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # BEACON rejected: 0
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ ### [PPS] ###
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: REPORT~ # SX1301 time (PPS): 1082883378
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: INFO: [jit] queue is empty
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: INFO~ ### [GPS] ###
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: INFO~ # GPS sync is disabled
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: INFO~ ##### END #####
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: RXTX~ {"stat":{"time":"2021-04-19 18:18:36 UTC","rxnb":1,"rxok":0,"rxfw":0,"ackr":0.0,"dwnb":0,"txnb":0}}
    Mon Apr 19 18:18:36 2021 daemon.info lora_pkt_fwd[1928]: INFO~ [up] PUSH_ACK received in 35 ms
    Mon Apr 19 18:18:37 2021 daemon.info lora_pkt_fwd[1928]: INFO~ [down] PULL_ACK received in 32 ms
    Mon Apr 19 18:18:40 2021 user.notice iot_keep_alive: Internet Access OK: via eth1
    Mon Apr 19 18:18:40 2021 user.notice iot_keep_alive: use WAN or WiFi for internet access now
2

Not sure what you actually did from this description but:

Gateway ID is a unique identifier that you get to make up so you can tell at a glance which gateway is being referred to in the logs - with some obvious ones blocked, like “my-gateway”

Gateway EUI is the unique identifier internal to the gateway - this HAS to exactly match.

3

Hi,

My gateway ID is made up of the WiFi MAC address and the number 4150. Example:
Mac Address: 11:22:33:44:55:66
GW ID: 1122334455664150

It doesn’t work for me either. :frowning: I notified the manufacturer, but they haven’t spoken back yet. I’d be happy if it worked because I bought it recently but haven’t been able to install it yet. :frowning:

4

The gateway ID is NOT the gateway EUI - you can enter anything you like to help you track your gateway in to the ID.

The gateway EUI HAS to be the EUI from the gateway web console. I’m not sure where you got the idea of using the WiFi MAC address and putting 4150 at the end.

Have you checked the manual?

Which version of TTN are you using?

What firmware version do you have on your gateway?

1 Like
5

Yes, I know the GW ID is not the same as the GW EUI. By default, this value is given by the device (GW ID). I don’t know where to read the GW EUI because it’s not listed anywhere. I would use v3 from TTN. It has the latest firmware: lgw-5.4.1618196981

1 Like
6

If you know the difference, what’s the mention of the WiFi MAC as an ID about?

7

I think this is how you can guarantee the unique ID.In principle, it can be anything, just don’t collide with another. I know well?

8

The manual shows you how to setup and it doesn’t use the WiFi MAC, it shows you where to look for the EUI that you can then enter in to the TTN gateway console.

9

It really is included in the manual. Unfortunately, I did not receive such a code for the device.

10

I read the description again. It does not write an EUI at Gateway. For end device only. I still wonder what the solution to the problem is.

11

Dragino hold an MA-L EUI block (at a cost of $3,085) starting A8-40-41 so it seems odd they would have stopped using it.

I can’t access my Dragino gateways where I am right now so I can’t look at the console.

12

The Gateway-ID is the MAC-adress you find on the backside of the LPS8 + “4150”.
The Gateway-EUI can be found in the V3 console and not in the lorawan-menu of the LPS8. It has “ffff” in the middle of the WiFi-MAC.

13

Yes, this MAC address is the same as the WiFi MAC address. To this is added the number 4150, as you wrote. However, I do not find the EUI. Can you send me a link to this where there is a description?

14

I am sorry but I can’t remember where I found it. If I look at the Gateway-EUI of my LPS8 in the TTN V3-console this EUI is build exactly this way.

15

On a laptop now so can see the PDF - pages 15 & 16 of the linked manual says it all. It would appear that Dragino has unfortunately referred to the EUI on their console as ID but it clearly shows an EUI starting with A8 40 41 being copied over and entered in to the TTN v2 gateway web console in to the Gateway EUI field.

Nomenclature is important, but you can’t assume everyone knows all the right words, particularly if the product’s manual isn’t in the native speakers language.

16

If I understand correctly, the formula is as follows (Dragino LPS8):

WiFi MAC address + 4150 = GW EUI

Exapmle:
MAC: 11:22:33:44:55:66
EUI: 11:22:33:44:55:66:41:50

17

For my Dragino gateways it looks like this:

TTN V2 11:22:33:44:55:66:41:50
TTN V3 11:22:33:FF:FF:44:55:66

18

Hello???

Dragino EUI’s start A8-40-41 as displayed on the gateways web console.

ANYTHING ELSE IS NOT A VALID EUI

Why make one up when Dragino have spent thousands of dollars ensuring you have a legitimate one?

19

I tested with these, but none work:

TTN V3 11:22:33:44:55:66:FF:FF
TTN V3 11:22:33:FF:FF:44:55:66
TTN V3 11:22:33:44:55:66:41:50

20

I did not write the real MAC address directly. Yes, it starts with the MAC address you typed (A8-40-41).