slicerwizard
Member
If you weren't monitoring two independent systems, it just means some noise was falsely decoded as an OSW. It happens from time to time.
Because bad decodes happen from time to time. The LTR protocol has a very weak error detection mechanism.Sometime in your program i saw LCN and ID that i didn't see in my 996t, why???
It's in the manual.and sometime i saw 04-123 lcn=4 ATB What ATB meen?
The 996 needs a tap.will this work with out any modifications to the 996T or do I need to have someone build me tap for it?
On Motorola mobiles (MaxTrac, GTX, etc.), the signal is on pin 11.Can you run it off professional grade radios if I gave you a diagram picture some where in the connector layout I think I might be able to pull a feed from it
Does this application support the PSR500 PC/IF output?
System Requirements
-------------------
- operating system:
LTR Analyzer seems to play well with:
- Windows 98 (FE and SE)
- Windows 2000
- Windows XP
- Windows Vista
- sound hardware capable of supporting
(or of being emulated by the Windows multimedia subsystem),
22 kHz 8 bit monaural (single channel) input audio sampling
- RF receiver (e.g. a scanner) with a discriminator tap installed
- this version of LTR Analyzer is optimized for discriminator outputs
and will not decode audio from a headphone jack
- an audio cable to connect the received audio to the PC sound hardware
(e.g. a discriminator to microphone input patch cable)
If you're using a scanner that spits out decoded frames on the serial port, you already have most of the information that LTR Analyzer generates from raw audio. So if your PSR500 says, for example, group 1-123 is active on LCN 5 and LCN 9 is free, what can LTR Analyzer add to that?Does this application support the PSR500 PC/IF output?
Slicerwizard,That signal is not from an LTR system. It sounds more like telemetry data.