Skip to content
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

POCSAG/DAPNET Support #118

Open
6 of 10 tasks
travisgoodspeed opened this issue Apr 14, 2019 · 4 comments
Open
6 of 10 tasks

POCSAG/DAPNET Support #118

travisgoodspeed opened this issue Apr 14, 2019 · 4 comments
Assignees

Comments

@travisgoodspeed
Copy link
Owner

travisgoodspeed commented Apr 14, 2019

Use this issue to track development of a POCSAG receiver, intended for use on Dapnet at 439.9875 MHz.

Progress:

  • Correct modulation, SYNC.
  • Receiving frames.
  • Decoding frames to recover meaningful text.
  • Standalone applet.
  • Power budget calculations.
  • Preamble polling to sleep between transmissions.
  • Checksum bit support.
  • Long Packet Support (Long Packet Support #107)
  • Error correction works.
  • Documentation checked for accuracy in source code and wiki.
@travisgoodspeed
Copy link
Owner Author

travisgoodspeed commented Apr 15, 2019

Successfully decoding packets with some code that is far too ugly to commit! Next free weekend should see proper support in the main branch.

@travisgoodspeed
Copy link
Owner Author

The power situation is pretty dire: We spend 16mA while actively listening, exhausting the coin cell in only six hours! As a temporary solution, I'm exiting the pager app when no packets have been seen for three minutes. Later, we can match the transmitter's timeslot to sleep between packets, hopefully extending usage to more than a day.

travisgoodspeed added a commit that referenced this issue Apr 20, 2019
…t eight letters of message, doesn't trigger display at the right moment. #118
@travisgoodspeed
Copy link
Owner Author

This module is still a work in progress, but documentation is up on the wiki.
https://github.com/travisgoodspeed/goodwatch/wiki/POCSAG

As far as power management goes, it looks like we can definitely reduce consumption from 16mA to slightly more than 1mA by keeping the radio in IDLE except when periodically sampling for the 480ms preamble. This will also fix the LCD fade out problem on CC430F6137-based watches, and depending on the settling time, we might be able to get even better lifetimes by shutting the radio off entirely between preamble-samplings.

travisgoodspeed added a commit that referenced this issue May 11, 2019
travisgoodspeed added a commit that referenced this issue May 11, 2019
@travisgoodspeed
Copy link
Owner Author

Average draw is down the 4mA by polling for the preamble, and that might be made a bit list. We're up to 24 hours of battery life.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant