LTR Analyzer released

[slicerwizard]

Just in time for Christmas, LTR Analyzer 1.0.

- decodes LTR datastreams via sound card

- determines LCNs for each system channel

- low CPU usage

- comes with a 700 line user manual / LTR tutorial


Requirements:

- Win32 (XP or Vista)

- Windows-compatible PC sound hardware

- discriminator-tapped receiver

- 2008 Lamborghini Reventon (optional, but couldn't hurt)


Linky: http://home.ica.net/~phoenix/wap/LTR/

[Saint]

I have been using this program for two hours and it seems to be working OK I have found LCN Order for 5 frequencies so far and have used the program on several other LTR Systems that I know the LCN Order of the frequencies and it is verifying them correctly.
Steve

[pro92b]

I plugged my PRO-2006 straight into the laptop running Windows 2000 and LTR Analyzer worked fine immediately. No resistors in the cable, unsupported operating system - why did I not have endless problems?

There are two minor issues. On all systems here that broadcast a CW ID group 253 is used. I think this is universal for LTR. The program reports unknown or invalid function. Oh, and my spell checker says you spelled signaling wrong in the doc.

Thanks for a great program!

[crayon]

Awsome! Lots of information in the .txt too. Well done.

[slicerwizard]

Originally Posted by pro92b

I plugged my PRO-2006 straight into the laptop running Windows 2000 and LTR Analyzer worked fine immediately. No resistors in the cable, unsupported operating system - why did I not have endless problems?

You must not be doing it right. Keep at it - I'm sure you'll figure it out!

There are two minor issues. On all systems here that broadcast a CW ID group 253 is used. I think this is universal for LTR. The program reports unknown or invalid function.

Could you post a sample from the log?

Oh, and my spell checker says you spelled signaling wrong in the doc.

American Heritage Dictionary

signal n. 1. a. An indicator, as a gesture or mechanical device, serving as a means of communication. b. A message communicated by such means. 2. Something that incites action: The execution was the signal for mass protests. 3. Electronics. An impulse or fluctuating electric quantity, such as voltage, current, or electric field strength, whose variations represent coded information. 4. The sound, image, or message transmitted or received in telegraphy, telephony, radio, television, or radar. a signal flare. -adj. Out of the ordinary; conspicuous: a signal feat. -v.-naled -naling -nals or -nalled or -nalling or -nals -tr. 1. To make a signal to. 2. To relate or make known by signals. -intr. To make a signal or signals. [Fr. < OFr. < Med. Lat. signale < Lat. signalis,
of a sign < signum, sign.] signaler n.

Thanks for a great program!

No prob! Now I have to add PassPort...

[pro92b]

Here's the full log during the CW ID which I was listening to while logging.

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

Opening device 'Crystal WDM Audio'


12/21/2007 16:58:11  starting decoding...

12/21/2007 17:00:45   + OSW: 0 02 02 253 01 33   Area=0  Invalid or unknown function
12/21/2007 17:00:45   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:45   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:45   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:45   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:45   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:46   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:46   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:46   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:46   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:46   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:46   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:46   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:47   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:47   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:47   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:47   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:48   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:48   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:48   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:48   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:48   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:49   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:49   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:49   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:49   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:50   + OSW: 0 02 02 253 01 33  Invalid or unknown function
12/21/2007 17:00:50   + OSW: 0 02 02 255 02 32  IDLE  LCN=2

[slicerwizard]

All fixed in version 1.1: http://home.ica.net/~phoenix/wap/LTR/

[nd5y]

Cool!!! This is s great!!! The only problem I have found is that it won't decode the data burst every 10 seconds on most channels, but I can't tell if that is a software or audio problem.

[pro92b]

The document mentions that transmitter timing is critical in sending a good idle burst. Andy's program does better than Eric's or my PRO-97 in catching the idle burst. But as you have found, some channels just can't be decoded.

Andy: Have you considered filtering repeater numbers to suppress false hits? Here is one example I logged:

+OSW 0 25 00 189 01 48 Invalid or unknown function

It is correctly flagged as invalid but it might be better to not display it at all. I believe invalid goto is 00 and 21-30, home is 00 and 21-31, and free is 21-31.

[kd5dga]

I love it.
Show alot of information.

[nd5y]

What are Andy's and Eric's programs?

[kd5dga]

To log from the program you mentioned running from the command prompt.
To understand I have no Idea to run from the command prompt. LTR Analyser is under my
C:\LTR ANALYSER. When I run the command you had said under the documentation I get a invalid command.
Can you give me a easy way to run under prompt?

[pro92b]

Click Start | Programs | Accessories | Command Prompt
Type C:\LTR ANALYSER\LTR-ANALYZER.EXE>LOG.TXT

[kd5dga]

This is what I get after I put that command line in;
LTR' IS NOT A RECOGNIZED INTERNAL OR EXTERNAL OPERABLE PROGRAM OR BATCHFILE.
I must be doing something wrong.
I vaigly remember under windows 98 in the command prompt that some programs required a setting change to make them run under command prompt. I am using windows XP home edition.

[pro92b]

Probably the path is wrong. Is the folder named LTR ANALYSER? You do need to have the folder name exactly right in the command.

Try this in the command prompt:

CD\
CD LTR ANALYSER

Does it find the folder? If not the folder name is wrong.

[Saint]

Originally Posted by kd5dga

This is what I get after I put that command line in;
LTR' IS NOT A RECOGNIZED INTERNAL OR EXTERNAL OPERABLE PROGRAM OR BATCHFILE.
I must be doing something wrong.
I vaigly remember under windows 98 in the command prompt that some programs required a setting change to make them run under command prompt. I am using windows XP home edition.

I have Windows xp home and I can get the program to run by going to the directory I have the program in and double click on LTR-Analyzer.exe and the program starts. Can you try this and see if you still have a problem ???
Steve

[slicerwizard]

Originally Posted by pro92b

Click Start | Programs | Accessories | Command Prompt
Type C:\LTR ANALYSER\LTR-ANALYZER.EXE>LOG.TXT

Because he put a space in his folder name, he needs to quote it:

Start / Programs / Accessories / Command Prompt

CD "\LTR ANALYZER"

LTR-ANALYZER >LOG.TXT


He could save himself some typing by creating a shortcut with the following properties on his desktop:

Target: %SystemRoot%\system32\cmd.exe

Start in: "C:\LTR ANALYZER"


That would start him off in to the right folder.

[slicerwizard]

Originally Posted by nd5y

Cool!!! This is s great!!! The only problem I have found is that it won't decode the data burst every 10 seconds on most channels, but I can't tell if that is a software or audio problem.

If you record the audio (you can use Windows' Sound Recorder program) and post it here, I'll investigate.

[slicerwizard]

Originally Posted by pro92b

Andy: Have you considered filtering repeater numbers to suppress false hits? Here is one example I logged:

+OSW 0 25 00 189 01 48 Invalid or unknown function

It is correctly flagged as invalid but it might be better to not display it at all. I believe invalid goto is 00 and 21-30, home is 00 and 21-31, and free is 21-31.

I have seen references on the net to various uses for some of those invalid LCN's, so I'd rather not limit what the program can display. For systems that don't use any unknown extended functions, I could see adding a switch (either on the command line or with a keyboard code - or both) to disable the "unknown function" display.

[kd5dga]

Ok I got it to work but once the decoding starts then windos displays a error report and the program shuts down.This is only at the command prompt.
I had found the right target.