SenseCAP M1 Gateway to TTN

Gateways
62

May I ask, can you share or confirm that you repurposed M1 according this guide?
GitHub - seeed-lora/WM1302-doc I still killed 7h during weekend tried to get online GW.

there was theory that TTN is not reachable, but it is

nmap eu1.cloud.thethings.network
Starting Nmap 7.93 ( https://nmap.org ) at 2024-02-18 21:29 EET
Nmap scan report for eu1.cloud.thethings.network (63.34.215.128)
Host is up (0.053s latency).
Other addresses for eu1.cloud.thethings.network (not scanned): 52.212.223.226
rDNS record for 63.34.215.128: ec2-63-34-215-128.eu-west-1.compute.amazonaws.com
Not shown: 997 filtered tcp ports (no-response)
PORT     STATE SERVICE
80/tcp   open  http
443/tcp  open  https
8888/tcp open  sun-answerbook

Nmap done: 1 IP address (1 host up) scanned in 5.00 seconds

somehwre read that no need to open any ports, as all " magic" happens auto in bground.

Thanks!

from rpi terminal → 

##### 2024-02-18 19:20:57 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 0
# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 0 (0 bytes)
# PUSH_DATA datagrams sent: 1 (125 bytes)
# PUSH_DATA acknowledged: 100.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### SX1302 Status ###
# SX1302 counter (INST): 90726994
# SX1302 counter (PPS):  0
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
#--------
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# Invalid time reference (age: 1708284057 sec)
# no valid GPS coordinates available yet
### Concentrator temperature: 27 C ###
##### END #####

JSON up: {"stat":{"time":"2024-02-18 19:20:57 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"temp":26.9}}
INFO: [up] PUSH_ACK received in 51 ms
INFO: [down] PULL_ACK received in 52 ms
INFO: [down] PULL_ACK received in 54 ms
63

Looks perfectly healthy.

I guess TTN does not report it to be online? What is the gateway_ID listed in your configuration json file(s)?

64

Evening… tnx for replay!

I did all from 0 again… this time I made ID as:

“gateway_conf”: {
“gateway_ID”: “gaa-868”,
/* change with default server address/ports */
“server_address”: “eu1.cloud.thethings.network”,
“serv_port_up”: 1700,
“serv_port_down”: 1700,

and I run it with screen in background, as I had theory that I made mistake it by making as sevice, this time ran as “script in bground”

$ screen -ls
There are screens on:
9030.pts-0.m1box (18/02/24 23:52:08) (Attached)
8267.pts-0.m1box (18/02/24 22:03:13) (Detached)
8217.ttn (18/02/24 22:02:56) (Detached)
3 Sockets in /run/screen/S-pi.

my IP ends with XX.XX.3.189 maybe somebody can see it there something coming from it…
Thanks!

65

That should be the gateway EUI. So a hex number of 16 characters, not an alpha-numeric string.

1 Like
66

Looking at your post from ~2 days ago (console view) this one? :-
eui=00016c001ff1e21c

Note when registering in TTN Console GW ID cannot be re-used if gateway deleted, the GW EUI can/should be re-used (Devices often use the term “gateway id” or similar in their documentation/gui set up rather than “gateway eui” or wherever which can lead to confusion. In the Console GW ID is user (lower case) text to be used for convenient though at time of registration it will often suggest an option of the form “eui-aabbccddee…” e.g in this case “eui-00016c001ff1e21c”

1 Like
67

Morgen! shame on me… yes, this fixed issue, I now see it as online on console! Thanks for support, ALL!

1 Like
68

Successfully got my Sensecap M1 to work with TTN, following the instructions above. But: you have to use an older raspy os based on debian 10 buster, not debian 11 bookworm. The reset script will not work, since directly writing to the gpio devices has been disabled. You’d have to use pinctrl instead, however I did not manage to adapt the reset script accordingly.