I tried several approaches to getting information out of a Humminbird 161. Finally got something useful by using minicom in a terminal window to capture streaming data from the unit. Minicom injects identifying stuff into the stream in a rather disrupting way, but many sentences remain usable. I capture the complete stream of output and post process it with a small commandline code to get clean sentences that have agreement between the transmitted checksum and a calculated one. It currently uses intermediate files in a batch arrangement, but it seems as though it would be straightforward to modify it for other styles of processing, such as pipes. I also had to make a cable for it from sketchy, often incorrect info. Hooking it up the first time was a bit shakey, cause it was a "it'll either work or smoke" kinda deal since I don't have a scope to check signals with. Works now, gets the $INxxx and $GPxxx sentences anyway, with good agreement between the gps unit and a Garmin etrex legend, esp. when the WAAS is up on both. Will try it out on a research project soon (next 2 weeks), more after the trial runs. -- View this message in context: http://www.nabble.com/Low-Budget-Bathymetry-tf2295912.html#a11002316 Sent from the qgis-user mailing list archive at Nabble.com.
_______________________________________________ Qgis-user mailing list [email protected] http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user
