Hi Matt,
I did a survey with some fairly decent SS data, however it seems there was a problem with the logging of the standard transducer's depth data. All the depth values are all around 0.25m, in spite of the sonar data looking good. (see attached jpeg). The only abnormality I can see is that DS data range was not set properly. It seems the Lowrance gave some sort of problem?
The consequence is that the slant-range correction does not work.
Now, I can go and edit all the depths, and have done so, but it seems the slant-range algorithm does not use the corrected depths, and it still does not work.

Can you kindly help me with this?

Regards,
Billy

Do you see this effect in any other of your tracks?
What are the two channels on the left, DS (bottom) and primary (top)?
Unfortunately I don't think there is a way to get the slant-range correction working here if the logged depths are not available, but it would be interesting to understand what is going on with your recording (we are planning to use modified depths for SRC in the future, btw).

Thanks for the prompt reply , Matt.
No I have not seen this before, and yes, bottom (DS) top (primary).
Every now and then while on the water the Lowrance primary display shows only the first meter or so with incorrect depths at around 0.25m. A reboot usually fixes this. It seems this is the root of the problem and that I need to check the primary display first before I log the data.
However what is strange is that the logged primary data in this case seem perfect.

I will keep the data until your SLC module can use the edited depth data.
Any idea how long before this is implemented, it will make for better corrections I am sure.

Thanks again,
Billy