Hi Matt!
Any news on this?

Riba wrote:
Sorry that this is taking so long Riba - I do plan to look at it as soon as time allows and hope to report something soon.

Matt,

I think there is a problem (and has been in the past) with importing sl2 file times during the months where there is an extra hour on top of UTC during BST (or perhaps the way Lowrance records the time stamps). In the past i have fudged it by importing, then changing the track start time. Sorry, should have questioned it earlier....

ill email you the results.

SL2 file times have always been a problem for us, because they do not store the absolute start time - only the relative offset of each ping of data. The way we try to solve this is by deducting the total time of the track from the last modified time of the sonar log and, although this often works, is also often doesn't. In particular I cannot use any test files that users in this thread sent to me because the zip/unzip process creates a new log file with a new modified time. Issues with modified times varying might be down the unit and the selected time zone, but I will investigate further. In simple terms, the best way to ensure correct start times for SL2/SLg and more recent HB logs is the make a note of the start time (you could drop a waypoint) and then manually adjust after import into RM. SL3 files do give an absolute start time, which is very helpful.

Matt, did you get a chance to look at the excel sheet? It shows various start times depending on global display and import settings....

Like you suggested, in the past I have edited the start time after import.
Cheers

Thank you Matt!
That is exactly what I have been doing all this time (writing the start time on a piece of paper and correcting latter). Also, the waypoints have the wrong time too so you cannot compare with them (I write down the time of some WP too so I can latter correct all of them accordingly :)
I just thought I should be able to have it done automatically.
Also, I believe my HDS Gen 2 touch has the possibility of recording sl3 files. Would you recommend recording tracks as sl3 files instead of sl2? Am I going to have some other problems (with BC or anything else)? RM is now supporting the sl3 format, right?

Matt wrote: The main problem for me is not this shift, but unclear for me (or wrong) work with time zones. I got files from device (Elite TI) in UTC, no way to change it. I tried all combinations of time related settings - no luck, I can't set RM to understand that my timezone is UTC+4, my files from device is in UTC, and I want to see track times in UTC+4, my local time.
I've found a workaround - freeware utility capable to modify "Created", "Modified" and "Accessed" time of single / multiple files by TZ offset. Then all tracks can be imported without manual time correction.
Hope RM will gives us such ability without additional utils.

So Matt
can you confirm that this still remain an unresolved issue up to 2.1.50 version. I'm still gettin wrong timing.

What sort of sonar log file is it? SL2/3? What time do you think it should be? If you can send it to This email address is being protected from spambots. You need JavaScript enabled to view it. I can take a look.

Matt wrote: files are sl2.
And every log opened had wrong starign time showed. sometimes even in minutes.
I'll send you some files via email