The Vag-Com to Android phone setup should work as long as the phone is OTG compatible.

But whether or not BtSSM will work with your ECU might depend on whether the ECU has been "defined". Do you have the ECU ID number?

BtSSM will work in two modes: if the specific ECU has been "defined", it should work, and all the parameters would be available (although many will have to be set up manually as "custom fields"). If that specific ECU has not been defined, it might not work, or might work only partially, but in some cases, a "use a proxy" setting in BtSSM will provide close to, if not full, parameter coverage.

If needed only for occasional diagnostics/logging, have you considered Romraider (RomRaider - Open Source ECU Tools | RomRaider / RomRaider) ?

 

The Vag-Com to Android phone setup should work as long as the phone is OTG compatible.

But whether or not BtSSM will work with your ECU might depend on whether the ECU has been "defined". Do you have the ECU ID number?

Thanks Plain OM for the response. Could you please tell me how to find ECU ID number?

I do have an OTG compatible Android phone.

BtSSM will work in two modes: if the specific ECU has been "defined", it should work, and all the parameters would be available (although many will have to be set up manually as "custom fields"). If that specific ECU has not been defined, it might not work, or might work only partially, but in some cases, a "use a proxy" setting in BtSSM will provide close to, if not full, parameter coverage.

If needed only for occasional diagnostics/logging, have you considered Romraider (RomRaider - Open Source ECU Tools | RomRaider / RomRaider) ?

I need to perform infamous P0420 diagnosis. I tried to use Romraider and I do not have a Windows OS computer. All of my laptops/Desktops have Ubuntu 18.04 and I have a tough time getting VAG-COM 409.1 KKL Cable setup on those computers. Infact, I had a tough time on setting the cable serial port identification setting on a Windows laptop (not mine) as well. Therefore, I thought that it is relatively easy to setup VAG-COM 409.1 KKL Cable and btssm on my old OTG compatible Android phone (ASUS Zenfone 5).

I may use Romraider if I can get VAG-COM 409.1 KKL Cable setup on my Ubuntu laptop. (There are few threads on this topic on Ubuntu and other forums.) Especially, I will go on this route if I do not have to worry about ECU ID on RomRaider.

 

Need to communicate with the ECU in the first place to get the ECU ID. However, via the ECU part numbers I found the related CAL IDs that would apply, and then searched the Romraider forums for them, but it appears they haven't been defined. (This presumes that your 2008 is up-to-date on all ECU reprogramming recalls.)

That still doesn't preclude the possibility of BtSSM working with your ECU, perhaps using a "proxy". There's a BtSSM forum at legacygt.com. The originator of BtSSM, heiche, and others might be able to help with this as well. (https://legacygt.com/forums/showthread.php/btssm-bluetooth-adapter-app-v-2-267811.html?). Alternatively, there's a contact page on the BtSSM website.

Romraider has forums for related discussion. Might want to ask there about using other operating systems (e.g., Ubuntu), and getting the cable to work. https://www.romraider.com/forum/ (There's been some cases of eBay Vag-Com cables not working. With good cables and recent versions of Windows, it's usually more or less plug and play; Windows should recognize the cable and look for a driver in memory or on-line.)

Also, with Romraider, the program seems to automatically find an ECU definition file that works, i.e., a proxy, even if it's not the actual ECU in the car, so that there's usually pretty good functionality from the start.

 

RomRaider help

Romraider has forums for related discussion. Might want to ask there about using other operating systems (e.g., Ubuntu), and getting the cable to work. https://www.romraider.com/forum/ (There's been some cases of eBay Vag-Com cables not working. With good cables and recent versions of Windows, it's usually more or less plug and play; Windows should recognize the cable and look for a driver in memory or on-line.)

Also, with Romraider, the program seems to automatically find an ECU definition file that works, i.e., a proxy, even if it's not the actual ECU in the car, so that there's usually pretty good functionality from the start.

Plain OM,

I installed drivers for VAG-COM cable on a Windows 7 computer and it says that the hardware is properly installed. I also installed RomRaider and tried upload ECU definitions file. I am not sure which ECU definition file to upload for my 2008 base 5MT PZEV.

I cannot get a log file without ECU definitions.

Do you have any idea which ECU definition file to use?
How do I test the communication setup? I do see a little blue LED lighting up.

Thanks a lot for your help.

 

No need to look for a specific definition file; there's cumulative ECU and Logger files to first download, unzip, and save in your computer.

Instructions for setting up the files, and the files to download, are in the first post of these two threads: ECU in RomRaider ? View topic - Latest RomRaider ECU Definitions (v 0.8.3.1b 10-07-09) (choose between Romraider Standard or Romraider Metric file to download, although essentially they are the same), and Logger in RomRaider ? View topic - Latest RomRaider LOGGER Definitions (currently version 346). Follow the instructions (at the top of the first post of each thread) for opening the files, saving them, and directing the Romraider (RR) ECU Editor, and RR Logger to their respective files.

When set up, these cumulative files should be be enough to get things started with most, if not all, standard parameters and switches.

When the Logger connects to the ECU, the ECU ID number will appear at the bottom of the Logger screen. If the specific ECU had been defined, and that definition is in the downloaded file(s), the CAL ID would also appear; otherwise it will show "unknown". Once the ECU ID is known, the Romraider Forum can be searched to see if there's a specific definition file (or files) for it, although at this point, based on my search, it looks as if that's not the case.

(As your car is MT, the RR "TCU" functions, of course, will not be applicable.)

Not sure about "testing" the communications set up. When RR Logger is running it will try to connect to the ECU. The ignition has to be On for the Logger to connect to the ECU. This will be shown at the lower left of the Logger screen. The COM Port should show at the upper left. If the Logger cannot connect, sometimes there's more than one port listed in the COM Port drop down, and changing the port often completes the connection.

Hope this helps.

 

Ecu id

Plain OM,

I did some research on RomRaider forum and found that I was using an obsolete definition file. The latest ECU definition files were right there and I loaded Metric English definition file. However, I still cannot log any data and my .csv file is empty.

I also found that my ECU ID is 52221A8007. Since I am getting that information, I believe that I have established communication with ECU. Please correct me if I am wrong.

I do not have a CAL ID.

Please see the attached screen shot of RomRaider.

Let me fiddle with the setup and see how I can log data.

Thanks a lot for all your help.

 

Click on Parameter List at the left, above Unselect All.

Once the lower left says to Select Parameters . . . it's indicating there's a connection, and a list to select from.

At the bottom left there's several tabs to select the way the data is displayed. Lot's of choices.

Once some parameters (and perhaps switches) are selected they will show in the screen in whatever format is chosen.

To create the .csv log, click on the Start file Log button at the top.

 

Logging Data

Thanks again Plain OM.

I did log data at idle speed. Will analyze and most likely post onto CarDoc's P0420 analysis thread.

 

That's great.

Yes, although P0420 thread is very(!) long now, that's probably a good place to deal with the code.

Did you use all the available parameters for the log, or just some selections.

I've attached a list of the parameters and switches that are listed in the FSM. The list is what the dealer's Subaru Select Monitor can access. Compare that to the list of parameters, and switches, that RR shows is available when it's connected to the ECU. (Some of the names in RR might be different that the list, but I would imagine that most, if not all, are included in RR. Of course, usually only a selection are used. If too many are selected, the rate at which the parameters are sampled is slower. In this regard, in the menu drop down at the top left, select "Enable Fast Polling" if that is available.)

 

Data Log



Plain OM,

Thanks again for FSM Subaru Select Monitor parameter list. Attached is what I logged. I did not log all the parameters but most. It looks like that RomRaider has extra parameters than available. Let me edit my selection and log parameters when engine is warmed up. Hopefully, I do not have two O2 sensors synchronizing as explained by CarDoc.

 

That's a good start.

I see Fine Learning Knock Correction, and IAM (Ignition Advance Multiplier) is included. Were "EGR Steps", "Knock Correction Advance" (KCA), and/or "Feedback Knock Correction" (FKC), available?

I've only had a quick look at the log data, but did notice that the CPC Valve (aka Purge Valve) is running while at idle. It starts out at a fairly low value, but goes up to 14%, while the engine speed and throttle remain low. It's unusual for the valve to be opened atall during idle.

A suggestion. In the Logger Settings drop down menu, de-select the time stamp item. That will change the Time data from min:seconds (based on the current computer clock) to cumulative time of the logging session, starting at 0 ms.

There's a few parameters that usually don't need to be routinely monitored/logged. Will get back to those later. (Fewer parameters can improve the speed at which they are sampled, and it simplifies the spreadsheet log. But too few can mean having to run another log with them added. I tend to maximize the list, leaving out ones that I now know will not be used.)

Going to research the ECU ID again. There might be a specific definition file in the RR Forum, but it's not listed in the cumulative logger definition file. Will get back to this as well.

Having the specific ECU definition adds more parameters, but your list of available parameters seems to be quite good based on what I see in the log. Perhaps provide a list of all the parameters that are available. Select all of them in the Logger screen (ignition On, engine Off, and RR connected to the ECU) and run a log session for just a few seconds. That will generate a spreadsheet file with all the parameters. Post it here.

 

All Parameters

That's a good start.

I see Fine Learning Knock Correction, and IAM (Ignition Advance Multiplier) is included. Were "EGR Steps", "Knock Correction Advance" (KCA), and/or "Feedback Knock Correction" (FKC), available?

I have fine learning knock correction only. Please see the attached available full parameter log file.

I've only had a quick look at the log data, but did notice that the CPC Valve (aka Purge Valve) is running while at idle. It starts out at a fairly low value, but goes up to 14%, while the engine speed and throttle remain low. It's unusual for the valve to be opened atall during idle.

Thanks for the observation. Does that mean that the purge valve is faulty?

A suggestion. In the Logger Settings drop down menu, de-select the time stamp item. That will change the Time data from min:seconds (based on the current computer clock) to cumulative time of the logging session, starting at 0 ms.

Will do this next time. Thanks for the advise.

There's a few parameters that usually don't need to be routinely monitored/logged. Will get back to those later. (Fewer parameters can improve the speed at which they are sampled, and it simplifies the spreadsheet log. But too few can mean having to run another log with them added. I tend to maximize the list, leaving out ones that I now know will not be used.)

I was thinking about reducing the parameter list. I thought that A/F ratio corrections 2 and 3 are not that important.

Going to research the ECU ID again. There might be a specific definition file in the RR Forum, but it's not listed in the cumulative logger definition file. Will get back to this as well.

Having the specific ECU definition adds more parameters, but your list of available parameters seems to be quite good based on what I see in the log. Perhaps provide a list of all the parameters that are available. Select all of them in the Logger screen (ignition On, engine Off, and RR connected to the ECU) and run a log session for just a few seconds. That will generate a spreadsheet file with all the parameters. Post it here.

Attached, please find the overall list of parameters that I can log. Thanks again for your help.

 

The list of parameters in the log is pretty good, although, the data for several is quite odd. Was this with the ignition On and engine Off? I have a vague recollection that odd numbers might happen when RR is using proxy definitions with the engine off. I did more searching for the ECU ID, and found a thread in the RR Forum that appears to have the ECU definition file.

The thread is RomRaider ? View topic - def request. 2009 Legacy 2.5i MT EZ1GC00A. In the last post, your ECU ID is paired with EZ1GC00A, which is the CAL ID I verified in another source that applies also to the 2008 Outback 2.5, non-turbo, MT, CAL-spec. The ECU definition file is the second Attachment in the first post, identified as "RR_EZ1GC00A.xml [686.99 KiB]"

Having the specific ECU definition file is good, but I understand there also has to be a corresponding Logger definition file included in the cumulative Logger definitions file. I looked there and haven't found this ECU there. However, I would still suggest downloading that CAL ID file, and, the same as was done with the ECU definition file before, save it in the same folder as the previous def file, and link it into the RR ECU Editor File Manager. (Don't remove the previous files; leave them.) Then try the RR Logger connected to the ECU (ignition on). If the CAL ID now shows EZGC001A, then it's probably good. Next is to look at the parameters . . .

In the list of parameters on the left side of the screen, see if some of them might appear with different names, and look for additional ones, such as Feedback Knock Correction. Also, in the TOOLS drop down menu, click on Learning Table Values. RR will ask if you want to stop current logging -- yes. If it gets that far, after a few moments RR will display a table of A/F Learning values relative to MAF ranges, and a grid of Fine Learning Knock Correction vs. Engine Load. The augmented list of parameters and the LTV are additional "extended" parameters etc., that could be of help down the road. Also, now, with the ignition on but engine off, the data for all the parameters should be more "reasonable".

We'll get back to sifting through all the available parameters to get to more manageable number after we confirm if the file works.

 

Logger Definition File

Thanks a lot Plain OM.

Updated ECU definitions with correct log file from RR thread.

Quick question. I still get an error when I open RR logger saying that "Card definition file not found".

Is this the same definition file that you specified? or something else?

Thanks

 

Thanks a lot Plain OM.

Updated ECU definitions with correct log file from RR thread.

Quick question. I still get an error when I open RR logger saying that "Card definition file not found".

Is this the same definition file that you specified? or something else?

Thanks

No, it's not the same. There is a separate "cars" definition file. It's used to generate simulated dynafmometer graphs in RR. It's not necessary otherwise. Nevertheless, it can be downloaded and saved in the same folder on your computer where the other Logger definitions files are stored. The name is "cars_def.xml".

 

Logs with correct definition files

Thank you for clarification Plain OM.

I loaded the correct ECU definition file (EZ1GC00A.xml) and acquired a couple of logs tonight. First one is with just the key in at the start up position with the engine not running. The second log was taken with engine running while warming up.

Tomorrow, I will acquire a couple (or more) logs while driving.

I was thinking of plotting A/F ratio sensor (i.e front O2 sensor) on top of rear O2 sensor on the same plot. Just looking at the data, I do see that A/F ratio sensor Lambda value is more or less constant (this sensor is new) and rear O2 voltage fluctuates a lot with unusually high voltage. Also A/F ratio sensor current is 0mA and I wonder why.

Please let me know what parameters to plot.

Thanks again for your help.

 

There are still parameters with blatently incorrect data; e.g., in the engine running log, the Rear O2 Sensor voltage is reaching over 300 V, Accelerator Pedal angle is well off zero but should be zero if the pedal was not being pressed, and Manifold Absolute Pressure is moving between zero and 250 kPa (whereas Atmospheric Pressure is 100 kPa). Something isn't right.

The A/F Sensor current is off zero only when the air-fuel ratio isn't at the nominal 14.6:1, or the Lamda isn't at the nominal 1.00. The current is what signals the ECU to change the fuel trim to bring it back to nominal. Really odd numbers in various parameters were in the earlier log as well, so there seems to be a problem in the connection with and/or data collection from, the ECU, and the absence of any indication of A/F Sensor current could be part of that.

Did RR Logger indicate the CAL ID at the bottom of the screen, next to the ECU ID?

Let's reduce the number of parameters. Perhaps there's too many, or there's an interaction (e.g., conflict) between some that's causing the data to be way off.

Clear all the Parameters and Switches.

Then select only:

A/F Correction #1 (%)
A/F Correction #3 (32-bit ECU) (%)
A/F Sensor #1 (Lambda)
Accelerator Pedal Angle (%)
Battery Voltage (V)
Coolant Temperature (C)
Engine Load (Calculated) (g/rev)
Engine Speed (rpm)
Fuel Injector #1 Pulse Width (ms)
Ignition Total Timing (degrees)
Intake Air Temperature (C)
Manifold Absolute Pressure (kPa)
Mass Airflow (g/s)
Oil Temperature (C)
Rear O2 Sensor (V)
Throttle Opening Angle (%)

 

New Data

There are still parameters with blatently incorrect data; e.g., in the engine running log, the Rear O2 Sensor voltage is reaching over 300 V, Accelerator Pedal angle is well off zero but should be zero if the pedal was not being pressed, and Manifold Absolute Pressure is moving between zero and 250 kPa (whereas Atmospheric Pressure is 100 kPa). Something isn't right.

New idling log shows different numbers. Pressure recorded by MAF sensor (which is new) is around 35 kPa. I am not sure if RR is reading right parameter here. I do have a new air filter (not clogged) as well.

The A/F Sensor current is off zero only when the air-fuel ratio isn't at the nominal 14.6:1, or the Lamda isn't at the nominal 1.00. The current is what signals the ECU to change the fuel trim to bring it back to nominal. Really odd numbers in various parameters were in the earlier log as well, so there seems to be a problem in the connection with and/or data collection from, the ECU, and the absence of any indication of A/F Sensor current could be part of that.

New idling log shows A/F labmda within 0.99-1.01 and 1.00 most of the time. Please keep in mind that this log is acquired during warm up.

Did RR Logger indicate the CAL ID at the bottom of the screen, next to the ECU ID?

Initially, I had a tough time getting RR read the new ECU ID file. As of the previous data set and current data, yes, RR logger did show CAL ID and ECU ID as shown in attached screen shots.

Let's reduce the number of parameters. Perhaps there's too many, or there's an interaction (e.g., conflict) between some that's causing the data to be way off.

Clear all the Parameters and Switches.

Then select only:

A/F Correction #1 (%)
A/F Correction #3 (32-bit ECU) (%)
A/F Sensor #1 (Lambda)
Accelerator Pedal Angle (%)
Battery Voltage (V)
Coolant Temperature (C)
Engine Load (Calculated) (g/rev)
Engine Speed (rpm)
Fuel Injector #1 Pulse Width (ms)
Ignition Total Timing (degrees)
Intake Air Temperature (C)
Manifold Absolute Pressure (kPa)
Mass Airflow (g/s)
Oil Temperature (C)
Rear O2 Sensor (V)
Throttle Opening Angle (%)

As shown in the current log, only the above parameters were acquired and the data are significantly different from previous logs (not sure why, but, could be incorrect decoding of digital data). Please let me know if these numbers make any sense. I am especially concerned with low manifold pressure at idling around 35kPa.

Thanks a lot again for all your help.

 

Logs while driving

Plain OM,

I took two more logs while driving below 45mph. Manifold pressure did increase upto 100kPa when engine RPM is around 2500. I guess, these data may make sense now. Please let me know what you think about credibility of data.

Thanks

 

All the numbers look good in terms of RR reading correctly (i.e., credibility).

However, in all three logs the rear O2 sensor voltage is oscillating quite a lot. (Not a good sign.)

With the engine off, the MAP reading should be the same as, or very close to, atmospheric pressure in your area, and the Atmospheric Pressure parameter reading in RR if it's being displayed. (Comparing against the local weather station or website is one way to check the operation of both those sensors.)

When the engine is started, the MAP will go down because of the vacuum in the intake manifold. The 35 kPa is fine. When the throttle plate is opened widely, the intake manifold is open to the intake duct which is essentially at atmospheric pressure, so the MAP will go up toward that. When the throttle is at 100%, the MAP will be very close to the Atmospheric Pressure. This is confirmed in the logs.

With the CAL ID showing, it looks as if RR picked up on the specific ECU definition file. However, the list of available parameters in the two screen shots is missing some that I'm familiar with, such as Feedback Knock Correction. I suspect this is because while there is an ECU definition file (the one you added), as I mentioned earlier, there doesn't appear to be a corresponding Logger file for the same ECU ID. I'll see if I can check on this with the folks on the RR forum.

In the meantime, could you try the Learning Values Table in the TOOLS menu to see if it works, and what result(s) it provides?

With that done, we can start adding back some parameters that probably could always be monitored/logged, and, as this is done in stages, watch for any discrepancies in the data as was apparent earlier. These would also include ones that should be included when looking at the P0420 issue on the other website.

 

All the numbers look good in terms of RR reading correctly (i.e., credibility).

However, in all three logs the rear O2 sensor voltage is oscillating quite a lot. (Not a good sign.)

I guess, I am going to interpret this as either,
1. Bad upstream CAT
2. Bad Rear O2 sensor (I have a new A/F ratio sensor and MAF sensor.)
or both.

With the engine off, the MAP reading should be the same as, or very close to, atmospheric pressure in your area, and the Atmospheric Pressure parameter reading in RR if it's being displayed. (Comparing against the local weather station or website is one way to check the operation of both those sensors.)

When the engine is started, the MAP will go down because of the vacuum in the intake manifold. The 35 kPa is fine. When the throttle plate is opened widely, the intake manifold is open to the intake duct which is essentially at atmospheric pressure, so the MAP will go up toward that. When the throttle is at 100%, the MAP will be very close to the Atmospheric Pressure. This is confirmed in the logs.

Thank you for the explanation.

With the CAL ID showing, it looks as if RR picked up on the specific ECU definition file. However, the list of available parameters in the two screen shots is missing some that I'm familiar with, such as Feedback Knock Correction. I suspect this is because while there is an ECU definition file (the one you added), as I mentioned earlier, there doesn't appear to be a corresponding Logger file for the same ECU ID. I'll see if I can check on this with the folks on the RR forum.

In the meantime, could you try the Learning Values Table in the TOOLS menu to see if it works, and what result(s) it provides?

With that done, we can start adding back some parameters that probably could always be monitored/logged, and, as this is done in stages, watch for any discrepancies in the data as was apparent earlier. These would also include ones that should be included when looking at the P0420 issue on the other website.

Now, with this ECU definition file, can I use btssm instead? I do not want to use this laptop while driving.

Thanks again for all your help.

 

BtSsm

Good Morning Plain OM,

I just want to thank you for posting in
https://legacygt.com/forums/showthread.php/btssm-bluetooth-adapter-app-v-2-267811p29.html
@post # 432 for me.

 

Good Morning Plain OM,

I just want to thank you for posting in
https://legacygt.com/forums/showthread.php/btssm-bluetooth-adapter-app-v-2-267811p29.html
@post # 432 for me.

Thanks. Might take some time for a reply. If you try BtSsm and have problems or questions, I can try to help, but they can also be posted in that thread.

Heiche is the developer, but a number of others there are quite familiar with the App and might help as well.

I've been running BtSsm on a tablet for about four years now, displaying a range of parameters whenever the car is in use. See https://www.subaruoutback.org/forum....org/forums/66-problems-maintenance/249641-bluetooth-alternative-romraider.html. (I've since somewhat improved the mounting that's shown there, and the range of displayed parameters changes from time to time.)

 

@priyadar

I've posted in the Romraider forum to see if the absence of the ECU ID in the Logger definitions file is the reason for some parameters not showing and the LTV not working. https://www.romraider.com/forum/viewtopic.php?f=8&t=15890&p=144460#p144460

There's also a response to the post in the legacygt.com BtSsm thread.

 

Good Morning Plain OM,

Thank you for posting in RomRaider forum as well.

I looked at the response from Prescitus and this is what I understand
________________________________________________________________________________
You can scavenge the RR forum and github for logger defs (sometimes found in the ROM defs thread for a given ECU/CALID)
or at least the logger memory addresses - that you can then use with the generic field defs to build the custom fields up in BtSsm
and/or supplement your RR logger defs to work for this car.

On its own, BtSsm will not know any more than RR logger defs.
_________________________________________________________________________

This means that I can use .def file(s) that I downloaded from Romraider forum in BtSsm. I am not sure how to build custom fields. I think I need that to get knock sensor data that you mentioned before.

________________________________________________________________________________

The only other thing worth trying (at least as a starting point) is the BASIC alias in BtSsm, then add some custom fields to it one by one....
from both the generic params (Pxxx) and then the engineering/extended (Exxx or 1/2/4-byte params) that might be defined for this ECU/CALID
or a previous CALID for the same Model/Make/Drivetrain/Market combo.... those too (if they're out there) should work just fine.
________________________________________________________________________________
I need to study ECU parameters and BtSsm programming to do this. It may take some time if I decides to do so. I will have a significant learning curve in here.
________________________________________________________________________________
With an old NA 4-banger and the slow VAG-com interface, I doubt he'd really need any high precision advanced fields anyway.
Just log the usual vanilla stuff and see how she goes.
________________________________________________________________________________

This means unless I use OBDLink LX/Tactrix open port tools and CAN bus, I cannot log a lot of data.

I will install BtSsm tonight and test in on VAG-COM cable and let you know how it goes.

I ordered downstream O2 sensor and I should get it this Thursday and most likely be able to install Thursday night. Hopefully by then, I will know what is bad.

Thanks again.

 

This means that I can use .def file(s) that I downloaded from Romraider forum in BtSsm.

With BtSsm you don't have to download and install any definition files. The reference to finding such files in the Romraider forum was in regard to adding Custom Fields. To the extent that BtSsm uses "definition files", they are installed by the developer.

I am not sure how to build custom fields

It's in the BtSsm Manual that's on the website. But we'll get to that; first steps first . .

I need to study ECU parameters and BtSsm programming to do this. It may take some time if I decides to do so. I will have a significant learning curve in here.

As noted earlier, when Romraider connects, it automatically shows a fairly comprehensive list parameters that are immediately available from the ECU, and that you can choose from with a simple checkmark. That makes it useful from the start. With BtSsm, initially, there will be a comparatively small list that the developer has set up as a "default". To get other parameters, Custom Fields have to be adde to the list. The two programs provide similar information in the end, but work differently, including the interaction with the user. Each has its advantages and disadvantages. Yes, there is a learning curve, indeed, for both, but it can be fairly fast.

This means unless I use OBDLink LX/Tactrix open port tools and CAN bus, I cannot log a lot of data.

No. The Vag-Com cable should be fine. (The poster is referring to some of the "extended" parameters, where the data retrieval can be set for more "bytes" so that the information comes faster and more precisely. It shouldn't be a factor in what we do here.)

 

BtSsm

Hi Plain OM,

I just installed BtSsm. Before that, I installed OTG checker and verified that my phone is OTG compliant. However, BtSsm did not detect VAG-COM cable. I guess, I am going to try with a different USB to micro USB cable.

Edit:
It looks like that there is difference between OTG cable and USB to micro USB cable.
https://www.quora.com/How-different-is-a-normal-usb-cable-from-OTG-usb-cable

Therefore, I may have to purchase one OTG cable and try with my old phone.


Thanks

 

Hi Plain OM,

I just installed BtSsm. Before that, I installed OTG checker and verified that my phone is OTG compliant. However, BtSsm did not detect VAG-COM cable. . . .

In BtSsm, did you set the ECU Interface in the App to use the USB cable connection?

From the BtSsm Manual (https://www.btssm.com/manual.html):

INSTALLATION
Adapter: Plug your supported adapter into your car's OBD2 port. This D-shaped connector is often located near the driver's left knee, under the dash

BtSsm app: If you haven't already done so, using your Android device, open "Play Store". Search for BtSsm, and purchase it

Open the BtSsm app for the first time. Press "Settings", then "ECU interface", and choose the appropriate adapter.
If the key is on, the app should discover your ECU in a few seconds.

In other words, the BtSsm App has to know which OBD "adapter" is being used, e.g., the USB cable/Vag-Com, or, e.g., the BtSsm K Bluetooth unit. If BtSsm isn't detecting the Vag-Com, it could be because it's not set to look for a USB "adapter".

 

OTG Cable test

Good Morning Plain OM,

I posted my issue with BtSsm on legacygt forum and yet to get a response. I also contacted btssm directly multiple times and did not get any response at all. I guess, it is just a single developer and not a company.

I tested my new OTG adapter on ASUS Zenfone 2 and plugged a USB stick into it and the phone did read teh entire drive. Thus, OTG cable is good. Since I managed to communicate with ECU via Windows my VAG-COM 409.1 cable should be good. Therefore, If BtSsm is certified to work with OTG compatible Android device, I cannot understand why BtSsm on Zenfone 2 cannot detect the ECU.

Read through your BtSsm thread and found that you are using BtSSK bluetooth adapter with your 7" Android tablet. Therefore, you did not have the problem that I have right now. I guess, I have to keep on trying my other Android devices (A few tablets and a one more phone.)

Thanks

priyadar

 

Proper Adapter/ECU ID

Thanks again Plain OM,

Yes, the issue was I did not select proper adapter as it was on default option 1. Changed to OP2/KKL usb+otg and you are correct that BtSsm did detect it within a couple of seconds.

Because of my Cal ID, BtSsm now says ECU is unsupported. It is asking me to create an alias. I thought of using Cal ID EZ1GC00A as alias and proceed. I also did some research and found your post on
https://www.subaruoutback.org/forums/66-problems-maintenance/503333-btssm-ecu-unsupported.html

which tells me that I have to use one of

2F220A4706

2F220A4006

2F22044706

Do you have any preference for above on my Cal ID EZ1GC00A?

 

. . . BtSsm now says ECU is unsupported. It is asking me to create an alias. I thought of using Cal ID EZ1GC00A as alias and proceed. I also did some research and found your post on
https://www.subaruoutback.org/forums/66-problems-maintenance/503333-btssm-ecu-unsupported.html

which tells me that I have to use one of

2F220A4706

2F220A4006

2F22044706

Do you have any preference for above on my Cal ID EZ1GC00A?

Those ECU ID's were for 2005's.

I don't think your CAL ID would work.

The legacygt.com BtSsm thread that is currently in use is a continuation of an earlier one that was very long. The administrators decided to close the earlier one and continue with the current one. That's why the current thread has "v.2" in it's title.

The original thread is https://legacygt.com/forums/showthread.php/btssm-bluetooth-adapter-app-v-1-closed-229709.html. In that thread there's mention of using a generic entry that is supposed to provide fairly good coverage of the ECM parameters. It's called, BASIC (all capitals). Apparently, it's entered exactly that way where an alias ECU ID would go. It appears it's been tried a number of times and has worked. Once that's running, it seems additional Custom Fields can be tried/added. Probably worth a try to get started. (Do a search for that term in thread for more details.)

 

I changed the rear O2 sensor today. Ran the engine under idle speed for 10 minutes.


I used the first 2005 ECU alias and btssm provided some results. I am not sure they make any sense. I will try to change the alias to BASIC tomorrow.

Thanks a lot for your help.

 

So it appears that a connection to the ECU is being made? What did the results look like?

Before trying the BASIC alias, it might be an idea to go to Settings and there find/use the option to delete aliases. That way the 2005 alias will be removed to avoid any possible conflict. This is also something that I saw suggested in the related posts of the earlier BtSsm thread.

 

Logs

I guess, I did not realize that .csv files cannot be attached, Please see .zip logs.

Thanks

 

Most of the parameters (albeit a limited list) in that log look reasonable except the MAF, which is jumping all over the place. There isn't any other parameter there to compare with. In your earlier Romraider logs, the MAF, where it was recorded, wasn't showing such a variation. BtSsm, with the BASIC setup, might be looking at an incorrect address in the ECU, but I'm not really familiar with how the software works.

Did you save a log from that test using the alias 2005 definition?

The last Romraider Log, using the specific ECU definition, was generally good (as long as not too many parameters, or conflicting parameters, were being monitored). We were going to add parameters to the shortened RR list, to see if any problems arise. Are you still interested in continuing with Romraider Logger?

 

Plain OM

I will continue with Romraider as the data were correctly decoded. Thanks

 

Plain OM

I will continue with Romraider as the data were correctly decided. Thanks

Okay for now.

The last RR logs were based on a reduced list of parameters in post #19 above. Here's the same list, with suggestions for additional parameters from those available to set up a base profile (today's additions in italics):

A/F Correction #1 (%)
A/F Correction #3 (32-bit ECU) (%)
A/F Learning #1
A/F Sensor #1 (Lambda)
Accelerator Pedal Angle (%)
Atmospheric Pressure (kPa)
Battery Voltage (V)
CPC Valve Duty Ratio %
Coolant Temperature (C)
Engine Load (Calculated) (g/rev)
Engine Speed (rpm)
Fine Learning Knock Correction (degrees)
Fuel Injector #1 Pulse Width (ms)
IAM (Multiplier)
Ignition Total Timing (degrees)
Intake Air Temperature (C)
Learned Ignition Timing (degrees)
Manifold Absolute Pressure (kPa)
Mass Airflow (g/s)
Number of Exh. Gas Recirc. Steps (steps)
Oil Temperature (C)
Rear O2 Sensor (V)
Throttle Opening Angle (%)
VVL Lift Mode
Vehicle Speed (km/h OR mph)

With RR connected to the ECU, set up this list of selections, and then under the FILE drop down menu at the upper left, select "Save Profile As", and give it a name. Save it. This way, any time RR is started up, you can go to FILE and "Load Profile", and this will set up RR to monitor/log the same list once again. Of course, additional parameters can be added, if needed, and additional profiles saved. But I think this list is a start.

To ensure it's working, make three logs:

1) A very short log with Key On, Engine Off.
2) With the engine warmed up, a one minute log with the engine idling, AC off, no other accessories or lights on, and no use of the accelerator pedal.
3) A log about one minute long while cruising steadily at a highway speed.

The numbers in these logs will help confirm if RR is working reliably, and provide a basic data set for troubleshooting.

 

Numbers generally look okay with the exception of the Rear O2 voltage. Going to call in @cardoc on this for the P0420.

 

Rear O2 sensor and A/F Lambda



Good Morning Plain OM.

Thanks a lot for analyzing my logs. Have a couple of questions.

1. What would be the typical type/value(s) for rear O2 sensor voltage data? I am under the impression that O2 sensor voltage will be converted to O2 percentage or a mass flow rate with a calibration.

2. Do you know the definition of front A/F lambda?

I am trying to plot data from both sensors on the same plot and I need a common unit.