Odd Cap+ problem on DSDPlus

[garys]

This is not related to the new version, which is why I've started a separate thread.

I've been monitoring a 4 frequency Cap+ system for some time now and have noticed some odd behavior when the Rest Channel changes and the program starts searching for the new RC.

The system is configured this way,

Cap+, 9999, 1, 1, 464.4500, 0.0, 0
Cap+, 9999, 1, 3, 451.5000, 0.0, 0
Cap+, 9999, 1, 5, 452.7000, 0.0, 0
Cap+, 9999, 1, 7, 452.1250, 0.0, 0

The issue is that when searching for the new RC, the program never checks 464.450. It will scan through the other three channels in order, but never 464.450. That becomes an issue when Channel 1 is the RC.

I've looked at the configuration until my eyeballs fall out, but can't see anything wrong.

Does anyone have any suggestions or thoughts?

 

[redbeard]

One CAP+ site I monitor looks like this:

Cap+,	4685,	0,	1,	855.81250,	0,	0
Cap+,	4685,	0,	3,	856.81250,	0,	0
Cap+,	4685,	0,	5,	857.81250,	0,	0
Cap+,	4685,	0,	7,	858.81250,	0,	0
Cap+,	4685,	0,	9,	859.81250,	0,	0

Notice that the site is zero not one and that the RX frequency is zero not zero point zero. Assuming also you sanitized the network ID with all nines, mine is set to the RR SID from the site URL in my example but that should not make a difference. My guess is on the site number being 1 on a single site system. But just a guess.

 

[cg]

A suggestion:
If I recall, the last number in each line is the order to display them (Sort Order). Try populating that, changing it around and see if it makes a difference.

 

[garys]

I'll give that a try, although it doesn't seem to make a difference on other systems. Well, at least Con+ systems.

Thanks.

A suggestion:
If I recall, the last number in each line is the order to display them (Sort Order). Try populating that, changing it around and see if it makes a difference.