Hello,
I can not believe it has been almost 5 months since the last beta!
I wanted to get some basic passport support in LTRTrunk before releasing another beta. It is in there but took longer than expected.
I still have no clue on uploading to the downloads section. Sorry for posting files on the forums.
LTRDump Program 5-May-2004 Beta Version
LTRTrunk Version 3.84 beta ec3
These programs are proof-of-concept versions to test
various aspects of LTR decoding. Eventually it will
be part of the Trunker/Etrunk programs.
LTRDump.exe will decode and display LTR information. It also
logs the data to a log file named ltrdump.txt in the same
directory as the program.
LTRTrunk.exe will track regular LTR, LTR-Net, Multinet LTR,
and Passport systems. Most of the Trunker features
like talkgoup and id tagging may even work.
These programs run in DOS and have similar requirements
to eTrunk, the EDACS trunk program. LTRDump.exe is based on
the eedump.exe program version 3.8.3. LTRTrunk.exe is
based on the etrunk program version 3.8.3.
Changes since the last release (beta ec2)
More changes to improve the program. Tuned the timing values and
decoder.
LTRDump
Time stamp and version info are added similar to other trunker dump
programs.
Passport check is done. Some values are guessed at so DCC (Area)
values other than 0 and some id values may not decode.
LTRTrunk
System ID is calculated and used. For regular LTR it is 0000 for
Area 0 and 0001 for Area 1. For Multinet it is calculated from
the xor masks since they should be unique to the system. For
Passport it is the Site ID of the system in Hex added to
the DCC (Area) times 1000 hex so 100A is a DCC of 1 with a
site id of 10 (decimal). System ID is filtered and can change
under some conditions.
Fixed problems with calculated 800 MHz and 900 MHz Multinet
frequencies.
Added basic Passport decoding (Finally!!!!).
Fixed crashing when decoding LTR systems due to noise causing the
system type to change. After the system id is determined the mode
is locked. To track another system save and exit.
Known Problems - LTRDump
Decoding of information is very basic. It will decode Regular
LTR and Multinet. The automatic LTR type detection really only
works on transmissions and not on bursts.
Some check values of Passport are guessed at. Some packets and
DCC (Area) values other than zero may not be decoded.
LTR-Net detection only works on a idle system.
Multinet and Passport frequency display is done modulus 31 so it
is possible for frequency information to be displayed on top of
other frequency information.
Known Problems - LTRTrunk
Decoding of information is very basic. It will decode Regular LTR,
Multinet, and Passport. CW-ID and extended commands may show up as
a talkgroup.
The system id (site id) of a passport group id is not used. This may
cause a local group to be merged with one or more different groups
from another site. The mobile unit id is not used.
If multiple systems share a frequency or errors occur then the
system type can change and collected information can be lost.
Some check values of Passport are guessed at. Some packets and
DCC (Area) values other than zero may not be decoded.
Frequencies for Passport are not automatically calculated yet.
A workaround is to use plan 0 and create a map file for each site.
No filtering of Regular LTR and Passport packets to reduce noise
being decoded as valid data. This will be looked at more as basic
decoding progresses.
73 Eric
I can not believe it has been almost 5 months since the last beta!
I wanted to get some basic passport support in LTRTrunk before releasing another beta. It is in there but took longer than expected.
I still have no clue on uploading to the downloads section. Sorry for posting files on the forums.
LTRDump Program 5-May-2004 Beta Version
LTRTrunk Version 3.84 beta ec3
These programs are proof-of-concept versions to test
various aspects of LTR decoding. Eventually it will
be part of the Trunker/Etrunk programs.
LTRDump.exe will decode and display LTR information. It also
logs the data to a log file named ltrdump.txt in the same
directory as the program.
LTRTrunk.exe will track regular LTR, LTR-Net, Multinet LTR,
and Passport systems. Most of the Trunker features
like talkgoup and id tagging may even work.
These programs run in DOS and have similar requirements
to eTrunk, the EDACS trunk program. LTRDump.exe is based on
the eedump.exe program version 3.8.3. LTRTrunk.exe is
based on the etrunk program version 3.8.3.
Changes since the last release (beta ec2)
More changes to improve the program. Tuned the timing values and
decoder.
LTRDump
Time stamp and version info are added similar to other trunker dump
programs.
Passport check is done. Some values are guessed at so DCC (Area)
values other than 0 and some id values may not decode.
LTRTrunk
System ID is calculated and used. For regular LTR it is 0000 for
Area 0 and 0001 for Area 1. For Multinet it is calculated from
the xor masks since they should be unique to the system. For
Passport it is the Site ID of the system in Hex added to
the DCC (Area) times 1000 hex so 100A is a DCC of 1 with a
site id of 10 (decimal). System ID is filtered and can change
under some conditions.
Fixed problems with calculated 800 MHz and 900 MHz Multinet
frequencies.
Added basic Passport decoding (Finally!!!!).
Fixed crashing when decoding LTR systems due to noise causing the
system type to change. After the system id is determined the mode
is locked. To track another system save and exit.
Known Problems - LTRDump
Decoding of information is very basic. It will decode Regular
LTR and Multinet. The automatic LTR type detection really only
works on transmissions and not on bursts.
Some check values of Passport are guessed at. Some packets and
DCC (Area) values other than zero may not be decoded.
LTR-Net detection only works on a idle system.
Multinet and Passport frequency display is done modulus 31 so it
is possible for frequency information to be displayed on top of
other frequency information.
Known Problems - LTRTrunk
Decoding of information is very basic. It will decode Regular LTR,
Multinet, and Passport. CW-ID and extended commands may show up as
a talkgroup.
The system id (site id) of a passport group id is not used. This may
cause a local group to be merged with one or more different groups
from another site. The mobile unit id is not used.
If multiple systems share a frequency or errors occur then the
system type can change and collected information can be lost.
Some check values of Passport are guessed at. Some packets and
DCC (Area) values other than zero may not be decoded.
Frequencies for Passport are not automatically calculated yet.
A workaround is to use plan 0 and create a map file for each site.
No filtering of Regular LTR and Passport packets to reduce noise
being decoded as valid data. This will be looked at more as basic
decoding progresses.
73 Eric