MSefi.com read only forum (Jan.15,2018)

So I tried ST for the first time today and it worked great. I was able to connect easily to the BT purchased from Phil with my laptop and android phone. I collected multiple logs that were uploaded to ST.com and then retrieved them this evening. I was worried at first because I looked in the file manager on the phone and it said there was no data, but no worries because they were already uploaded and I had set the phone to dump the files after upload. Very cool!

Of course I was out with my friends and had to walk around showing all of them the runtime data on my phone!

It has been some time since I have used MLV VE Analyzer as I usually use the live version in TS. What is the correct process to analyze several logs on the same msq file. I collected about 6 different logs today and want to collectively analyze them to the msq that was running.

Thanks, Mark

Good feedback... Both Shadow Logger and ShadowTuner.com are still pretty basic, but good solid comms and log transformations are the key concerns first... The additional bells and whistles are coming.

It has been some time since I have used MLV VE Analyzer as I usually use the live version in TS. What is the correct process to analyze several logs on the same msq file. I collected about 6 different logs today and want to collectively analyze them to the msq that was running.

When you have the File Open Dialog up, press the CTRL or Shift key to do multi select of the files. Then they will all load at once and you can use them all as input for VE Analyze.

Thanks Phil, I knew it was easy...

More feedback; I noticed that some times Shadowlogger would say that it was connected to the Bluetooth adapter but that the BT couldn't connect to the controller. Usually after waiting for a short time it would connect and work fine. Or if it was not connecting, restarting the app would still throw the error but then connect after a short pause. There were other messages but I can't remember them as we were on a rockcrawling trip today. I will pay attention to them next time and forward to you.

Mark

So once shadowlogger is running it works great. I am still having an issue with my HTC Incredible with getting to the start read point. my phone connects right away to the bluetooth adapter with no issues every time. But then i see an error flash by that says that the bluetooth cannot connect to controller. It eventually works but I have not been able to figure out if there is a starting sequence that should be followed or what I am actually doing that achieves the connection. Once it connects then it is very stable, even through stops when the motor is turned off( to run in for beer) it always comes right back and continues reading and logging.
It also uploads with no issues,ever. It would be cool to have a downloading indicator.

How do you access the accelerometer or gps related logs?

Thanks, Mark

What version are you using? It will say in the top right corner, next to the title.
There should be no special start up sequence, it should just connect when you start, if it fails, you should be able to hit the "Start Runtime Reads" Button.

To log the Accelerometer data you have to turn that on in Preferences, then the FRD files need to be transformed by either ShadowTuner.com or the beta TunerStudio MS

I am using 1.07 now and was at 1.05. I was hoping that it would be different in the new release but it is the same in that respect.

Actually 1.07 did make an attempt at addressing that, but i think it created a new problem... In 1.05 at least if it failed, I think you just generally needed to press the Start Runtime Reads button, but in 1.07 it seems the button function gets out of sync... I need to get a fix out for that. It is messing up the CommDebug log too.

I was wondering what the CommDebug option was for. I believe that right after toggling it the connection started up? coincidence?

I had 1 other user using MSII Base code that said that happened to him too. It didn't start working on startup, but when he started Comm Debug it did...
All Comm Debug does is:
- stop all reads
- start a Comm Debug log file with all bytes sent and received
- re-interrogate the controller to identify it
- start runtime reads

Then when you stop Comm Debug:
- Stop Runtime Reads
- Close the Comm Debug Log
- Bring up the comm Debug in an email to send to me.

So it _should_ be the same thing as pressing "Start Runtime Reads"