Thanks for the help. I see a variety of messages relating to LMIC-node in the TTI console.
I have ordered a Dragino ( LT-22222-L LoRa I/O Controller) which I will use for development. This looks pretty perfect for my sensor experiments needs (as a ‘cuckoo canary’!)
regards,
pjjH
Details
I have at least one issue remaining which looks like Link ADR rejection received - #2 by Hulkco
If you are not seeing anything in the device console, I’d suspect this byte swap as being the issue.
That was the issue. I was aware from the comments in the lorawan-keys.h file about 2 or the 3 inputs being lsb but I had not noticed the byte order toggle and I incorrectly assumed that the TTI UI was emitting the array-initializer in the form usable by LMIC. This was an eyesight error on my behalf (I have a strong preference for text-based interfaces. see below) and I now realize I had an expectation that TTI console would complain to me about Dev and App EUIs that were unknown.
From the LMIC-node documentation:
Registration is not further described here
I think I may submit a PR for this! I note that the end-device key data is retrievable via JSON from the command-line (here is for the end-device; I assume the app key can be retrieved similarly). I would rather codegen the file from this rather than go through n clicks on the TTU web UI. Similarly, it is a bit of a pain to copy paste stuff from the device definition repository via the web UI. It would be nice to have a script which probed the MCU and looked up its characteristics in the repo and added the device via the API (either command-line or HTTP)
C:\packages\ttn>.\ttn-lw-cli.exe end-devices list --application-id tgrid-lmic-test
[{
"ids": {
"device_id": "eui-70b3d57ed80004f2",
"application_ids": {
"application_id": "tgrid-lmic-test"
},
"dev_eui": "70B3D57ED80004F2",
"join_eui": "5A2E9402C5D4C87A"
},
"created_at": "2022-01-01T22:32:27.796Z",
"updated_at": "2022-01-02T15:41:05.100Z"
}]
Please find attached a snippet of the log from startup
LMIC-node
Device-id: wifi-lora-32-v2
LMIC library: MCCI
Activation: OTAA
Interval: 60 seconds
000000029681: Event: EV_JOINING
000000031742: Event: EV_TXSTART
000000033857: doWork job started
000000374814: Event: EV_JOINED
Network Id: 19
Device Address: 26092A4E
Application Session Key: 21-1A-6D-FD-F1-1A-A8-DC-FD-7C-50-23-48-2C-C2-BE
Network Session Key: A8-4E-0B-C0-04-67-6E-44-E7-1E-49-93-82-E6-3C-64
000000377732: doWork job started
000000381059: Input data collected
COUNTER value: 1
000000381944: Packet queued
000000384171: Event: EV_TXSTART
000000725377: Event: EV_TXCOMPLETE
Up: 1, Down: 1
Downlink received
000001469086: Event: EV_TXCOMPLETE
Up: 3, Down: 3
Downlink received
RSSI: -61 dBm, SNR: 9.0 dB
Port: 0
000001499731: Event: EV_TXSTART
000001840963: Event: EV_TXCOMPLETE
Up: 4, Down: 4
Downlink received
RSSI: -63 dBm, SNR: 8.7 dB
Port: 0
000001871608: Event: EV_TXSTART
000002212842: Event: EV_TXCOMPLETE
Up: 5, Down: 5
Downlink received
RSSI: -60 dBm, SNR: 9.0 dB
Port: 0