NefMoto

After using the ME7Logger utility, I realized it's pure greatness and wanted to start an open source GUI program to make it even more useful.

I've already finished the basic parsing routines, and created a class library that will make it easy for developers to interact with the ME7Logger session and allow for easy, real-time display and/or processing of the output.  As an example, I've created basic form that allows for starting and stopping of a log session, and displaying all the logged variables real-time in a text box control.
I've made it possible to start a new logging session right directly from a session/log file, or while connected to the ecu.

Now that the proof of concept is complete, I'd like to make the GUI useful.  Editing configs in visual way (instead of editing text files), and graphing data on charts, widgets, and other general dashboard type controls, are my initial goals.  Where it goes from there, we'll see.

This is written in C#, so you'll need Visual Studio with the ability to hook up to a Team Foundation Server for source control.  If anyone is interested, go to codeplex and sign up for an account if you don't already have one.  Download the source and plug away.

https://github.com/sbloom82/VisualME7Logger

I hope this draws some interest!

EDIT: You can download the current release of VisualME7Logger here:

https://github.com/sbloom82/VisualME7Logger/releases/download/v2018.07.02.28/VisualME7Logger.exe

Current Version is v28

To run VisualME7Logger:
Copy the VisualME7Logger.exe into the ME7Logger directory before running!

The MELogger bin directory should be in the same directory as the VisualME7Logger.exe file, and the bin directory should contain ME7Info.exe and ME7Logger.exe

VisualME7Logger requires at minimum .Net 4 framework (4.5 and 4.5.1 also work)
Windows 8: If you receive a "Smart screen" warning upon executing the program, right click on the exe and select Properties.  On the Properties page, click the "Unlock" button to stop these warnings.

See attached screenshots

Like:)

I thought about doing something like this but making it so ALL the ME7 softwares (logger, info, check, etc) are on the same GUI. There is already a couple GUIs for the different softwares and they are good but I would like to see them all together in one GUI, plus the things you mentioned. Unfortunetly I don't have time to be doing this and I have troubles with getting ME7logger to work on my car...so there goes my motivation..I'm interested in seeing your end results though.

I like it and would contribute but don't have a C# IDE. I hope this takes off.

Visual Studio C# Express is free, and if it doesn't have direct TFS support, you can download Team Explorer separately to check out/in source.

Attached are few screenshots of the quick UI I threw together to show how easy it can be to create real-time charts in .Net.  This is literally just a few lines of code on the form that makes this work.  This currently uses the output library that I wrote and can display the results real-time on the screen from a log file or directly hooked up to the car.  I know this isn't very functional as of yet, but it's just proof that we can make charts and other controls very easily, and hopefully we can make something even better than what's currently out there, and for free!!! 

I would say I have about 8 hours total into this whole project.  Just think what could be done with a little bit of help and time.

Very cool!  :)

Worked on this a bit more last night.  Focused on parsing out the ecu file so you can select the measurements that you want to log right on the UI.  Will add logic for saving different measurement configurations for different logging profiles.  With this part complete, I should be able to finish off a more complete GUI for configuring and logging a session with a few clicks of the mouse rather quickly.

The first version which can hardly count as a beta is complete.  (See next post down)

Extract the zip file's contents to your ME7Logger directory.

Execute by running VisualME7Logger.exe (you will need .Net Framework 4 installed)

Choose ECU File, Select a few measurements, or load from a config file.

Click start logging... enjoy.  It will get better, I promise.  :)

Zip file attached here

Worked on it a bit more tonight.  Added Ecu File Creation, auto saving/loading of last configuration, other minor tweaks.

gone testing it tonight :)

p.s. i think that injector duty cycle calculation will be useful feauture

Very nice Project!!

doesnt work for me because i have COM3 port cable (COM1 busy at my laptop)

I'll add some more options tonight to allow you to use the right com port.

lol open the config file with notepad and change it to com3 then lol

so please show me where it is
because i didnt find it in both configs (visual logger cfg & ecu cfg)

inside my logger folder is a file called savedconfig , open it up with notepad and inside ,

[exe]
logger=C:\audi stuff\loger\bin\ME7Logger.exe
info=C:\audi stuff\loger\bin\ME7Info.exe
[dir]
logs=C:\audi stuff\loger\logs\
[logs]
configfile=1.8T Sport ORG.bin.se_template.cfg
[params]
defaultcom=0
setcom=1
comport=COM1
useftdi=0
setsr=0
samplerate=20
realtimesave=0
realtimedisplay=0
timesync=0
timestamp=0
single=0
autoclose=0
customlog=0
customlogpath=C:\audi stuff\loger\logs\custom.csv

it is 'ME7Logger GUI' config file lol

Ha, yeah, that won't work with the VisualME7Logger.

 I've put some work into this already... I'll have something ready tonight for sure.

 ;D woops , I am wrong then lol , thought that was part of the config  :P

Here's a new version with a new options screen.

right now, the graph only displays the following variables, so if you want to see anything there, make sure to include these variables.
"nmot" //EngineSpeed
"plsol" //BoostPressDesired
"pvdkds" //BoostPressureActual

update v1.4 available (check link on first post for download)

Added ability to run logger screen from log file as playback.

This is pretty awesome, thank you.

I like what you have done with this, nice work.  I'm looking forward to trying it out. 

I have run into a problem when trying to load a config file.  After starting the Visual ME7Logger I select Load ECU file, that goes ok and the measurements list is populated with numerous variables.  Next I select Load Config File and select the config file I routinely log with.  When the application proceeds I get fault stating:

System.FormatException: Input string was not in a correct format and several more lines indicating the program is having a problem with the config file.

Are there particular rules that the config file must adhere to? 

Upload your config file here and I will figure out what's wrong with it.

It just looks for the "[LogVariables]" line in the config file and once that's been read it will start reading in the selected variables by reading each line that doesn't start with ";" and getting the name by splitting on the first space after the variable name on that line.

I might suggest that you should just select all the variables that you have existing config file the first time around and save a new one.

version 1.6 uploaded.

Added support for ME7Check.
Added support for saving settings and config file from menu without starting a log.

Thanks for putting this together ...........

This is awesome!

Some more changes are in the works!

Working on configurable charting. 

I'll try to get some other stuff in with the next release too.  Hang tight!

looking forward to the next update  ;D, I was just in my junk room looking for an old laptop to keep in the car for this  :D, the motorways round my way are always empty at 12 midnight when I come home from my work  8), makes for good testing grounds lol

Version 1.7 Uploaded.

Added configurable graphing variables.  Choose any variable to plot on the graph.

Added graph image captures, freeze frame, general UI cleanup... other various updates

 ;D thanks , will be testing this today  ;D got a bit of a  problem with the car getting into 3 figures  ::)

One more update today.  I will probably slow down on this project for a while unless there are any other requests.  Cleaned up the UI a bit... got rid of the stupid rpm gauge. Made labels nicer.  Added tooltips to the graph lines.  Added options for vertical and horizontal graph resolution.

Posting yet another version to fix some bugs.  Sorry for the barrage of updates.

oh.. forget that it is GUI and trying to run it standalone
you should make a msgbox for such idiots like me :)

btw doesnt work for me (and me7logger too) because 'cant open com port' error=2 0x1
only vag-com can connect for reading logs

i will try to play with bauds..

This is just a wrapper around me7logger, so if you cant get that to work, this wont work for you either.   Sounds like you just need to specify the correct com port (look in device manager to find out which one your cable is using)  let me know if you need help, I can walk you through it.

if you are using a vcds cable you may need the vcp drivers

im using usb-kkl cable

download this and install the driver:
http://www.ross-tech.com/vag-com/usb/virtual-com-port.html

Once you install this, you might have to use the windows device manager and "disable" the virtual com port driver to make vag-com work the way it did with the other driver.

it is installed
i know which com-port it used and how to change it
but only vag-com can connect
other tools like me7logger and lemmiwinks are not
nefmoto logger can connect but saw only zeroes except calc egt which are ok

Hi,
finally i was able to test it and i have to say: you are improving the best! Thank you so far!
But i also have to say i have encountered a little problem during the graphic mode:
with the display-setting "line" or any related it looks really strange. the only possible view i could use was the point/fastpoint-style, but it was pretty annoying because it was pretty slow. did anybody have the same problem or is able to guess what causes this issue?
but although: the text-showing window in the right is cool add-on!

The fast-line/fast-point are going to give you the best performance possible.  The other options are in there merely as a beta option.  Regardless, any real-time graph plotting will be pretty processor intensive.  I have a 5-7 year old laptop (slow for today's standards) and it is able to display 10+ variables on the graph and keep up just fine.  Open up your task manager and see how the VisualME7Logger is performing regarding CPU%.
Your graph does looks a little funny though... seems like you rpm variable is jumping all around on you.  I'd be interested to see what those logs look like to see how it made a graph that looks like your screenshots.

i was wondering whether it is a problem of sample rates. so that the logger asks for a value and there isnt already one, so its using zero (but it looks like it uses infinity or something really big...)
but changing them had no effect.
maybe i have to explain that my "normal" me7logger is not always producing "." while logging, but sometimes also "o", the hint that the time gets too small. Maybe this could be reason for it? never had problems with the normal logs though.
the loggings that produced this behaviour lool normal so far. if you want to i can attach them although

Yes, attach the log file that was generated. there should be nice, smooth, linear values in there. I'll take a look.  Your graphs should look much nicer than what you see.  See the screenshot on the first post as example.

Concerning performance, another thing you can do is dial down the refresh rate of the logging screen.  Instead of refreshing every 50ms (I think that's default) try something more like 100ms or 250ms.  That should significantly increase the performance once you find the sweet spot.

there you go

Well, using the logger screen from your log file as the source works as I'd expect it to.  Perhaps there's something weird/unexpected with the real-time output from ME7Logger.... or maybe I just screwed something up with real-time logging.  I'll make sure real-time logging works for me tonight.

In the mean time, can you output the me7logger stdout and stderr to text files so I can look at those?  You'll need to run the ME7logger from the command line, but do it with the following additional params

Like this:
ME7Logger.exe "all my options go here" > C:\temp\loggerout.log 2> C:\temp\loggererr.log

I don't need a big crazy log session or anything... Just start up the logger, rev the engine a few times, and stop the logger.

Those files would greatly help... but like I said, maybe I just hosed up something with real-time logging as a whole, which I will check out tonight.

Just checked out real-time logging here at lunch, and yeah, there definitely was an issue of some sort.  I must have already corrected it and not pushed out a release though, cause when I tried to debug it I didn't get the same error.  I'll post a new version for download now.  If this still does not work for you, I'll need those stdout and stderr output files to see what your issue is.

Version 1.12 is available.

Corrected a few issues that would have made it difficult for first time users to run the logger.
Added more graceful error handling on the logger screen.
Corrected issue with running logger or writing to a log file that had a space in the path.
Corrected issue with error upon loading a new ecu file.

Should be getting more stable.
currently trying to track down an issue with weird graphing on XP.

Version 1.13 is available

added ease-of-use features such as moving the filter options above selection grid and out of the menu, added combobox with suggestions for graph variables. 

Also merged the VisualME7Logger.Output.dll into the exe so there's only one required file.

Version 1.13 has been tested and works on XP.

Very nice. Thanx!!

I finally got this to create a log file but is there a way to get this into excel format instead of a text document?

Also I'm not sure if I set this up correctly but live data isn't displayed. I input two variables(request - plsol and actual boost - pvdkds_w) in under the graph tab with correct resolution and still no display.

1) Excel can read .csvs
2) DO NOT POST EXCEL FILES HERE. They're useless because its almost impossible to get them back to far more useful .csv format they started with.
3) ECUxPlot reads .csvs, not excel files.

Alright understood. I had no idea it can read .csvs, just tried it and I wish I knew that a while ago. thanks

You have to make sure to select the variables that you want to log from the measurements tab first.  Those variables may then be used in the graph tab.

Alright I'll give it a shot thanks!

It does not work for me , I'm trying to load ecu file and it does not load it :(

If you would like to send me the ecu file you are attempting to load I can try it out.  Also, please make sure you have the latest and greatest version.

I don't think that's a problem with specific ecu file , because i tried different files and it does not load any file :(
I think that it could be problem with my OS or sth ... i have win7 64bit. Even reinstalled net framework but it didn't help.

i was tried same, even with win xp, program cant load ecu file, any help with that?
ME7 loger gui works well in my PC.

try this version if you are having trouble loading an ECU file.  I've put in a message if loading the ecu file fails, or if it doesn't read any measurements out of it.  Also there is now a label that will tell you how many measurements are loaded, and how many are being filtered out.

it shows now meny errors.. Firts i create a ecu file,(it works, the ecu file is created)  and after that i like to load this..but it shows errors.

See if you get any further with this.

bah. missed the file.

Steve, I didn't forget about the maps you needed, email me again with the software base you're going to run and I'll make you an OLS :)

Also, very cool of you to be staying on top of this. A+ work.

DD

Success ! Thanks SB_GLI  :) this version loads ecu file with no problems. Today i will test it in car if i can log with it .
 

Excellent.  Please report back how it goes!

Hei

Now with ecu file loading and logging is everything OK(log file is saved correctly), but in visual side, i cant see any logged values on real time...

Okay.. looks like there is a problem reading in the real time output from ME7Logger.  I wonder if you might have an older version of ME7Logger that didn't have the option to output the real time data to the screen?

I need two things:

1) from the Options screen, choose the "Write ME7Logger output to file".  This will write a text file (either in the logs dir or in the root dir, can't remember where) that will write all the realtime data read from ME7Logger to that text file.  I'd like to see what's actually being read.  Upload that file here.
2) Zip up your ME7Logger directory and upload it here.  I would like to run exactly the version you are running on your machine.

With these two things I should be able to get to the bottom of the problem easily.

If you think you have an older version of ME7Logger, download the latest one and give it a try with that.

hi

I have me7 logger v1.20 ( i think thats the laterst version) http://nefariousmotorsports.com/forum/index.php?topic=837.0

I was cleaning my logging programs folder and zipped all what you need... i made one smaal log file too with my spare ecu on table. NB! my ecu name is modified to SNAKEY (it is 06A906032HJ) ( just for fun). I tried to log another ecu too, the results was same, no realtime values...

Thanks!  I will look into it tonight!

Of course, I was unable to reproduce this issue using the output file you sent me.  At the moment I am stumped as to what might be the issue.  Works on my pc and that's good enough, right?  ;)

I've created a debugging version that hopefully will help me narrow down where the issue is.  My thought is that it's reading the output fine, but either the output lines aren't being sent up to the UI or the screen is not being properly refreshed based on the refresh rate chosen.  Please try out this version. It will create a DEBUG.TXT file that will hopefully tell me where your problem is.  Hang in there, we'll get it working!

Okei. i was logging same things as before, here is debug file..

If anyone who is having troubles with real time data not being displayed wants to try this version and let me know if it works, that'd be great.  Running this will create a debug.txt file in the ME7Logger dir as well which I would like you to send back to me so I can see what's going on.

Don't use this version if it already works for you though.. there's a bit of overhead involved in writing the debug file that you wouldn't want when real time logging.

Thanks.

grreat work! I will start using it in my S4 B5 and give you my feedback

Version 1.18 uploaded. 

Major addition was implementation of profiles to allow for saving logging settings for multiple vehicles or logging sessions.

Version 1.19 uploaded.

--Add/remove variables from the graph while logging. 
--Bold label font for variables plotted on the graph. 
--Added increase/decrease of sample rate for log playback (fast forward)

Perfect! Very good tool you have created here SB_GLI :)

Thanks!  I got some good use out of your tuning wizzard this weekend as well!!!

Is anyone using this????  I haven't received much feedback on it as of late.  If you are using it let me know how it works for you!  If there's anything that it's lacking or any other suggestions, please let me know!!!

I haven't had a chance yet, but my car is nearly complete and I will certainly use it!

I think it's very cool and I have only used it for log playback a couple/few times. When I get time I will play with it more. I like how it shows the variables also. That clears up confusion for a person that doesn't have them memorized(me). excellent work!

Version 1.20 uploaded.
--Added expressions for calculated variables.  Example:  Boost in psi, "([pvdks_w] - 1000) * .0145"
--Added data grid control for chart selection and copy to csv
--Added session output display for easier session troubleshooting

 ;D thank you very much for the update , should have replied when you posted earlier , I use it quit a lot , usually at 12pm on my way home on an empty motorway  ;D .

keep up the good work .

jim

I should mention, the expressions are based off of NCalc.  See their website for details on syntax.

https://ncalc.codeplex.com/

For example, I'm using it to see fuel injector duty cycle on the graph.  Here's my expression for that:


If you downloaded v1.20 already, you should do it again as I corrected an annoying bug with edits to expressions not working until you restarted the program.  oops ;)

Version 1.21 uploaded.

Added an EEProm tools screen which allows for reading/writing/cloning of SKC, VIN, and Immobilizer data.
Corrects EEProm checksums
Corrects EEProm Death Code (due to flash checksum error)

you the man SB!

Nice  :) feel free to steal the vin decoding out of my EEPROM tool  :)

very good project .
I will test it as soon as a get my hand on a me7

I gave the new version of VisualME7Logger a try.
Tested to read my EEPROM (OBD) and all seems to work but when I saved the changed file it reduced the .bin file size.

Is it as it should be or am I doing something wrong?

(Note: first time I use the program and messing around with it to learn)

I tried to reproduce this but couldn't.   If you send me your original and the changed file I might be able to see what happened.

great tool!
tested it today with boot mode to make an immo-off ecu
worked good, thanks

but its strange usage algorithm for me
oh.. english is not my native. but i will try to explain..
for example - goal is to copy immo id, skc and vin from ecu1 to ecu2.
so i need to open ecu1.bin (or read it from cable) copy all to notepad (btw something like copy-to-another eeprom or temporary fields will be very useful option i think), open ecu2.bin, paste ecu1 data from notepad and now i want save it to ecu1_2.bin but there is an error when im trying to save a new file (which doesnt exist) and i cant save it to ecu2.bin because i need it as a backup. so im copying ecu2.bin, rename it and save to em. its not hard after hex-editing, parsing etc and as i said before - its a great tool! you are awesome :) but it can be little friendly :)

The goal is to have no hex editing involved.  :) I think if I instead exposed the hex data for the immobilizer data it would make it easier to use.  Then you could just clear out the fields you don't want to clone, and it won't clone that over.

this allows you to run the checksum right in the program?
i corrected the path because at first i was getting an error
is this checksum a valid way of doing it. or is it still in testing?

No, it just runs ME7Check.exe against your bin.  It does not correct checksums, only validates your file.

ya i figured it wouldnt fix them but its a nice little interface to check them

Well done

Version 1.22 Uploaded

--Added Option to turn off real time display while logging as this can cause the logging to fail in some case.
--Added communication options for Connect, Communication and LogSpeed
--Other minor bug fixes.

Hi,

i still got the graphic view errors another user had in this thread befor. In my case i use the newest 1.22 version. The problem seem to happen only on floating numbers f.e. the nmot rpm is displayed correctly but the nmot_w is not displayed correctly. Every value wich has a XXX.XX format doesnt show correct. All XXX without .XX show correct.

The Log file itself is clean and look good the problem only happen on the real time view.

I assume you live in a part of the world that uses commas as the decimal separator?  I can try and make a fix for this for you to try out if that's the case. 

Does the ME7Logger log file contain "." or "," for decimal places?  I would like to confirm this.

If ME7Logger indeed uses "." regardless of your culture, I think all that I need to do is force English culture when I parse decimals and we should be good to go.  I will try to make this change tonight for you to try.

Please try the new version 1.22.1 that I uploaded. This should correct the decimal parsing issues.

yes i has the same problem with "," system separator

using "." now in my laptop without any issues

Are you saying you changed the system culture settings on your pc to use dots over commas? or that this latest update made it all work for you?   8)

i was changed system decimal separator to dot due to problems with reading logs and some other apps
not even tried new ver

Request: can you make the default log file extension be .csv and not .log?

Also, can you make the graph data variable list UI include the alias? Or maybe add some sort of add/remove panes (i.e. make a pane on the right which lists all the variables enabled) with some sort of add/remove arrows rather than add/delete buttons? Not sure that request makes sense :)

great application btw, been experimenting with it..

That request makes sense I think.  :)  If you go right to the graph and start clicking the variable labels on the left, it will create the graph variables right there for you, instead of having to use the form to enter in all the records.  I find this easier. 

Then, to keep from having to do all that again for logging on other cars, just clone profiles and it'll bring all the graph variables over too.

Being able to use expressions is great...but is there a way to calculate stuff between two different rows of log (if only two adjacent ones?). What I am interested in is calculating accel, WTQ and WHP using expressions but for that I need to be able to access data from previous row to calculate speed delta. That's for beginners. In the perfect world I would also need a way to smooth the output via some averaging function (that would retain running value) over X data points...

Any chance on that?

Thanks!

Oh! LOL.

That makes sense :)

So, another request: auto calculate range from the .ecu file scale (e.g. 0..255 or 0..65535 times factor, or -128..127 etc).

Very doable, although I need to put a little thought into how to make calculations over a number data points work in a way that is generic and usable for other things. Any suggestions?

The problem is... there's not necessarily an ecu file associated with the log you are viewing.  visual logger doesn't even look at an ecu file when you are just playing back a log file.  I can add that in, but it will be weird when it doesn't work in playback mode.

Hmm.. maybe on playback you can scan the whole log file before playback and find min/max?

I have one request: please make the ecu file editable within visualme7logger :) so it would be easy to add new variables and edit existing. That is main thing that i'm missing now :) other than that it is very useful tool.

Also, would it be possible by default to add graphs to variables that i am currently logging? min max would be dynamic current min max from start of logging to current timestamp, color would be randomized. While logging we can change everything anyway (line style, color, etc.) :)

I started ME7Logger and then the VisualME7Logger, which I had pre-configured, upon selecting "Start Log" I received the following message:

(http://www.myaudis4.com/tuning_images/vis_me7l_err_msg.png)

ME7Logger and VisualME7Loggere reside in the same directory.

Don't do this. Let the program start the logger


AFAIK VisualME7Logger looks for bin\ME7Logger.exe, which means it has to be in the same dir as "bin"

Just put VisualME7Logger in the ME7Logger directory and run it from there.  It executes ME7Logger from the bin directory when you start logging.

Also, I like all the enhancement requests coming in.  When I get some free time I will try to incorporate the changes that have been suggested.  But in the meantime, it's all open source, anyone can contribute. ;)

Thanks, I'll try those suggestions.

Finally had a chance to test this out. Hats off to you, SB! Question... Am I able to view past logs in "playback" mode once the session has been closed? Looked through the thread a few times, and although it seemed like I could, still can't find a way.

SB_GLI, have you fixed this? It kinda doesn't work with expressions... For example [ti_b1] * 720 gives me ~150000 :) Currently I'm using / 100000 hack :)

Yeah, I thought so.  There's probably something just in the expressions.  I used some open source code for that.

Request: can you make the default output .csv be the filename the ME7L normally outputs?

template-yyyy-mm-dd etc...

constantly overwriting the same .log (ugh, not csv) isn't so hot if you want to keep your logs around (and organized)

Version 1.23 is available:

RELEASE NOTES

Log scrolling
Default Log File
Tail Log File option (troubleshooting)
bug fixes

THANK YOU!

Still can't figure out how to do this. A little help?

in the config screen, set communication to "Log File"

Turned out to be a bit of a bitch actually.  When you use -R (real time) you have to specify a file path it -o or else it doesn't work.  I had to write it into VME7L logger to create the file name like ME7L would.  ;)  All for you!!!

me as well  :-[

Look 3 posts up.

 :D you type faster than me lol , by the time I posted that , you replied twice  ;D

hi
i think decimal places setting in expressions tab would be helpful because 86.13456666666666666666666667 % injector duty cycle looks weird  :)

Use the Round function.

oh i see
thanks

is there any other expressions that can be useful for logging?
btw im using now

Does that even work?  If I remember correctly, you need brackets around your variable names otherwise it won't work.

The other expressions that I use are Boost Actual and Boost Desired in PSI.  I don't have those actual expressions handy right now.

yep it work

boost actual in psi:  Round(([pvdks_w] - 1000) * .0145, 2)
boost desired in psi: Round(([plsol] - 1000) * .0145, 2)

replace the 1000 with absolute pressure variable if you're fancy like that.

Thanks a lot! Been trying to figure this out or a while.

Not sure if this is possible, but might be a neat project/addition to the visual logger.

I see a buddy use this on the diesels all the time, pretty handy tool.
Ford calls it a cylinder contribution test. Not sure what kind of math it runs to figure this out, guessing it is doing something like reading the speed of the 10 pulses after firing and compares them to each other to give you a relative comparison.

Skip to 2:30
https://www.youtube.com/watch?v=xUHiobK0-kE


Can also use this for what they call a relative compression test.
We would basically pull a fuse to keep the motor from firing and crank the starter. Wont give you a number, but can see quickly if there are any flyers.

Any thoughts?

Interesting.

Crank rpms are something like 300-400, which means 5 revolutions per second, times six cylinders is 30 up/down pot motions. Compression happens every other cycle so you have 15 compression events within a second when cranking. To measure relative compression with some clever calculations would require at a minimum 15 samples per second (easy to accomplish) *IF* they are not exactly synchronized so that the pulse count changes for the 10-15s you would be required to crank to get results. Probably 30 samples would make more sense. Seeing that I can log tons of variables at the same time at 20 samples per second, I don't see a problem doing this wit a few variables at 30 samples per second and even higher.

What is the highest anybody logged at to date?

You'd have to log real time tone ring count for last x-amount of time (I think there is a variable that has 20ms resolution for that, so 50 samples per second resolution), current crank angle (probably not a problem), bank deviation from crank angle (also not a problem, not sure if couple degrees of deviation people usually have on the heads would mean anything, but putting it in here for consideration) and map cylinders to crank angles and do some calculations.

Interesting project and absolutely doable.

Ya shit would def be happening fast :)
I wonder if ford has the routine running on the ecu itself and spitting out the result so it is not limited by the cable.
It does shut off if you get the rpm up too high, think he said it was more than a few thou rpm though.

It really was a handy way to see misfires or if a cylinder needs some attention.

Great tool, just can't get it working on my car.
Loaded ecu file. trying to connect, but nothing.
error! Exit code:4. (cause=0x4).
Using COM7
Tried fast-0x 10, slow-0x 11. HM0, HM2 (don't know what these mean). Log speed 56000. Nothing.
Car is ME7 Golf 4 1.8T.

I have blue chinese KKL adapter and original VCDS.

Could problem be inside car? K-line? Need direct wire?

use me7info.exe which coming with me7logger tool to determine connection settings
in my case slow-0xFE working good

Version 1.25 Uploaded
Added support for addition log file types - VCDS, Maestro

Show axis labels for select variables.

Moved logging screen initialization off of logger session thread to minimize logging timeouts while starting a new log.

Many other small additions and bug fixes.

Thanks for the update, SB  8)

x2!

Thanks SB, this last update fixed all my 2.7t logging issues ;)

nice

Somebody help me please? I tried all the baudrates, slow-fast etc and nothing works. Here is a log of the error I got. Car is me7.5 1.8t 032SJ

Try logging with the instrument cluster fuse removed.  I've had multiple ecus in my jetta. While most logged fine, there were a couple I have run across that just would not log, or would timeout while logging, unless the cluster fuse was pulled.

Also, 19200 baud may help.

With the fuse removed the car doesn't start because of immo. What I'm doing wrong?

Start the car, then pull the fuse.

Having an issue when selecting com port within VisualME7Logger (as opposed to using FTDI which works, but only when using Visual by itself) logger says "cannot open com port", but using ME7Logger GUI works fine (using the same com port I specify within Visual). I can't use FTDI in Visual because of some new conflict with a program called emutility that I use to communicate with a Roadrunner board for real-time emulation at the same time. Visual will only start logging using FTDI with the usb cable for the emulator unplugged. If I plug the emulator in while a logging session is open it will work, BUT if I stop/restart a session it won't connect again saying "cannot echo cable". If I use the GUI it works fine with the emulator plugged into the usb port. I'm using ver 1.25. Hope I got my point across been effing with this for the last 5 hours..haha Having Visual working with it's live data stream/graphing makes the whole process easier, and I'd love to get it working again.

I'll help you get this rolling.  Send me the session output data (there's an option to view this on the logging screen)... See if anything in there does not coincide with an option you selected.  Maybe there's a bug that you found.

Just wanted to post what end up fixing this issue...Steve informed me that you need to type the word "COM" as well as the com number (I was only typing the number) in the COM field. Big thanks to him for getting back with a solution! I had been successfully using FTDI up to this point, but when trying to use another piece of software could not use both at the same time.

Wow, this is a sweet piece of software!! Thank you so much for putting it all together!!

Just got a Dell venue 8 setup to run everything with a vcds cable. It was fun (not >:(), but it works (somehow ;D).
I have always found it easier to use a kkl cable, but wanted the 1 for all action on this.

Also set up Google drive and have the logger set to log to that folder. Pull up in the driveway, and logs are on a computer with a usable screen by the time I get to it.

Thing I am trying to get sorted now is keeping the screen from shutting off while running vis logger. Anybody know how to set this up for just certain apps, or am I stuck doing it the old fashioned way?

Something else that would be cool would be to have conditions for alarms or something.
Ex: if pvdk_s > 2500, then action. The action could be something like a sound and/or a .jpeg splash.

Id have this on there in a heartbeat  ;D
(http://i.kinja-img.com/gawker-media/image/upload/s--ifbo8YOZ--/1275421562946925893.jpg)

Guys, I've got a problem with Visual logger.

When I try to open session I get the following message: FT_GetLibraryFunction in dll (as shown in attachment)

I've got VCDS12.12 Clone, KKL Vag-Com for 409.1, Galletto 1260 clone and kwp2000 + cable

When this error appeared I used the galletto cable because there is a 323rl chip in it.

What could it be? Drivers, cable?

The cloned VCDS and Galletto will not work.

I'd probably should have done what you guy say everytime...

Delete unused drivers.

Got it working like a charm now, blue kkl cable ch340 chip inside.

excellent software solution, but I'm getting here is after saving the parameters of ... not very convenient to start all over again ???

(http://)

dang commas for decimal points.

Send me your VisualME7Logger.config.xml file.

that is, it's my fault to set limits on the variable display graphics? ;D

here Fail

sorry for my english, I'm from Russia

Understood ... everything was
If the field within the function to change the value to the point
HH.00 change the keyboard without touching on YY.00 .00
in faile VisualME7Logger.cfg.xml
prescribed YY.00, resulting in an error loading the configuration
I will follow up on this ... thanks ...
if you consider that in the next version of the program :D

I understood
I changed the value of the maximum schedule
using the keyboard

if you remove xx.00

enter yy

all is well. cfg in the value yy

if

remove only xx

and enter instead yy

then, in the cfg "yy.00"

What causes an error

I use GOOGLE translator

when I am translating back

English to Russian your message

I getting delusions  :(

sometimes funny

It is because your native language expects decimal numbers to use a comma as the decimal separator, instead of a dot.  .Net is trying to parse a decimal and expects a comma, but the config file saves the decimals with a dot.  I've "fixed" this in other parts of the application, must have missed this.

I will send you an update tonight if I can get some time.

This should correct the issue you were having.  There might be some other untested code in here, so sorry if there are other bugs.  :)

Thank you for your work

So I tried using visual logger today and every time I tried starting the log, I would get a message stating could not connect to ecu, could not connect to ftdi, or test echo sent and no response. I then tried the standard ME7logger and it worked with no issue like usual. So I continued trying to get visual me7logger to work by verifying my com ports and such with no luck. I always use the "USE FTDI" communication option with the me7logger gui and I tried that with the visual logger as well.

Now the big dilemma, now I can not connect to the normal me7logger or nefmotoflasher!!! I am getting the same issue errors as with the visual logger. I ahve been using me7logger every day with no issues for the past year+ and this is so frustrating. Does anyone have some helpful insight as to what's going on?

I tried uninstalling my kkl blue cable driver and reinstalling it with no success in getting my software to connect to my ecu.

Edit: I got my me7logger back up and running by switching the cable to another physical usb port. Weird but it worked. Still no luck with getting visual logger working though

How do you Load a CSV Log in VisualME7Logger?

cool program  ;D

go into options , change communication to log file .   

it keeps crashing and I think it's an issue with Me7logger itself because this was happening when I was using another GUI. Whats this about? Logger works for random periods of time, then it drops out. Using a blue kkl on com3 then I switched to com4 with no change in effect.

I'm using 125000 log speed and it seems to prevent it from happening most, but it still keeps crashing. any other baud rate and it crashes immediately.

This is actually the same issue that kept me from using me7logger in the past.

MKIV's hate ME7logger.  The cluster interferes with k-line communication more often than not.  You can try a lower baudrate (38400) and when that doesn't work, pulling the cluster fuse will work flawlessly.

It is my understanding that in order to avoid troubles with the immo, you pull the fuse when the car is running. Do you put it back in when the log is over or after the car is off?

Also, it turned my airbag light on, unplugging the cluster fuse. I'm gonna reset DTC's tomorrow to see if It goes away.
Mk4 GTI 1.8t AWP HS box

I have a newly arisen issue with this program where it will will not let me COM link ever and if i use FTDI and specify the location, it will fail.

The only way i get it to work is i have to start up VCDS and enter the engine module, then close it and i can finally log with VisME7.

If i stop the log for a few minutes and attempt to open a new session it will fail again.

It almost seems like the program is not allowed to open communication with the dongle so i have to open it with VCDS which leaves the "window" open for a certain amount of time.

Anyone have this issue?

*Ross-Tech HEX-CAN-USB*
Win10

intelligent mode off? VCP driver?

Yes, and yes.

yes

Have a car with these exact same faults. Worked great for a month, didn't use it for a while, then this. Went through and deleted all the invisible drivers as well in hopes of success. Tried FTDI as well as Com and the same on both. Logs for 3-5 sec. then crashes with the same window. Using a blue generic kkl cable.

yep.  me7logger just doesn't work well on mkivs. I've found that it gets progressively worse over time as well, which I don't quite understand.  I've also had more luck, in the same car, with different physical ecus.  Also some softwares on the same physical ecu work differently some better, some worse.

Pull the cluster fuse (or run dedicated kline) and it works flawlessly.  It's a major PITA.  If only we had some ME7Logger source code...

Thanks for the replay, SB. Everything you've mentioned is what we've noticed.

SB is right about the MKIVs... Pulling the fuse or dedicated K-line works fine. I went dedicated K-line because I had issues with the cluster messing up flashing with my 032HS. I still use the stock OBD port, just with a switch to bypass the cluster and other junk on the K-line.

Thanks for this awesome program SB!

Anyone know if immo defeating the ECU makes it work more reliably?

Good question. I have my immo enabled so I can't say...

I don't think so.

Any specific tricks/ issues logging B6 A4's? Can't connect to the ecu (8E0909018BC). It's definitely not a cable issue, as I use this often, but mostly for MK4's. Fault simply says "can't connect to ecu".

*Edit  Just tried an '02 8E0909018F and it worked great with no change in PC settings. The BC car also had an aftermarket radio, but I could connect with VCDS, which usually isn't the case if something's on the k-line.

Been fighting with this a little bit this evening, 2000 B5 A4, ME7.5 ECU from a TT225.

Set everything up and connected with the engine not running, the logger started, produced a display with some values for a split second then crsahed with a full screen wall of text, something about incorrect input type near the top, i didnt get a screenshot as i'm using a shitty windows tablet. The one posted on the previous page looked similar.

I figured it was because the engine wasnt running, and it had received some unknown signals.

Start the engine, and it wont connect at all. Tries for a bit, then gives up with error 4. I thaught it might have locked the com port up when it crashed, but VCDS works fine.

Rebooted the PC thinking the software had gone wonky in the background, still couldnt connect.

Looking in the log folder theres a CSV file with four rows that it managed to created on the first run.

I've attached that CSV, despite it being a bit pointless.

Any ideas?

K line interference... ME7Logger has an issue with this.  You can try logging with the cluster fuse pulled.  I know this is an issue for just about every MKIV, but I've had this issue in other cars too.

Thanks.

Some further testing showed that with the ignition OFF the software worked perfectly, as soon as the ignition was powered on the data stopped.

Tried to find a cluster fuse, but the only one listed on the panel didnt actually power the cluster down, it just put "FUSE" on the mileage screen. I also didnt really fancy driving around with no instruments. Decided to rewire the K_Line behind the cluster instead.

As standard on the B5 (and all VAG's i presume) the K line runs to the cluster, then from the cluster to the ECU. I believe its done like that because the ECU and Cluster use the same wire to do the IMMO handshake. When you connect to the ECU you can hear a relay or something inside the cluster clicking as it sets up the communications between the two sides.

So i cut the two wires, and ran them to a DPDT switch. In one position its wired as per factory. In the other position it disconnects the cluster completely, and connects the K_Line directly to the ECU.

Preliminary testing shows its a success. With the switch in the bypass position the logger connects perfectly and continues running with the car started. Win! With it in the other position it all works as per factory (including Logger not connecting). I need to get a smaller more discreet switch, and i'll mount it somewhere accessible once i've done some more testing.

I put my switch behind the fuse box door on my Mk4. Drill a hole just above the fuse panel opening, plenty of room in there. That said, I leave it in bypass 99% of the time. If I need to VCDS a component usually on the k-line I just pop it open and switch over.

A k-line bypass is pretty much a mandatory mod on some ME7.5 cars. Mine pissed me off no end until I did it. Logging without gauges sucks so pulling the cluster fuse isn't a good option...

Just an FYI for some folks. In order for ME to get VisME7L to start logging i have to open up and enter into the engine module in VCDS FIRST! After that i close out VCDS and start logging with VisME7L just fine. Works everytime. ;)

does this help with timeouts?  I might have to try.   I have to pull my cluster fuse to log my mkiv currently, and it's a major pita.

This didn't help timeouts on mine.  When I get a moment I will have to install a bypass switch.

That sounds related to vcds "intelligent" mode. Make sure it is unchecked.

I just got visualme7logger working a few hours ago (I've had the .exe for months now but I forgot to place it into the me7logger directory lol) and I took a little drive/recorded a log and I've gotta say! nice job! I really appreciate your hard work!

Howdy, I forgot to mention in my previous post, I'm a graphic designer and I would love to assist if anyone is interested in working with me on adding a "dashboard"-like function in Visualme7logger. I have no experience writing programs or applications and my coding experience doesn't go any further than web design using adobe muse (which doesn't require much coding lol)...

I could design a few skins for users to choose from and break each element of the gauges down into layers so that a collaborator could take the layers and implement them into the program so that they function and translate the data visualme7logger displays on the graph, and displays the data on the gauge. To make things easier, rather than offering gauges for hundreds of parameters, We would just make a dashboard that contained, for example, something like 7 or 8 of the main parameters that the average logger would like to see on a gauge (boost, oil temp, AFR... maybe battery voltage idk...). Initially I have 3 skins in mind. black leather (to match black leather/vinyl audi and vw interiors), Some electronic digital gauge theme (likely a black background with neon colored gauges... Ever see the digi dash on an 89 subi? kind of cheesy but if I brought it up to speed a bit I think it would be great.) and then a traditional themed skin, like gauges in a classic mustang... Everyone could pitch ideas at me if we get the idea in motion. Either with words or with a picture.

I thought if anyone was open to the idea and has the skill and experience necessary to take my designs and bring them to life in the program I could get to work on my end of the work. I'd break the gauges down into pieces (needle, numbers, full gauge, empty gauge, partial gauge, background...). Just let me know if anyone would like to work on this with me (@SB_GLI ?) and tell me what image format would be necessary for the project and I'll work on it as soon as I've got time.

-Royce

Things I would like to see in VisualME7L.

Dashboard
Keyboard shortcut to toggle between logging data, and viewing live data only without logging.
Being able to change the default location for saving logs

Doesn't hurt to ask, right?   :)

We're lacking coders willing to spend effort, not designers, unfortunately.

In the 10+ years I've had code up on github, I can count the number of patches and commits from other people on one hand.

That is a pretty nice suggestion imo! and I also second your first suggestion too  :P  ::)

I'm sorry to hear about that @nyet. I notice a lot of the same whenever I visit github for a download... Often times a high volume of DLs but little to no comments whatsoever... Have you considered reaching out through other hosting/collaboration websites intended for developers to host source code/program downloads and connect with a more active group of individuals who are like minded and also wish to collaborate more so than users on github?

I sent you a PM regarding a possible way to raise funds to provide further development on new apps/additions to apps like this... Money that you can use to afford more "sick days" from work, but that will actually be used for nefmoto related application development. It would be just like a paid work day  ;D

hi there!

Yes, like needle gauges.

I thought you were the coder?  ;)

I know, I know. I've given up on that.  ;D  I'll just leave the default windows screensaver/ background too. Haha

I'm trying to add an expression so the live fuel trim (block 001 in VCDS) displays as a percentage rather than in decimal. I've read that this can be done by subtracting 1 from frm_w and then multiplying by 100. I tried adding this expression using the supplied example in the program, but keep getting "invalid expression name".

Here's how I'm typing the expression..

([frm_w] - 1) * 100

I'm using "frm_w" in the name field, and % in the unit field.

Any insight? Wrong variable? Wrong expression layout?

Thanks!

EDIT: Had to add a name without the underscore in the name field...

So you figured it out?

Yes.

haha awesome sweet, i just happened to need this same thing tonight! Thanks!

no luck on that.

I have tried using visualME7Logger several times. Everytime it I use it it seems to corrupt my ME7Logger version1.20. Has anyone else had this issue? ME7logger then has to be placed in a new folder, unzipped, and then I have to recreate my ecu and config files to get ME7Logger working again. Very frustrating. I'm sure it's user error, but I have no idea what I am doing wrong.

When I set up VisualME7Logger,
I use the same FTDI setting for communication
and the rest are default
I am just graphing nmot for testing
I use the same config file that I use for ME7Logger
I start the session and get an error, cannot connect to ecu. And the I get the same error when I try to use ME7Logger...

Anyone have any ideas about what I am doing wrong?

Possibly immobilizer interfering? If so open nefmoto and visualme7logger. Bring the nefmoto window to the top and connect. once connected now disconnect. close nefmoto and then connect in visualme7logger. always works for me. once connected you can close session and reopen session as many times as you want until you turn off the ignition. once the ignition has been turned off you'll need to repeat this procedure in order to connect and begin logging again. Also, try not using FTDI, instead use your cable as a virtual com port. You'll need to download the rosstech VCP driver.

Brand new to logging and ECU tuning in general.  This worked like an absolute charm.  Blue eBay cable with FTDI VCD drivers on win8.1x64.  Very awesome!

hi Guys

to my problem:
try ME7.1.1 test ecu with ols300 on the table.
Visual logger connect and have no problems with KKL cable. ->  all ok, logging many variables, no problem with config (baudrate....)

I put the cabel  in RS4 car over OBD ori ECU  (551K), no OLS300
Visual logger says can not connect to ECU!!
What could be the reason?
Remove fuse from dash after motor run and then connect I have not tried yet
right ECU file loadet, change Baudrate,speed  and so on -> same error
test with ori ME7logger I have not tried yet...visuallogger better for tuning with ols300

thanks for feedback


i test this on Monday:
1. Remove fuse from dash after motor run and then connect
or 2nd variant ->  engine run, connect with nefmoto flasher or VCDS -> disconnect ...an then connect Visual logger

Hello

i have test the 2 options..
-> ignition on...nefmoto flasher connect and disconect..open visuallogger...all great

-> next step start the engine...engine in idle...nefmoto flasher connect fail -> see the picture, what could be the reason?
-> test with vcds kabel "intelligent" mode off, same issue

thanks for help 

I have now the following solution.

Build me one adapter for me7 ecu.
Plug of a broken ecu, plug from a old harenss
all wire 1:1 connection -> except pin 43 (k-line)
old usb cable (shielded) connect on ecu plug pin 1(-) , pin 62 (+) and pin43 (kline) this goes to an OBD plug with switch

in practice:
disconnect plug from ecu -> install adapter -> connect adapter with harness from the car
switch passage kline -> start the car -> switch interrupted kline to the dash -> log

can log all Me7 without cutting something ;D

simpley circuit diagram

Seems excessive to avoid cutting a single wire, and running a single wire, but different strokes!

yes exaggerated for a single car
I want to measure in different cars, can not each cut kline at customer cars

I see now. Thanks for the clarification.  :-*

I've been meaning to make a breakout adapter just like that.

Just disable IMMO and go to your ecu file created by Logger.

Change Connect      = SLOW-0x11   to  0x00 and you dont have to cut or rewire anything ever again.
You will be able to LOG on the fly - car running.

Even with the k-line being interrupted by the other modules on the vehicle? 

Not seeing how slowing the connection speed will eliminate the interruptions over the stock k-line.

Sent from my Pixel XL using Tapatalk

Immo is interaption. Dissable it and change connect speed.

What about non-immo vehicles, like mbox S4? Would slowing the speed down help?

I'm in the same boat, engine on logger won't load anymore. It did a few times before, then all of the sudden it stopped working. Nothing that I know of has changed. Joy...

Sent from my Pixel XL using Tapatalk

Pull the eeprom, FF the immo.
Change connection speed to 00
Play with boudrate.
Report your findings.

I can't find where the compiled package download is. Did the link disappear with codeplex going away?

https://github.com/sbloom82/VisualME7Logger this ??

Yeah, looks like it's gone now.  Here's the latest version.  It may have a few new previously unreleased "features".

Mbox doesn't have immo. That's off the table.
Change connection speed, alright how and where? Checked ME7logger didn't see it in there, also checked advanced settings under the com port, same nothing regarding speed. Unless it's labeled differently.

Baud rate, I'll try that, after I figure out the speed connection you mentioned.

Thank you!

Sent from my Pixel XL using Tapatalk

very good software dear friend's thank you all for your job

Hi. I'm trying to get this to work, but I'm getting an error when loading an ECU bin, for creating an ECU file.
The error is in the image bellow. From pt-BR to en-US is something like: "The system could not find the specified file in...".

My machine runs Windows 10 x64. Tried too on a Virtual Machine with Windows 7 x32, same error.
I tried to put VisualME7Logger.exe on the root of C:, and the ecu bin too, same error. I dont know why it cant find the file.

If someone can figure out this, I appreciate. Thansk.

Are you really installing from the sources?

Did you try following the instructions in the OP?

http://nefariousmotorsports.com/forum/index.php?topic=4830.msg47392#msg47392

Pay attention to the item in red.

Sorry for not paying attention nyet. Now the Logger creates with success the ECU file.
Thanks for the help!!

This thing is awsome. Been playing with it for the last days.
1000 times better for logging my car now.
The only downside is that I need to remove the cluster fuse. But my ECU eeprom is immo-off, so dont matter.
Now I have an good environment setted up for calibrating my car (1984cc stroker, E100, 400whp target).

I am using vag-commander cable. On nefmoto working without any problems. But on loger i get this error

With dump KKL calbe,only FT232RQ... The logger is working fine  :D

Sorry for the question to some but is windows 8 the “minimum” OS or the required OS?

Did this site die or am I just missing the obvious?

Minimum. Nobody uses win8 :P

There we go. all I needed to know thanks

just got an idea while reviewing the log within Visual logger. Would be nice to be able to deselect variables without having to click each variable to open and uncheck the box.  If the box could be placed next to the variable title, going through the log selecting specific things you want to view would be a bit quicker.  SB_GLI do you think this would be possible?

How would I figure out what calculation I need to create an expression to view MAF voltage and G/S on the log similar to EcuXplot? Meaning my Maf g/s shoot way above the voltage, so there's considerable separation in between but more importantly they're not the same arc. I'm not sure what the math or expression would be to attempt this. 

I've attached the same logs, one in ECUxplot and the other in visual logger.

Thanks!

When i get the logger running and it goes to open a session i get a closed connection and it says Error 4. is that the ECU rejecting the connection request?

if that's the error I'm thinking of, I have to open the engine module in VCDS FIRST, then I can start my VME7L log. Weird and annoying, I guess it opens the can gateway allowing comms or something.

i think you gonna call me noob of the noobs but how can i log my car to obtain offset and factor numbers?

Why did you quote the OP?

Anyway, thats what ME7Info.exe is for. It is documented in the ME7Logger utility.

Sorry for that, wich cable do i need to do logs and calc offsets?

Did you read anything in my sig?

Ok got bored, did a video thing... Maybe it'll be helpful for some folks.

Since i'm bored with all this free time....

https://www.youtube.com/watch?v=9-4zX1T9Aa4&feature=youtu.be

there is a tool menu in vme7l

and create ecu file option here

yeah I realized that after

Question for NyNet and SB_GLI or whoever else can answer this:

Why do i have to open VCDS and enter the ENGINE-I module BEFORE i can start a VisME7Logger session? If i dont i get "error 1".

Is there a handshake/request that the tool does not do that VCDS does?

This is the case for mine and 3 or 4 other cars i've setup (B6 and B7s).

Cannot answer this correct but me7logger works like this on most cars with immo:
Turn ignition on, turn logger on, start car.

There is a codechange poster by PRJ but i dont know what it does.
You will have to review this with IDA i think.

http://nefariousmotorsports.com/forum/index.php?topic=14119.msg114367#msg114367

On cars without immo (swaps in mk1,2,3, eg) you dont have to do this and it will connect always from my experience.

How can I add logger (and flasher) for Volvo to this project?

Hey do I just have the dumb or do I always have to select yes on the UAC prompt for unknown developer. My wife sometimes uses this laptop so I dont want to just fully turn off UAC.  ::)

Has anyone run into this issue?

Meh ignore that, ill just debug and report back what the resolution was.

That was embarrassing... incorrectly installed it. At the very least did a pull request to provide a warning if you didn't follow directions.

Hello,

i have test to log my ME7.8 in my 996tt... :-)
But it fail... with my original bin File I can create an ECU File, but he does not find any Identifaktions....
With empty EngineID I get a error... but if I write some EnigineID to it I get the Error: Engine ID Setup '996' but is ''

Is it possible to use this great tool for logging my 996tt?

Have a nice Day
Martin

Hey guys. I have passat b5 1.8t awt, FTDI cable, Windows 10 64bit. With connection everything is ok, but after starting and ~10sec it gives an error "input string was not a correct format". I have tried to start app before starting the engine. I checked my region setting in windows ( I have dot there). But still I receiving this error. Help please

A bit update on my problem. Some people here wrote that try to connect via NefMoto and disconnect. After that start me7logger and it will work until you turn of the ignition. So you can have as many sessions as you want. And IT WORKED :))

A FormatException occurred on my system as well.

Setup:

• - Windows 10 Home 21H2 64-Bit
• - Cable Rosstech HEX-USB+CAN
• - S4 B5
• - ECU 8D0 907 551D (stock, no tuning)
• - Logged variables:

lamfa_w         ;TargetAFRDriverRequest                ; Lambdasoll Fahrerwunsch (word)

wkr_0            ;IgnRetardKnockControlCyl1            ; zylinderindividuelle Zündwinkelspätverstellung KR

wkr_1            ;IgnRetardKnockControlCyl5            ; zylinderindividuelle Zündwinkelspätverstellung KR

wkr_2            ;IgnRetardKnockControlCyl3            ; zylinderindividuelle Zündwinkelspätverstellung KR

wkr_3            ;IgnRetardKnockControlCyl2            ; zylinderindividuelle Zündwinkelspätverstellung KR

wkr_4            ;IgnRetardKnockControlCyl6            ; zylinderindividuelle Zündwinkelspätverstellung KR

wkr_5            ;IgnRetardKnockControlCyl4            ; zylinderindividuelle Zündwinkelspätverstellung KR

wped             ;AccelPedalPosition                       ; Normierter Fahrpedalwinkel

I setup VisualME7Logger according to the instructions provided in the video (https://www.youtube.com/watch?v=9-4zX1T9Aa4).

As described in the thread http://nefariousmotorsports.com/forum/index.php?topic=17419 (http://nefariousmotorsports.com/forum/index.php?topic=17419), I can

• - only connect VisualME7Logger after having connected with NEFMoto VW Audi ME7 Flasher Logger 1.9.4.3.
• - as soon as I start the engine a FormatException occurs and the engine stops immediately.
• - as long as the engine is running I cannot connect to the ECU with NEFMoto VW Audi ME7 Flasher Logger 1.9.4.3.
• - as long as the engine is running I cannot connect to the ECU with VisualME7Logger 2018.07.02.28.

Can anyone tell me what I need to do to solve the issue with the FormatException? Is it the solution to change something in the region settings of windows os?

Try to connect without cluster. I have found that many 4B and 8D clusters make problems

Thanks for your tip. This means driving without speed indicator, tachometer and warning lights....

Did you disconnect the complete instrument cluster? So all three connectors (blue connector, gray connector and green connector)?

...Ah, sorry. I just see that this has already been discussed: http://nefariousmotorsports.com/forum/index.php?topic=12466.msg103350#msg103350

Yes, same findings, with separated K-Line no more problems
on these cars I install second OBD-port with K-Line switch