Thread: test compilation

testing the AS GPS HS antenna (from the manual that comes with the puck)...

Confirm the Heading Sensor Operation
(Heading Sensors only [AS GPS HS])
It is important to confirm that the Heading Sensor is installed correctly by
reviewing the heading digital readout.
NOTE: This procedure should be performed at slow speeds, in calm, open water, in a
large area that is far from shallow water, boats, or other obstacles.
1. Press the MENU key twice to open the Main Menu.
2. Select Navigation tab > North Reference > Magnetic.
3. Press the EXIT key.
4. Select Setup tab > Select Readouts.
NOTE: If the Select Readouts menu option does not appear under the Setup
tab, change the User Mode to Advanced. Select Main Menu > Setup tab >
User Mode > Advanced.
5. Select a Readout position and use the RIGHT or LEFT Cursor keys to
select Heading. Select another Readout position and select Course.
6. Press the EXIT key until the Main Menu is closed.
7. Press the VIEW key until the Sonar View is displayed on the screen.
8. Navigate the boat in a straight line, in calm, open water at 4.5 mph.
Compare the Heading digital readout on the screen with the Course
(COG) digital readout. The readouts should be within approximately 5°
of each other.
Adjust: To adjust the zero point of the Heading Sensor, selectMain
Menu > Navigation tab > Heading Offset. Press the RIGHT or
LEFT Cursor keys to adjust the setting.
If the procedure failed: If the Heading digital readout is
significantly different than the COG, the Heading Sensor might be
installed in a location with too much magnetic interference. Check
the installation location and possible magnetic disturbances in the
area.

Originally Posted by rnvinc

Contour XD lake list

ContourXD Map Lake List by State - Download PDF Added

boogidy boogidy

Mounting a shoot thru xducer in aluminum boat...

img]http://www.crappie.com/crappie/attachments/fishing-electronics-photography/130736d1373385239-transducer-help-humminbird-597-ci-hd-optional-inside-hull-transducer-mounting-pvc-tube-1.jpg[/img]

HB "Temperature Graph"...

It's basically a historical trend of the temp of the water surface at the exact point on the lake of each "ping"..

We all know that the unit plots the most "recent" ping data at the rightmost edge of the screen...

At the very same time the unit also records and plots the water temp in the "Temp Graph" at the rightmost edge of the screen right above the sonar ping's data...

This gives the user a trend of the water temp thru the exact track of lake surface water history showing on the screen...

The 20° "range" is merely how the unit graph is set up ..
*10° above water temp at that ping...
*10° below water temp at that ping....
*current water temp at that ping in the middle...

This has a very limited use for the user because its unlikely for there to be a very big swing in water temp simply in the sonar and water temp "history" showing on the screen...

It could, tho, easily be used to find shallow underwater springs....by trolling thru shallow water..a sharp drop in the "temp graph" trend could very well indicate the boat just passed thru an underwater spring...

Or maybe for those that fish outflow waters of power plants...a sharp increase in water temp could indicate the boat just passed thru the power plant outflow stream...

No apology necessary Ferdi. The different GPS Receiver names get as confusing as the unit names sometime (there is no GRP-HS model GPS Receiver). I don’t know where your original post about the AS-GRP is at.


For future reference:
AS-GRP needs 6.300 or higher version software
AS-GPS-HS needs 6.570 or higher version software

The unit also has to be compatible with this accessory. Some units may receive these (or higher) levels of software but may still not be compatible. An example of this would be the 598ci HD Si unit which currently uses a software version of 6.640 but it is not compatible with either the GRP or GPS-HS GPS Receivers.

All in one HB xducer...

Sonar
HD Side Imaging/HD Down Imaging 180° coverage
455kHz / (2) 86° @ -10db
800kHz / (2) 45° @ -10db
Digital Signal Processing (DSP) DualBeam PLUS w/ SwitchFire
200kHz / 20° @ -10db
83kHz / 60° @ -10db
Depth: 1500', 5000'*
8000W (PTP), 1000W (RMS)**
Precision GPS
Built-In Cartography: TriFuel
DUAL SD CARD SLOTS - Use one slot for advanced cartography. Use the other to save screenshots, sonar recordings and waypoints


*Optional 50 kHz transducers available for extreme deepwater use.
**To obtain 1000W, optional deepwater transducer required.[/QUOTE]

The 200kHz depth data helps in some of the automatic SI sonar functions like the Auto Sensitivity but not a whole lot besides that.

The 200kHz depth data will control how often the unit pings the 200kHz sonar as long as the Max Depth is set to "Auto".

Setting the Max Depth to any manual setting controls the maximum amount of time that the unit will wait until pinging again (it will ping sooner if it gets a bottom reading).

The only tie-in between the 200kHz depth data and the Si sonar data is in how often the unit can ping the Si sonar. This can be slowed down if the unit is having to wait a long time as the unit searches for the bottom reading.

The water column area is a product of the Si sonar data - not the 200kHz sonar data. This is why someone with bad 2D sonar data can still have good Si sonar data.

Posted by Bill Carson (from HB) at another forum...

i]It is Humminbird’s recommendation that you always use the most recent version of software available for your model. We update software for various reasons. Fixing minor bugs, adding new features, changing functionality of existing features. We do this for the benefit of the consumer who uses our products.

However there are individuals who believe that there are benefits to using lower versions of software than what we are currently loading on production units. On products built today, you cannot go back any further than version 5.600. There were hardware changes made at this time which will not allow you to go back further without “bricking” your unit.

At the same time, it is also possible to “brick” a unit going back only one previous release if the unit firmware becomes corrupt or the hardware is damaged during this process. ‘Bricking” a unit IS NOT covered under warranty. However, if you successfully go back a version of software and your unit operates properly after the downgrade but later has workmanship issues unrelated to software, these repairs would be covered under warranty during the standard warranty period. Humminbird charges the standard repair fee if resolving “bricking” issues.

PLEASE NOTE: There are several situations which can cause issues if you are not running the most recent version of software. Unit Networking is software version sensitive. Sharing waypoints between units is software version sensitive. If you are not networking products then the risk of running lower versions is minimized . Again version 5.600 is definitely a line in the sand which cannot be crossed.[/i]