can you try changing the TIG position from horizontal to vertical (probably need some sticky tape )
Any idea about reach in km’s / miles? Tested in real life?
@humaxnerd or anyone having attached the UART: care to post some longer logs? (If only to see it indeed looks like the Basic Station logs, which would then probably use some Station to Packet Forwarder Protocol Bridge on TTN’s V2, which could also be the culprit of not getting all OTAA Join Accepts?)
Am I right to assume that TTN selected the TIG for the Join Accept downlink for the failures? Which gateway is selected upon success? And is it then always using the same SF on success? (Like: LMIC starts with SF7, likely to get the Join Accept in RX1, and increasing the SF after some failures; some other libraries simply always use SF12, often getting the Join Accept in RX2.)
Assuming all nodes nicely perform channel hopping: any details on differences in SF? And like @UdLoRa asked: what’s the differences in RSSI/SNR for the different nodes? (See also the details in TTN Console when clicking an item in the application/device’s Data page, or the gateway’s Traffic page.)
Well, given the shortage of EU868 devices, but not of US915, I’m quite sure that those won’t have to make any modification at all.
Would you be able to clarify what you mean about the shortage? Did they hand out the US/AU915 version at the conference as well?
My main reason for asking about the mod was because I thought only the EU868 version was given out, therefore the mod would have to be done.
It’ll be interesting to see what the difference is between the two boards. If it was as simple as soldering the resistor in another spot, I don’t see why the US/AU915 is going to be released later in the year rather than now.
Just curious, how did you get this output? I understand what the pinouts are, but would you be able to explain these few things:
How did you read this data?
How did you connect the board via the pinouts to the computer? Was it an adapter of some type?
What software did you use?
Did you have to know which baud rate to use and if so, how’d you figure this out?
Would really appreciate it if you could answer those questions. At the moment, I’m not sure how you pulled it off.
Yes. Also to people who wanted EU868. On Slack:
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.)
Just like with the The Things Gateway: https://www.thethingsnetwork.org/docs/gateways/gateway/faq.html#q-i-want-to-get-in-depth-insightread-debug-messages-of-my-gateway-is-that-possible
Or: Raspberry Pi to monitor serial output of a node or TNN Gateway, and alert on Slack or Telegram if the voltages match, but it seems they do:
@ElectronicallyE, At the conference they said RS Online will start selling from next week. This may only be from their UK and US websites.
@TonySmith, this is for the US and EU.
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.
Updated the image with pinouts, in order to document your finding:
@humaxnerd which Baudrate did you use? is it the same (115200@8N) as in https://www.thethingsnetwork.org/docs/gateways/gateway/faq.html#q-i-want-to-get-in-depth-insightread-debug-messages-of-my-gateway-is-that-possible ?
Although I really want to get a UART connection running to this thing I’m lacking time today, thus I cannot provide the logfiles requested by @arjanvanb in $69 Gemtek Gateway: The Things Indoor Gateway
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!
…but earlier you wrote the following; wouldn’t that make it unsuitable for outdoor use? (At least in Europe.)
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.
That might also explain the following?
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.
Are you sure that your nodes send on more than 3 channels?
I can confirm that for my gateway.
They are already in Europe. Compliancy checks are now on the critical path
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…)