PRO-96 control channel dump/display utility

[Unitrunker]

PRO-96 owners that have the appropriate programming cable can now use their radio to display APCO P25 control channel activity. Folks familiar with Trunker/ETrunk and the associated programs Dumper/EDump have had the ability to do so for Motorola and EDACS systems using a discriminator tapped radio and a small, cheap and easy to build circuit called a data slicer.

Now PRO-96 owners can display comparable P25 information without the need to a discriminator tap or special circuitry. Attached is the program "pro96dmp" which will display the control channel messages sent out by the system to the mobile and handheld radio.

Instructions:

Unzip the pro96dmp.exe to a directory.

[optional] Create a shortcut to the EXE. For the command arguement, type the name of the serial port that connects to your PRO-96.

Attach cable to computer and PRO-96.

Power up PRO-96.

Select an active APCO P25 system.

On the PRO-96, press PRG FUNC PRG PRG.

Double-click on the short cut or run the program pro96dmp from a command line as in the following example:

C:\> pro96dmp COM1

If everything is working correctly you will see output similar to the following:

 -BB 00 00 BE E0 91 3E 09 8D 60 9B 8B 9B8B Network Status Broadcast Mfg 00 LRA 00 WACN BEE09 Sysid 13E channel 0-98D(866.2875)(voice service requests only,registration services only)
  02 00 0A 0D 0C 04 0B 37 09 63 60 91 6091 Group Voice Grant Update G 0c04 on channel 0-A0D(867.0875) G 0963 on channel 0-B37(868.9500)
  3A 00 00 11 3E 01 01 09 8D 60 A5 86 A586 RFSS Status Broadcast Mfg 00 LRA 00 Sysid 13E Sub 01 Site 01 Ch 0-98D (voice service requests only,registration services only)
  09 90 0F 00 00 00 00 00 00 00 EF 7F EF7F Telephone Voice Grant Update I 000000 timer 0000 channel 0-F00(875.0062)
 -BB 00 00 BE E0 91 3E 09 8D 60 9B 8B 9B8B Network Status Broadcast Mfg 00 LRA 00 WACN BEE09 Sysid 13E channel 0-98D(866.2875)(voice service requests only,registration services only)
  00 90 04 61 04 63 04 61 04 63 10 A1 10A1 Group Voice Grant channel 0-461(858.0125) I 610463 -> 6304
 -80 90 05 61 05 61 05 61 05 61 D7 A2 D7A2 Group Voice Grant channel 0-561(859.6125) I 610561 -> 6105 (3.3 frames per second)
  3A 00 00 11 3E 01 01 09 8D 60 A5 86 A586 RFSS Status Broadcast Mfg 00 LRA 00 Sysid 13E Sub 01 Site 01 Ch 0-98D (voice service requests only,registration services only)
  09 90 0F 00 00 00 00 00 00 00 EF 7F EF7F Telephone Voice Grant Update I 000000 timer 0000 channel 0-F00(875.0062)
 -B4 00 45 19 4C 28 01 CD 7C A0 38 1A 381A Reserved
  3D 00 13 25 E0 32 09 15 75 62 1B 36 1B36 Identifier Update  mfg 00 Ident 1 bw 12.5khz offset 178 space 032 base 09157562
  00 90 05 61 05 61 05 61 05 61 33 96 3396 Group Voice Grant channel 0-561(859.6125) I 610561 -> 6105
 -BA 00 00 11 3E 01 01 09 8D 60 41 B2 41B2 RFSS Status Broadcast Mfg 00 LRA 00 Sysid 13E Sub 01 Site 01 Ch 0-98D (voice service requests only,registration services only)
 -80 90 04 61 04 61 04 63 04 61 FE 34 FE34 Group Voice Grant channel 0-461(858.0125) I 630461 -> 6104 (4.0 frames per second)
  34 00 45 19 4C 28 01 CD 7C A0 DC 2E DC2E Reserved
  00 90 05 61 05 61 05 61 05 61 33 96 3396 Group Voice Grant channel 0-561(859.6125) I 610561 -> 6105
  05 90 00 00 00 00 00 00 00 00 D1 C3 D1C3 Idle
 -B4 00 25 07 44 28 01 CE 43 D8 0E 77 0E77 Reserved

Pressing any key will stop the display. A short report of radio channels, system ids, and identifiers (channel maps) is displayed. Pressing a key a second time causes the program to exit.

Good luck and happy 4th of July to everyone.

-rick

[fmon]

Hi Rick,

Running the program on
Location: Chesapeake, VA
System Type: Motorola ASTRO 3600 baud
Sysid: 7A32
CT: 116.13
Digital Type: APCO-25 Mixed Mode
and produced the following report.
0 Base 851006250 Spacing 6250 Offset –45000000

I’m on com1 and using the Blackbag cable with the following indicated on scanner display’
V-Scanner
PC/IF Port
Remote Acces
CLR to EXIT

Thanks for the program, I hope to get it running correctly.

Happy Birthday USA.

[kikito]

Like I just said on the Trunker list, thanks for this resource Rick.


Just for comparison with fmon, I get this on my VHF 9600 system:


0 Base 851006250 Spacing 6250 Offset -45000000
1 Base 762006250 Spacing 6250 Offset 30000000
channel 0-DC0(873.00625)
channel 0-F00(875.00625)
channel 1-040(762.40625)
channel 1-180(764.40625)
channel 1-2C0(766.40625)
channel 5-627(860.85000)
channel 5-647(861.05000)
channel 6-5D5(860.33750)
channel 6-5E1(860.41250)
channel 6-617(860.75000)
channel 9-5E2(860.41875)
WACN BEE00 Sys 142 Sub 02 Site 01 channel 6-5D5(860.33750)
WACN BEE00 Sys 142 Sub 02 Site 02 channel 9-5E2(860.41875)

[DaveIN]

Hi Rick,

Not working here yet. This is APCO-25, 3600 Baud, GRE 30-2290 cable and black bag software cable.

Here is my dump:

C:\pro96dmp>pro96dmp com1
pro96dmp (C) Copyright 2004 <rfmobile@swbell.net>
Version 2004.07.04
usage ...
pro96dmp port [ -verbose ]
where port is one of COM1, COM2, COM3, or COM4
(press any key to exit)

E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow! (10.0 fr
ames per second)
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow! (6.7 fra
mes per second)
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow! (7.5 fra
mes per second)
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow! (6.7 fra
mes per second)
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!
E 00 00 00 00 00 00 00 00 00 00 00 00 FFFF Warning: OSP stack overflow!

0 Base 851006250 Spacing 6250 Offset -45000000


C:\pro96dmp>pro96dmp com1 -verbose
pro96dmp (C) Copyright 2004 <rfmobile@swbell.net>
Version 2004.07.04
usage ...
pro96dmp port [ -verbose ]
where port is one of COM1, COM2, COM3, or COM4
(press any key to exit)

C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEnq to eAck (500 ms).
C:\work\pro96dmp\PRO96.CPP(432): Sending 05 05
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eAck to eEcho (50 ms).
C:\work\pro96dmp\PRO96.CPP(109): discarded 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(219): acked following echo 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(119): packet 02 00 00 00 00 00 00 00 00 00 00 00 00 0
3 03
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEcho (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEnq (50 ms).

C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEnq to eAck (500 ms).
C:\work\pro96dmp\PRO96.CPP(432): Sending 05 05
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eAck to eEcho (50 ms).
C:\work\pro96dmp\PRO96.CPP(109): discarded 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(219): acked following echo 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(119): packet 02 00 00 00 00 00 00 00 00 00 00 00 00 0
3 03
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEcho (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEnq (50 ms).

C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEnq to eAck (500 ms).
C:\work\pro96dmp\PRO96.CPP(173): Warning, Warning: radio not responding.
C:\work\pro96dmp\PRO96.CPP(432): Sending 05 05
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eAck to eEcho (50 ms).
C:\work\pro96dmp\PRO96.CPP(109): discarded 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(219): acked following echo 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(119): packet 02 00 00 00 00 00 00 00 00 00 00 00 00 0
3 03
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEcho (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEnq (50 ms).

C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEnq to eAck (500 ms).
C:\work\pro96dmp\PRO96.CPP(432): Sending 05 05
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eAck to eEcho (50 ms).
C:\work\pro96dmp\PRO96.CPP(109): discarded 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(219): acked following echo 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(119): packet 02 00 00 00 00 00 00 00 00 00 00 00 00 0
3 03
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEcho (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEnq (50 ms).

C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEnq to eAck (500 ms).
C:\work\pro96dmp\PRO96.CPP(432): Sending 05 05
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eAck to eEcho (50 ms).
C:\work\pro96dmp\PRO96.CPP(109): discarded 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(219): acked following echo 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(119): packet 02 00 00 00 00 00 00 00 00 00 00 00 00 0
3 03
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEcho (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEnq (50 ms).

C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEnq to eAck (500 ms).
C:\work\pro96dmp\PRO96.CPP(173): Warning, Warning: radio not responding.
C:\work\pro96dmp\PRO96.CPP(432): Sending 05 05
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eAck to eEcho (50 ms).
C:\work\pro96dmp\PRO96.CPP(109): discarded 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(219): acked following echo 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(119): packet 02 00 00 00 00 00 00 00 00 00 00 00 00 0
3 03
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEcho (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEnq (50 ms).

C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEnq to eAck (500 ms).
C:\work\pro96dmp\PRO96.CPP(432): Sending 05 05
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 05 bad chsum
C:\work\pro96dmp\PRO96.CPP(184): Received 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eAck to eEcho (50 ms).
C:\work\pro96dmp\PRO96.CPP(109): discarded 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(219): acked following echo 06 bad chsum
C:\work\pro96dmp\PRO96.CPP(119): packet 02 00 00 00 00 00 00 00 00 00 00 00 00 0
3 03
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eReply to eEcho (50 ms)
.
C:\work\pro96dmp\PRO96.CPP(432): Sending 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(119): packet 02 39 44 03 80
C:\work\pro96dmp\PRO96.CPP(136): Worker transitions from eEcho to eReply (50 ms)
.

0 Base 851006250 Spacing 6250 Offset -45000000

[Unitrunker]

Folks,

If you see a bunch of zeroes like the example above ... it means the radio is not tuned to a P25 control channel.

Try hitting "scan". When the radio settles on a P25 system, press "man". You should see the P25 system's 5 digit WACN and 3 digit SYSID on the bottom line of the PRO-96 display. At that point you can press "PRG FUNC PRG PRG" and proceed with the software.
-rick

[Unitrunker]

Originally Posted by fmon

Hi Rick,

System Type: Motorola ASTRO 3600 baud
Sysid: 7A32
CT: 116.13
Digital Type: APCO-25 Mixed Mode

The program only works on 9600 baud P25 control channels. You'll have to use Dumper or Trunker for a system like the one above.

-rick

[kikito]

I noticed I get a lot of "stack overflow" when I don't have a good or scratchy signal. That might be DaveIN's problem.

[Unitrunker]

Originally Posted by kikito

Just for comparison with fmon, I get this on my VHF 9600 system:

Thanks Kikito. If you could, send me a 5 minute dump. My guess is the system isn't sending out the identifiers (channel maps).

Regards,
Rick

[RFfreeTLD]

Dump is working on a MPSCS 9600 site from Michigan.

Is there an easy way to copy/paste from screen to a file? Or an option to dump data to a file? Copying from the console/command screen and paste into text didn't yield all the data correctly.

(I'm using Win XP and the 'Purple' cable.)

[Unitrunker]

If you run the program from a command window, you can cause the programs' output to be sent to a file instead of the screen.

Output-to-screen example:

C:\> pro96dmp COM1

Output-to-a-file example:

C:\> pro96dmp COM1 > output.txt

This second example places the results into a text file named "output.txt".

In both cases, you must press a key to cause the program to stop dumping live control information. Press a key a second time to cause the program to exit.

-rick

[rdale]

"Attach cable to computer and PRO-96.
Power up PRO-96. "

When I do that my Pro96 powers up in clone mode and I can't get anywhere from that point...

[Pro-95]

COOL! 8)

Disregard the request in the PM.

When I get off work I'm going to review the dump in detail.

[SEMTTP]

I am using a radio shack cable attached to my programing cable for the pro-96 and this cable has a USB end. For regular programing it works fine, however when I open the dump program it says that it cannot find the com port hit any key to exit. On the scanner it says:

V-Scanner
PC/IF Port
Remote Acces
CLR to EXIT

help?

[Pro-95]

Originally Posted by erchambers

I am using a radio shack cable attached to my programing cable for the pro-96 and this cable has a USB end.

USB usually likes to be called COM0:, At least for some programs.

[fmon]

Originally Posted by rdale

"Attach cable to computer and PRO-96.
Power up PRO-96. "

When I do that my Pro96 powers up in clone mode and I can't get anywhere from that point...

Now press PGM FUNC PGM PGM

[rdale]

fmon: That would be skipping the "Select an active APCO P25 system. " step...

Anyways pressing that does nothing except alternate the display from *CLONE MODE* to V-Scanner

If I go to the channel, do the keypad, then put the cable in the program does nothing til I hit a key and then get

0 Base 851006250 Spacing 6250 Offset -45000000

- Rob

[kikito]

Originally Posted by rdale

Anyways pressing that does nothing except alternate the display from *CLONE MODE* to V-Scanner

- Rob

When I press PGM FUNC PGM PGM, mine says:

V-Scanner
PC/IF Port
Remote Acces
CLR to EXIT

Once you hook it up and run the program, then where it says "Remote Acces", it starts alternating between: ***IN USE*** and Remote Acces.

[kikito]

Originally Posted by rdale

"Attach cable to computer and PRO-96.
Power up PRO-96. "

When I do that my Pro96 powers up in clone mode and I can't get anywhere from that point...

The way I do it and works for me is:

1. Turn on scanner
2. Tune to 9600 control channel
3. Press PGM FUNC PGM PGM
4. Hook up cable
5. Run pro96dmp.exe program

[mikey60]

Here's what I get off of the Detroit Tower (Sub 02, Site 09) on the MPSCS in Michigan. There's a couple of odd frequencies listed there (859.00625 for example, the MPSCS uses only frequencies in the 866-869 range). Also note a couple of channels listed in the cellular band at the bottom.

In all, very interesting data being presented. I realize this is more proof of concept, but it might be nice to keep the control channels for adjacent sites in a separate list.

Mike

0 Base 851006250 Spacing 6250 Offset -45000000
channel 0-500(859.00625)
channel 0-640(861.00625)
channel 0-780(863.00625)
channel 0-8C0(865.00625)
channel 0-9F5(866.93750)
channel 0-A00(867.00625)
channel 0-A45(867.43750)
channel 0-A95(867.93750)
channel 0-AE5(868.43750)
channel 0-B13(868.72500)
channel 0-B2F(868.90000)
channel 0-B33(868.92500)
channel 0-B35(868.93750)
channel 0-B37(868.95000)
channel 0-B39(868.96250)
channel 0-B3B(868.97500)
channel 0-B3D(868.98750)
channel 0-B40(869.00625)
channel 0-C80(871.00625)
WACN 92493 Sys 796 Sub 02 Site 02 channel 0-B3D(868.98750)
WACN 92493 Sys 796 Sub 02 Site 04 channel 0-B37(868.95000)
WACN 92493 Sys 796 Sub 02 Site 05 channel 0-B3B(868.97500)
WACN 92493 Sys 796 Sub 02 Site 06 channel 0-B33(868.92500)
WACN 92493 Sys 796 Sub 02 Site 09 channel 0-B35(868.93750)
WACN 92493 Sys 796 Sub 02 Site 0A channel 0-B2F(868.90000)
WACN 92493 Sys 796 Sub 02 Site 1A channel 0-B13(868.72500)

[mikey60]

Here's what seems to be the culprit on the false frequencies:

-89 90 06 40 00 00 00 00 00 00 8F AE 8FAE Telephone Voice Grant Update I 000000 timer 0000 channel 0-640(861.00625) (6.0 frames per second)

All of the Telephone Voice Grants come up with incorrect frequencies.

Also, P25 systems use Decimal talkgroup IDs, so this:

-82 00 0A 3F 07 DA 0A 3F 07 DA 4C CB 4CCB Group Voice Grant Update G 07da on channel 0-A3F(867.40000) G 07da on channel 0-A3F(867.40000) (5.8 frames per second)

should be:

-82 00 0A 3F 07 DA 0A 3F 07 DA 4C CB 4CCB Group Voice Grant Update G 07da on channel 0-A3F(867.40000) G 2010 on channel 0-A3F(867.40000) (5.8 frames per second)


Information coming out of the program is great! Thanks for taking this on and figuring out the control sequences!

Mike