Robinator
Member
Setting up Unitrunker with the RTL-SRD radios on the San Antonio EDACS system and it's working great.
While setting up and monitoring Gold Simulcast, I found a Target ID/Talkgroup (1029, 08-005) which is carrying the same traffic from the 1046, 08-026 talkgroup (Bexar County SO Central Open). My BCD436HP is receiving the 1046, 08-026 properly but this Target ID does not display on Unitrunker at all.
Update: I found a 1046 on the call history as a "Joins" but never as a "Call".
Update: now the 1025 Target ID has the 1046 traffic and the 1029 Target ID isn't displaying anymore. Not sure what is going on here.
Also found Target ID/Talkgroup 772, 06-004 which is the same traffic as 625, 04-141 (San Antonio Fire/EMS District-1 Access). Again, the BCD436HP is correctly showing the talkgroup and Unitrunker does not show the 625 Target ID, only the 772 Target ID.
Update: the 625 Target ID showed as a "Joins" once and never as a "Call".
Is this a known issue with Unitrunker (target ID errors)?
-Rob
While setting up and monitoring Gold Simulcast, I found a Target ID/Talkgroup (1029, 08-005) which is carrying the same traffic from the 1046, 08-026 talkgroup (Bexar County SO Central Open). My BCD436HP is receiving the 1046, 08-026 properly but this Target ID does not display on Unitrunker at all.
Update: I found a 1046 on the call history as a "Joins" but never as a "Call".
Update: now the 1025 Target ID has the 1046 traffic and the 1029 Target ID isn't displaying anymore. Not sure what is going on here.
Also found Target ID/Talkgroup 772, 06-004 which is the same traffic as 625, 04-141 (San Antonio Fire/EMS District-1 Access). Again, the BCD436HP is correctly showing the talkgroup and Unitrunker does not show the 625 Target ID, only the 772 Target ID.
Update: the 625 Target ID showed as a "Joins" once and never as a "Call".
Is this a known issue with Unitrunker (target ID errors)?
-Rob
Last edited: