Unfortunately at the end I went to pick up my gateway to discover they only had the US 915 MHz available. The guy behind the counter suggested me to reflash the firmware to make it work on the 868 MHz band.
(But that advice seems bogus, given the solder pads.)
Starting in February 2019, versions for EU and US are made available while India, Japan, China and Australia will follow in the first half of 2019. There are 4 different versions available - EU868, US915, AS923 and CN470.
Seeings Australia and United States use 915 MHz, Iām assuming they are referring to AS923 for the later release, not AU915.
The delay must mean that there are some hardware changes for AS923. Iāll be interested to see what these differences are.
I use 115200,8,n,1. You can use any terminal program. For example TeraTerm. For the connection to the computer I use a FTDI serial USB converter and you must set it to 3v3.
I will post some extra data captured from the serial port.
For whoever is into some more investigation: the Kickstarter gateway also allows for entering commands using the UART. Of course, the TIG is quite different, and I cannot quickly find any references to something similar in the code, but: maybe!
Potentially yes but then depends on thermal management of the unitā¦issue is more at higher temps, a low temp sensor driving a simple heater (relay switching high wattage resistor over supply line?!) or using self heating if well insulated takes care of lower temp excursions so careful placement e.g. out of direct sunlight etc. likely mitigating the issueā¦ outdoor in water proof housing can mean shorter feeder cables and easier placement (no drilling walls etc!)
At this price (~1/10th pre-built outdoor unit cost) if only 2 or 3 prove worthy out of 6 then still up on the dealā¦and outdoor failures still good for indoor deployment of course!
Just thinking of POE and a weather proof enclosure. Iām not too proud to use a ufl to SMA/N adapter. I can already see that Iām going to have to buy one of those inexpensive network/SWR analyzer tools so that I can make my own collinear antennas.
Maybe TTN always selects the TIG to transmit the Join Accept (which then somehow is not transmitted, or not received by the node), until the node happens to hop to a channel that is not received by the TIG? TTN Console should reveal that in the application/deviceās Data page and the gatewayās Traffic page.
I checked it against my parallel running MatchX gateway:
indeed the EU-TIG seems to receive only 3 channesl 868.1, 868.3 and 868.5, while i see the MatchX receiving data on other channels from same set of nodes.
This explains why i see such a huge packet loss on the TIG
Seems the channel plan inside the gateway is unsuitable for TTN?
Luckily, Iām quite sure the configuration is fetched from the remote CUPS (and if not, then the firmware is checked daily, as noted in āThe LNS connection breaks down every 24 hours and comes back afterwards. Is this normal?ā above).
(But then: it should obviously be able to transmit a Join Accept, even if only listening to those 3 channelsā¦)
Maybe its obvious, but if the three numbers of @humaxnerdās US-gateway are 915 one can distinct the US from the EU version by the number (21) on the sticker.
Thanks for your reply and options. The selection through which gateway the down message will go is standard with the gateway with the best rssi. In this case all other gateways has a rssi from around -100db and the TIG -43db, so it is a logical selection to use the TIG. I have also double checked the selected region and that one is also correct and is already running successful for other gateways.
