Yes, resetting the 831 should do the trick. I found out that in start.sh which is called during system startup (systemd ttn-gateway.service) this is actually done before starting to talk to the device. The problem was that this script uses RPI GPIO pin 22 but the converter board which is part of the starter kit uses pin 17.
Unfortunately I could not find any documentation for the converter board and I saw the information concerning pin 17 as a side remark in one of the tutorials.
Once changing the pin configuration now the board heats again and it connects to ttn after each reboot as expected. Communication with the WisNode also works fine.
Thanks for your help
Can you remove/ cut one side of strip? Why we don’t remove because heat sink is same dimension of entire converter board but can’t fit inside enclosure! If you buy enclosure, you just need remove one side strip and don’t put heat sink on top! We have another thermal filter for you.!
In addition, to help you cut the one side strip, Pls use tweezers and cutter to remove one side strip,passed cutter over border to make it easier to snap, and snapped it with tweezers. the tools we recommend to use below one
I apologize now didn't see your question, what is your configuration of this module is not understand place, please refer to this url(link text) if there is doubt please reply here or send us E-mail, we will give you a reply as soon as possible
After that, I was able to continue up to Step $5.
There, I have an error when I try
pi@RAK831:~/RAK831_LoRaGateway-master/lora_gateway/libloragw $ sudo ./test_loragw_reg
./test_loragw_reg: error while loading shared libraries: libmpsse.so: cannot open shared object file: No such file or directory
After all it turns out not to be a problem with the gateway! I tested the gateway yesterday with a non RAK end node and it works perfectly. The problem is somehow related to the software on the RAK end-nodes. With 2 RAK end devices not working I got lead down a wrong past.
I will now try to solve the end node problem which is most likely a specific 915_AU frequency configuration problem.