Hi Trevor,
RM will use the lowest numbered available channel for depths. In your situation, it *should* be using the downscan channel (2), as primary (0) is not available. What is probably happening is that, for some reason, there are some pings from channel 0 and RM now considers this to be the primary for that track. I have seen this situation before..
Maybe we can do a more robust check on availability of channel data (i.e. at least a reasonable amount available before declaring it the primary), but since we will be overhauling things in that area anyway, to allow explicit use of any channel as primary, we might just leave it for now.
cheers,
Matt