New Fort Carson P25 system

Status
Not open for further replies.

whwandell

Member
Joined
Sep 20, 2005
Messages
9
Location
Colorado Springs, CO
Hi,

I thought I knew how this worked, but evidently not. How do I set up the extended tables in win96 for my 2096/96 using the data from Pro96com, which has three identifier tables listed. The method described in the Pro96com manual (pages 26-29) doesn't seem to make sense, and gives very strange values for the extended table entries. I did the calculations and set up the tables anyway, but so far no results. Search function does find at least some of the the TG's/ VC's as per RR, so the data there is certainly right, and the difficulty is definitely on this end.

I have a few more techie type questions (possibly answered elsewhere but not found as yet), and maybe you can push me in the right direction anyway.


(Download of the RR listing for the system also appears to do nothing (would have been too easy!), so I'm now out of ideas).

Thanks!
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
When I programmed my '96 to handle Wyolink (which has non-standard trunking tables) I had to enter the tables into Win96 manually. RR download doesn't necessarily do the tables automatically. Look and see if this is so.

(That's about the extent of my help )
 

whwandell

Member
Joined
Sep 20, 2005
Messages
9
Location
Colorado Springs, CO
That appears to be the case ... I had the same experience with Wyolink while on vacation a while ago but never bothered to figure out what was going on since i was just passing through.
There has to be a way but I'm currently stumped as to how to proceed.
Thanks for the reply - if I find out the secret I'll let you know!
 

whwandell

Member
Joined
Sep 20, 2005
Messages
9
Location
Colorado Springs, CO
So where / how did you come up with the table entries - that's where I'm stuck, since I can't find any way to calculate the various parameters that make sense.

Thanks!
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
Wyolink page had the tables already.

I've never seen a writeup on how to figure them out. I'm sure somebody on RR knows but it's not me.
 

whwandell

Member
Joined
Sep 20, 2005
Messages
9
Location
Colorado Springs, CO
No such luck finding that info from the site - probably it's a bit more classified.

We'll eventually find out. I know there's a method using what data can be dredged up from here and there, so we'll see what RR experts can come up with. Sort of a challenge now ..,

Thanks again ...
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
Take a look at other similar systems to get an idea.

JK


Maybe you really do mean to be helpful but I know myself well enough to know that this is not sufficient explanation to work for me. I can generate lots and lots of ideas. Chances are that they'll all be wrong.
 

eyes00only

Member
Joined
Jun 26, 2004
Messages
2,812
Location
Denver Colorado
I was trying to be helpful. The DOD system in the same area could give him an idea of what parameters to look at. Of course I could be wrong.

JK
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
What he needs to know is how to convert parameters seen in Pro96com to trunking tables.
Guessing might work but you'd always wonder....
 

whwandell

Member
Joined
Sep 20, 2005
Messages
9
Location
Colorado Springs, CO
Right. I have several local mil sites working, including USAFA and Peterson AFB, Fort Carson has recently "started" conversion to the new system and not much info is out there yet. Have found a methodology for 3600 baud sytems that doesn't help a lot for 9600 - major differences.

Will keep lookin' ..

Thanks!
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
After wrestling with trunking tables and finding them fairly straightforward he's having issues matching decodes not being done on his Pro-96 vs seeing TGs come and go in Pro96com.

Could this system be ESK or something that the Pro-96 won't decode?

How could one tell?

Someone has been submitting system info which suggests that the system can be monitored (doesn't it?).

(I'm too far away from the system to try anything myself)
 

greenthumb

Colorado DB Administrator
Database Admin
Joined
Feb 29, 2004
Messages
1,942
It's not ESK (EDACS Security Key) since it's a P25 system. It has to be something to do with the tables. If someone can run pro96com on it and get the tables that are being broadcast, it could help.
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
It's not ESK (EDACS Security Key) since it's a P25 system. It has to be something to do with the tables. If someone can run pro96com on it and get the tables that are being broadcast, it could help.

That's what we did back channel.

I guess it could be his radio since the radio failed before he could try the tables I generated using Pro96com and the instructions from the manual.

I suppose it could have been a radio failure to decode before it failed even worse.

So- is anybody in COS using a Pro-96 on the new Ft. Carson system?
 

Cryptolog

Member
Premium Subscriber
Joined
Dec 16, 2004
Messages
205
Location
Colorado
It runs fine on my PSR500 with mode set to "P25 Auto" and the tables blank. I'd think a Pro-96 would work with Rx Mode set to MOT and MOT 9600 CC set to Normal (using Win96). I'm told there's more/different data in the P25 control channel data stream than with the old analog system so tables aren't needed. I just submitted a couple more TGs to the database.
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
It runs fine on my PSR500 with mode set to "P25 Auto" and the tables blank. I'd think a Pro-96 would work with Rx Mode set to MOT and MOT 9600 CC set to Normal (using Win96). I'm told there's more/different data in the P25 control channel data stream than with the old analog system so tables aren't needed. I just submitted a couple more TGs to the database.

The PSR500 is smarter than the 96 and reads the data stream and does its own table construction.
A capture of the tables held in the PSR500 would be useful to see as it would be what the 96 needs to have manually entered.

I did a side-by-side on Wyolink last summer as I drove thru. The '197 just needed control channels. The '96 had to have a complex trunking table pre-entered. (The table is posted on the Wyolink page here in RR.)

I'll be down in the Springs later this month and maybe I can capture the tables in my own Pro-197 radio and also try out the developed trunking tables in my '96 and see if it'll play. Depends on reception as I won't be going south of the north end of the airport but I'll be up on the hill to the NE. (assuming the trip actually happens)

Problem is that whwandell has a broken radio now so he can't test the trunking table or listen to the system which was the point of the exercise.
 

whwandell

Member
Joined
Sep 20, 2005
Messages
9
Location
Colorado Springs, CO
Thanks for the idea! Have a friend who has a 500 who may or may not have been monitoring FtC. Will see what he's been able to do, and easy enough to transer flles/data.. Good info about the differences between radios. Might force me into upgading.
 

tracker1

Member
Joined
Dec 19, 2002
Messages
52
Location
Pueblo County
Try this table

I ran Unitrunker against one of the control channels and came up with this configuration. It works on my old PRO-2096.

Choose MOT 9600 CC - Multi table

# Ch LO Ch Hi Base Freq Offset Step
0 0 4095 851.00625 0 6.25
1 4096 8191 762.00625 4096 6.25
2 8192 12287 382.91250 8192 12.50
 

GrayJeep

Member
Premium Subscriber
Joined
Jan 6, 2007
Messages
967
Location
N. Colo.
I ran Unitrunker against one of the control channels and came up with this configuration. It works on my old PRO-2096.

Choose MOT 9600 CC - Multi table

# Ch LO Ch Hi Base Freq Offset Step
0 0 4095 851.00625 0 6.25
1 4096 8191 762.00625 4096 6.25
2 8192 12287 382.91250 8192 12.50


That should nail it firmly in place.

Thank you!
 
Status
Not open for further replies.
Top