Damned, i really would like to know why my TTIG is around 800-900ms late, compared to a MatchX1701 which has GPS PPS and is on time.
They are on same physical network & same subnet using same backhaul?
Perhaps all mine are running consistently 800-900ms late! 
With nothing to show otherwise and reference against I would have no way of knowing!..Its all relative…mind you RX1 & RX2 windows seem to work ok…
If someone at MatchX wants to send me an eval sample of the 1701GW I will happily put it through its paces in one of my test networks and compare to see if I see anything similar! 
Availability on RS NL is 09-07-2019, is there any supplier other than RS to deliver in Europe?
1 Like
Hello!
just received my TTIG.
no connector to the power outlet…
Where to buy one?
Where to have plan du print one?
Keep in mind there are two fully independent possible issues:
-
If the timestamp in the gateway report is accurate to a GPS reference, which is what the example a few posts up appears to be dissecting. Worth checking if all three actually think they are referenced to GPS and not say an IP network time server
-
The latency of the report getting from the gateway to a server. This does depend on IP network backhaul reliability and delays, and is a concern because it can lead to missing downlink windows.
These two concerns are completely independent - you could have a signal report referenced by a wire to a national standards time source reach the server an hour after the receive window closed. Or you could have a lightning fast IP network deliver a packet a few milliseconds from its end on the air, but with an erroneous timestamp from 1970…
Phone Charger 3d printed adapter for the TTIG
1 Like
and what antenna/node/tracker/power did you use ?
Mix of usual standby’s - Semtech/iMST LoRaMotes (Folded F PCB ant’s) and RAK5205 Trackers (PCB Patch ant’s or small RAK rubber ducks 
) or RAK811 break boards. Signal range was topology and clutter limited rather than power/SF. On 2nd day I also set up a SMTC LoRa IOTSTK as reference platform logging locally vs through TTN or Cayenne from 2 of the LoRaMotes so I has some comparison of coverage between TTIG & my ‘reference’ platform. - Results look very similar on 1st pass as not pushing range this close in…still analysing
I think Sod’s Law has struck! Has anyone using this GW seem similar?
I managed to register 1st 4 TTIGs over recent days, quickly and no problems, all seem to be working fine and on soak test or been used for quick deployment tests as above example. Today I have registered the 5th unit and look to have a problem.
After configuring system all seems fine with device seen on WiFi network, connection is strong, IP address secured and supporting internet connection is fine. GW shows solid green LED. Registered device ok on TTN, can see it active in console and is shown as ‘connected’. The console device page shows the ‘Last Seen’ is updating regularly as expected therefore being seen by TTN backend. If I power cycle the device I see same process of flashing LED as it starts up and pings back end then secures local wifi/solid connection…nothing unusual compared to the prior 4…
Looking at traffic page I see no traffic activity 
and stats show no packets received. Device is registered as EU868 and is on ttn-router-eu… router. All the other test TIGS and other GW’s at same location or nearby are seeing the test node traffic and various devices that transmit in the area but for this device zilch!
I can see it listed in the noc.thethings…
I would suspect it is wrong Freq build and not hearing nodes but configured for 868 in console and whilst there is nothing on lable/device to confirm version its was delivered in same batch as the other 4 and also device model looks to be set as TBMH10086800… which looks hopeful wrt build freq!
Have reset and reconfig’d 3 times with same result. Obviously given warning wrt deleting EUI’s on TNN console havent considered that drastic step…
Any suggestions? 
exactly…
nonsense… but that’s my impression 
1 Like
Thanks for posting! 
Printed one this afternoon…another just finished and 3 more in process
EU mains pin/adapter holes no use here in UK but as you can see have alternate plans…just needed a holder as obviously unit cant stand up when powered given bottom cable entry;-)
e.g.: wall or wooden frame mounting etc.
BTW given relatively poor internal antenna would recommend NOT winding excess cable around unit when in operation as may further mask/perturb signal but rather let it hang free
1 Like
Just checked on RS UK site and looks like next availability isn’t until mid June! so unless they have a spares stock to cover defective units it looks like RMA’ing the troublesome unit might be a futile exercise in short term…may just sacrifice it to test potential physical changes and experiments inc re-housing, adding alternate external ant etc…
Pity availability so poor as would likely order another 5/6 (10?) to have communities & potential clients test and play with…
Yes, thanks - had been trawling the earlier thread messages looking for possible solutions this evening and saw this also - might try to hack in coming days A lot has happened in last couple of months and so I forgot seeing the pin out references and the R86 resistor hack to enable logging on the CP2102N port…
1 Like
Looking at yesterday data, I found a point collected at 2.6km, with no particular effort on gw placement. Not bad. As soon as I become used to it, I will open and put a better antenna and then move under the roof.
is there any supplier other than RS to deliver in Europe? or any plans for other suppliers?
Any ETA on AS923 and AU915 support?
some strange tripletts, shown by TTIG
1 Like