DAPNET pager setup seems to be working, up to a point. I'm seeing messages directed to the "us-mi" gateway (good), and seeing transmissions on my pi-star (good), but the Flipper Zero isn't hearing them (bad).
My best bet is that the pi-star is a little off frequency compared to the Flipper Zero and that I'll need to tweak the calibration. Time to get the SDR out to see what I can see.
If you are on DAPNET please page me at "w8emv" via "us-all" or "us-mi".
wait, my #pistar has #POCSAG tx support!
some details at
https://einstein.amsterdam/?page_id=2130
Ticket open with DAPNET, since it's entirely possible that I could make this all work once I get all of the accounts configured.
#DAPNET #flipperzero #F0 #pocsag #pistar
The POCSAG pager receiver for the Flipper Zero is from xMasterX and the code is here
https://github.com/xMasterX/flipper-pager
It's tuned by default to the DAPNET Web frequencies, which are in the ham 70cm band, on 439.987500 MHz.
There is a worldwide DAPNET network, but (alas) the closest existing one to me on the map is in Toledo Ohio, unlikely that I'll hear any signals from there.
https://github.com/DecentralizedAmateurPagingNetwork
(add to the project list)
#pager #pocsag #DAPNET #flipperzero #F0
Installed the "Dark Flippers" version of the Flipper Zero firmware, called "Flipper Zero Unleashed".
https://github.com/DarkFlippers/unleashed-firmware
So far it looks like a pretty good distribution - not a lot of visible UI changes, a bunch of additional applications, including a simple "spectrum analyzer" that expands into the 70cm band and a POCSAG pager receiver.
Now to read a bunch of documentation / mash some buttons to see what they do.
[ #FlipperZero #f0 ]
0
Detecting F measurement jumps
https://asa.scitation.org/doi/10.1121/10.0015045
"If you've worked with time-series f0 measurements, you know that sudden discontinuities in f0, due to consonantal junctures, non-modal phonation etc., are quite common. Maybe you want to identify places where these occur .... Maybe you're curious about the files with sudden jumps ... Either way, this R script will help you identify f0 jumps in a time series f0 measurement" https://github.com/jsteffman/f0-jumps #F0 #jumps #measure
0
Detecting F measurement jumps
https://asa.scitation.org/doi/10.1121/10.0015045
"If you've worked with time-series f0 measurements, you know that sudden discontinuities in f0, due to consonantal junctures, non-modal phonation etc., are quite common. Maybe you want to identify places where these occur .... Maybe you're curious about the files with sudden jumps ... Either way, this R script will help you identify f0 jumps in a time series f0 measurement" https://github.com/jsteffman/f0-jumps #F0 #jumps #measure
@tty @d6 Ah! I think I understand what you're asking.
So, this whole thing doesn't require any change to the assembler. It uses just an old boring ;label reference.
That label can be named anything, the ;meta #f0 DEO2, is kind of like setting a vector, but we're not worrying about that right now, #f0 is a non-specified device in Varvara.
The assembler sees ;meta, and write the position of the @meta label, which could be any other name too.
https://git.sr.ht/~rabbits/drifblim/tree/main/item/src/drifblim.tal#L446
@tty @d6 The metadata is part of the rom.
https://git.sr.ht/~rabbits/nasu/tree/main/item/src/nasu.tal#L1389
The #f0 is only so the emulator can also become aware of that metadata. For example, to rename the window, to draw an icon, etc..
@d6 I think what I would do is instead of a header, is expect the first bytes to be LIT2 $2 #f0 DEO2, and use the second and third byte to locate the address of the meta data.
Nasu would begin like
|0100 ( -> ) ;about #f0 DEO2
https://git.sr.ht/~rabbits/nasu/tree/main/item/src/nasu.tal#L1387