Topic: Losing Temp display

[EZM]

Had the new boat out on her maiden voyage yesterday - most everything went well. I am running i-pilot link, 3 head units, 898 and two 858's on an Ethernet.

I went to the screen where I could set up my display readouts (voltage, time, depth etc....) and attempted to insert temperature in place of the navigation Cos (as I am on smaller to medium sized freshwater lakes and don't  need this displayed all the time).

Most of the time, the temp does not show up after I change it, on a few occasions, it shows up then magically reverts back to compass .....

not sure what the issue is ............ any thoughts?

[Humminbird_Greg]

EZM,
On some of the Views in the units the digital readouts are coded to show only certain types of information and cannot be changed or may change according to the View that you are on or the function that you are using.  Look under the Select Readouts portion of your operations manual.

[EZM]

Thanks Greg,

That explains my poltergeist .... lol .... however, water temperate is a critical piece of info and having no ability to see it on many of the navigation screens (unless you drop depth out of the only available box) is not great. ...... maybe an opportunity for future changes?

Lakes and Rivers flowing in or out of Lakes or other watersheds, further north, where stratification (water temp and oxygen) patterns differ from the continental US, this is a critical feature for DURING navigation. we need to be able to find the right conditions that hold fish - water temp is one critical factor.

Up here, during navigation, we need to see the depth (so we don't tear our leg off the outboard) AND we need temp - to see the difference in water temp as this is where certain species of target species are found.

With only one customization box (where depth must take precedence due to safety) not having the temp option isn't ideal.

I vote we add another box or at least make these customizable. My heading (Cos) is irrelevant on a water body I'm completely familiar with (in my case).

Thanks for pointing that out .... at least I know it's a limitation of the unit - not a malfunction.