[pheno]

Originally Posted by ingenieur

I prefer to use a data logviewer rather than the gauges, but then this is more of a diagnostic tool rather than for tuning. Glad to see this forum is actively participating in the feedback as your recent versions have become very versatile, flexible, and easier to configure. Cheers mate!

Thanks! I appreciate it.

About play back function I'm also looking at adding a graph window along with gauges. And I believe there is more to come !

[TDIwyse]

Originally Posted by jakeybear

"Good grief Charlie Brown... How's a man supposed to keep up?"

Deer me ... I missed this post. Ha! Love it ...

[Mik325tds]

Originally Posted by pheno

Two things found:

Version from 05-mar used faster windows style.
Curve tracker had to go for now.

Haha, hilarious! Gotta show this to my team...

[Smonkey09]

The used laptop I bought just for running BMW software arrived. Tonight after work I plan to try to install all of the software needed to run logging/diagnostics.

I found the following job on fiverr that I thought was interesting. For those people who are not the most technical, they may appreciate the optional install assistance services. Who knows, if I have trouble getting things to run I may ask this guy for help!

https://www.fiverr.com/cj83lex/give-...-code-your-bmw

[iaknown]

Originally Posted by Smonkey09

The used laptop I bought just for running BMW software arrived. Tonight after work I plan to try to install all of the software needed to run logging/diagnostics.

I found the following job on fiverr that I thought was interesting. For those people who are not the most technical, they may appreciate the optional install assistance services. Who knows, if I have trouble getting things to run I may ask this guy for help!

https://www.fiverr.com/cj83lex/give-...-code-your-bmw

If you need remote support I have someone that can help, just PM me.

[TDIwyse]

Originally Posted by iaknown

If you need remote support I have someone that can help, just PM me.

This helped me a lot... Thanks again for that suggestion iaknown.

[iaknown]

Originally Posted by TDIwyse

This helped me a lot... Thanks again for that suggestion iaknown.

[Smonkey09]

Originally Posted by iaknown

If you need remote support I have someone that can help, just PM me.

Cool. I'll give it my best to install everything this evening.

[Smonkey09]

So I got EDIABAS up and running today based on Mik325tds's guidance on page two of this thread. Got results when I ran fs_lesen and everything. I then proceeded to change my fuel filter and purge the air in the lines before starting by running EKP360.prg, again per Mik325tds's guidance. Ran the job twice, in fact. Car started right away.

However, I'm having no luck connecting to car via INPA or Test-O. Any suggestions would be appreciated:

-Win 8.1 64-bit
-I bought the green cable per the ebay link on first page
-Updated driver per FTDICHIP.com
-Followed all guidance in this thread - EVERYTHING Mike325tds said to do on page 2.
-Right clicked tool32.exe and INPALOAD.exe, ran 'Troubleshoot compatibility' and selected suggested settings (Windows 7 for INPA)
-Right clicked both executables again and selected run as administrator
--EBIDAS 7.3.0, INPA-Loader v5.0.6

Also followed all guidance in the attached pdf document (except step 5 - running OBDsetup.exe - as guy who provided software said this isn't needed with current version).

Only posting this on the thread vs sending PM because I think other folks would benefit, but if this is something better addressed via PM let me know.

[pheno]

Originally Posted by Smonkey09

So I got EDIABAS up and running today based on Mik325tds's guidance on page two of this thread. Got results when I ran fs_lesen and everything. I then proceeded to change my fuel filter and purge the air in the lines before starting by running EKP360.prg, again per Mik325tds's guidance. Ran the job twice, in fact. Car started right away.

However, I'm having no luck connecting to car via INPA or Test-O. Any suggestions would be appreciated:

-Win 8.1 64-bit
-I bought the green cable per the ebay link on first page
-Updated driver per FTDICHIP.com
-Followed all guidance in this thread - EVERYTHING Mike325tds said to do on page 2.
-Right clicked tool32.exe and INPALOAD.exe, ran 'Troubleshoot compatibility' and selected suggested settings (Windows 7 for INPA)
-Right clicked both executables again and selected run as administrator
--EBIDAS 7.3.0, INPA-Loader v5.0.6

Also followed all guidance in the attached pdf document (except step 5 - running OBDsetup.exe - as guy who provided software said this isn't needed with current version).

Only posting this on the thread vs sending PM because I think other folks would benefit, but if this is something better addressed via PM let me know.

What kind of error did you get with Test-O. Basically there's dependency on EDIABAS only but I haven't tested it with Win8.1 64-bit.

[ingenieur]

If you are able to run Tool32 to bleed the fuel system then I'm not sure why INPA or Test-O has a problem. Ediabas only will allow 1 program at a time to run.

[DWR]

Originally Posted by ingenieur

Ediabas only will allow 1 program at a time to run.

Not sure what you mean by this. I certainly have had 2 instances of TestO open at the same time. Can you elaborate?

[DWR]

Originally Posted by Smonkey09

-I bought the green cable per the ebay link on first page
-Updated driver per FTDICHIP.com
-

I forgot to post this a long time ago. There is a source that sells pre-tested cables. They sell logging software, so they have a vested interest in getting good cables to their customers. Just getting the "green" ones isn't always a guarantee. That's why these guys test them. Unfortunately, this forum will not let me post the website. But if you google Bimmer Software, you will find the cables under the Products menu.

[Smonkey09]

Originally Posted by DWR

I forgot to post this a long time ago. There is a source that sells pre-tested cables. They sell logging software, so they have a vested interest in getting good cables to their customers. Just getting the "green" ones isn't always a guarantee. That's why these guys test them. Unfortunately, this forum will not let me post the website. But if you google Bimmer Software, you will find the cables under the Products menu.

If the cable works with EDIABAS, do you think the cable could still be the reason for having issues with INPA?

[DWR]

Originally Posted by Smonkey09

If the cable works with EDIABAS, do you think the cable could still be the reason for having issues with INPA?

Nope. Just wanted to let folks know, in case anyone else was contemplating getting started.

[ingenieur]

Originally Posted by DWR

Not sure what you mean by this. I certainly have had 2 instances of TestO open at the same time. Can you elaborate?

What I meant to suggest is a common error for new users - to open Tool32 for example - and then go and try INPA, NCSexpert, or Test-O without closing Tool32 and Ediabas (ebas32.exe) first.

[pheno]

Actually TestO does not check for used com ports or try to reserve Ediabas during start. It will give 'API-006 ACCESS DENIED' or similar error when trying to run a job IF some other program like Tool32 is open.

[Smonkey09]

Originally Posted by ingenieur

What I meant to suggest is a common error for new users - to open Tool32 for example - and then go and try INPA, NCSexpert, or Test-O without closing Tool32 and Ediabas (ebas32.exe) first.

Well crap. Yes, I was trying to do this. However, it is because when I try to go into INPA without tool32 connected, and I click F1 (Info), I get all "?????????" in the connection info fields. However, when I am connected to the car in tool32 and go to INPA without closing tool32, I see proper connection info (such as "C:\EDIABAS\ECU" instead of "??????????."

[iaknown]

OK guys help me out here......What is the O2 reading parameter in TestO? I thought it was: STAT_LSU_rLam_WERT but I am getting nada.

Also, does Torque read O2 or air/fuel ok for you guys that run it?

[TDIwyse]

Originally Posted by iaknown

OK guys help me out here......What is the O2 reading parameter in TestO? I thought it was: STAT_LSU_rLam_WERT but I am getting nada.

Also, does Torque read O2 or air/fuel ok for you guys that run it?

That's the value I use in TestO, and it agrees well with the data from Torque. Although TestO is giving lambda and Torque converts that into a stoicheometry number.

For instance, when I was tracing down my intermittent O2 sensor issue, when the sensor would get "stuck" at a 14.5 AFR on Torque, TestO would show STAT_LSU_rLam_WERT as being ~1.01xx. With the new O2 sensor once the car warms up a couple mins and at idling/cruising that value will be 2.0 and the Torque AFR will be 29.

At least that's what I'm seeing on my car...

[iaknown]

Originally Posted by TDIwyse

That's the value I use in TestO, and it agrees well with the data from Torque. Although TestO is giving lambda and Torque converts that into a stoicheometry number.

For instance, when I was tracing down my intermittent O2 sensor issue, when the sensor would get "stuck" at a 14.5 AFR on Torque, TestO would show STAT_LSU_rLam_WERT as being ~1.01xx. With the new O2 sensor once the car warms up a couple mins and at idling/cruising that value will be 2.0 and the Torque AFR will be 29.

At least that's what I'm seeing on my car...

Thank you. I had my piggyback tied into the O2 signal and screwed something up. It is disconnected now and I have 0 on everything, lambda, AFR, (TestO and Torque). I really hope I hurt the sensor and not the drivers in the dde. Weird thing is I'm not seeing any codes for the O2 at all...

[TDIwyse]

Originally Posted by iaknown

Thank you. I had my piggyback tied into the O2 signal and screwed something up. It is disconnected now and I have 0 on everything, lambda, AFR, (TestO and Torque). I really hope I hurt the sensor and not the drivers in the dde. Weird thing is I'm not seeing any codes for the O2 at all...

I hope you get your issue sorted out soon. Are you getting any codes?

I'm not entirely sure if the TestO and Torque Lambda/AFR reported values are the actual sensor values, or if it's a calculated value. The way those values snap from 1:1 to something reasonable after ~ 1-2 minutes of driving makes me think it might be a calculated value... However, I've never seen 0's for those.

This is where getting a direct measurement by splicing into the sensor would be beneficial. However, one runs risks by doing this.