SD Card Logging Issues

[NigeT]

Week I finally got TunerStudio too connect over BT - I had to remove the MS3 BT device from Windows and repair and get new COM port signed to get it to work! Seems faster over BT strangely, but I got exactly the same error when trying to download a log from the SD card.
This seems a very consistent failure.

[NigeT]

Since USB without BT adapter and BT without anything plugged into USB show the same symptoms does this suggest a firmware or even a hardware issue? Thanks.

[LT401Vette]

Seems faster over BT strangely

We normally try avoid talking about feelings on this board as that will typically run for pages with no results. MSQ's and logs will produce real answers.

However, that being said, your comment above would indicate to me you have some sort of problem on your USB. BT is convenient, but should never be faster than USB.

[NigeT]

That makes a lot of sense and I am concerned that my perception could be misleading. Doesn't the fact that TunerStudio reports the same error for both BT and USB interfaces not suggest that something they use in common for SD card interactions is faulty?
Could you guide me as to what I should log to help diagnose this? I don't remember seeing any configuration in TunerStudio that could impact the functioning of USB, but please correct me if I'm wrong. Do you know of any logging that could possibly indicate what is wrong, or is it just time to make my car unusable for a few weeks and send the MS3 back to MS-Labs?

[NigeT]

P.s. Thanks for the continued assistance - it is appreciated.

[Reverant]

Can you remove the SD card from the ECU and see if it has log files on it, and if so, are they ok or corrupted?

[LT401Vette]

A TunerStudioAppDebug.txt may provide more info about what the error is.

Starting with Reverant's idea seems god though, if the PC can't read the log, then the MS never will

[NigeT]

I thought it'd already said that the laptop was able to read the files off the card, apologies if not.
Thanks, Nigel.

[NigeT]

Oh and the files cover ok and the logs can be properly accessed by MegaLogViewer MS software.

[NigeT]

I got a log of attempting to download log files from the SD card. This was over Bluetooth because it was easier than pulling the adapter off the serial port so I could try USB.
I tried the oldest file first - it failed. I tried a bit more recent file and surprisingly it seems to have succeeded. I then tried the most recent likely to have data and one from this morning and they both failed.
Hopefully this link will work since I could not find a way to attach a plain file and not a photograph.
https://www.dropbox.com/s/308ah182yozjk ... g.zip?dl=0

[NigeT]

Is there a problem with the zip file?

[NigeT]

@Phil did that log file show anything or is there something else I can do to help with problem diagnosis? I will try pulling the SD card out this weekend but since I've been able to plug it in the laptop and read logs off it before when I was having this problem reading via MS3 & TunerStudio I'm not expecting any different now. I do have a brand new 16GB class 10 SD card to put in in place of what I currently have in there (can't remember, probably class 4). Thanks, Nigel.

[LT401Vette]

It looks like it is downloading fine, then stops...
A read comes up short and times out. It seems several attempts at the next commands to the controller fail, but then it comes back.

I'm not sure if it is a comms issue or perhaps something on the card tripping up the firmware/

Did you do a fresh format or try a different card?
I know you did say you can read the files from the PC.

[NigeT]

Hi Phil, yes I have been able to read all the files into my laptop and then open them ok so far. I haven't pulled the SD card out yet this time though (pulling trim off, carpet up etc is a bit of a pain), I will try to do so tomorrow. I do have a brand new card that I'll put in instead; does it need formatting in any particular way for best results?
Are the card drives used in MS3s typically a bit flaky? Never had a failure with any other device; laptops, cameras, tablets, phones...
Comms failures are rather more worrying; does this mean that tune burns may be corrupt?
Other than putting a new SD card reader work better is there anything else I can enable to get more diagnostic information to narrow this down.
Thanks, Nigel.

[NigeT]

Swapped in the new SD card today. Copied the 95 .MS3 files straight off the old SD card onto my laptop using its internal card drive. TunerStudio converted all the .MS3 files.
Thanks, Nigel.

[LT401Vette]

does this mean that tune burns may be corrupt?

Quite doubtful... If TS does not get a positive confirmation from the firmware that a write or burn did not complete successfully, it will retry. If it fails after 3 attempts, you will get error messages.

In this case reading the SD files back, you are getting error messages because the data is stops and is not making it back to TS successfully to process. It is really a matter of whether that is because there is some reason the file is hanging the firmware or a comms issue is disrupting the read.

[NigeT]

Thanks Phil. Seeing as the laptop can read the flies and TunerStudio can convert them... is there any reason to think that the files are hanging the firmware? Are there any limitations that the firmware had on the files that it is not controlling, given that it writes them? I don't really get what property that a file might have that makes it unreadable by the firmware but readable by Windows Explorer or whatever...

[LT401Vette]

is there any reason to think that the files are hanging the firmware?

Not that I know of, I might be more inclined to think there is something about the card itself.

[NigeT]

I don't see how that marries up with the fact that the card has never shown any problems anywhere other than in the MS3. It even apparently writes fine in the MS3 and every file written has been copied off cleanly by the laptop using its internal card reader.

[LT401Vette]

Agreed that it is odd, but seems easy to try a different card.

Serial noise seems odd as the engine isn't even running.

Downloading over serial is working for the rest of us, so what is different in your case? The only likely differences are the card, the cable or perhaps something about the formatting of the card.