Getting datalogging working

[motorboy]

Hey Guys,
I got PRJs software working.
The only thing left is how to get datalogging working.
I tried winlog and the dash loaded without a problem but it doesn't load the driver file (WinlogM232FastDiag.dll). When i try to load the file it says "Error: This does not appear to be a valid WinLog driver file". Does anybody have solution?

2nd i tried datalogging with Tunerpro. The .adx file loads and i set up the com port. I saw a difference in the baudrate between Tunerpro and Windoes device Manager (187504 to 9600) i tried to match it in the devicemanager but max was 128000 so i changed the baudrate in the definition file. I tried to connect it to the adapter but that didn't work either.

I would like to get it work at least in Winlog.

Adapter is a simple KKL one With usb connector.

A little problem that occured while i tried some stuff in Tunerpro was that the fuelcut Launch control didn't seem to work. I changed the rpm to about 2.5K RPM but it wouldn't cut. The spark cut LC works without a flaw. I couldn't test many things because my car isn't registered yet.

[vwnut8392]

Hey Guys,
I got PRJs software working.
The only thing left is how to get datalogging working.
I tried winlog and the dash loaded without a problem but it doesn't load the driver file (WinlogM232FastDiag.dll). When i try to load the file it says "Error: This does not appear to be a valid WinLog driver file". Does anybody have solution?

2nd i tried datalogging with Tunerpro. The .adx file loads and i set up the com port. I saw a difference in the baudrate between Tunerpro and Windoes device Manager (187504 to 9600) i tried to match it in the devicemanager but max was 128000 so i changed the baudrate in the definition file. I tried to connect it to the adapter but that didn't work either.

I would like to get it work at least in Winlog.

Adapter is a simple KKL one With usb connector.

A little problem that occured while i tried some stuff in Tunerpro was that the fuelcut Launch control didn't seem to work. I changed the rpm to about 2.5K RPM but it wouldn't cut. The spark cut LC works without a flaw. I couldn't test many things because my car isn't registered yet.

for tuner pro you leave your actual com port settings default in device manager. the com port speed in the ADX is the proper speed, you raise it any higher you will get glitching and any lower it will not connect in the ADX. but in the ADX leave the com port speed default at 9600 and in the commands it should be 187500 baud. make sure you have the right com port selected in tuner pro and ignore the little "test" button they have there, it always seems to fail but my car always connects. also one other thing to try is set your cable to COM1 in device manager. my computer got picky for some strange reason if i had the cable on any other com port.

for the fuel cut i dont know whats going, i dont use it. spark cut is way more fun. PRJ will have to chime in on the fuel cut launch control issue.

ignore.JPG

Also if using the ADX in the github repo its pretty much useless anyway. there isnt anything configured in it other than a couple variables. there is no dash or anything setup. i posted a worked well defined ADX in the ADX development thread on here. that one will do much better for you when trying to get something going.

[motorboy]

Thank you fir your help
!!!

[prj]

Install Visual Studio 2010 redistributable, and it should recognize the driver.
https://www.microsoft.com/en-us/down...s.aspx?id=5555

[rafa89]

First, let me thank PRJ for sharing his extensive and awesome work, that takes our engines to another level!

I'm running PRJmod for some time now, but a can't get data logging work (winlog), even after reading m232.org page and every single post on this forum about m232 several times!

I'm using ross-tech cable and also tried a blue kkl cable, without any luck. I tried with windows 10 and 8.1.

When I press WOT I can get vag-com to work. My car has no immo (92'). Another fact is that when fastlogging is enable, the led on the cable is blinking, so I think there is data streaming.

I have attached a print of my configurations...

Any input would be appreciated! Thanks!

[Acki]

Use RealTerm and show us what you receive.

[rafa89]

Realterm doesn't recieve any data. Just can't open the port, the status is always closed...

Any sugestion?

Thanks!

[prj]

Yes that's because the cable is not in dumb mode. Open VCDS, go to the options, uncheck "boot in intelligent mode", press test, then save, exit VCDS and it should work after.

[rafa89]

Thanks for your input!
Yes its in dumb mode. That was one of the things that I have done, that tip is on some post...
I have tried ross-tech, blue cheap cable and E1260, without any luck...

[prj]

Well then there is something wrong with your port config. Try assigning another port, try something not used, maybe COM10 or COM12 or so.
COM1 on older computers is native.

Also, you can't have both TunerPro and WinLog accessing it at the same time. If you don't know that... For that you need a COM splitter.

COM ports are exclusively opened. If one app is using it nothing else can.
You can try getting VCDS Lite to work through the com port also.

[rafa89]

At this stage I'm just trying to setup Winlog. Doesn't even have the tunerpro opened.

Just tried all three cable with higher port, without success.

Removed all vcds / drivers etc from the computer, installed everything from the beginning, nothing.

tried vcds lite, nothing...

Running out of pacience for something trivial like configuring a com port!

Will try a old laptop with win7 32b...

[prj]

VCDS Lite must work if you hold pedal WOT, you must be able to connect.
If you can't connect with VCDS Lite but you can connect with the normal one it's 100% COM port configuration problem.

Sorry, can't help you further.

[Acki]

But you started the engine without WOT and also did a „key off“ event before? Only to spoke about?
both chips you have using the prj mod?

[rafa89]

prj VCDS (reading engine module) works when I turn the ignition on doing WOT. Didn't test to read the module with VCDS Lite. Gona test this week.

Acki I have done all hardware mods, of course. So far the sequence I have adopted is: Connect the cable to PC, install the drivers and COM Port -> Open Winlog -> Configure device on Winlog -> Turn on the ignition -> Hope it to work -> Hope shattered (Just to be clear, I only press WOT when I want to connect regular VCDS).

Thanks for your time folks!

[prj]

So test the module with VCDS Lite and with KKL cable, not rosstech.