DSDPlus Cap+ and Con+ Systems Colliding – DSDPlus Lock Issues

[Facsimile]

I have two separate systems - one documented and the other undocumented. I am currently following the undocumented one to get it submitted. Problem is, DSDPlus is having a hard time sticking with one system. It keeps jumping back and forth between the two leading to what looks like confusion itself within the DSDPlus log.

Here are the two systems:

1) Undocumented Cap+ system (Kendallville, IN) ~15 miles away
2) ERS-OCI Wireless TRBOconnect Con+ (SITE #6 in Goshen, IN) ~45 miles away

Both share 463.475 MHz.

Within Notes.txt, I found the following:

Added DMR system disambiguation via DCC support in the DSDPlus.frequencies file.

This feature is primarily designed for Cap+ systems where sites share common frequencies.
DCC values can be appended to DMR channel entries in the DSDPlus.frequencies file.

Example:

Cap+, 1234, 3, 1, 454.7625, 0.0, 0, 12

Cap+, 1234, 7, 1, 454.7625, 0.0, 0, 14


If FMPx is manually tuned to 454.7625 and DSD+ detects a Cap+ datastream,
DSD+ will use the received digital color code to determine whether site 3
or site 7 is being monitored.

A DCC does not need to be added to a DMR frequency entry unless disambiguation is required.

Obviously, this does not work between system types as I have tried adding the DCC to the end.

I've tried adjusting gain but it's a double-edged sword - too low of gain I can't decode anything from the undocumented system. Increased gain just gives me the fight between the two. If only there was an option to narrow down decoding of DMR types like there is with NXDN. I will attach the logs below in the event anyone has any suggestions.

Thanks


Update: I restarted DSDPlus and have only had the conflict happen once in the past 4 hours.

 

[mtindor]

I have two separate systems - one documented and the other undocumented. I am currently following the undocumented one to get it submitted. Problem is, DSDPlus is having a hard time sticking with one system. It keeps jumping back and forth between the two leading to what looks like confusion itself within the DSDPlus log.

Here are the two systems:

1) Undocumented Cap+ system (Kendallville, IN) ~15 miles away
2) ERS-OCI Wireless TRBOconnect Con+ (SITE #6 in Goshen, IN) ~45 miles away

Both share 463.475 MHz.

Within Notes.txt, I found the following:



Obviously, this does not work between system types as I have tried adding the DCC to the end.

I've tried adjusting gain but it's a double-edged sword - too low of gain I can't decode anything from the undocumented system. Increased gain just gives me the fight between the two. If only there was an option to narrow down decoding of DMR types like there is with NXDN. I will attach the logs below in the event anyone has any suggestions.

Thanks


Update: I restarted DSDPlus and have only had the conflict happen once in the past 4 hours.

It's a real pain when that happens. I don't really have any suggestion for you. You seem to do a lot of 400 mhz sleuthing. You might want to consider a yagi (even if you have to keep it inside) for some directionality.

There was some tropo here late into the morning today. Maybe that was the case with you -- and then when it died down, you pulled in the closer sight (just a guess).

Mike

 

[Facsimile]

You might want to consider a yagi (even if you have to keep it inside) for some directionality.

That's exactly what I use and it's indoors. How did you know?

I'm starting to think I must be in a prime spot with all the tropo!

 

[mtindor]

That's exactly what I use and it's indoors. How did you know?

I'm starting to think I must be in a prime spot with all the tropo!

LOL. Lucky guess. Yeah I think are probably in a decent spot for tropo. When the weather conditions are right you seem to have windows into other states just like i do.

At any rate, good luck with the battling conrol channels!

m