Things UNO will not join TTN (US frequency plan)

ruk · February 1, 2018, 9:26pm

My Things Gateway and Things Uno arrived today here in Canada, the “backer” editor. I’d selected “Let us decide based on your address” for the frequency plan when I ordered.

On the packing slip attached to the box there’s a handwritten “TTGW868X1” and “TTU868X1” which makes me wonder whether I received the devices for the wrong frequency plan; additionally, I was sent only a UK and EU plug adapter, so needed to use my own adapter.

However, I proceeded with the setup of the Gateway and this was problem free, and it’s showing as “connected” on the Things Network console with the “United States 915MHz” frequency plan I selected on activation.

Setting up the Things Uno, however, I’ve run into a problem.

When I first plugged in the Uno, the default sketch ran, and I saw traffic in the Traffic tab of the Things Network console every minute. The “frequency” column for this traffic was 868.

I identified the Device EUI of my Uno as outlined, and then created a TTN Application and copied and pasted the appEui and appKey into the QuickStart sketch.

I set the freqPlan to TTN_FP_US915.

When I upload the sketch, however, the join fails, and the serial monitor output is as follows:

-- STATUS
EUI: 0004A30B001BFE78
Battery: 3263
AppEUI: 70B3D57ED0009C47
DevEUI: 0004A30B001BFE78
Data Rate: 7
RX Delay 1: 1000
RX Delay 2: 2000
-- JOIN
Model: RN2483
Version: 1.0.1
Sending: mac set deveui 0004A30B001BFE78
Sending: mac set adr off
Sending: mac set deveui 0004A30B001BFE78
Sending: mac set appeui 70B3D57ED0009C47
Sending: mac set appkey A089BD843E502DBE3B35D37A91082891
Sending: mac save 
Sending: mac set ch status 0 off
Sending: mac set ch status 1 off
Sending: mac set ch status 2 off
Sending: mac set ch status 3 off
Response is not OK: invalid_param
Sending: mac set ch status 4 off
Response is not OK: invalid_param
Sending: mac set ch status 5 off
Response is not OK: invalid_param
Sending: mac set ch status 6 off
Response is not OK: invalid_param
Sending: mac set ch status 7 off
Response is not OK: invalid_param
Sending: mac set ch status 8 on
Response is not OK: invalid_param
Sending: mac set ch drrange 8 0 3
Sending: mac set ch status 9 on
Response is not OK: invalid_param
Sending: mac set ch drrange 9 0 3
Sending: mac set ch status 10 on
Response is not OK: invalid_param
Sending: mac set ch drrange 10 0 3
Sending: mac set ch status 11 on
Response is not OK: invalid_param
Sending: mac set ch drrange 11 0 3
Sending: mac set ch status 12 on
Response is not OK: invalid_param
Sending: mac set ch drrange 12 0 3
Sending: mac set ch status 13 on
Response is not OK: invalid_param
Sending: mac set ch drrange 13 0 3
Sending: mac set ch status 14 on
Response is not OK: invalid_param
Sending: mac set ch drrange 14 0 3
Sending: mac set ch status 15 on
Response is not OK: invalid_param
Sending: mac set ch drrange 15 0 3
Sending: mac set ch status 16 off
Response is not OK: invalid_param
Sending: mac set ch status 17 off
Response is not OK: invalid_param
Sending: mac set ch status 18 off
Response is not OK: invalid_param
Sending: mac set ch status 19 off
Response is not OK: invalid_param
Sending: mac set ch status 20 off
Response is not OK: invalid_param
Sending: mac set ch status 21 off
Response is not OK: invalid_param
Sending: mac set ch status 22 off
Response is not OK: invalid_param
Sending: mac set ch status 23 off
Response is not OK: invalid_param
Sending: mac set ch status 24 off
Response is not OK: invalid_param
Sending: mac set ch status 25 off
Response is not OK: invalid_param
Sending: mac set ch status 26 off
Response is not OK: invalid_param
Sending: mac set ch status 27 off
Response is not OK: invalid_param
Sending: mac set ch status 28 off
Response is not OK: invalid_param
Sending: mac set ch status 29 off
Response is not OK: invalid_param
Sending: mac set ch status 30 off
Response is not OK: invalid_param
Sending: mac set ch status 31 off
Response is not OK: invalid_param
Sending: mac set ch status 32 off
Response is not OK: invalid_param
Sending: mac set ch status 33 off
Response is not OK: invalid_param
Sending: mac set ch status 34 off
Response is not OK: invalid_param
Sending: mac set ch status 35 off
Response is not OK: invalid_param
Sending: mac set ch status 36 off
Response is not OK: invalid_param
Sending: mac set ch status 37 off
Response is not OK: invalid_param
Sending: mac set ch status 38 off
Response is not OK: invalid_param
Sending: mac set ch status 39 off
Response is not OK: invalid_param
Sending: mac set ch status 40 off
Response is not OK: invalid_param
Sending: mac set ch status 41 off
Response is not OK: invalid_param
Sending: mac set ch status 42 off
Response is not OK: invalid_param
Sending: mac set ch status 43 off
Response is not OK: invalid_param
Sending: mac set ch status 44 off
Response is not OK: invalid_param
Sending: mac set ch status 45 off
Response is not OK: invalid_param
Sending: mac set ch status 46 off
Response is not OK: invalid_param
Sending: mac set ch status 47 off
Response is not OK: invalid_param
Sending: mac set ch status 48 off
Response is not OK: invalid_param
Sending: mac set ch status 49 off
Response is not OK: invalid_param
Sending: mac set ch status 50 off
Response is not OK: invalid_param
Sending: mac set ch status 51 off
Response is not OK: invalid_param
Sending: mac set ch status 52 off
Response is not OK: invalid_param
Sending: mac set ch status 53 off
Response is not OK: invalid_param
Sending: mac set ch status 54 off
Response is not OK: invalid_param
Sending: mac set ch status 55 off
Response is not OK: invalid_param
Sending: mac set ch status 56 off
Response is not OK: invalid_param
Sending: mac set ch status 57 off
Response is not OK: invalid_param
Sending: mac set ch status 58 off
Response is not OK: invalid_param
Sending: mac set ch status 59 off
Response is not OK: invalid_param
Sending: mac set ch status 60 off
Response is not OK: invalid_param
Sending: mac set ch status 61 off
Response is not OK: invalid_param
Sending: mac set ch status 62 off
Response is not OK: invalid_param
Sending: mac set ch status 63 off
Response is not OK: invalid_param
Sending: mac set ch status 64 off
Response is not OK: invalid_param
Sending: mac set ch status 65 on
Response is not OK: invalid_param
Sending: mac set ch status 66 off
Response is not OK: invalid_param
Sending: mac set ch status 67 off
Response is not OK: invalid_param
Sending: mac set ch status 68 off
Response is not OK: invalid_param
Sending: mac set ch status 69 off
Response is not OK: invalid_param
Sending: mac set ch status 70 off
Response is not OK: invalid_param
Sending: mac set ch status 71 off
Response is not OK: invalid_param
Sending: mac set pwridx 5
Sending: mac set retx 7
Sending: mac set dr 3
Response is not OK: invalid_param
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed

The MicroChop on my Uno is labeled RN2483.

Is it possible that I’ve got an Uno designed for the EU frequency plan paired with a Gateway that’s set for the USA frequency plan?

BoRRoZ · February 1, 2018, 11:39pm

Hi, I’m afraid you’re right … RN2483 = EU, you should have received one with an RN2903 radio module

arjanvanb · February 2, 2018, 6:18am

If the node is EU, then:

…would be weird, unless the gateway’s hardware is also EU hardware, and the selected frequency plan is somehow ignored (or errors while loading a wrong frequency plan do not stop the gateway from starting to listen on its default frequencies).

So: both your node and gateway seem to be using EU frequencies and hardware.

You can easily remove the gateway’s white cover. What does the LoRa module state for its type? I think LG8271 would be EU. Or maybe even easier: what does http://things-gateway.local/info show for “Gateway card”?

(As an aside: nodes do not pair with a gateway. They just transmit and hope one or more gateways receive their packet and forward it to TTN.)

ruk · April 2, 2018, 6:59pm

It turns out that I was shipping an EU Gateway and an EU Uno; they’ve now been replaced with US versions of both, and all is well.