Raymarine forum

Full Version: a/c/e/eS/gS-Series MFD Sonar Prioritization with Multiple Data Sources
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
a/c/e/eS/gS-Series MFD Sonar Prioritization with Multiple Data Sources

In Automatic Multiple Data Source (MDS) Mode, SeaTalkNG data is preferred to SeaTalkHS (RayNet). With multiple SeaTalkNG sources, they are ranked by CAN Address highest to lowest.

Depth Databoxes within a Fishfinder application page/pane will reflect depth determined by the fishfinder sounder whose imagery is being displayed within that Fishfinder application page/pane. When automatic Depth source selection (HOME->SET-UP->SYSTEM SETTINGS->DATA SOURCES->DEPTH->AUTO) has been configured instrument depth will be prioritized over fishfinder depth within the Databar, Data Application panels, and Databoxes of all other applications, (Chart, Radar, Weather, etc.).

With multiple fishfinder sounders, there is a ranking list based on the model of fishfinder sounder:

1. CP570
2. CP470
3. CP370
4. CP450C
5. CP300
6. DSM300
7. DSM30
8. a67
9. a67 WiFi
10. a77
11. a77 WiFi
12. e7D
13. c97
14. c127
15. e97
16. e127
17. a97
18. a127
19. a78
20. a78 WiFi
21. a68
22. a68 WiFi
23. a98
24. a128
25. eS78
26. eS98
27. eS128
28. CP100

If there are multiple identical models (e.g. two networked CP100s), the highest serial number is preferred.

In the event that you have two sonar modules and the top prioritized module provides only depth, while a secondary module provides depth and temp, the data sentences are handled on an individual basis. Therefore, depth will be taken from the first unit, while temp will be taken from the second. Here is an example of this in the real-world. You have a CP450C depth-only transducer and a CP300 depth/temp transducer. The system will take depth from the CP450 and temp from the CP300.

It is important to note that the visible presence of a bottom signal does not necessarily mean that the system recognizes that as bottom and therefore may pull the data from the next prioritized sonar source. To check this, simply turn on the “white line” overlay on the desired sonar application. If the white line is not present said sonar does not have a signal sufficient enough to classify it as bottom and the system will progress to the next prioritized sonar for a depth reading.

If you happen to lose bottom with your top prioritized sounder and a secondary sounder has a bottom reading, the data box will populate with that secondary information.

If no fish finder apps are open, the system will continue to ping the sonar modules that were activated from the last active sonar page configuration. If those modules lose bottom the system will go into “bottom finding mode” in which it uses the prioritization list to ping the highest ranked sounder. It doesn’t try to locate bottom with a secondary sounder unless you open an app instance that includes no higher prioritized sonar.

Reference URL's