It seems like TTOG used up 500MB of mobile data in a matter of days:
Description
Session Start
Session End
Usage
Afrihost APN Usage 2019-05-26
2019-05-26 00:00:00
2019-05-26 23:59:59
385.52KB
Afrihost APN Usage 2019-05-27
2019-05-27 00:00:00
2019-05-27 23:59:59
33.24MB
Afrihost APN Usage 2019-05-28
2019-05-28 00:00:00
2019-05-28 23:59:59
38.02MB
Afrihost APN Usage 2019-05-29
2019-05-29 00:00:00
2019-05-29 23:59:59
65.65MB
Afrihost APN Usage 2019-05-30
2019-05-30 00:00:00
2019-05-30 23:59:59
48.74MB
Afrihost APN Usage 2019-05-31
2019-05-31 00:00:00
2019-05-31 23:59:59
54.36MB
Afrihost APN Usage 2019-06-01
2019-06-01 00:00:00
2019-06-01 23:59:59
66.88MB
Afrihost APN Usage 2019-06-02
2019-06-02 00:00:00
2019-06-02 23:59:59
39.46MB
Afrihost APN Usage 2019-06-03
2019-06-03 00:00:00
2019-06-03 23:59:59
59.13MB
Afrihost APN Usage 2019-06-04
2019-06-04 00:00:00
2019-06-04 23:59:59
33.22MB
Afrihost APN Usage 2019-06-05
2019-06-05 00:00:00
2019-06-05 23:59:59
35.81MB
That’s more than 30MB per day! And some days 60MB. That’s crazy. Normal UDP packet forwarders use about 3.5MB of data per day, which means TTOG leaks a lot of unnecessary data to the internet
I’ve factory reset the gateway and will recharge the sim card with another 500MB and see if this happens again. If it does I’ll have to dive down into the firmware and see what is using all the data.
Just in the process of setting ours up. I have the 3.09.99 Firmware (GUI is showing 3.04.09) - when I go to upload the new Firmware it states it is already at the latest version? Packet Forward option missing from menu (asking for provisioning code).
I received TTOG US version yesterday from Connected Things and was trying to set it up this morning. I was able to see the gateway on my network (over ethernet) and attempted to update the firmware but then found that it already had the most recent version installed (opdk-1.00.17).
I then tried to use 4G by setting the APN for the SIM card and there was a message that the gateway was rebooting. The in progress icon never went away and eventually I could no longer connect to the gateway in the web browser. The router shows the TTOG at the same IP but whenever I enter that address into the browser I get:
This site can’t be reached
10.0.0.83 took too long to respond.
Search Google for [module 1 pkt settings]
ERR_CONNECTION_TIMED_OUT
I have power cycled the TTOG and the router, my home network still shows the TTOG connected at the same IP but the web browser will not connect to that address.
Not sure what to do next - I am in over my head with these devices unfortunately as I have very rudimentary skills with networks. Connected Things has already referred me to TTN community when I questioned the lack of documentation provided with the TTOG.
Edit: I’m sorry - I see now the posts above and the setup instructions on the web page that indicate:
Did you connect the gateway via 3G/LTE? It will take a few minutes before the gateway will start routing messages. To open the ODU GUI again, you should manually set the IP address: IP address: 192.168.11.100 Subnet Mask: 255.255.255.0 Router: 192.168.11.10 Now, you can access the web interface via: 192.168.11.10.
I did try the IP address that was displayed while the gateway was trying to reboot - it was not any of those listed above and wouldn’t connect either but I will try this when I get back to lab.
Ours is running well so far. Paired with a Taoglas antenna.
My only complaint is the weatherproof Ethernet connector. If you’re not careful it will depress the tag, and pull the connector outwards slightly… I had an intermittent connection at first. Trick is to tighten the cable clamp last whilst applying slight downward pressure.
Just tried that. Setting to 2 seems to remove the error during transmission!
I have a feeling the global_config may have a minus value for gain?
Still not 100% it is Tx’ing however… Need to do more testing. Can see ADR packets going out to nodes - but no changes. RX is excellent though. Solid performance. Most nodes around 110 and SNR positive. Still on SF10 from older gateway though. Expecting to see them all on SF7 by now.
With Gain set to 2 I’m getting TX on SF7 successfully to the nodes.
However, anything on SF12 doesnt seem to reach them. TTN is attempting to optimise our nodes with this new gateway. Sending out ADR packets on at SF12.
Looks like some tuning needs to be done to the gateway config?
Also, I noticed watching the data/traffic to the nodes live when received by two Gateways the channel ID is different. Channel 2 on our MatchX and tektelic corresponds to channel 7 on the TTOG. Unsure if thats an issue?
Once a node has joined it should not be using SF12 for RX2. It should be at SF9. So anything transmitted at SF12 will not be received. If you search the forum you will find messages stating TTN V2 falls back to SF12 if the node does not respond to SF9.
I can’t recall if an easy fix was found. Some searching should help.
Regarding the channel numbers, these depend on the order of the channels in the configuration. The configuration differs between the two gateways, that causes the different channel numbers. As long as both report the same frequency that’s fine.
Thanks for the info! Still very much on the learning curve.
Interesting. I do believe with our older MatchX Gateway I was able to reboot these nodes with downlinks… Although nearly a year has past since then.They are transmitting on SF10. Downlinks from TTN RX on SF12 at max transmit power (watching the logs).
So from understanding your post - the node wont ‘hear’ the SF12 transmission as it currently set below this spread factor?
A node listens on a single SF as per standard. Listening on multiple SFs would consume a lot more energy or make the node less sensitive (reducing radio range). So the node should be listening at SF9 in the RX2 window (as instructed during OTAA join) and will not receive anything transmitted at other SFs.
You could try downlink as that should (still) use the network default SF9. (If you do try, please check the gateway console and let us know at which SF the downlink is transmitted)
Interesting… I’ve sent downlinks to these Nodes this morning. I’m not seeing them send on the TTN Gateway traffic. I see the uplinks (hourly), instantly followed by the ADR Optimize packet. But the manual downlink never appears?
Looks like I needed to use the First schedule, or the ADR optimise overrules the manual downlink. Facepalm. Was slowly going crazy watching the logs on the TTOG sending ADR thinking it was the manual downlinks.
Successfully managed to reboot our nodes over the air, and get everything down to SF7 with the new Gateway install.
Hi - I’ve been given 3 TTOG to set up at 3 locations for environmental monitoring. I’ve got network access and everything physical is ready to go… the problem is I’ve been handed this project with no previous experience! I’m trying to set up the gateways themselves and I’m not sure where I’m meant to go to do it… could someone help me with the initial steps & hopefully I’ll be able to work it out from there?
