Migrating TTN kickstarter GW to V3

Gateways TTKG - The Things Kickstarter Gateway
1

Hi
I have attempted to migrate a TTN kickstarter GW to V3.
I also have an end node device ( based upon RN2903 ) that has been migrated to V3 .
I also have a Multitec Conduit gateway still set up for V2.

For testing all are in same room.

the TTN kickstarter GW appears as connected in V3 console.
The end node is registered and set up in V3 console

If multitech gateway is turned off. I do not see any packets or requests from the end node
in the V3 console while looking at gateway traffic or application ( device ) traffic.
Below is a snapshot of the uart serial connection from the TTN kickstarter gateway during a sessions with transmissions from the end node.

If i turn on the Multitech gateway still operating as V2, the traffic/packets from the end node show up in the V3 application console for the device.

NOTE! the frequency band is the same on gateways and end device.
All within close range so signal level is not the problem.
It appears from the uart listing below, that the TTN gateway did get the lora transmission and did attempt to send it to V3 stack.

i am not sure what the packet rejected indications are coming from ?
or what LGMD:Rejected packet (0x11) indicates.

here is the uart snapshot …

MQTT: Sending status packet
MQTT: Sending status succeeded: 102
LGMD:LORA: Accepted packet

LGMD:LORA: Accepted packet

MQTT: Sending UPLINK OK
MQTT: Sending UPLINK OK
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 103
LGMD:Rejected packet (0x11)

MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 104
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
LGMD:LORA: Accepted packet

MQTT: Sending UPLINK OK
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 105
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 106
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
LORA: Kick LoRa module with ACK after not acked it for 60s
LGMD:LORA: Accepted packet

MQTT: Sending UPLINK OK
LGMD:Rejected packet (0x11)

MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 107
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3765
MON: APP Stack size: 3292
MON: LoRa Stack size: 3869
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 108

Can anyone point me in the proper direction to locate the issue ?

thanks

Ken

2

If they are close together, the signal-level is a problem. The signal is to strong like someone shouting at your ears - you can hear it but you don’t understand it.
There should be a few meters or a wall between the node and the gateway.

3

Hi Thanks for the comment.
I understand the issue, and the end device is more than a few meters away from gateway and i have reduced end device TX power to an acceptable level, and Multitech gateway is closer and having no issues at all, and before migrating to V3 on the kickstarter gateway, there was no issues communicating between GW and end device at these locations.
So i think the current issue is something else.
Ken

4

@johan @htdvisser this is yet another user with issues migrating their Kickstarter gateway, any pointers to help get them operational?

5

Hi
in case it makes a difference. I am located in US, using RN2903 module.
The V2 Gateway ( Multitech) is going thru the ttn-router-us-west router and the TTKG gateway is using the nam1.cloud.thethings.network gateway server.

As described before … RN2903 end device shows up properly in the V3 console with V3 App when going thru the V2 Multitech gateway, but nothing shows up at all thru TTKG gateway even though the V3 Gateway console shows that the gateway is connected.

also the device had also been removed from the previous V2 applications.

any suggestions on debugging this further would be welcome.
Ken

6

Hi
After re-reading docs and deleting the V3 gateway entry ( actually a number of times ) and using a new Gateway ID each time, when adding the kickstarter gateway back in and checking, and double checking the ID and keys and everything else associated with this process. I finally have my kickstarter GW migrated to V3 and my end device communicating to the V3 console thru both gateways.
I still am not sure exactly what setting was causing the problem. ( GW ID or API key or something else ) but all seems to be fine now. The symptom of having the gateway say it was connected on the gateway console yet not passing any packets to the application console probably was the key to understanding the issue, but i did not understand the system and setup well enough to help me.
so just brute force, delete and start all over again and again was all i was able to do.
I do not look forward to migrating the other gateway, but that is a project for another day.
Regards Ken

1 Like