You are using an out of date browser. It may not display this or other websites correctly.

You should upgrade or use an alternative browser.

You should upgrade or use an alternative browser.

- Thread starter jamiewmorris
- Start date

- Status
- Not open for further replies.

When I switched to a different site (P25 control and voice), a user kept having 4-5 duplicates, but it seemed like the other traffic was fine (not nearly as busy of a site as the main one though). This started while I had been running the dongle for much longer than previously (~16 hours), so I'm probably going to pick up another when they restock and see how that goes.

Using a RTL-SDR on both UniTrunker 1.0.32.7 and 1.0.33.5 utilizing both 2 VCOs and 1 VCO (only monitoring control).

Please explain what you mean by "second duplicate call".It just started occurring a couple days ago when I noticed unitrunker tuning to a channel and then a second later ignoring it when it receivesthe second duplicate call. Weirdly enough, I've gotten three in a row where Unitrunker tunes to it on the first, ignores when it gets the second, then tunes back on the third.

This is a picture of what I am seeing.....each line you see on the right where it shows it shows "-" and then "Dig" in the next line is one person keying up. It will show the "Dig" and then create the second line with the "-".

As you may notice, it doesn't do it every single time. Notice the FD1 call near the bottom of the picture. It just shows the "Dig" svc indicator. But like you see at the top of the picture....Sheriff Office 1 talk group the "Dig" and then the "-" (I have the most recent at the top of the screen).

Please explain what you mean by "second duplicate call".

So, when the person originally keys up on their radio, I get the initial "Call" from Unitrunker. About 500ms to 2 seconds later I will get a second "Call" from the same radio ID for the same target, and in some cases about 2-3 seconds after the original "Call" I will get a third from the same radio ID to the same target.

I could not see the time stamp or source ID from Jaime's screen shot.

For Jaime - here is an easier way to get an image from your screen:

https://answers.microsoft.com/en-us...rtsc-key/d75c9690-60cf-4adf-9139-c5b5ac159997

This is definitely a bug. I will put this into the backlog of things to be fixed.

I will post another screen shot on Monday with timestamps.

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

gain 82 FB FF E7

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

gain 80 FB FF E7

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

gain 8C FB FF E7

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

gain 85 FB FF E7

PLL LO 856538750 prescale 1 Quotient 59 SDM 31579 error 5.

PLL LO 856538750 prescale 1 Quotient 59 SDM 31579 error 5.

gain 9B FB FF E7

PLL LO 856538750 prescale 1 Quotient 59 SDM 31579 error 5.

PLL LO 856538750 prescale 1 Quotient 59 SDM 31579 error 5.

gain 80 FB FF E7

PLL LO 856538750 prescale 1 Quotient 59 SDM 31579 error 5.

PLL LO 856538750 prescale 1 Quotient 59 SDM 31579 error 5.

gain 80 FB FF E7

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

PLL LO 856345000 prescale 1 Quotient 59 SDM 30697 error 54.

gain A0 FB FF E7

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

gain B1 FB FF E7

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

gain 87 FB FF E7

PLL LO 856445000 prescale 1 Quotient 59 SDM 31152 error 79.

PLL LO 856445000 prescale 1 Quotient 59 SDM 31152 error 79.

gain 8A FB FF E7

PLL LO 856595000 prescale 1 Quotient 59 SDM 31835 error 5.

PLL LO 856595000 prescale 1 Quotient 59 SDM 31835 error 5.

gain 82 FB FF E7

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

gain 88 FB FF E7

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

gain 80 FB FF E7

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

gain 8C FB FF E7

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

PLL LO 857288750 prescale 1 Quotient 59 SDM 34992 error 79.

gain 90 FB FF E7

PLL LO 856595000 prescale 1 Quotient 59 SDM 31835 error 5.

I could not see the time stamp or source ID from Jaime's screen shot.

For Jaime - here is an easier way to get an image from your screen:

https://answers.microsoft.com/en-us...rtsc-key/d75c9690-60cf-4adf-9139-c5b5ac159997

This is definitely a bug. I will put this into the backlog of things to be fixed.

Also, the picture I posted above only shows it for the crosspatch case where it goes from DXP to XP. However, this also occurs for the Fire and EMS Dispatch channels that are multiselect where they go from DMS to MS, and since it now sees it as analog it detunes.

Was just wanting to be thorough,

Thanks for the help

- Status
- Not open for further replies.

- Replies
- 6

- Views
- 527

- Replies
- 19

- Views
- 2K