castillaricardo Posted January 20, 2023 Report Share Posted January 20, 2023 I've been using Megalogviewer HD to review logs but I'm not having luck importing the logs without manually modifying the CSVs. Maybe I'm missing something, but I go to 'Logging' > 'Export', select 'Full Log' and 'File Time'. Once the file is exported it contains a blank line after the units, and I'm not able to import into MLVHD unless I remove them both. See screenshot in the link below. Am I missing something? I've contacted EFI Analytics about this but haven't gotten a response yet. Linked is a sample exported log where line 3 contains the units, and line 4 is the white line, and the same log with these lines removed that I'm able to import into MLVHD. Any ideas? https://1drv.ms/u/s!Amu_1gWOWFlvgT42-HPtrtikjpBj?e=1w9vPW Quote Link to comment Share on other sites More sharing options...
Pete_89t2 Posted January 20, 2023 Report Share Posted January 20, 2023 Next time you export your log in PCLink, try skipping the "File Time" parameter. I've been using MLV HD histogram features for some time now to fine tune my fuel tables with ECU logs, and I never had a problem with MLV HD importing my logs when I did the export as follows in PCLink: "Logging" > "Export", select only "Full Log" check box. Quote Link to comment Share on other sites More sharing options...
castillaricardo Posted January 20, 2023 Author Report Share Posted January 20, 2023 I tried as you said but still get the same error. I've uploaded the new exported log to OneDrive too. It has the same units line and blank line that I have to manually remove. Quote Link to comment Share on other sites More sharing options...
Adamw Posted January 22, 2023 Report Share Posted January 22, 2023 I think the problem is we have a unnamed padding column in the export so there is no character between the quotation marks, MLVHD doesnt seem to like that. If I put any character where I have the two pink lines below then it opens fine. Im not sure if that column needs to be there for some reason or if it is just an oversight. Ill ask Vaughan to have a look when he gets a minute. castillaricardo 1 Quote Link to comment Share on other sites More sharing options...
castillaricardo Posted January 22, 2023 Author Report Share Posted January 22, 2023 Thank you, Adam. Adding a character as you said did the trick in my older logs as well. One more tiny thing I noticed is that Lambda 1 says Lambda1 in the exports (missing a space). Obviously not an issue, just figured I'll mention it because the other Lambda [2-8] do have a space. Quote Link to comment Share on other sites More sharing options...
castillaricardo Posted January 30, 2023 Author Report Share Posted January 30, 2023 I noticed yesterday that the padding column is not present with internal ecu logs and imported into MLVHD without modification Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.