LTR Analyzer released

[kirchmar]

analyzer...

I just installed this program today and have it running, under the decoding section is says...
avg sampling rate: 22208 modulation: 60-80 (static) 10-30 (talking)

but it is not listing any lcns or groups while they are transmitting...what is wrong?

Also, when analyzing, do you only do one channel at a time or can you scan several 800mhz channels?

 

[slicerwizard]

I'm thinking of it running on older dedicated machines that support '98 OK but nothing above.

You can stop thinking about it and start doing it.

You can download version 1.6 now.

 

[slicerwizard]

I just installed this program today and have it running, under the decoding section is says...
avg sampling rate: 22208

Ouch. That's rather high. Is that after the program has been running for a few minutes?

modulation: 60-80 (static) 10-30 (talking)

but it is not listing any lcns or groups while they are transmitting...what is wrong?

Can you turn up the gain any higher? If you can't get it working, post a short recording (15 seconds of voice) and I'll see if I can get it working.

Also, when analyzing, do you only do one channel at a time or can you scan several 800mhz channels?

You can do it either way.

 

[cg]

you had asked earlier for Multi-Net logs in order to look into adding MN support. Did you get what you needed? I have Passport systems available to monitor as well. Just let me know what files or format you need.

chris

 

[kirchmar]

LTR Analyzer Rev 1.5 (c) W. A. Porrett [wap@ica.net / slicerwizard@gmail.com]


Scanning for audio input devices...

1 audio input device found:

#1 'NVIDIA(R) nForce(TM) Audio': [device supports 22 kHz 8 bit mono input]

Opening device 'NVIDIA(R) nForce(TM) Audio'

Press any key to start decoding.



*** Warning - output is not logged to disk ***

Press '?' for help summary

starting decoding...

+ OSW: 0 13 11 092 26 70 Area=0 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 20 13 095 22 47 Invalid or unknown function
+ OSW: 0 20 13 095 22 47 Invalid or unknown function
+ OSW: 1 31 27 228 01 52 Area=1 Invalid or unknown function
+ OSW: 0 12 31 187 00 0B Area=0 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 26 00 115 30 69 Invalid or unknown function
+ OSW: 1 27 29 250 08 7B Area=1 Invalid or unknown function
+ OSW: 0 31 31 063 29 47 Area=0 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
- OSW: 0 31 31 195 06 27 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
- OSW: 0 29 18 158 23 15 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 26 01 092 23 47 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 26 01 092 23 47 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 23 31 092 22 47 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function


[Help]

Active keys:

I: Toggle Invalid OSW display mode [is ON]
S: Show stats
R: Reset stats
Q: Toggle quiet mode [QM is OFF]
Esc: End program


LCNs seen: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Monitored: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Groups seen: -none-

+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
\ Avg sampling rate: 22190 Hz Modulation: 32%

This is what is in the analyzer box after 3 hours of monitoring....

can anyone help decipher what is means and what I need to do?

 

[slicerwizard]

+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function
+ OSW: 0 13 11 092 26 70 Invalid or unknown function

can anyone help decipher what is means

Um, you're monitoring something other than standard LTR?

 

[slicerwizard]

you had asked earlier for Multi-Net logs in order to look into adding MN support. Did you get what you needed? I have Passport systems available to monitor as well. Just let me know what files or format you need.

chris

22 kHz 8 bit mono WAV files are best. My ISP seems to be able to handle 5 to 10 MB attachments.

 

[DaveH]

You can stop thinking about it and start doing it.

You can download version 1.6 now.

Great, I shall download it immediately, if not sooner...

Dave

 

[DaveH]

Great, I shall download it immediately, if not sooner...

Dave

(>>Fast-Forward>>) (but not to Future Shop )

Program starts without any problem, runs OK, decodes well, gives
useful info...couldn't ask for anything else.

Dave

 

[kd5dga]

I agree it is a good program.

 

[kd5dga]

I posted to the wrong thread;
I found out today the radio makes the big difference. My old pro92 does not provide a good output for the program, but my PRO433 does. I dont see as many error that I would with the PRO92.

 

[Jay911]

I guess I need to make a 'real' tap on one of my scanners. I've never bothered with the 0.1uf cap, because of the lack of availability locally (RS doesn't exist here, and even when they did, didn't have that), so all my scanner taps are just one wire to the tap point and one wire to ground. So LTR Analyzer reports 'overdriven' or however it says the signal is too strong.

 

[snoopyII]

ok so I modified my 785D per the instructions on the RR WIKI page for a discriminator tap. I lauched LTR Analyzer and the the avg sampling rate is right on the money ranging from 22049 to 22051, modulation level on static is at 54% with the +20% gain on, a bit low possibly? And drops to anywhere between 12-50% when receiving. However, its is not decoding anything, not even showing anything. The tap is a .01 μF Ceramic disc capacitor solderd to LND6 FM Det. Out. Just like it shows in the pictures. The scanner is RX clearly, with a fairly strong signal (the audio can be clearly understood), and is displaying a TG ID in the proper LTR form. Is the cap the wrong size? Any Ideas?

 

[Saint]

Discriminator Tap

I guess I need to make a 'real' tap on one of my scanners. I've never bothered with the 0.1uf cap, because of the lack of availability locally (RS doesn't exist here, and even when they did, didn't have that), so all my scanner taps are just one wire to the tap point and one wire to ground. So LTR Analyzer reports 'overdriven' or however it says the signal is too strong.

I have a Pro-2045 scanner and all I have is a wire to the tap point and one to the ground and I have no problem using any of the decoder programs make sure you use windows volume control to tweak the volume on the line in, this may be your problem.
Steve

 

[kd5dga]

The ouput modification to the PRO433 is very similiar to the 785 that SNOOPY II talks about. I did not use a capacitor just a 10k ohm resistor in series with the tap but at the socket and not at the test point. There is no information on the web except for today that I had posted on the pro433. I had alot of homework to do before I made the modification.
Yes, the PRO433 is a uniden made scanner.
Te work took me a hour or two to include the research.
Now I know my pro92 does not give the data that it should and I modified as per instructions.Plus the pro92 (version 3.28)does not trunk LTR as well as the pro433.

 

[Comint]

. . . . The tap is a .01 μF Ceramic disc capacitor solderd to LND6 FM Det. Out. Just like it shows in the pictures. The scanner is RX clearly, with a fairly strong signal (the audio can be clearly understood), and is displaying a TG ID in the proper LTR form. Is the cap the wrong size? Any Ideas?

Well obviously the mod works - at least for Motorola and EDACS - otherwise there would have been numerous complaints before now. However, as has been mentioned iin these forums many times before, a larger value capacitor, such as 4.7uF or 10uF, is better.

A 0.01uF capacitor has a reactance (AC resistance) of approximately 53,000 ohms at 300 Hz, and 5,300 ohms at 3000 Hz, whereas a 10uF capacitor is only 53 ohms at 300 Hz, and 5.3 ohms at 3000 Hz.

Unlike Motorola and EDACS, LTR uses sub-audible tones (below 300Hz) for signalling, so the high reactance of the 0.01uF capacitor, is probably causing excessive attenuation of the low frequency signals from the discriminator tap.

Comint

 

[kd5dga]

I can say I am not electronics wizzard. Thats why I ask questions.
Omitting the capacitor is a good thing to do or subsitute with the values you mentioned?
Would this be good all around if the scanner is used for LTR analyser and other programs like T4WIN and Unitrunker?

 

[Comint]

Omitting the capacitor is a good thing to do

Not really, but others use discriminator taps without a capacitor, and get away with it, without having any obvious problems.

or subsitute with the values you mentioned?

Much better to use a 4.7uF, or 10uF capacitor, in series with a 10k resistor.

Would this be good all around if the scanner is used for LTR analyser and other programs like T4WIN and Unitrunker?

Yes.

--
Comint

 

[nd5y]

It is a good idea to always use a capacitor when hooking up anything to your PC sound card. Especially if it does't have a seperate line out jack.
Usually the sound card mic jack has a DC voltage which is necessary because most PC mics are electret condenser types that require a bias voltage to operate.
You don't want that voltage going into a receiver.

 

[kd5dga]

Tom,
good point with the capacitor. I may insert one this weekend.
So for LTR analyser is running fantastic and with alot less error decoding.I think that the radio makes the difference.
I know this is a little off topic but there should be a forum on radio modification(s)
However I learn allot from radioreference.com