Hello, I am still working on a P25 decoder. I managed to spend over a week finding out my AR5000 does not pass the P25 waveform cleanly.:mad: 9600 baud EDACS is no problem with the AR5000. It appears there is too much level shifting of the waveform for a clean P25 decode. There is some circuity in the AR5000 between the Discriminator Output and the Demod Output. There is a mod to tap directly off the Discriminator Output. With the bad output I could not get a good decode of the sync bits and data clock recovery did not work well.

DV Dongle AMBE Codec: Potential. Windows Xp Key Generator Activation. I'm wondering if anyone has heard of this thing called the DV dongle. Using some provider driver software and code.

I tried my WinRadio G305e today as a test and the waveforms look a lot better. I still need to feed it through the decoder and see if I can get good decodes. Back to Square One. 73 Eric I can't thank you enough for going to this effort. I suppose the discriminator problem is to be expected if there's not a direct output.

You said back to square one? You can't reuse any of the software code or is this a hardware problem? If you can get a firm yes or no on this I'll be eternally indebted (well especially if the answer is yes) 73 Steve PeterGV 3:48 PM. I actually spent some time exchanging email with the people at DVSI today. According to them, the AMBE-2xxx chips are designed to only decode audio streams from other AMBE-2xxx chips. They will NOT decode an extracted P25 audio stream. While I had always understood the AMBE was backwards compatible with IMBE, the DVSI folks said, very specifically when asked, that the stream formats were different, and that the AMBE-2xxx part would not do P25 audio (assuming you extracted the P25 digital audio and clocked it correctly to the chip).