Hi!
Are there any benefits in logging sidescan data as sl3 instead of sl2?
The position data seems to be similar from what I've heard (1 meter resolution) but do they store more data from each ping or do anything else that might improve the sidescan data?

I'm still using an old version of software on my Lowrance Gen 2 Touch but now when we have sl3 support I will do an upgrade of the software.
Hopefully it will insert heading data from my gps compass in the file also, it refuses to insert heading data with the current software that only supports sl2.

/hakan

As far as I am aware, there is no real benefit unless you are logging SS3D data, which can only be logged to SL3. We can't use that data yet, but it would still be worth logging if you can.. As far as RM is concerned, no benefits (although we can get an absolute track start time from SL3).

Thanks for the info!
I'll upgrade and hope that they have sorted out the bugs and inserted heading.
Once you get 3D running it will upgrade to some new hardware ;)

/hakan

Is it confirmed that SL3 still only has a 1 meter resolution? I'm very curious why they chose this, when horizontal WAAS performance is less than 1m 95% of the time, assuming the chip-set on the Lowrance units utilize all the WAAS correction messages. Even with smoothing in the interpolation algorithm, shouldn't additional precision pay dividends? I would think 0.1m precision would be perfect. It wouldn't be that much more data stored even if they had to jump from a float to a double (or similar) to accommodate.

I think it was a missed opportunity when moving to the new format, let's put it that way. This is especially annoying for those putting a higher precision GPS through their units, as this extra precision is lost. As you say, data storage is readily available and very cheap these days so a bit of extra file size wouldn't really be an issue.

The data is exactly the same as sl2 EXCEPT if you are using the new 3D sidescan module. They made the new format specifically to hold the new 3D sidescan data so it could be played back.

If they had any imagination a more elegant solution would be to have it default to sl2 and only go to sl3 if the 3D sidescan module where hooked up. Speaking of lack of imagination, why put in a Bluetooth module and then not even bother to add a Bluetooth keyboard profile so you could use an actual keyboard for waypoint and track names instead of pecking at a lame onscreen keyboard. The Bluetooth is worthless for the 99% of consumers who don't have Bluetooth Power Poles.