FMC Devens

[ecps92]

According to the database that is a Phase 2 system and the TGs are marked T for TDMA, Unitrunker will not decode voice on a Phase 2 system.

??? it is a a Type II not Phase 2

P25 TRS's are a 3 character SysID
Analog are 4 character SysID - this includes those who are the ole analog systems, but using P25 Voice

 

[RaleighGuy]

??? it is a a Type II not Phase 2

P25 TRS's are a 3 character SysID
Analog are 4 character SysID - this includes those who are the ole analog systems, but using P25 Voice

Last night the system type was listed incorrectly in the database, it was corrected and updated this morning, at the time I posted that the information is what was in the database.

 

[ecps92]

Last night the system type was listed incorrectly in the database, it was corrected and updated this morning, at the time I posted that the information is what was in the database.

But. also using this as a learning opportunity for those who may not know how to READ even the basic SysID

 

[garys]

At least it wasn't ALL UPPER CASE, with fifteen exclamation points.

It was submitted incorrectly a while back, and/or an error was made.

No need to yell. It's been updated. I don't ever get up there to verify.

In the future, if you see a mistake in the DB, instead of yelling on the forums, just submit the correction.

 

[W1KNE]

I'll submit an update as soon as I figure out HOW to receive this system on my SDS radios - I seem to be missing a setting. Unitrunker decodes it fine, but my SDS will lock onto the control channel (and identify the system) but not report traffic.

Again, apologies if my statement offended you - it certainly was not my intent.

Not offended. Just trying to emphasize that corrections need to be submitted, otherwise systems may remain incorrect.

I have tried on both my SDS and x36 the last time I was up there in July but no luck. I suspect it needs to have the manual table entered in like I posted before. I haven't tried it as I haven't been up there since.

 

[tip]

Now I feel bad!

To all... thanks for all you do and for your efforts. Greatly appreciated!

Tip

 

[W1KNE]

Now I feel bad!

No, don't! It's good y'all found an error that I was able to fix. Hopefully this will help us figure this all out.

 

[RaleighGuy]

No, don't! It's good y'all found an error that I was able to fix. Hopefully this will help us figure this all out.

Wish I was closer, I'd love to check it out. Got four of them figured out near me during the cheap gas pandemic

 

[ecps92]

Wish I was closer, I'd love to check it out. Got four of them figured out near me during the cheap gas pandemic

We've got 3 of them in New England and each should be correct in the SNE Wiki as well as the RRDB
now you make me think CT and NH might be incorrect, going to check now

Nope - alll set
NH is true P25 and CT is atleast visable to this tourist set for Analog with P25 voice

 

[W1KNE]

So here is a question, and a reason to have to revisit. If this truly is a Type II hybrid system, the TGs previously seen, 3, 5, etc. are incorrect.
@Bmacs when you've run the system, have you identified any TGs? Is this just an anomaly of the Uniden scanner when set to P25, it decodes the TGs as 1/16 of the analog value? (i.e. TG 3 is really TG 48).

 

[Bmacs]

Hi Mike,

If you look at post #17, Unitrunker identifies one of the TGs as 64. I haven't yet had time to revisit programming the system on my SDS, but when I set up the individual channels as OFT - the SDS reports the TGs as 1-7 (and 19) and a NAC of 0B6. So yes, it appears the SDS is incorrectly reporting it (/16)

Bill.

 

[tip]

Here I go again... have downloaded the latest DB (1/28), and for the life of me, I cannot locate an entry for FMCD. I'm likely staring right at it but... Help?

 

[W1KNE]

Yes, there is an issue with the talkgroups in the database. Hang on, I will fix them now.
EDIT
Unfortunately you will need to wait for the next Sentinel update. The TGs were still invalid TGs for the system type.
They've been corrected.

 

[tip]

Ok... updated to the latest DB (02-04-2024) using latest Sentinel (2.05R03).

Looking in Massachusetts,-Worcester County (and Middlesex County)... Federal Medical Center Devens (FMCD) is nowhere to be found (by me). I've checked Nationwide, Statewide, and County Systems.

 

[ecps92]

Ok... updated to the latest DB (02-04-2024) using latest Sentinel (2.05R03).

Looking in Massachusetts,-Worcester County (and Middlesex County)... Federal Medical Center Devens (FMCD) is nowhere to be found (by me). I've checked Nationwide, Statewide, and County Systems.

I see it in the Web RRDB

Federal Medical Center Devens Trunking System, Devens, Massachusetts

Federal Medical Center Devens Trunking System Profile

www.radioreference.com

 

[tip]

I see it in the Web RRDB

Federal Medical Center Devens Trunking System, Devens, Massachusetts

Federal Medical Center Devens Trunking System Profile

www.radioreference.com

When I connected to update stuff on my 325P2 with Procomm, yes I was able to see it and import to that radio. Cannot see it in Sentinel DB however.

 

[W1KNE]

I see it in the Web RRDB

Federal Medical Center Devens Trunking System, Devens, Massachusetts

Federal Medical Center Devens Trunking System Profile

www.radioreference.com

It's not showing up in Sentinel. I suspect I know why too. Still working on it.

 

[tip]

Took the 325P2 to work today, after importing the FMCD details to the scanner. Fantastic signal, 5 bars. Still nothing heard all day. Did ID scan as well as search, nothing picked up.

 

[tip]

When I connected to update stuff on my 325P2 with Procomm, yes I was able to see it and import to that radio. Cannot see it in Sentinel DB however.

I meant ProScan above not Procomm

 

[W1KNE]

Did you enter the custom table? That's where the issue most likely lies.