Using Android 4.2.2 Tablet with a75 MFD both fully updated. After several hours of use both tablet and a75 become completely locked up, the MFD won't even switch off by pushing its power button.
How did your test go?
I've just submitted another post as the whole a75 is becoming unresponsive to inputs/screen selections after about 4-5hrs use requiring a reboot to solve. It's fully updated to v19.03
Q1. How did your test go?
A1. See my prior post ... in short, we were unable to duplicate the reported issue.
Q2.I've just submitted another post as the whole a75 is becoming unresponsive to inputs/screen selections after about 4-5hrs use requiring a reboot to solve. It's fully updated to v19.03
A2. Given the reported symptom, it is recommended that the MFD be sent to Raymarineâ€™s Product Repair Center to be bench checked / serviced.
Q1. Is there anything I can do "in the field"?
A1. Should the Navionics Sonar Logging feature be enabled, you may want to try configuring it to OFF. I am aware of no other options which may correct the reported symptom other than possibly performing a System Settings and Data Reset command. Unfortunately, should the problem persist, then there would be no other recommendations other than to have the MFD bench tested/serviced by the Repair Center.
Q2. Would a large area of Navionics charts affect it?
A2. With the possible exception of having enabled the Navionics Sonar Logging feature and then having executed it continuously for a very, very long time as specified above, I am aware of no issue related to the use of Navionics cartography which may trigger the reported issue.
I've switched off Sonar Logs and the MFD has been running well for 9 hours with no sign of:
a) the unit becoming unresponsive
b) the android app freezing.
It would appear that this has therefore (temporarily) solved our problem
It's unfortunate that we can no longer contribute to Sonar Charts, however, basic functionality is more important. Perhaps this can be sorted in v19.04?
Unfortunately, no further LightHouse II software releases are currently planned. As I suspect that the problem is associated with logging for long periods of time, you may want to consider configuring the feature OFF when not "mowing the lawn" to perform data collection.