The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 802 - File: showthread.php PHP 7.4.33 (Linux)
File Line Function
/showthread.php 802 errorHandler->error





Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[CA] [CA11] Networked MFDs with CPU/resource issues
04-18-20, 06:27 PM (This post was last modified: 04-20-20 05:18 PM by Chuck - Raymarine - Moderator.)
Post: #1
[CA11] Networked MFDs with CPU/resource issues
Hi There-
We are cruising full time, currently in Mexico. We have two MFDs networked (via SeaTalk ng): An A65 at the helm, and an ES98 at the nav station. Also other various Ray devices. We are running Navionics Platinum+ chart card in the A65 unit, since we want SonarChart Live data visible to the person at the helm.

Like other posters on this forum, we are discovering that the CPU/Memory resources of these MFDs are no match for the flood of data created by the SonarChart Live feature, especially when coupled with multiple tracks, etc. We have ghost rebooting issues, screen draw issues, freezing issues, etc. The unit at the helm is almost unusable.

Questions:
1) It is my understanding that LightHouse 3 is available for our ES unit, but not the A, and therefore we should NOT update. Correct?

2) Is there any update in the works for Lighthouse 2, to change the way the units handle data by default?

3) Given the limited capability of the A unit, is there (PLEASE!) a way we can run the chart card in the ES unit (taking advantage of more computing power), but still display SonarChart Live data on the unit at the helm?

4) Has Ray/Navionics considered an option where the system only logs SonarChart Live below a certain depth? These numbers are not meaningful to us at depths greater than 75 or 100 feet, but we don't really have the option of shutting it off, as we are often traveling in areas where there is NO current depth information, or one very outdated (and inaccurate) lead line depth recorded from the 1800's every mile or two.

4 a) The idea that we "turn off sonar logging when this data is not needed" is, I'm sure you can agree, not a very workable solution for those sailing full time in often skinny water. What other actions can we take to reduce the data load on these MFDs, or other ways to lighten the load and improve their usability?

5) In order to get these MFDs up and running closer to capacity again, do you recommend a power on reset? If so, which order do we do them in? With chart card installed, or no?

Any answers and details you can provide are much appreciated.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
[CA11] Networked MFDs with CPU/resource issues - randy@onlinecruisingguide.com - 04-18-20 06:27 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)