POCSAG/DAPNET setup question

oxoocoffee

Hello,

I like to get some clarity on the "proper" setup of POCSAG/DAPNET.
After getting registered and got password and Auth key, I created a separate profile (for testing)
In the new profile, I selected Quick Setup followed by picking POCSAG/DAPNET.
Then I selected a server from a list and provided my callsign and Auth key I was sent in the email.
Now I can see on the Status page DAPNET with a green icon

So if I understand correctly, now I can select "Stay connected in background" and if I switch to any other profile C4FM, etc I will be getting messages in the background and I would have to switch back to the DAPNET profile to read it? or if I need to send a message?
Or is DAPNET functionality available from other profiles while it is running in the background (reading and sending)?

Also, what does it mean (attached screenshot) IRC: 8? I see these once in a while without sending them.
Where can I read about it?

Also, I did use Telegram POCSAG/DAPNET bot ( https://telegram.me/db0usd_dapnet_bot ) to test a message after I got /auth and followed with /call

oxoocoffee

Here is an update. Not sure if I stumbled into a bug.
After my initial post and connecting to POCSAG, I did least the open spot 4 pro running.
About 3-4 hr later I opened a page again and I see the Status connector connecting, and DAPNET little icon is not green. I did not make any changes. But if that matters, the internet was out since my ISP was at home for service. This was just internet, but the connection to home WIFI was up and OPenSpot was never rebooted by me. When the technician was working outside on the internet line I did hear on my HT, that open sport lost connection to the internet in the look. Not after 25-20 min internet was restored (all work outside of the home). So that is the best description I can provide.

With the initial post above, I did see various extra entries in the log. Now I am only seeing this. I do not see any reconnection log entries or attempts

22:30:51 httpsrv-ws: [0] websocket opened with token b9609e99
22:30:51 httpsrv-ws: [0] websocket opened with token b9609e99
22:30:59 net-chk: ok (19 ms)
22:31:08 pwr: batt 100% 4135mv usb 1500ma cpu 32.4Â°C chg 0ma
22:31:59 net-chk: ok (15 ms)
22:32:08 pwr: batt 100% 4135mv usb 1500ma cpu 32.4Â°C chg 0ma
22:32:59 net-chk: ok (20 ms)
22:33:09 pwr: batt 100% 4139mv usb 1500ma cpu 32.8Â°C chg 0ma
22:33:59 net-chk: ok (17 ms)
22:34:09 pwr: batt 100% 4135mv usb 1500ma cpu 32.4Â°C chg 0ma
22:34:59 net-chk: ok (18 ms)
22:35:09 pwr: batt 100% 4135mv usb 1500ma cpu 31.5Â°C chg 0ma
22:35:59 net-chk: ok (21 ms)
22:36:09 pwr: batt 100% 4135mv usb 1500ma cpu 32.8Â°C chg 0ma
22:36:59 net-chk: ok (22 ms)
22:37:09 pwr: batt 100% 4139mv usb 1500ma cpu 31.1Â°C chg 0ma
22:37:59 net-chk: ok (17 ms)
22:38:09 pwr: batt 100% 4139mv usb 1500ma cpu 31.5Â°C chg 0ma
22:38:59 net-chk: ok (18 ms)
22:39:09 pwr: batt 100% 4130mv usb 1500ma cpu 32.8Â°C chg 0ma

So to make it work, I had to go to Connectors / DAPNET and just press save. No other changes.
Then I started to see extra logs and DAPNET was connected

HA2NON

Please read https://hampager.de/dokuwiki/doku.php?id=faq

oxoocoffee

Ok thank you for the link.
Any information about the second post?

HA2NON

We'll add TCP keepalive handling to help avoiding broken idle connections.

oxoocoffee

Awsome, Thank you

As far as one of my previous questions about enabling it running In background,
Am I correct to assume that I can switch to ther profiles and it will In backgroun under different background?

HA2NON

Each configuration profile represents a different set of settings. If you want to have the DAPNET connector in background in all profiles, then enable its background setting for each profile.

oxoocoffee

Great and thank you !!!
Perhaps it would be good to ass extra comment for clarity in manual?

73

oxoocoffee

Hello

Running v23 beta. When I power on the open spot, the device connects to wifi and ten it is trying to connect to DAPNET. Status states Connection and led is toggling between amber and blue. It sits like this for ever and never connects

Here is the log

14:43:26 httpsrv-ws: [1] websocket opened with token 27f6d71e
14:43:47 pwr: batt 100% est. 30h0m 4107mv usb 0ma cpu 33.7°C chg 0ma
14:43:47 net-chk: ok (21 ms)
14:45:00 httpsrv-ws: [0] websocket opened with token 27f6d71e
14:45:00 httpsrv-ws: [1] websocket opened with token 27f6d71e
14:45:00 httpsrv-ws: [1] websocket opened with token 27f6d71e
14:45:12 httpsrv-ws: [0] websocket opened with token 27f6d71e

In order to connect I have to click Connectors / DAPNET / Save after each power on in order to actually connect. The run in background is checked off

73

Tyrbiter

In order to connect I have to click Connectors / DAPNET / Save after each power on in order to actually connect. The run in background is checked off
If you enable run in background does this help?

If not, then it's a beta and SharkRF will no doubt correct this if it is a bug.

oxoocoffee

i know It beta, that it is why I am testing and reporting
I will try to enable background tomorrow and see how it goes and report

73

HA2NON

Issue has been fixed in (currently beta) firmware v24. Thank you for reporting!

oxoocoffee

HA2NON

It seems to work, but I found another issue. Note if this existed before or was introduced between v23 and v24.

The issue is that for some reason firmware does revert itself.
Here is a scenario I was able to repeat a few times with the same results

I have 4 profiles
1. C4FM
2. BM
3. D-Star
...
10. DAPNET

Initially, I was at profile 1.

1. Go to Settings and enable beta firmware / Save
2. Go to Tools and do a force firmware check followed by an upgrade
3. After download I was still on profile 1.
4. Verify that on Status that v24 was installed
5. Switch profile 10 (to check if the initial bug was fixed). I noticed that it was "connecting" but never finished "connected".
6. Next did go to Connections and press Save and DAPNET connection were established right away.
7. Next I did try to power off and on the unit to see if it will reconnect on cold boot. It was sitting on "connecting for about 5 min". So I pressed Save and again it was able to reconnect.
8. Then I realized that firmware was back to v23 under profile 10
9. So I did try to check for firmware and upgrade again. After the unit was rebooted v24 was shown.
10. Each time I was switching profile firmware was reverted to v23 from v24

So eventually after I did flash v24 for the N-th time, I decided to uncheck "Check beta firmware".
After that it is staying on v24

73

HA2NON

The firmware reverts to the previous version if a reboot happens in 1 minute after the new firmware boots. The new firmware is finalized if the uptime reaches 1 minute.

oxoocoffee

So what you saying, switching too quickly between profiles after flush is considered reboot?

If that is so, then original bug reported is fixed
73

HA2NON

The openSPOT4 reboots when switching configuration profiles.