GithubHelp home page GithubHelp logo

ic880a-gateway's People

Contributors

gonzalocasas avatar johanstokking avatar patrick99999 avatar remcoder avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ic880a-gateway's Issues

Question about updating

Hi, Installed this git on my raspberrypi 0 w whit iC880A and iC880A LoRaWAN Gateway Backplane v2.0 some time ago, and i guess i need to update it from time to time... are there any place somebody has written a how to ?

E

RF output out of spec

I have noticed that the TX gain table in the global_conf.json file is exceeding the max RF output power that the internal power amplifier on the iC880a can handle. See the Datasheet https://shop.imst.de/media/pdf/22/67/a8/iC880A_Datasheet_V0_50.pdf at page 18.
The datasheet contains also an example how the tx_lut should look: https://shop.imst.de/media/pdf/22/67/a8/iC880A_Datasheet_V0_50.pdf at page 26 to 27.

And the datasheet also mentions on page 21 that the rssi_offset of both radios should be set on -169 instead -166.

Should the global_conf.json be modified to avoid damage to the amplifier or I'm missing something?

Edit 1: I have found the right settings to do in the global_conf.json: see https://www.wireless-solutions.de/downloads/Evaluation-Tools/LoRa_Lite_Gateway/WiMOD_LiteGateway_QuickStartGuide_V1_5.pdf at page 15.
They use this settings in their own LiteGateway which use the same iC880A concentrator board.
This is also confirmed in the datasheet of the LiteGateway. See the "Transmitter power level configuration in TX gain table" in https://www.wireless-solutions.de/downloads/Evaluation-Tools/LoRa_Lite_Gateway/WiMOD_LiteGateway_Datasheet_V1_5.pdf at page 9.

So the tx_lut in the global_conf.json should look like:

        "tx_lut_0": {
            /* TX gain table, index 0 */
            "pa_gain": 0,
            "mix_gain": 8,
            "rf_power": -6,
            "dig_gain": 2
        },
        "tx_lut_1": {
            /* TX gain table, index 1 */
            "pa_gain": 0,
            "mix_gain": 11,
            "rf_power": -3,
            "dig_gain": 3
        },
        "tx_lut_2": {
            /* TX gain table, index 2 */
            "pa_gain": 0,
            "mix_gain": 10,
            "rf_power": 0,
            "dig_gain": 0
        },
        "tx_lut_3": {
            /* TX gain table, index 3 */
            "pa_gain": 0,
            "mix_gain": 14,
            "rf_power": 3,
            "dig_gain": 1
        },
        "tx_lut_4": {
            /* TX gain table, index 4 */
            "pa_gain": 2,
            "mix_gain": 8,
            "rf_power": 6,
            "dig_gain": 3
        },
        "tx_lut_5": {
            /* TX gain table, index 5 */
            "pa_gain": 2,
            "mix_gain": 8,
            "rf_power": 10,
            "dig_gain": 2
        },
        "tx_lut_6": {
            /* TX gain table, index 6 */
            "pa_gain": 2,
            "mix_gain": 8,
            "rf_power": 11,
            "dig_gain": 1
        },
        "tx_lut_7": {
            /* TX gain table, index 7 */
            "pa_gain": 2,
            "mix_gain": 9,
            "rf_power": 12,
            "dig_gain": 2
        },
        "tx_lut_8": {
            /* TX gain table, index 8 */
            "pa_gain": 2,
            "mix_gain": 11,
            "rf_power": 13,
            "dig_gain": 3
        },
        "tx_lut_9": {
            /* TX gain table, index 9 */
            "pa_gain": 2,
            "mix_gain": 10,
            "rf_power": 14,
            "dig_gain": 2
        },
        "tx_lut_10": {
            /* TX gain table, index 10 */
            "pa_gain": 2,
            "mix_gain": 11,
            "rf_power": 16,
            "dig_gain": 2
        },
        "tx_lut_11": {
            /* TX gain table, index 11 */
            "pa_gain": 2,
            "mix_gain": 12,
            "rf_power": 20,
            "dig_gain": 0
        },
        "tx_lut_12": {
            /* TX gain table, index 12; this is a duplicate of index 11 due to hardware limitations, see datasheet */
            "pa_gain": 2,
            "mix_gain": 12,
            "rf_power": 23,
            "dig_gain": 0
        },
        "tx_lut_13": {
            /* TX gain table, index 13; this is a duplicate of index 11 due to hardware limitations, see datasheet */
            "pa_gain": 2,
            "mix_gain": 12,
            "rf_power": 25,
            "dig_gain": 0
        },
        "tx_lut_14": {
            /* TX gain table, index 14; this is a duplicate of index 11 due to hardware limitations, see datasheet */
            "pa_gain": 2,
            "mix_gain": 12,
            "rf_power": 26,
            "dig_gain": 0
        },
        "tx_lut_15": {
            /* TX gain table, index 15; this is a duplicate of index 11 due to hardware limitations, see datasheet */
            "pa_gain": 2,
            "mix_gain": 12,
            "rf_power": 27,
            "dig_gain": 0
        }

Problem using remote settings file

Hello, thanks for creating the push, but do you know why I am having this error now?

error: The following untracked working tree files would be overwritten by merge:
B827EBFFFEFCDAA2.json
Please move or remove them before you merge.
Aborting

Thank you.

Help: what for settings?

Why I must fill out the settings like email, lat/long and so on? what is this information used for? I can edit it all on the TTN account.

Save data offline

Hi,

is it possible to save the data from node locally (in raspberry pi sd card) before sending the data to TTN?

downlink doesn't work.

Hi,
I installed ic880a-gateway as shown and I am testing it using an arduino uno node with an SX1276.
Sending informations from my node to the TTN works fine but from ic880a-gateway to the connected device doesn't work, but i have to mention that in the "start.sh" code interface, the gateway seems to correctly send the message.
do I have to change my node ??
any advice could help!
thanks.

This setup is not working anymore?

Hi there!
Am I right that this repository is not up-to-date and working with its resources?

I found that install.sh is referring to a binary called poly_pkt_fwd, but it seems that the code
at https://github.com/TheThingsNetwork/packet_forwarder doesn't compile to a binary callled poly_pkt_fwd (anymore?).

What would be the current approach if i want to build a gateway with RPi and ic880a?
I guess the stuff at https://github.com/TheThingsNetwork/lora_gateway is still usable?
What packet forwarder is the best choice atm?

Thanks in advance for any hints!

start.sh : change ping target in testing internet connection

Hi all
About the case that in the beginning of start.sh there is an internet connection testing, by pining to google.com ...

  • there are network environments where net admins do filter icmp traffic to google (maybe not in the field, but while testing gateways in laboratories)
  • there is a workaround to this problem by ralphtheninja's pull request here and reixd 's suggestion

wouldn't be more generic to test gateway's connectivity by pinging to a more TTN related url, and what would that be ?
I believe this should be less possible to be filtered and if no ping to it, then the gateway is facing a real connectivity problem !!

regards

Can I rename the gateway name

Hello,
Thank for sending the black pane. I received it satureday.
I just configured my second gateway. For now it will remind at home close to my first gateway.

During the installation, I answered yes for the remote configuration and at the end the gateway was renamed to ttn-gateway. However, now I have two gateway with the same name, name I switched of the first.

I red your doc and you wrote

By default, the installer changes the hostname of your Raspeberry Pi to ttn-gateway (to prevent collisions with other Raspberry Pis in your network). You can override this in non-remote configuration mode.

As I chosed remote configuration, I should not rename it? What happen if I do it, because I can not have two devise on the same network. Why should not it be renamed for remote configuration?

Thank for your reply.
Pierre

can't connect without any failure

Hi there,
I've tried every thing what i found on google...but I'can't connect to the ttn network. this is my status and syslog:
ttn@ttn-gateway:~ $ service ttn-gateway status

  • ttn-gateway.service - The Things Network Gateway
    Loaded: loaded (/lib/systemd/system/ttn-gateway.service; enabled; vendor preset: enabled)
    Active: active (running) since Mon 2018-08-13 19:56:52 CEST; 58min ago
    Main PID: 211 (start.sh)
    CGroup: /system.slice/ttn-gateway.service
    |-211 /bin/bash /opt/ttn-gateway/bin/start.sh
    `-543 ./poly_pkt_fwd
    ttn@ttn-gateway:~ $ sudo tail -f /var/log/syslog
    [sudo] Passwort f�r ttn:
    Aug 13 20:55:20 ttn-gateway systemd[911]: Listening on GnuPG cryptographic agent and passphrase cache.
    Aug 13 20:55:20 ttn-gateway systemd[911]: Reached target Paths.
    Aug 13 20:55:20 ttn-gateway systemd[911]: Listening on GnuPG cryptographic agent (access for web browsers).
    Aug 13 20:55:20 ttn-gateway systemd[911]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
    Aug 13 20:55:20 ttn-gateway systemd[911]: Reached target Sockets.
    Aug 13 20:55:20 ttn-gateway systemd[911]: Reached target Timers.
    Aug 13 20:55:20 ttn-gateway systemd[911]: Reached target Basic System.
    Aug 13 20:55:20 ttn-gateway systemd[911]: Reached target Default.
    Aug 13 20:55:20 ttn-gateway systemd[911]: Startup finished in 180ms.
    Aug 13 20:55:20 ttn-gateway systemd[1]: Started User Manager for UID 1001.
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA datagrams sent: 2 (444 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA acknowledged: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [DOWNSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_DATA sent: 4 (0.00% acknowledged)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets sent to concentrator: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # TX errors: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [GPS] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Invalid gps time reference (age: 1534186326 sec)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Manual GPS coordinates: latitude 10.00000, longitude 20.00000, altitude -1 m
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### END #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### 2018-08-13 18:52:36 GMT #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [UPSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets received by concentrator: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets forwarded: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA datagrams sent: 2 (444 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA acknowledged: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [DOWNSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_DATA sent: 6 (0.00% acknowledged)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets sent to concentrator: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # TX errors: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [GPS] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Invalid gps time reference (age: 1534186356 sec)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Manual GPS coordinates: latitude 10.00000, longitude 20.00000, altitude -1 m
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### END #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### 2018-08-13 18:53:06 GMT #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [UPSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets received by concentrator: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets forwarded: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA datagrams sent: 2 (444 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA acknowledged: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [DOWNSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_DATA sent: 6 (0.00% acknowledged)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets sent to concentrator: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # TX errors: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [GPS] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Invalid gps time reference (age: 1534186386 sec)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Manual GPS coordinates: latitude 10.00000, longitude 20.00000, altitude -1 m
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### END #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### 2018-08-13 18:53:36 GMT #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [UPSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets received by concentrator: 1
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets forwarded: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA datagrams sent: 2 (444 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA acknowledged: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [DOWNSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_DATA sent: 6 (0.00% acknowledged)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets sent to concentrator: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # TX errors: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [GPS] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Invalid gps time reference (age: 1534186416 sec)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Manual GPS coordinates: latitude 10.00000, longitude 20.00000, altitude -1 m
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### END #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### 2018-08-13 18:54:06 GMT #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [UPSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets received by concentrator: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets forwarded: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA datagrams sent: 2 (444 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA acknowledged: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [DOWNSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_DATA sent: 6 (0.00% acknowledged)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets sent to concentrator: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # TX errors: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [GPS] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Invalid gps time reference (age: 1534186446 sec)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Manual GPS coordinates: latitude 10.00000, longitude 20.00000, altitude -1 m
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### END #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### 2018-08-13 18:54:36 GMT #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [UPSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets received by concentrator: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets forwarded: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA datagrams sent: 2 (444 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA acknowledged: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [DOWNSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_DATA sent: 6 (0.00% acknowledged)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets sent to concentrator: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # TX errors: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [GPS] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Invalid gps time reference (age: 1534186476 sec)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Manual GPS coordinates: latitude 10.00000, longitude 20.00000, altitude -1 m
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### END #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ##### 2018-08-13 18:55:06 GMT #####
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [UPSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets received by concentrator: 1
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets forwarded: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA datagrams sent: 2 (444 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PUSH_DATA acknowledged: 0.00%
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [DOWNSTREAM] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_DATA sent: 6 (0.00% acknowledged)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # RF packets sent to concentrator: 0 (0 bytes)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # TX errors: 0
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: ### [GPS] ###
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Invalid gps time reference (age: 1534186506 sec)
    Aug 13 20:55:36 ttn-gateway ttn-gateway[211]: # Manual GPS coordinates: latitude 10.00000, longitude 20.00000, altitude -1 m

SPI is enable.
Power supply is original from RPI (V2.0)
I connect the IC880a with the backplane and an raspberry pi 2.0 Version B

Could anybody help me?
kindly regards
Elbeato

Packet forwarder problem

Hello,
I am installing a Lora WAN gateway but before I began suddenly I found that the packet forwarder has been on hold https://github.com/TheThingsNetwork/packet_forwarder
and in the TTN-ZH I found that the install.sh will use it

Build packet forwarder

if [ ! -d packet_forwarder ]; then
git clone -b legacy https://github.com/TheThingsNetwork/packet_forwarder.git
pushd packet_forwarder
else
pushd packet_forwarder
git fetch origin
git checkout legacy
git reset --hard
fi
make
popd
so my question is that will I found a problem in sending data to TTN ?
In the link above of packet forwarder you can see that they suggest " Semtech packet forwarder or MP packet forwarder. How to use one of them instead of packet forwarder ?
Thank you in advance.
Yassine

how to best disable wifi

I read that using Wifi is not great due to interference with the LoRaWAN signal.

I'd like to encourage you to add in the Documentation (readme) a suggested best-practice method to disable wifi for the ttn-zh project. I've found various approaches. But this one seems like a good one to me:

add new line
dtoverlay=pi3-disable-wif
to
boot/config.txt

as described here:
https://raspberrypi.stackexchange.com/a/62522/58012
referencing:
https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README

Question: Does this allow fine timestamps?

Hi there,

for TDoA (Time Difference of Arrival) triangulation for geopositioning we need very precise timestamps. Have you tried in your setup whether timestamps can be retrieved in nanoseconds instead of the default microseconds? To know that would be really great! Thanks a lot in advance!

Best wishes!

Please add in the desription

  • How to create a ssh file
  • always download the latest raspiban file
  • use a fritz box or other hub that has dns and thus can resolve [email protected]
  • add how to enter a wifi network, and one without password

gateway no longer visible

since 20hours my gateway is not seen by ttn after working for 2 years now without any known errors.
Looking at syslog ist seams to work like always. no errors.
Where should I look for the error.
thomas

power-via-gpio

Power via gpio

Are there possible safeguards that could be stated ?
Are there possible safeguards on the pcb (tindie) that could be implemented (barral connector)?

https://github.com/ttn-zh/ic880a-gateway/blob/spi/images/power-via-gpio.jpg

I don't want to forget this thought: if already thought thru: please close, otherwise tracker until sure of power.


I go and find some pi reference and may add below this line.

http://raspberrypi.stackexchange.com/questions/1617/how-do-i-supply-power-through-the-gpio

Not possible to clone ic880a-gateway.git when using Buster

Due to a voltage interruption to my RPi the SD card with the gateway software on it crashed.
Time to make a fresh card with the latest Raspbian light software.
I have done this several times without any issue, but it is the first time with BUSTER LIGHT.

I have followed all the steps in the wiki. When I arrived at the clone step I got an error message:

start screen dump:

ttn@raspberrypi:~ $ git clone https://github.com/ttn-zh/ic880a-gateway.git ~/ic880a-gateway

Cloning into '/home/ttn/ic880a-gateway'...

/usr/lib/git-core/git-remote-https: error while loading shared libraries: er▒: cannot open shared object file: No such file or directory

ttn@raspberrypi:~ $

stop screen dump

json file

it says:

"if you want to use the remote configuration option, please make sure you have created a JSON file named as your gateway EUI (e.g. B827EBFFFE7B80CD.json) in the Gateway Remote Config repository."

How do I do that?

time receiving

Hi !
thank you for your Job !
I have just one probleme why I receive date every minute and not in really time
thears some configuration for fix that

issu

Select LoRaWAN network type upon installation

Hi,

First of all, thanks for this nice work.

I have though a request to extend the installation script to ask whether the gateway will be a LoRaWAN public or private network. One more question like "Do you use LoRaWAN private network? [y/N]" in the script...
This information is in the global_config.json file in the "SX1301_conf" section as :
"lorawan_public": true,

I don't know if this information can be replaced in the local_config.json.
It took me the whole day to figure out that my system was not working reliably because my endpoints are for private network and the default values for this parameter is true ! If adding this question can save other people hours of research....

I thank you in advance,
Best regards,
OM.

GPS working but not syncing time

Morning all,

I've spent some time trying to resolve this, and discussed on the TTN forums. I'm beginning to suspect there may be a code issue.

I did a clean install of Stretch and got the GPS module set up and working first. It's a Raspi3 so I reconfigured the serial ports to feed the NMEA to the hardware UART. Using GY-NEO6MV2 module. That gets me reliable position information on ttyAMA0:

...
$GPRMC,225036.000,A,51xx.xxxx,N,000xx.xx,W,0.00,200.38,090318,A*71
...

I then installed and configured ttn-zh per the wiki. Everything is up and running and the concentrator appears to be seeing the GPS:

...
Mar 9 22:47:09 ttn-dev-gw ttn-gateway[538]: INFO: Reference longitude is configured to 0.000000 deg
Mar 9 22:47:09 ttn-dev-gw ttn-gateway[538]: INFO: Reference altitude is configured to 0 meters
Mar 9 22:47:09 ttn-dev-gw ttn-gateway[538]: INFO: GPS is enabled
...

(I say ‘appears’… it isn’t throwing any errors about opening the serial port. I’m slightly suspicious that I can still cat /ttyAMA0 in another shell.)

However, the gps time reference is defaulting to unix epoch. It looks like perhaps an initial sync was missing:
...
Mar 9 22:49:32 ttn-dev-gw ttn-gateway[538]: ### [GPS] ###
Mar 9 22:49:32 ttn-dev-gw ttn-gateway[538]: # Invalid gps time reference (age: 1520635659 sec)
Mar 9 22:49:32 ttn-dev-gw ttn-gateway[538]: # Manual GPS coordinates: latitude 0.00000, longitude 0.00000, altitude 0 m
Mar 9 22:49:32 ttn-dev-gw ttn-gateway[538]: ##### END #####
...

Per the example above, the timestamp on each sentence format is correct. I’ve also patched the PPS output from the GPS module to pin 19 on the iC880a concentrator, although I don't think this matters.

I've had a look at poly_pkt_fwd.c and there's nothing obvious I can find, although this suggests there may be some work remaining:

            printf("### [GPS] ###\n");
            //TODO: this is not symmetrical. time can also be derived from other sources, fix
            if (gps_enabled == true) {

and:

            //TODO: is this okay, can time be recruited from the local system if gps is not working?
            /* get a copy of GPS time reference (avoid 1 mutex per packet) */
            if ((nb_pkt > 0) && (gps_active == true)) {
                    pthread_mutex_lock(&mx_timeref);
                    ref_ok = gps_ref_valid;
                    local_ref = time_reference_gps;
                    pthread_mutex_unlock(&mx_timeref);
            } else {
                    ref_ok = false;

...although by my reading that suggests alternate sources should only be used if the gps isn't working.

Thoughts?

Typo mistake I think!

Please change the command while installing the packet forwarder in this link
after these two commands:
$ git clone https://github.com/ttn-zh/ic880a-gateway.git ~/ic880a-gateway
$ cd ~/ic880a-gateway

It should be: $ sudo ./install.sh spi

But it is like : $ sudo ./install.sh

spi is missing and it's confusing most of the people.

Strange behavior from my gateway

Hello All,
I have a strange behavior and I would like to know if you can help to understand.

Let me first describe how is my structure.

I have 2 nodes in a orchard at about 450m altitude. There are not above the tree and the foliage, but on the top (you we will better understand later). One of station is in the middle of the orchard and the second at the end.

The gateway it on the top of my camping car, at about 900m of the first station and about 1100m of the second.

I know that my gateway is not well located because it is at a lower altitude than my nodes and there are winyard between them.

Between June and September 2018, in general the transmission were fine.

End of April 2019, I turned on my nodes and the gateway for new measurements, while the trees did not have foliage yet and the transmission started well (the nodes transmit each hour). The leafs appeared and grew up. And suddenly, at the same time (within one hour) , the gateway do not receive and transmit the messages from the nodes.

As it happen at the same time, I though about a problem with the gateway, but not. Then I moved the gateway at about 500m from the nodes, almost at the same altitude and the area is clearer. The nodes stated to transmit again. Great!

It ran well for about 2 weeks until my Gateay MicroCard broke. I changed and reinstalled it. The nodes transmitted again but only fro 4 hours.

** nodes stop transmitting at the same time again**. Or let say may be , the gateway do not receive the message, because the nodes has not stoppred working. For me, its still transmit.

I thought again an issue with the new installed gateway, but not, the gateway worked (I can see the green status at TTN console . Then, I moved the gateway at about 50m from the nodes and the nodes started transmitting!

My guess is as the foliage “covers” the nodes (even if there are at the top of the tree), the foliage act as an obstacle, but it can not explain why the two nodes stopped transmitting at the same time, first all because the apple tree has very less foliage at the second node. My guess is the foliage would make an obstacle, the node will not stop transmitting during the same hour, but may be, with a couple of days of delay.

Then I would to understand why this behavior?
Why the node stop transmitting at the same time, and why it works when I move closer the gateway, while last year, it worked at 1km of distance.

Can it be the power of transmitting, how changed automatically?
Can it be possible that the gateway’s range (sensitivity) somehow dropped and how can I check it and fix it?

I configured as in the example: https://github.com/matthijskooijman/arduino-lmic/blob/master/examples/ttn-abp/ttn-abp.ino#L218

Note, I am using for now (but I will change to OTAA) ABP activation method.

Thank for your point of view and have a nice evening/day.
Cheers

Gateway

Hi,
we are setting up a lora gateway and we followed the same steps mentioned in https://github.com/ttn-zh/ic880a-gateway. but we are unable to find complete procedure to run the gateway connected to thethings network. we will be glad to help us in resolving the issue.
Thanks in Advance!
Regards

How to update?

How do I update the gateway? Can I just rerun install.sh?

Improvement on antenna

Hello guys.
First I would like to say that your job is impressive! I wish I lived in Zurich. We do not have most coverage here in Lausanne and Yverdon, even if I heard that Octanis installed a gateway recently near the EPFL.

I am not a RF guy, but I work with some of them.In my opinion it should be of importance to specify in your wiki that the antenna SHOULD be a 1/2wavelength. If 1/4wavelength, the mounting instructions are missing a rock-solid copper-foil ground plane.

Once more, thumbs up for all the work you are doing!

Important power

What does this mean exactly?

Plug the iC880a (WARNING: first power plug to the wall socket, then to the gateway DC jack, and ONLY THEN USB to RPi!)

Use with pure LoRa?

Hi, can this software be used with pure Lora (not LoraWAN) with custom protocol?

Thanks in advance

Gateway not connected

Hello, as of last month I successfully connected my gateway to the network.
Since then however, I have not been able to successfully recreate this connection even though nothing has changed in the configuration.

Illustration:
lorap issue

The current gateway I am using is a ic880-gateway using the TTN legacy packet forwarder protocol. My gateway is (succesfully) registered using the documentation in the README.md of this repository.

You can find my remote config here

915MHz alternative?

Hi Guys,

The IMST iC880a board only supports 868MHz. Is there any way to have a 915MHz implementation (legal requirements here in Australia)?

Please help. Thanks

ttn-gateway service entered failed state

Hey guys,
After installing the install.sh and rebooting, I wanted to check if the service was running (since it was not being shown in the console) and here is what I got:

rxhf@radek-gw2:~/ic880a-gateway $ sudo service ttn-gateway status
● ttn-gateway.service - The Things Network Gateway
Loaded: loaded (/lib/systemd/system/ttn-gateway.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2017-08-04 17:33:02 UTC; 4s ago
Process: 9538 ExecStart=/opt/ttn-gateway/bin/start.sh (code=exited, status=1/FAILURE)
Main PID: 9538 (code=exited, status=1/FAILURE)

Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: INFO: Beacon is disabled
Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: INFO: Monitor is disabled
Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: INFO: Contact email configured to "[email protected]"
Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: INFO: Description configured to "Radek Gateway 2"
Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: INFO: Successfully contacted server router.eu.thethings...work
Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: INFO: [main] Starting the concentrator
Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: ERROR: Version of calibration firmware not expected, ac...ed:2
Aug 04 17:33:02 radek-gw2 ttn-gateway[9538]: ERROR: [main] failed to start the concentrator
Aug 04 17:33:02 radek-gw2 systemd[1]: ttn-gateway.service: main process exited, code=exited, status=...LURE
Aug 04 17:33:02 radek-gw2 systemd[1]: Unit ttn-gateway.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

I get this "failed to start the concentrator" quite often in my other gateway, but after retrying a few times the gps_packet_forward it works. Should I just retry with this one as well? If so, how? By rebooting it and rechecking the status of the service over and over?

ERROR: [main] failed to start the concentrator

I've just received my IC880a gateway module and built it following the guide at https://github.com/ttn-zh/ic880a-gateway/wiki.

I'm running the latest Raspbian Stretch Lite build and the Pi connects by LAN cable.

The Pi is a model B2, power is povided by a 5V 2.5A usb power official power supply.

I have tripple checked all of the jumper connections and they match the pin-out from the article.

However I don't see my gateway as connected in the TTN dashboard.

I've run the following commands to try and troubleshoot the issue:-

ttn@ttn-gateway:~ $ service ttn-gateway status
● ttn-gateway.service - The Things Network Gateway
Loaded: loaded (/lib/systemd/system/ttn-gateway.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-02-14 22:10:27 GMT; 343ms ago
Main PID: 4665 (start.sh)
CGroup: /system.slice/ttn-gateway.service
├─4665 /bin/bash /opt/ttn-gateway/bin/start.sh
└─4676 sleep 0.1

ttn@ttn-gateway:~ $ service ttn-gateway status
● ttn-gateway.service - The Things Network Gateway
Loaded: loaded (/lib/systemd/system/ttn-gateway.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-02-15 09:34:05 GMT; 751ms ago
Process: 5875 ExecStart=/opt/ttn-gateway/bin/start.sh (code=exited, status=1/FAILURE)
Main PID: 5875 (code=exited, status=1/FAILURE)

ttn@ttn-gateway:~ $ sudo tail -f /var/log/syslog
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: INFO: Statusstream data is enabled
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: INFO: Beacon is disabled
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: INFO: Monitor is disabled
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: INFO: Contact email configured to "MY_EMAIL_ADDRESS"
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: INFO: Description configured to "TTN"
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: INFO: Successfully contacted server router.eu.thethings.network
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: INFO: [main] Starting the concentrator
Feb 14 22:12:21 ttn-gateway ttn-gateway[5287]: ERROR: [main] failed to start the concentrator
Feb 14 22:12:21 ttn-gateway systemd[1]: ttn-gateway.service: Unit entered failed state.
Feb 14 22:12:21 ttn-gateway systemd[1]: ttn-gateway.service: Failed with result 'exit-code'.
Feb 14 22:12:26 ttn-gateway systemd[1]: ttn-gateway.service: Service hold-off time over, scheduling restart.
Feb 14 22:12:26 ttn-gateway systemd[1]: Stopped The Things Network Gateway.
Feb 14 22:12:26 ttn-gateway systemd[1]: Started The Things Network Gateway.
Feb 14 22:12:27 ttn-gateway ttn-gateway[5333]: /opt/ttn-gateway/gateway-remote-config /opt/ttn-gateway/bin
Feb 14 22:12:28 ttn-gateway ttn-gateway[5333]: Already up-to-date.
Feb 14 22:12:28 ttn-gateway ttn-gateway[5333]: HEAD is now at 8fd2594 Merge pull request #568 from zara-lab/master
Feb 14 22:12:28 ttn-gateway ttn-gateway[5333]: /opt/ttn-gateway/bin
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: [TTN Gateway]: Use Gateway EUI B827EBFFFE7CB189 based on eth0
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: *** Poly Packet Forwarder for Lora Gateway ***
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: Version: 2.1.0
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: *** Lora concentrator HAL library version info ***
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: Version: 3.1.0; Options: native;
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: ***
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Little endian host
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: found global configuration file global_conf.json, parsing it
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: lorawan_public 1, clksrc 1
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Configuring TX LUT with 16 indexes
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: radio 0 enabled (type SX1257), center frequency 867500000, RSSI offset -166.000000, tx enabled 1
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: radio 1 enabled (type SX1257), center frequency 868500000, RSSI offset -166.000000, tx enabled 0
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 0> radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 1> radio 1, IF -200000 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 2> radio 1, IF 0 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 3> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 4> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 5> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 6> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora multi-SF channel 7> radio 0, IF 400000 Hz, 125 kHz bw, SF 7 to 12
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: gateway MAC address is configured to AA555A0000000000
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Found 2 servers in array.
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Server 0 configured to "127.0.0.1", with port up "1680" and port down "1681"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Server 1 configured to "iot.semtech.com", with port up "1680" and port down "1680"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Found 5 system calls in array.
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: System command 0: "df -m"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: System command 1: "free -h"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: System command 2: "uptime"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: System command 3: "who -a"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: System command 4: "uname -a"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: monitor hostname or IP address is configured to "127.0.0.1"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: monitor port is configured to "2008"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: ghost hostname or IP address is configured to "127.0.0.1"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: ghost port is configured to "1918"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: downstream keep-alive interval is configured to 10 seconds
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: statistics display interval is configured to 30 seconds
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: upstream PUSH_DATA time-out is configured to 100 ms
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: packets received with a valid CRC will be forwarded
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: packets received with a CRC error will NOT be forwarded
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: packets received with no CRC will NOT be forwarded
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: GPS serial port path is configured to "/dev/ttyAMA0"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: SSH path is configured to "/usr/bin/ssh"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: SSH port is configured to 22
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: HTTP port is configured to 80
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: NGROK path is configured to "/usr/bin/ngrok"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Reference latitude is configured to 10.000000 deg
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Reference longitude is configured to 20.000000 deg
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Reference altitude is configured to -1 meters
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: GPS is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Using fake GPS coordinates instead of real.
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: antenna_gain 0 dBi
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Upstream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Downstream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Ghoststream data is disabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Radiostream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Statusstream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Beacon is disabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Monitor is disabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Platform configured to "IMST + Rpi"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Contact email configured to "[email protected]"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Description configured to "Update me"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: found local configuration file local_conf.json, parsing it
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: redefined parameters will overwrite global parameters
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: local_conf.json does not contain a JSON object named SX1301_conf
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: gateway MAC address is configured to B827EBFFFE7CB189
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Found 1 servers in array.
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Server 0 configured to "router.eu.thethings.network", with port up "1700" and port down "1700"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: packets received with a valid CRC will be forwarded
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: packets received with a CRC error will NOT be forwarded
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: packets received with no CRC will NOT be forwarded
Feb 14 22:12:29 ttn-gateway systemd[1]: ttn-gateway.service: Main process exited, code=exited, status=1/FAILURE
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Reference latitude is configured to 53.566631 deg
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Reference longitude is configured to -1.532979 deg
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Reference altitude is configured to 115 meters
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: GPS is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: antenna_gain 0 dBi
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Upstream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Downstream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Ghoststream data is disabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Radiostream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Statusstream data is enabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Beacon is disabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Monitor is disabled
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Contact email configured to "MY_EMAIL_ADDRESS"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Description configured to "TTN"
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: Successfully contacted server router.eu.thethings.network
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: INFO: [main] Starting the concentrator
Feb 14 22:12:29 ttn-gateway ttn-gateway[5333]: ERROR: [main] failed to start the concentrator
Feb 14 22:12:29 ttn-gateway systemd[1]: ttn-gateway.service: Unit entered failed state.
Feb 14 22:12:29 ttn-gateway systemd[1]: ttn-gateway.service: Failed with result 'exit-code'.

Do you have any suggestions on what I should check?

Regards

Steve

No downlink since update

I had issues with the gateway, so I did an update. The issue was that the gateway stopped forwarding packets after 4 days, and showed offline in the TTN backoffice.

After the update I do not receive any downlink messages anymore. In de TTN backoffice I can see in the traffic overview of the app that the downlink message is received by TTN, but no data on both of my nodes. These nodes worked fine before the update.

Uplink data seems to work fine.

Os = 9 (stretch), raspbian

Edit: I did rerun the install script, and the gateway did a reboot. Now the downlink messages are working again. I am curious however how can I troubleshoot this on the gateway if similar events occur?

Use without TTN?

Hi,
I have the RAK831 Gateway and I want to use it with my custom code and backend server, can this software be used in any way to do this?
Thanks

Error: Failed to start the concentrator after using 5V, 4A adapter

I am using 5V,1.6A adapter, my remote config file is pushed to the repository, I have edited the reset code into my start.sh file, my SPI is enabled as well.

#! /bin/bash

Reset iC880a PIN
SX1301_RESET_BOARD_PIN=22
echo "$SX1301_RESET_BOARD_PIN_22" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio$SX1301_RESET_BOARD_PIN_22/direction
echo "0" > /sys/class/gpio/gpio$SX1301_RESET_BOARD_PIN_22/value
sleep 0.1
echo "1" > /sys/class/gpio/gpio$SX1301_RESET_BOARD_PIN_22/value
sleep 0.1
echo "0" > /sys/class/gpio/gpio$SX1301_RESET_BOARD_PIN_22/value
sleep 0.1
echo "$SX1301_RESET_BOARD_PIN_22" > /sys/class/gpio/unexport

Test the connection, wait if needed.
After restating it, and checking the gateway status by running
sudo service ttn-gateway status

I get
● ttn-gateway.service - The Things Network Gateway
Loaded: loaded (/lib/systemd/system/ttn-gateway.service; enabled; vendor pres
Active: active (running) since Tue 2019-01-08 09:40:48 GMT; 1s ago
Main PID: 1610 (start.sh)
CGroup: /system.slice/ttn-gateway.service
├─1610 /bin/bash /opt/ttn-gateway/bin/start.sh
├─1614 git pull
├─1615 git fetch --update-head-ok
└─1616 git-remote-https origin https://github.com/ttn-zh/gateway-remo

Jan 08 09:40:48 ttn-gateway systemd[1]: Started The Things Network Gateway.
Jan 08 09:40:48 ttn-gateway ttn-gateway[1610]: /opt/ttn-gateway/gateway-remote-c
lines 1-12/12 (END)

When i run sudo tail -f /var/log/syslog

Jan 8 10:09:55 ttn-gateway ttn-gateway[4693]: INFO: Beacon is disabled
Jan 8 10:09:55 ttn-gateway ttn-gateway[4693]: INFO: Monitor is disabled
Jan 8 10:09:55 ttn-gateway ttn-gateway[4693]: INFO: Contact email configured to "[email protected]"
Jan 8 10:09:55 ttn-gateway ttn-gateway[4693]: INFO: Description configured to "Faclon_TTN_Gateway"
Jan 8 10:09:55 ttn-gateway ttn-gateway[4693]: INFO: Successfully contacted server router.eu.thethings.network
Jan 8 10:09:55 ttn-gateway ttn-gateway[4693]: INFO: [main] Starting the concentrator
Jan 8 10:09:55 ttn-gateway ttn-gateway[4693]: ERROR: [main] failed to start the concentrator
Jan 8 10:09:55 ttn-gateway systemd[1]: ttn-gateway.service: Main process exited, code=exited, status=1/FAILURE
Jan 8 10:09:55 ttn-gateway systemd[1]: ttn-gateway.service: Unit entered failed state.
Jan 8 10:09:55 ttn-gateway systemd[1]: ttn-gateway.service: Failed with result 'exit-code'.
Jan 8 10:10:00 ttn-gateway systemd[1]: ttn-gateway.service: Service hold-off time over, scheduling restart.
Jan 8 10:10:00 ttn-gateway systemd[1]: Stopped The Things Network Gateway.
Jan 8 10:10:00 ttn-gateway systemd[1]: Started The Things Network Gateway.
Jan 8 10:10:00 ttn-gateway ttn-gateway[4722]: /opt/ttn-gateway/gateway-remote-config /opt/ttn-gateway/bin
Jan 8 10:10:05 ttn-gateway ttn-gateway[4722]: Already up-to-date.
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: HEAD is now at f031abf Merge pull request #1167 from Taher1322/master
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: /opt/ttn-gateway/bin
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: [TTN Gateway]: Use Gateway EUI B827EBFFFE0B103C based on wlan0
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: *** Poly Packet Forwarder for Lora Gateway ***
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: Version: 2.1.0
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: *** Lora concentrator HAL library version info ***
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: Version: 3.1.0; Options: ftdi;
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: ***
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Little endian host
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: found global configuration file global_conf.json, parsing it
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: lorawan_public 1, clksrc 1
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Configuring TX LUT with 16 indexes
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: radio 0 enabled (type SX1257), center frequency 867500000, RSSI offset -166.000000, tx enabled 1
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: radio 1 enabled (type SX1257), center frequency 868500000, RSSI offset -166.000000, tx enabled 0
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 0> radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 1> radio 1, IF -200000 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 2> radio 1, IF 0 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 3> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 4> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 5> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 6> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora multi-SF channel 7> radio 0, IF 400000 Hz, 125 kHz bw, SF 7 to 12
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: gateway MAC address is configured to AA555A0000000000
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Found 2 servers in array.
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Server 0 configured to "127.0.0.1", with port up "1680" and port down "1681"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Server 1 configured to "iot.semtech.com", with port up "1680" and port down "1680"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Found 5 system calls in array.
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: System command 0: "df -m"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: System command 1: "free -h"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: System command 2: "uptime"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: System command 3: "who -a"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: System command 4: "uname -a"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: monitor hostname or IP address is configured to "127.0.0.1"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: monitor port is configured to "2008"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: ghost hostname or IP address is configured to "127.0.0.1"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: ghost port is configured to "1918"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: downstream keep-alive interval is configured to 10 seconds
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: statistics display interval is configured to 30 seconds
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: upstream PUSH_DATA time-out is configured to 100 ms
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: packets received with a valid CRC will be forwarded
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: packets received with a CRC error will NOT be forwarded
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: packets received with no CRC will NOT be forwarded
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: GPS serial port path is configured to "/dev/ttyAMA0"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: SSH path is configured to "/usr/bin/ssh"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: SSH port is configured to 22
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: HTTP port is configured to 80
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: NGROK path is configured to "/usr/bin/ngrok"
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Reference latitude is configured to 10.000000 deg
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Reference longitude is configured to 20.000000 deg
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Reference altitude is configured to -1 meters
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: GPS is enabled
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Using fake GPS coordinates instead of real.
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: antenna_gain 0 dBi
Jan 8 10:10:06 ttn-gateway ttn-gateway[4722]: INFO: Upstream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Downstream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Ghoststream data is disabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Radiostream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Statusstream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Beacon is disabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Monitor is disabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Platform configured to "Lorank"
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Contact email configured to "[email protected]"
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Description configured to "Update me"
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: found local configuration file local_conf.json, parsing it
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: redefined parameters will overwrite global parameters
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: local_conf.json does not contain a JSON object named SX1301_conf
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: gateway MAC address is configured to B827EBFFFE0B103C
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Found 1 servers in array.
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Server 0 configured to "router.eu.thethings.network", with port up "1700" and port down "1700"
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: packets received with a valid CRC will be forwarded
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: packets received with a CRC error will NOT be forwarded
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: packets received with no CRC will NOT be forwarded
Jan 8 10:10:07 ttn-gateway systemd[1]: ttn-gateway.service: Main process exited, code=exited, status=1/FAILURE
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Reference latitude is configured to 19.117190 deg
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Reference longitude is configured to 72.887140 deg
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Reference altitude is configured to 16 meters
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: GPS is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: antenna_gain 0 dBi
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Upstream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Downstream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Ghoststream data is disabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Radiostream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Statusstream data is enabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Beacon is disabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Monitor is disabled
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Contact email configured to "[email protected]"
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Description configured to "Faclon_TTN_Gateway"
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: Successfully contacted server router.eu.thethings.network
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: INFO: [main] Starting the concentrator
Jan 8 10:10:07 ttn-gateway ttn-gateway[4722]: ERROR: [main] failed to start the concentrator
Jan 8 10:10:07 ttn-gateway systemd[1]: ttn-gateway.service: Unit entered failed state.
Jan 8 10:10:07 ttn-gateway systemd[1]: ttn-gateway.service: Failed with result 'exit-code'.

The status on TTN console is still non connected.

Please help me with this issue..

My gateway stop transmiting

Hello
I installed and configured two gateway following that procedure. Wedenesady, I stopped my gateway and when later I restated it, no way to be seen by TTN.
I have a second and same gateway and this one can be seen by TTN but now message are transmitted to TTN throught the second gateway.

Regarding the first gateway, which stop working, I moved iit to my place and I switch it on. Once again, from my flat, the gateway can not be seen by TTN.

I am planning to reinstalled it, but first there is a way (a command from Raspberry) to check the gateway (concentrator, antenna, application, etc...)?

Note that my Raspberry connected to the concentrator, starts well. I can be remotely connected to it, and I have an internet access. In spite of this, the gate way is not seen by TTN. Can it be possible that Gateway remote configuration file is corrupt?

Thank
Cheers

"not connected" on TTN.

Hello, I am currently creating a LoRaWAN outdoor multi-channel gateway fora university project. I purchased a RPi3 B+ and an ic880A and followed the guide on https://github.com/ttn-zh/ic880a-gateway/wiki, I even added my gateway ID to the remote-config repo. However, by the end of the installation my gateway status is “not connected” on TTN. Can anyone please help out. Here are some logs from my RPi.

After running sudo systemctl status ttn-gateway.service I receive the following,

ttn@ttn-gateway:~ $ sudo systemctl status ttn-gateway.service
● ttn-gateway.service - The Things Network Gateway
Loaded: loaded (/lib/systemd/system/ttn-gateway.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2020-02-08 12:42:02 +04; 11min ago
Main PID: 317 (start.sh)
Tasks: 4 (limit: 2200)
Memory: 16.2M
CGroup: /system.slice/ttn-gateway.service
├─317 /bin/bash /opt/ttn-gateway/bin/start.sh
└─686 ./poly_pkt_fwd

Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: ##### 2020-02-08 08:52:55 GMT #####
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: ### [UPSTREAM] ###
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: # RF packets received by concentrator: 0
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: # RF packets forwarded: 0 (0 bytes)
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: # PUSH_DATA datagrams sent: 1 (287 bytes)
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: # PUSH_DATA acknowledged: 0.00%
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: ### [DOWNSTREAM] ###
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: # PULL_DATA sent: 3 (100.00% acknowledged)
Feb 08 12:52:55 ttn-gateway ttn-gateway[317]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)

And after running sudo tcpdump -AUq port 1700 I get,

ttn@ttn-gateway:~ $ sudo tcpdump -AUq port 1700
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:57:54.091133 IP ttn-gateway.52747 > 52.169.76.203.1700: UDP, length 12
E…(u.@[email protected]…+.4.L…B$…s…’…cJ
12:57:54.344801 IP 52.169.76.203.1700 > ttn-gateway.52747: UDP, length 4
E . …@.-…4.L…+…Hd…s.
12:57:55.962624 IP ttn-gateway.54597 > 52.169.76.203.1700: UDP, length 287
E…;u.@[email protected]…+.4.L…E…‘oh.;…’…cJ{“stat”:{“time”:“2020-02-08 08:57:55 GMT”,“lati”:25.31234,“long”:55.49102,“alti”:0,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:0.0,“dwnb”:0,“txnb”:0,“pfrm”:“IMST + Rpi",“mail”:"[email protected]”,“desc”:“LoRaWAN gateway for Smart Campus Mobility System at the American.’…cJ.”}}
12:58:04.221134 IP ttn-gateway.52747 > 52.169.76.203.1700: UDP, length 12
E…(xG@[email protected]…+.4.L…|…’…cJ
12:58:04.538464 IP 52.169.76.203.1700 > ttn-gateway.52747: UDP, length 4
E . …@.-…4.L…+…

After running sudo tail -f /var/log/syslog , I get:

ttn@ttn-gateway:~ $ sudo tail -f /var/log/syslog
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # RF packets forwarded: 0 (0 bytes)
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # PUSH_DATA datagrams sent: 1 (287 bytes)
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # PUSH_DATA acknowledged: 0.00%
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: ### [DOWNSTREAM] ###
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # PULL_DATA sent: 3 (0.00% acknowledged)
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # RF packets sent to concentrator: 0 (0 bytes)
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # TX errors: 0
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: ### [GPS] ###
Feb 8 13:00:56 ttn-gateway ttn-gateway[317]: # Invalid gps time reference (age: 1581152455 sec)

Any and all help will be appreciated :)

ch2i board wiring

with ch2i board used to connect RasPi to ic880a RESET has different pins (namely 11@Raspi instead of 22@Raspi). How can those be changed by software?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.