Incorrect file header error when trying to open log file

[lt1350]

Hi, I tried the search function without much help. I have recently gotten set up with an mpvi pro and aem wide band and everything has been working fine. I recorded a log on my way into work today and just went to open it and I am getting an error that says Unable to open file. Incorrect file header. What would cause this issue? I can open a log that i recorded last week just fine. I have not updated anything in the last week and I saved this file the same as I normally do. I am new and still have a LOT to learn. Is there anyway to recover this file so I can review it? Or should i consider it lost. Any idea what happend for this particular file?
Thanks for any help!

[daniel76309]

I see you are not getting any help with this. Did you get it figured out? I am having the same problem, but I have found that yesterday's log might not open, but today's will, i.e. it is an intermittent problem, and has nothing to do with the files having been recorded with a previous version of the software or whatever. In reading your post and thinking about this, I read something about the file being corrupt and now am wondering if it might be due to glitch happening while recording, i.e. which possibly could occur with a faulty USB cable. I am going to give that a try. If you learn anything, please post--obviously you are not alone. I am not all that knowledgeable about this either. trying to learn.

[b4black]

Add me to the list. Using the beta version for months now without issue. I can open old files, but can't open a file I recorded three days ago. Nothing odd or abnormal about this scan, other than not opening.

Frustrating.


Edit - just updated to Version 4.4.4 - same problem

[mechanicboy]

3 years later and this still hasn't been solved? I'm running into the same issue

[winter63]

bump having same issue?

[hjtrbo]

Posting a fucking log would help. What are we, fucking physic?

[Devan Montano]

Well if they could open the log file maybe they could send it. That?s the problem smartass

[chevota]

hjtrbo has a point. So I edited a file to give the error, per the screenshot. I was able to attach the file, because obviously if you have a file that gives an error, you have a file to post.
Sorry Devan, I couldn't resist

error.jpg

31 Jul '24 pm.hpl

I think the file is screwed, but posting it does seem like an obvious thing. I don't know how those things are written but it makes no sense to me, and I don't have a decoder ring so I wouldn't know how to spot what is wrong, or correct it if I did.
The only clue I can give you is the header seems to be the very first bit of data. How much of it is the header I don't know, but better than some bit somewhere else. Or maybe the whole file is hozed and it faulted on the header because it was the first thing it looked at.
Fyi, out of over 1500 of these I have zero bad ones. Even when the USB was pulled out mid recording, the file was still good. So if it was a one time thing I'd just write it off. If more often then I'd write a ticket to find out wth is going on.

[hjtrbo]

Well if they could open the log file maybe they could send it. That?s the problem smartass

Righto dip shit. What's opening a file got to do with attaching it here.

[hjtrbo]

I think the file is screwed

Yeah, looking at it in hex doesn't give anything obvious bar the first few bytes. The rest is encrypted. I'm voting she's also toast.

[skylinedan]

Block head for you.