I am not able to extract this file, getting error message with it. Any idea what to do? My gateways firmware version is 3.04.09. I also do stuck in the provision code window. And do not have the mentioned configuration page for packet forwarder 
I had the same issue trying to extract the archive on my Linux computer. But I uploaded it anyway to the gateway via the web UI and the upgrade worked.
My TTOG was configured for LTE about two weeks ago. I just realised it stopped forwarding packets a couple of days ago because the 4G connection failed. A power cycle does not solve the issue. The 3G/4G log is attached.
3G-4G LTE Log.txt (3.7 KB)
So I decided to enable DHCP on ethernet, which disables 3G/4G. Then I enabled 3G/4G again by specifying an APN name. All this was to make sure all the mobile settings are correct. After applying I can’t access the gateway on the fallback IP and it doesn’t request an IP via DHCP. Even a power cycle doesn’t bring the gateway back (wrong IP settings on router)
The gateway is now accesible on the static 192.168.11.10 IP and I can log in. The web UI however still indicates that 3G/4G is not connected.
On the sim card provider’s website I can see the sim card has data and that there was a data session today. A couple of KB’s of data has been used. But no packets are forwarded to TTN.
@jpmeijers Thanks for your kind hint! That’s exactly, what I suffered from! I did an upload of the tar.gz-file now and firmware update worked fine! System is updated to version “opdk-1.00.17” now and up and running! Thanks again!
My current firmware version is now:
opdk-1.00.17
Is this the latest formware, because in the filename i read 3.09.99.
If this is the case than the gateway is now up and running.
If i try to use the web-upgrade on the downloaded 3.09.99 firmware i get an " * Invalid firmware file." error
2 Likes
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.
2 Likes
I can confirm that a gateway can use less. This gateway has used 5.2 MB average per day and is connected to two networks:
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).
Any help much appreciated.
Hi,
I did use the above mentioned update-link https://connectedthings.store/files/WAPS-232N_LW_OPDKGUIForGeneric_3.09.99_3952121863.tar.gz and got a system with
firmware version “opdk-1.00.17” up and running (Packet Forward option availible!)
regards,
Suitbert
School boy error - file had been downloaded more than once (1)
Hardware needs the exact original filename to upload.
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.100Subnet Mask:255.255.255.0Router:192.168.11.10Now, 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.
Noticed today our is failing to transmit.
In the logs I can see TX errors relating to invalid power output?
Not 100% sure its configured correctly for TTN?
RX is absolutely fine with a good 20km range.
TX Power Output errors -
INFO: tx_start_delay=1493 (1493.562500) - (1497, bw_delay=1.500000, notch_delay=1.937500)
INFO: [down] PULL_ACK received in 15 ms
INFO: unsupported RF power for TX - 27 => use max 25 instead
JSON down: {“txpk”:{“imme”:false,“tmst”:3475817020,“freq”:869.525,“rfch”:0,“powe”:27,“modu”:“LORA”,“datr”:“SF12BW125”,“codr”:“4/5”,“ipol”:true,“size”:22,“ncrc”:true,“data”:“YHMhASaKMAAFA9KthANB/wABs6NEjQ==”}}
As far as we can see - no TX from Gateway
Have you set antenna gain parameters somewhere?
Still at the default value of Zero (0)
You could try setting it to -2 or 2. Not sure which of the two at the moment, need to check the source.
1 Like
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.
Okay making some progress here.
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.
1 Like