Hello,
This version should decode Passport systems using DCC codes of 2 and 3.
The LTRDump screen and logfile format is improved. Better display of data. I was able to figure out some more Passport protocol stuff. Frequencies will be displayed or logged if they can be determined.
LTRDump Program 10-Nov-2004 Beta Version
LTRTrunk Version 3.84 beta ec4
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, Multi-Net 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 ec3)
More changes to improve the program. The majority of the work
was done to LTRDump this release.
LTRDump
Passport check is done! The last bits are determined (hopefully).
For Multi-Net and Passport the radio ID (if available) is displayed
to the right of the talkgroup prefixed by a RID: label.
Added frequency calculation to Passport only. No all bands are
supported and some bands may be improperly calculated. The
frequency is displayed to the right of the talkgroup/RID info.
Change the log file format. Frequencies will be used if available.
The Passport neighbor message has a new format:
DCC:0 450MHz N:1 S:70 RI Nbr-> 450MHz N:1 U 463.88750
The left section, before the "Nbr->" gives the site information
showing the band, network id, site id, etc. The right side gives
the neighbor information showing the band, network id, and
frequency (or LCN). The example shows this site is on the 450 MHz
Band with a network id of 1 and site number of 70. The "R"
indicates this is a registration frequency. The "I" indicates an
idle channel and is replaced with a "B" if the channel is busy.
The neighboring site is also on the 450 MHz band with a network id
of 1 and a frequency of 463.8875. The U is for a bit with an
unknown purpose. If None appears instead of a frequency or LCN
then the site either has no neighbors or no neighbor information
was defined. I noticed some sites will only send neighbor
frequencies on some of the site frequencies.
Minor fixes
LTRTrunk
Passport check is done! The last bits are determined (hopefully).
Added frequency calculation to Passport only. No all bands are
supported and some bands may be improperly calculated. Use plan
0 to override.
The Affilate and Neighbor information logging works. It will
also show frequencies. A Affilate message showing the home
channel assignment is added.
Minor fixes
Known Problems - LTRDump
Decoding of information is very basic. The automatic LTR type
detection really only works on transmissions and not on bursts.
LTR-Net detection only works on a idle system.
ESAS is not detected or decoded.
Multi-Net 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,
Multi-Net, 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.
Sometimes the system id will come up as 0000 or 0001 instead of
the site number based system id. Restarting the program usually
fixes it.
If multiple systems share a frequency or errors occur then the
system type can change and collected information can be lost.
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
This version should decode Passport systems using DCC codes of 2 and 3.
The LTRDump screen and logfile format is improved. Better display of data. I was able to figure out some more Passport protocol stuff. Frequencies will be displayed or logged if they can be determined.
LTRDump Program 10-Nov-2004 Beta Version
LTRTrunk Version 3.84 beta ec4
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, Multi-Net 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 ec3)
More changes to improve the program. The majority of the work
was done to LTRDump this release.
LTRDump
Passport check is done! The last bits are determined (hopefully).
For Multi-Net and Passport the radio ID (if available) is displayed
to the right of the talkgroup prefixed by a RID: label.
Added frequency calculation to Passport only. No all bands are
supported and some bands may be improperly calculated. The
frequency is displayed to the right of the talkgroup/RID info.
Change the log file format. Frequencies will be used if available.
The Passport neighbor message has a new format:
DCC:0 450MHz N:1 S:70 RI Nbr-> 450MHz N:1 U 463.88750
The left section, before the "Nbr->" gives the site information
showing the band, network id, site id, etc. The right side gives
the neighbor information showing the band, network id, and
frequency (or LCN). The example shows this site is on the 450 MHz
Band with a network id of 1 and site number of 70. The "R"
indicates this is a registration frequency. The "I" indicates an
idle channel and is replaced with a "B" if the channel is busy.
The neighboring site is also on the 450 MHz band with a network id
of 1 and a frequency of 463.8875. The U is for a bit with an
unknown purpose. If None appears instead of a frequency or LCN
then the site either has no neighbors or no neighbor information
was defined. I noticed some sites will only send neighbor
frequencies on some of the site frequencies.
Minor fixes
LTRTrunk
Passport check is done! The last bits are determined (hopefully).
Added frequency calculation to Passport only. No all bands are
supported and some bands may be improperly calculated. Use plan
0 to override.
The Affilate and Neighbor information logging works. It will
also show frequencies. A Affilate message showing the home
channel assignment is added.
Minor fixes
Known Problems - LTRDump
Decoding of information is very basic. The automatic LTR type
detection really only works on transmissions and not on bursts.
LTR-Net detection only works on a idle system.
ESAS is not detected or decoded.
Multi-Net 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,
Multi-Net, 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.
Sometimes the system id will come up as 0000 or 0001 instead of
the site number based system id. Restarting the program usually
fixes it.
If multiple systems share a frequency or errors occur then the
system type can change and collected information can be lost.
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
