-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected address 002029569
for FLEX message in 1.1.8
#191
Comments
My thoughts: it missed the set of instructions. Aka the frame that became prior to this group message. Recently (6 days ago) my long running setup also started missing messages. It turned out they have changed something to the P2000 paging network. The signals came in much stronger than usual and overloaded the SDR. I made recordings with rtl_fm and sox with various gain settings to pick the right one. |
@bierviltje are you running v1.1.9? I would be interested in how you did the fine tuning. Maybe via a Twitter DM if you use Twitter? My |
Edit: Please discard my previous comment, I came to the conclusion I was running on 1.1.8 as well without knowing. Yes this issue is fixed in 1.1.9 |
Not sure if this has been mentionec anywhere but FLEX offers up to 16 groupcodes, in the range 2025968-2029583 Since there can be multiple groupcalls at the same time, these groupcalls need to be seperated somehow. The first groupcode is always 2029568. The busier the networks becomes, the higher the groupcode. So if this application only supports 2029568, it really has to support all 16 groupcodes in order to receive all groupcalls. |
I received the following via MNG 1.1.8:
This is unexpected and some googling results state that
002029569
is a group message. I see that 1.1.9 has the following change mentioned:I expected several other addresses to show. Is this fixed in 1.1.9 or have I misconfigured MNG? I expected a list of addresses instead of
002029569
.I know that the following addresses are a somehow available as they are listed on a website:
The text was updated successfully, but these errors were encountered: