EVOScan questions

[Greg E]

Received this PM earlier and figured I'd address it here:


First, I gotta say, all your hard work is amazing, you guys made an awesome breakthrough with the Chromed stuff.

So, for my question, I'm goin Chrome once I have other things sorted out with my car, in the mean time, my old palm logger died on me so I purchased EvoScan and their cable to use with my '92 TT, to familiarize myself with the works of things, I finally got the cable today and had a hard time last night connecting, once I finally got it to connect, it would only connect with the 1.3x setting and the MMC (1G/12pin) setting with baud rate of 1953 and everything seemed jittery and slow.

I wasn't sure if your custom .xml files would work for me since I'm just running the stock ECU at the moment, or if I indeed need to replace the original file with yours, or if there's other settings or explanations for my issue. I thought I'd ask you, since EvoScan is your choice of logging for your Chromed ECU's.

Thanks man!

Unless you're using the tactrix 2.0 cable you should always use the 1.3 option. Even if you're not using the tactrix 1.3 for logging.

My chrome evoscan XML file will connect and display values if used with a 1G but many of the values will not be correct. This is because the data being sent by the MUT requests are calculated differently than the OBD1 cars. Some things *may be* correct but you are better off using the MMC options with the evoscan file that came with the program.

[Kx1984]

Oh so use 1.3 ?

What not just use 2.0 with my tactrix?

Kx

[Greg E]

If you're using the tactrix 2.0 then you must use the 2.0 evoscan setting. If using any other cable, use the 1.3 logging option.

[Nihil]

Oh so use 1.3 ?

What not just use 2.0 with my tactrix?

Kx

This question was in regards to stock, non flashable first gen ECU's and using EvoScan just as a general logging software. If you're all setup with the Chrome flash capabilities, follow those instructions.


If you're using the tactrix 2.0 then you must use the 2.0 evoscan setting. If using any other cable, use the 1.3 logging option.

Thanks for clearing this up Greg, so from what I can tell, EvoScan as just a day to day regular use logger, is kind of slow.

[Greg E]

Yep.

All my evoscan file does it adapt it to work with Chrome. That's all.

[Nihil]

Yep.

All my evoscan file does it adapt it to work with Chrome. That's all.

Yeah, except, using the tactrix and 2.0 the baud rate is at 15645 so you get quicker sampling rates, right? I'm assuming there's no work arounds to get OBDI cars up to that, in EvoScan? The program itself is pretty awesome, just slow, I dig the gauge layouts though.

[Greg E]

I have no idea how to get the OBD1 ECU to communicate faster.

How many items do you log at once?

[Nihil]

I haven't logged anything yet, I literally just got the cable last night when I got off work, went out in the dark n fiddled with it for about 15 mins until I got it to connect and noticed it was slow and jittery. Going off of the stated settings for Chrome vs what was working for me, I assumed the settings were the culprit for my results and had the question of OBDI capabilities.