repost. "dg" TG's showing up as "Dg".

Status
Not open for further replies.

jets1961

Member
Joined
Jan 21, 2002
Messages
235
Looking at the documentation with trunker 3.83 it explains that “Gd” is a digital non-encrypted TG and “gd” is an encrypted TG. The funny thing is that groups that are in fact encrypted show up a non-encrypted “Gd”. I know at times theses groups that show up as non-encrypted are sometimes run in the non-encrypted mode but 99.5 % of the time they are full encrypted. I have tried setting the “TRACKDIGITAL” line to both 1 and 0. When I first start trunker it will for a few seconds report the encrypted groups correctly and then after a few second as “Gd”. Any thoughts on this problem?

Added: is it possible that once trunker detects a non-encrypted call on an usually encrypted TG that it will report as a non-encrypted group? System 4032d.

Thanks, Joe
 

richster

Member
Joined
Dec 19, 2002
Messages
532
Location
Regina, Sask.
Hi jets1961,

Have you tried other programs on 4032d such as T4win or demo88 to see if they misreport the call type?

Is it possible?

1. That Trunker has a "glitch" with this particular system and is misreporting the call type. Try running Demo88, it's an excellent program for motorola systems. With Demo88 if you see the number 8 after the TG-ID (in hex), it's telling you it's an encrypted TG. Trunker must not be working right for the 4032d system.

2. That ALL programs are consistantly misreporting the call type. The only thing I can think here is that the 4032d system doesn't use the number 8 for determining an encrypted TG. This one is rather unlikely, but hell you never know.

3. Your system needs an exorcism.

*edit* Wait scratch number 2, Trunker wouldn't be displaying TG's as digital first then analog next if number 2 was the case. I'd say it's number 3.

Regards,
Richster.
 

loumaag

Silent Key - Aug 2014
Joined
Oct 20, 2002
Messages
12,935
Location
Katy, TX
jets1961:
A little problem, I am assuming you are trying to track the system 0x4032, since there is no system "4032d". (Decimal 4032 = 0xfc0 and 0x4032d = 292957 decimal)

Now on to the problam. I suspect that part of the problem is no so much Trunker but rather that since the Project-25 radios can detect encryption on the fly the CC does not need to announce the TG as encrypted, and hence Trunker doesn't know. I am sure that if my guess is wrong, someone will jump in with good information.
 
Status
Not open for further replies.
Top