With no schematics available how would an add on board ever be developed without some extensive reverse engineering?
So Unidens have reference clocks that are so jittery and/or off-frequency that they can't handle slow 4800 or 6000 baud symbol streams? And fixing the clock will yield a 50% improvement? This is what you're suggesting? Are you aware that software decoders (TRUNK88, UT, DSD+, ...) don't even have reference clocks? No offense, but you're sounding as far off base as the thread starter.
Then where would your maybe 50%?? improvement come from? Sounds like you're trying to move the goalposts.I never stated that the Uniden referece was so jittery and off-frequency.
These days, we record audio files, upload and download them, then feed them to DSD+; why would DSD+ think "Hm, I'd better check the PC's time base every now and then as I munch through this audio data... Wait a sec, what am I checking for?"Kind of funny how you state that software decoders have no base clock, maybe they don't but I would bet that the software decoders use the computers time base as a trigger.
Well, I can post links to some raw audio files that DSD+ will decode perfectly. The only clock involved is the sound hardware's sampling clock, and those are anything but precise. LTR Analyzer, for example, uses 22 kHz sampling (22050 Hz), but due to driver bugs, sound hardware might actually serve up 22222 Hz or 21600 Hz audio (a whopping 2% error), but LTR Analyzer just plods on, serving up clean decodes. TRUNK88 does the same thing with 3600 bps data - 21600 Hz sampled audio decodes just as well as 22050. So a super-accurate clock isn't a requirement.Almost ANY RF or data circuit had some form of reference clock, not sure how the world would work without one.
You'll be generating data? You'll have a repeatable RF input to the radio for your A/B testing and you'll be extracting BER measurements from the radio via a serial or USB connection? Or will you just be using your Mark I ear? Can it hear a 5-10% improvement? (I doubt it...)I am short on time at the moment, but when I get a chance I will investigate the base clock and maybe try a more stable reference JUST to see what happens. Maybe NOTHING, maybe an improvement, let the data speak for itself.
You'd be well on your way to a 50% improvement if you discovered that Uniden didn't implement Golay FEC on IMBE voice frame data, but alas, they already do. But your clockwork won't find any firmware bugs, even if those that may exist.I dive in head first with no bias about how something should be programmed or configured and if they there is menu or a button I am tying all options. Kind of funny how in as little as 5 minutes I may have painted myself in the corner using the tools, settings and options that are provided and then when I flag something, the software/firmware/developers look at me and say "your not supposed to do that"!!!
Well if the configuration, menus or software options allow me to paint myself into the corner, then there is a problem with the configuration, menus or software!!! Something is not right and there are not enough checks and balances.
Fine by me. It's your time to do with as you see fit. Seriously, there is nothing wrong with experimentation, so go for it, but let's keep our expectations realistic...When I have time, I WILL be playing with the base clock, using a more stable time base reference as well as seeing what else I can find good, bad or indifferent.
Or perhaps you're just delusional - and a terrible speller, BTW. Your "maybe we need GPS receivers in scanners" idea shows just how unqualified you are to make any technical judgments. Honestly, I have to ask if you and James are Dunning–Kruger candidates?Perhaps we are stumbling on "something sensitive" and the cann't-doers or otherwise do-not want us to go down these paths of reasearch - hummm - unlikely but pausable....
Of course you don't. Unlike you, some of the posters in this thread have made significant contributions to the hobby.And ask yourself: What have you done or tried to do to improve our Hobby? ( and really don't want your response
Lovely straw man you have there; be sure to keep it away from flames or logic. God forbid that anyone who wants to see LSM improvements should point out when others are blindly stumbling down dead end paths.Finally - if you are indeed Happy and Content with the Status Quo and do not want or care about improve possibilities, then why bother even responding
Of course we shouldn't have to, but this thread is about "I can't wrap my head around how a CQPSK signal is badly handled by an FM demodulator wrt translating +/-45 and +/-135 degree phase shifts into 4 discrete audio levels suitable for dibit extraction, so I think a better timing reference on the RX side will magically fix that particular problem as well as undo the timing slews that simulcast and multipath impart to the RXd signal", so you're off topic dude.my point is WHY should I or any owner of a brand new product advertised as supporting P25 have to modify, accessorize or reverse engineer something to get it to do what should be it's basic functionality?
It actually gets worse then that... read my post about their new squelch table solution.. mind boggling. They're trying to fix this by holding the squelch open consistently.I saw in some other thread that the newer models still have a P25 Waiting Time setting; is that true? If so, that's utterly ridiculous and just another indicator of how badly Uniden is failing at digital. Say it ain't so.
It actually gets worse then that... read my post about their new squelch table solution.. mind boggling. They're trying to fix this by holding the squelch open consistently.
Thanks Joe and perhaps someone can offer to look and those solutions you pose as my hope was to spur ideas and perhaps get the Next Gen folks looking at various methods, which some have outlined prior..
Funny a few years ago SDR was thought to never be available due to cost and compute power - now for $20 you get a USB and free software..
Thx
Bill
Your observations on the HP1 should tell you immediately that the problem isn't with any timing mechanisms at all. Symbols can be recovered in software without any timing reference of the site controllers themselves. But you have to have the right hardware to do it. There is no way to fix this without a complete redesign of the radio. Once the right hardware is in place, you then need some cleaver software to take advantage of said hardware.Agree with your comments and I only have the HP-1 and must also go to Full Open just to get an OK reception...hence my impossible quest to se if any possible improvement could be used as a work-around to gain another 25% (just a number) better signal without going to a Yagi...
Max is a very smart fellow, and so is slicerwizard. You shouldn't be so dismissive of his opinions.I understand the coding issue as Max made it clear in another post ... was a great post..as I am not a P25 SME...
You'd be better off using the old GRE based receivers of the nineties. Those radios were modular in their design. You could probably control the RF section with an Arduino. The schematics for all those radios are also freely available online. Without one, you're pretty much dead in the water. In the unlikely event you obtained one for a Uniden radio, you would still need to make changes in the firmware. It is hackable however..The first is to design and implement an add-on board using either DSP or CML Micro chips that re-modulates CQPSK to C4FM that can bypass the radio's last IF.
SDR# made some changes to their plugin code recently. Those changes open up a huge opportunity for scanner type functionality via SDR hardware. Things are going to get interesting real soon...The other would be to build our own software (maybe using SDR) that would incorporate correct handling of CQPSK for P25 and also add support for DMR, NXDN, conventional and trunk following, and even the proper handling of narrowband 12.5 KHz with 2.5 KHz deviation audio levels.