[plain OM]

Yes, RRLogger is a data-logger. It has live data display options (graphs, digital, analog pointer gauges etc) and can save the data to a spreadsheet file.

I had read on the Romraider forum that some had initial difficulty installing it on W8 -- something to do with drivers. When I installed it on my W7, and connected the cable, Windows took care of finding the drivers etc, and it was plug/install-and-play. So I'm interested in knowing if FreeSSM and RR install and run with the KKL cable on W8 in the same way. Look forward to your update.

 

[1 Lucky Texan]

will FreeSSM work with the tactrix cable?

just wondering, I'm still on the learning curve with RR. Got it reading, but logging not so much. (thought I was logging yesterday - can't find the file. But for some reason, notepad was filled with junk????)

 

[dralb]

Yes, RRLogger is a data-logger. It has live data display options (graphs, digital, analog pointer gauges etc) and can save the data to a spreadsheet file.

I had read on the Romraider forum that some had initial difficulty installing it on W8 -- something to do with drivers. When I installed it on my W7, and connected the cable, Windows took care of finding the drivers etc, and it was plug/install-and-play. So I'm interested in knowing if FreeSSM and RR install and run with the KKL cable on W8 in the same way. Look forward to your update.

I'll try it tonight and post my results.

 

[ntippet]

Good read about the founder of Enginuity / RomRaider.

My bout with open source tuning

 

[bokiv]

Does anyone knows what will happen if after oil change oil dilution ratio value is not reset? Is it possible to reset oil dilution ratio value if i try to re-flash ECU?

Regards
BV

 

[jnail]

Hi, sorry to ask a question that probably has been asked already, but I have been searching, and can't find an answer.
I have a 2001 outback, and I downloaded the freessm software.
The cable I have says KKL vag-com for 409.1

when I plug the cable into the subaru, into the black plug at the bottom left of the dash. and I start the free-ssm software. In preferences, it passes the comunication test, but when I click on the engine button, I get an error that says "no or invalid answer from the ecu"

Do I need a different cable? Or is it a driver issue, and something I can fix with this cable? I have seen some info about different chip sets in the cables, but I don't really understand it.

I am doing all this with the igniton turned on, and the com port is correct. please help!

thanks

 

[Greenmamba]

You will probbaly need the VAG-K+CAN Cable. See post #616 (Stig) in this regard.

 

[plain OM]

. . . I had read on the Romraider forum that some had initial difficulty installing it on W8 -- something to do with drivers. When I installed it on my W7, and connected the cable, Windows took care of finding the drivers etc, and it was plug/install-and-play. So I'm interested in knowing if FreeSSM and RR install and run with the KKL cable on W8 in the same way. . . .

Answering my own question, but thought I'd post if it might help others.

Just installed both FreeSSM and latest Romraider on a laptop running Windows 8. Both installs went smoothly. Also downloaded the latest Romraider Logger definitions (didn't bother with the ECU defs --- not using that side of it) and the "cars_def" file; both placed in the main Romraider folder in Program Files.

Both programs started up and recognized and set up the driver for the VAG COM KKL-409 cable on COM3. I set-up the "location of the defs files" in the "Settings" menu of Romraider. (Logger found the "Def file" but not the "cars_def" xml file that was in the same place; however, it kept wanting to go to the website to download the "cars" file. I'm not sure what was happening, but the last time I removed the "cars" file from the Romraider folder, and re-installed it, it worked.) Both programs were then tried with my car (07 OB) and worked the same as was my experience when using a computer with Windows 7.

So, yes, both appear to work fine with W8.

Question: In the Romraider Logger "Settings" drop down menu list there's something new (for me) in the version I have (0.5.6/RC6). It's listed as "CAN bus Logging (2007+)", and an additional explanation that appears when the cursor is on the line is: "Select to enable logging via CAN bus using a J2534 compatible cable".

Is there any advantage to this, and if so, is the J2534 available as readily as the KKL-409 type? Is this the same as the VAG-K+CAN commander cable that Stig mentions back in post #616 and elsewhere?

 

[BroozerX]

Good day.

I've been searching for quite a few months now to get any decent information from my 99 Subaru (impreza GTT), tried pretty much any VAG COM/KKL version i could get my hands on.

Strange enough, with my 409.1 type (ch340t chip), i can get realtime information in Romraider and ECUexplorer, but it cant connect to ECU in both FreeSSM and Evoscan (Evoscan keeps saying my FTDI drivers are not installed, if i force-install them, none of the programs are working anymore).

So just ordered the VAG-K+CAN one, from the Ebay site Stig mentioned, but i noticed there are quite a few VAG-K+CAN versions around, Commander 1.4 and 3.0(upto 3.6) and just K+CAN version without Commander.

I just refuse to buy a Openport 1.4/2.0 cable, they are very expensive and still at a risk it wont work. (specialy on programs you have to buy like Evoscan or Dashcommand), the tactrix one is close to $200 with shipping.

 

[cardoc]

will FreeSSM work with the tactrix cable?

just wondering, I'm still on the learning curve with RR. Got it reading, but logging not so much. (thought I was logging yesterday - can't find the file. But for some reason, notepad was filled with junk????)

You have to record the data. It doesn't do it automatically. Under Settings, click on Control File Logging with Defogger Switch. When you want to record, push the button, then again to stop and save the file.

Under Settings, click Log File Output Location and then choose where to save the logs.

And you have to have a spreadsheet program to open the recorded logs. I use Excel.

 

[Tapani]

Memorized code that I can not clear :-(

Hi all,

For some reason I am not able to clear a memorized diagnostic trouble code in our 2007 2.0 n/a Forester.

There's a memorized P2441 indicating that one of the secondary air injection valves do not work - I opened them both and jigled them with the freeSSM - both work ok. And it's not in the upper part for current codes.... also, there's the code 64 in the cruise control probably triggered by the one I can not clear.

What do I do wrong?

Thanks,

Tapani

Finland

 

[tdelker]

You can always disconnect the battery, step on the brakes for a minute or two (to make sure you drain any capacitors holding memory) wait a few minutes and reconnect the battery. The car will have to relearn its set points.

 

[Tapani]

I disconnected the battery - but did not stand on brakes.... no help.

The memorized code was still there.

Tapani

 

[1 Lucky Texan]

that code is likely recurring.

I had to address secondary valves stuck by removing about 15 codes and reflashing the ECU. Just hope yours stick closed. They are expensive parts, there's no evidence the design has been improved, they are tricky to replace. They are only used for a few seconds on a cold start. I have had no issues with them disabled for years.

while not Forester specific (maybe check at the Forester Forum) here's the thread at NASIOC - 06 WRX Air Pump Removal - is it safe?? - NASIOC

 

[Tapani]

Yeah, the story is that the valves with Hitachi ECU on the N/A engines can not be disabled by reflashing.

The system is slightly different from the USM turbos - there's only one relay kicking both valves simultaniously. They both do work.

Maybe one was frozen shut when it was cold - there's plenty of condensation from the exhaust. The reed valves a slightly open .....

Maybe the P2441 is triggered differently from the turbos - since there's only one relay the valves must be tested at the same time.

Tapani

 

[BroozerX]

Big thanks to Stig, the VAG+K one he mentioned i recieved today, and it indeed makes FreeSSM work on a 1999 model

Sadly, Evoscan is acting somewhat weird, though it does connect (Openport 1.4, Subaru), it give very false info back (like 187 degree coolingfluid).

 

[cardoc]

Big thanks to Stig, the VAG+K one he mentioned i recieved today, and it indeed makes FreeSSM work on a 1999 model

Sadly, Evoscan is acting somewhat weird, though it does connect (Openport 1.4, Subaru), it give very false info back (like 187 degree coolingfluid).

How do you know the temperature data is false?

 

[Tapani]

Drive Cycle G ?

Has anyone seen this in the manuals?

If I understand correctly this procedure lets the ECu do the self test and see if the memorized condition is still present. It may not be possible to clear it at all w/o going thru these motions ?

Any comments?

Tapani

12.Drive Cycle
A: PROCEDURE

For the troubleshooting, there are seven driving patterns of drive cycles A to G. Driving in the specified pattern allows to diagnose malfunctioning items listed below. After the repair of the following trouble items, be sure to drive the vehicle with the specified drive patterns to check whether the function is resumed correctly.
​

1. PREPARATION FOR DRIVE CYCLE

1) Check battery voltage is more than 12 V and fuel remains half [20 — 40 l (5.3 — 10.6 US gal, 4.4 — 8.8Imp gal)].
​

2) Disconnect the test mode connector.

NOTE:
• Except for the water temperature specified items at starting, be sure to carry out the diagnosis after the engine is warmed up.
• Perform the diagnosis twice if the DTC marked with *. After completing the first diagnosis, stop the engine and perform second diagnosis in same condition.
​

8. DRIVE CYCLE G

1) Remove the battery negative terminal, and reconnect after 10 seconds have passed.
2) Start the engine and warm-up engine until coolant temperature is 80°C (176°F).
3) Start the engine and warm-up engine until coolant temperature is 40°C (104°F).

NOTE:
Do not let engine coolant temperature drop below 5°C (41°F).
​

4) Start the engine and warm-up engine until coolant temperature is 80°C (176°F).
5) Start the engine and warm-up engine until coolant temperature is 40°C (104°F).

NOTE:
Do not let engine coolant temperature drop below 5°C (41°F).

6) Start and idle the engine.

​

DTC Item Condition *

P0410 Secondary Air Injection System — *
P0411 Secondary Air Injection System Incorrect Flow Detected —
P0414 Secondary Air Injection System Switching Valve “A” Circuit Shorted —
P0417 Secondary Air Injection System Switching Valve B Circuit Shorted —
P1418 Secondary Air Injection System Control “A” Circuit Shorted — *
P2440 Secondary Air Injection System Switching Valve Stuck Open (Bank 1) — *
P2441 Secondary Air Injection System Switching Valve Stuck Closed (Bank 1) — *
P2442 Secondary Air Injection System Switching Valve Stuck Open (Bank 2) — *
P2443 Secondary Air Injection System Switching Valve Stuck Closed (Bank 2) —
​

 

[cardoc]

During a "drive cycle" the ECM is testing emission components in different categories. After a repair is performed and the ECM reset it forces a series of test on the operations of emission components to insure proper function. It also compares data to programmed parimeters. The drive cycle does not only occur after a reset. The ECM performs the test at varying intervals when it sees an opportunity to test a system. Some test are performed at start up, others in the background while you drive. These test and bad results trigger the CEL/MIL.

If after a repair and the emission monitor is set after testing a problem is still present the light and code(s) come back on indicating the issue hasn't resolved. Every manufacturer/model has its own drive cycle.

 

[Tapani]

Right, thanks for your answer.

How come then I still have the P2441 in the memorzed section and not in the current list? And the memorized one will not reset with the freeSSM.

It appears on the memorized list a second after I finnish the reset w/o any self test by the ECU. And nothing on the current list......

Thanks,

Tapani