-
-
Notifications
You must be signed in to change notification settings - Fork 678
Pocsag did not recognize the bitrate right #2546
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
Comments
same here... thru the first 1s buzz from the signal, it sets to 512bit...it worked randomly once and detected right, could See the message. H4M. |
Which firmware version ? |
Tested with 2.1.0 and the actual nightly. Behaviour is the same |
Same here. Maybe a quick fix would be the possibiltity to manually select the baud rate in addition to the automatic detection? |
Still no Updates 🤔 |
No, but you can get your hands on it maybe ? |
Hi, Time ago, you had to choose 1200 or 2400 Baud in Config page. I regret this time too. An easy way could be to come back to this manuel choice, why not "auto/1200/2400". |
Describe the bug.
Pocsag thinks it´s a 512 bit transmission, but it´s a 1200 bit one
Reproduction
Switch on, goto Pocsag app
Expected behavior
Finest Decoding
Environment/versions
No response
Anything else?
We have 3 main transmitter for pocsag in germany. the have some sort of preamble which let Pocsag think it´s a 512 bit transmission. After that preamble pocsag sticks onto that speedrate. But the transmission comes with 1200. This leads to complete undecoded messages, all violet.
If i switch right after the preamble to that frequency the speedrate will be recognized right and decoding works fine.
The text was updated successfully, but these errors were encountered: