PRO-96 control channel dump/display utility

[ChrisP]

I know it works here very well. If you don't mind saying, which system are you trying to decode information from?

Mike

It is a new VHF trunked system for the Justice Department in Washington State (Justice Intergrated Wireless Network or JWIN). I haven't posted the frequencies in the database yet, as I was hoping to get a little more system info together first.

- Chris

 

[ChrisP]

ChrisP: That's exactly what is happening to me. Regardless of how many times people restate the quite simple instructions, it's not going anywhere past that stage.

- Rob

I'm just curious as to what is keeping this from working. It seems like I've done all the steps required, and it should be working.

I'm still trying various combinations of cables & computers and will see what happens...

- Chris

 

[ChrisP]

PRO96DMP.EXE - Success!

OK, it looks like after several tries with different computers & such I have finally gotten PRO96DMP to work for me. I'm still not sure why it did not want to work on my computers that were running Win98, but when I switched over to my laptop running Win2k, I started getting this while running in the verbose mode:

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
05 90 00 00 00 00 00 00 00 00 D1 C3 D1C3 Idle
34 00 55 05 30 64 01 9F 0A 00 77 0D 770D Reserved Mfg 00
3B 00 00 BE E0 A7 15 79 D5 70 DA AA DAAA Network Status Broadcast Mfg 00 LRA 0
0 WACN BEE0A Sys 715 channel 7-9D5(866.73750)(data,voice,registration)
-96 00 00 40 FF FF FF FF FF FF B6 D1 B6D1 op=16 unknown single OSP
C:\work\pro96dmp\PRO96.CPP(119): packet 02 96 00 00 40 FF FF FF FF FF FF B6 D1 0
3 5A
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)

But I noticed that interlaced among the bad checksum messages there were snippets of what appeared to be trunking system info. I then tried running with the program dumping to the output.txt file and started seeing this:

-B4 00 75 04 C4 64 01 9F 0A 00 C7 2D C72D Reserved Mfg 00
-96 00 00 40 FF FF FF FF FF FF B6 D1 B6D1 op=16 unknown single OSP
34 00 D5 1F 40 14 01 D1 55 00 0E 8E 0E8E Reserved Mfg 00
09 90 12 C0 00 00 00 00 00 00 F2 BA F2BA Telephone Voice Grant Update I 000000 timer 0000 channel 1-2C0(855.40625)
-B4 00 55 05 30 64 01 9F 0A 00 93 39 9339 Reserved Mfg 00
-B4 00 B5 1F 40 14 01 9F 0A 00 7F 2F 7F2F Reserved Mfg 00
29 00 01 0F 2A 42 00 28 AC 04 FF D7 FFD7 op=29 unknown single OSP
34 00 35 07 6C 64 01 9F 0A 00 E1 21 E121 Reserved Mfg 00
-BC 00 00 37 15 01 0C 49 C5 70 B9 0B B90B Adjacent Status Broadcast Mfg 00 LRA 00 Sys 715 Sub 01 Site 0C channel 4-9C5(866.63750)(data,voice,registration)
-B4 00 95 04 8C 64 01 9F 0A 00 D0 46 D046 Reserved Mfg 00 (5.0 frames per second)
3A 00 00 17 15 01 0F 79 D5 70 1D 7C 1D7C RFSS Status Broadcast Mfg 00 LRA 00 Sys 715 Sub 01 Site 0F channel 7-9D5(866.73750) (data,voice,registration)
3D 00 13 25 E0 32 09 15 75 62 1B 36 1B36 Identifier Update mfg 00 Ident 1 bw 12.5khz offset 120 space 50 base 762006250 hz
-96 00 00 40 FF FF FF FF FF FF B6 D1 B6D1 op=16 unknown single OSP
-B4 00 75 04 C4 64 01 9F 0A 00 C7 2D C72D Reserved Mfg 00
34 00 E5 1F 40 14 01 F0 95 00 EF F0 EFF0 Reserved Mfg 00
05 90 00 00 00 00 00 00 00 00 D1 C3 D1C3 Idle

Ah, ha! Things are starting to look up here, but I can't exactly figure out why I was seeing all the error messages in the verbose mode and not seeing them in the text file mode. Also wondering why things won't work at all on a Win98 computer, but seem to work on a Win2k laptop.

One question about the output I'm getting. Since PRO96DMP seems to default to an 800 Mhz band pand, how does one translate frequencies shown in the output data to VHF?

Here's the system data that shows up at the bottom of the dump file:

0 Base 851006250 Spacing 6250 Offset -45000000
1 Base 762006250 Spacing 6250 Offset 30000000
channel 1-2C0(766.40625)
channel 4-9C5(866.63750)
channel 4-9C9(866.66250)
channel 7-9D5(866.73750)
WACN BEE0A Sys 715 Sub 01 Site 02 channel 4-9C9(866.66250)
WACN BEE0A Sys 715 Sub 01 Site 0C channel 4-9C5(866.63750)
WACN BEE0A Sys 715 Sub 01 Site 0F channel 7-9D5(866.73750)

The frequency that this data channel is on is currently 167.4625 MHz...

Thanks to all in this forum for the helpful suggestions!

- Chris

 

[SCPD]

Re: PRO96DMP.EXE - Success!

OK, it
I'm still not sure why it did not want to work on my computers that were running Win98, but when I switched over to my laptop running Win2k, I started getting this while running in the verbose mode:

Any one else running Win9X/ME with the same problems reported by Chris?

[ I don't have a Win 9X/ME system for testing so this is likely the problem. ]

-rick

 

[rdale]

My issue is with a Win98 machine... Win96 works fine, and I don't have easy access to a WinXP box that has a serial port.

- Rob

 

[SCPD]

Also ... I need to upload a newer version that fixes a few problems. I see the version Chris runs is using the wrong opcode for the Identifier update messages (it's a $34, not a $3D). That's probably why 700 and/or 800 mhz frequences are showing up on a 167 Mhz system.

-rick

 

[SCPD]

Re: PRO96DMP.EXE - Success!

-B4 00 75 04 C4 64 01 9F 0A 00 C7 2D C72D Reserved Mfg 00

That's the identifier update - new version handles this better.

34 00 D5 1F 40 14 01 D1 55 00 0E 8E 0E8E Reserved Mfg 00

Another identifier update - new version handles this better.

09 90 12 C0 00 00 00 00 00 00 F2 BA F2BA Telephone Voice Grant Update I 000000 timer 0000 channel 1-2C0(855.40625)

Ignore these. It's an unknown Motorola proprietary TSBK.

29 00 01 0F 2A 42 00 28 AC 04 FF D7 FFD7 op=29 unknown single OSP

Now identified as a status query response.

3D 00 13 25 E0 32 09 15 75 62 1B 36 1B36 Identifier Update mfg 00 Ident 1 bw 12.5khz offset 120 space 50 base 762006250 hz

This is wrong. Fixed in next version.

-96 00 00 40 FF FF FF FF FF FF B6 D1 B6D1 op=16 unknown single OSP

This one is still unknown.

-rick

 

[ChrisP]

Thanks for the info, Rick.

I'll keep an eye out for your newer version of pro96dmp.exe

- Chris

 

[mikey60]

is the Opcode the first byte of the OSP anded with a value?

I've been playing with the interface as well (finally got it to successfully read the data from the radio, but the approach I'm taking so far is a bit slow.)

I'd love to see the source of you're utility if you're willing to share it, if not, that's up to you as well...

Last question... Any luck being able to read the control channel date using the sound card input? I hate to tie up my Pro96 for this since I can't listen to the system while I'm doing that.

Mike

 

[SCPD]

is the Opcode the first byte of the OSP anded with a value?

Yes. It's the lower 6 bits.

I'd love to see the source of you're utility if you're willing to share it, if not, that's up to you as well...

Send me an email.

Any luck being able to read the control channel date using the sound card input? I hate to tie up my Pro96 for this since I can't listen to the system while I'm doing that.

Getting the data out of the radio and into the computer is half the battle. There's a whole range of Reed Solomon and Galois Field math involved.

We're closer but still have a ways to go.

-rick

 

[MattSR]

Hi Rick, is it possible for me to obtain the source as well? I am always interested to see how this works in the back end.

Is there any possibility of modding Unitrunker so that it can use the PRO96 in this mode to read the control channel? This would take away all the hassles of buffer amps etc etc

Cheers,
Matt

 

[tuttleje]

Does anyone have information on how you can determine with the Pro96com program which tower in a APCO 25 system is receiving a specific radio's transmission? Is it hidden in the data dump?

 

[mikey60]

Does anyone have information on how you can determine with the Pro96com program which tower in a APCO 25 system is receiving a specific radio's transmission? Is it hidden in the data dump?

Not with any certanty... About the only chance you have is to see if the radio is on the site you're monitoring. Sometimes you'll see the system ACK message on the other information screen. Other than that, it's all on the affiliation screen.

Mike