Like Aleksander Nowakowski mentioned the "nRF Master Control Panel for Android" does recognise the UID, URL and TLM frame. It was a great help for validating the beacon.
As mentioned, the code is provided as is, but could be a starting point. I'm going to order a nRF52 kit and see if I find some time to port it the the new chip.
Hi again, nRF MCP should also parse and display TLM packets. At least it has been implemented :) The thing may be that the beacon transmits one TLM packet every few seconds and it is not visible on the main screen (which is refreshed every second with the most current packet before the timer fires) but you could be able to press the MORE button and see all historical packets from the device. The TLM packet should be visible there. I hope that was the issue, not the implementation.
Hi again, nRF MCP should also parse and display TLM packets. At least it has been implemented :) The thing may be that the beacon transmits one TLM packet every few seconds and it is not visible on the main screen (which is refreshed every second with the most current packet before the timer fires) but you could be able to press the MORE button and see all historical packets from the device. The TLM packet should be visible there. I hope that was the issue, not the implementation.
