Humminbird Side Imaging Forums
Side Imaging Forums => 997c SI, 998c SI & 999ci HD SI => Topic started by: Humminbird_Greg on April 25, 2012, 03:51:57 PM
-
Just looking for information here as to everyone's experience with loading waypoints to their units after updating to the 6.180 (Waypoint Management) software.
-
Mine worked fine. I exported my nav data to SD card, deleted all nav data on 998, put sd card in computer, opened in HBPC, created my groups (no waypoints in Home only groups) moved waypoints to groups saved to sd, turned on unit asked if I wanted to load, selected yes, the "file" structure on 998 looks just like it did in HBPC.
I currently have 5 groups under home and no way points in Home. My default group is Misc and then I sort them from there by moving them to an existing group or creating a new one.
-
I put the SD card in after I have started the 998 and the waypoints load just fine. If I put the SD card in and then turn the unit on the waypoints do not load.
-
Thanks guys, this is the type of feedback I was looking for. Now, why is this different from one unit to another
-
Greg, that would be a good question to ask your guys. They build these things..
I would guess, cpu timing, single thread or multi thread. bus management, card slot reliability, for starters..
chuck
-
Sonar2000,
That was more of a rhetorical question and one I realize I should now not have asked. The point of this poll is to demonstrate that some units do act differently so that Engineering would know to take a closer look at the how and why this is happening.
-
ok, good way to go. Hopefully some one will realize your survey value.
chuck
-
Wow, wish I had seen this post a year ago.
I had hell with 6.180 and WMS. I had 1197 and 998 units and both had problems.
Waypoints would load fine. WMS did seem more sensitive to WP corruption. Or caused it?
Tracks were a horror story because I had "third-party" products like Lance Vick's Boatlanes and Tommy Martins GpsLakeMaps. WPs would load, but tracks were ignored.
Track problem was HB released WMS and failed to document at the time the HB Track data-format was changed. Found out this after weeks on phone with 3rd parties and HB Support.
Shortly afterward, HB Tech Bulletin was release to run all navigation data thru HumminbirdPC to verify and validate NAV data. HBPC did not fix one single track and my units continued to crash access NAV data and tracks continued to not load or corrupt the NAV directory.
All NAV data was run thru HBPC and loaded via SD/MMC cards. Finally used GPSBABEL to convert HB GPX data to Lowrance USR format and also obtained USR from 3rd parties. Then ran the USR files thru HBPC which recreated a new GPX file which was successfully loaded onto units.
Only worked by "forcing" HBPC to convert the USR to GPX data. HBPC FAILED to correct its own GPX data.
I believe HBPC 4.3.8 still has this fault.
-
You dont have to force HumminbirdPC to convert Lowrance *.USR files to *.GPX files. This is done by selecting File Open then selecting the proper Files of type. I do know that with some Lowrance units that you can save their Nav Data in several different formats; I think currently that version 3 with depth is the one that works best but cannot guarantee that everything will convert correctly.
It sounds like HumminbirdPC failed to recognize that the track files that you converted from a non-Humminbird unit source would not work correctly. It did not generate the track files but may have not been able to convert them into a usable form from the Lowrance file. Anytime you use track, route or waypoint data from a non-Humminbird source you can have conflicts like this.