[Tonybest]

Originally Posted by kenneth

Anybody can help with this datalogging?

I can help... am I the one that provides the pencil and the pad to log the data?

[Pseudo Nim]

Originally Posted by Tonybest

I can help... am I the one that provides the pencil and the pad to log the data?

No - you're clearly the one that provides creativity and sharp wit. :P

[kenneth]

Originally Posted by Tonybest

I can help... am I the one that provides the pencil and the pad to log the data?

Thanks Antoine, I can always count on you

However, I tried logging this morning and the data is there, but the procede reader says it cannot access the data, WTF. So I will need to get the data logging reader to work first, Arrrgh!

Glen any idea why I get this message?

What I have been abe to see, is that Wastegate DC is 60% and error code is 11727, in hex language is 2DCF

I'll go ask on the Technical forum.

[Pseudo Nim]

Originally Posted by kenneth

Thanks Antoine, I can always count on you

However, I tried logging this morning and the data is there, but the procede reader says it cannot access the data, WTF. So I will need to get the data logging reader to work first, Arrrgh!

Glen any idea why I get this message?

What I have been abe to see, is that Wastegate DC is 60% and error code is 11727, in hex language is 2DCF

I'll go ask on the Technical forum.

I don't think 2DCF in and of itself is a concerning error.

I'm glad you have a Procede (I thought you had the JB junk). Try this: just run the engine with the laptop plugged in and look at the column for error codes: don't need to datalog, IF there is an error code it will show it intermittently.

I suggest turning off the code clear function of the Procede for the time being (you may throw a cat code if you're catless, but that's ok). Also, don't bother datalogging. What you need to do is just view the error codes for the time being.

[kenneth]

Originally Posted by Pseudo Nim

I don't think 2DCF in and of itself is a concerning error.

I'm glad you have a Procede (I thought you had the JB junk). Try this: just run the engine with the laptop plugged in and look at the column for error codes: don't need to datalog, IF there is an error code it will show it intermittently.

I suggest turning off the code clear function of the Procede for the time being (you may throw a cat code if you're catless, but that's ok). Also, don't bother datalogging. What you need to do is just view the error codes for the time being.

Thanks for your comments. However, I would like to be able to actually datalog doing full throttle accelerations through 2,3,4th gear, this way I can know for sure if it is a boost issue or not. If everything is working properly, I should be able to show a nice boost curve (with/without taper).

So do you know how to get the datalogging to work? It is recording, but not able to open it so I can see the graphs!

[Pseudo Nim]

Originally Posted by kenneth

Thanks for your comments. However, I would like to be able to actually datalog doing full throttle accelerations through 2,3,4th gear, this way I can know for sure if it is a boost issue or not. If everything is working properly, I should be able to show a nice boost curve (with/without taper).

So do you know how to get the datalogging to work? It is recording, but not able to open it so I can see the graphs!

Not in front of PC now but you're looking for "Vishnu Analysis". I can't remember if it was a separate program or a menu option within the Vishnu tool. Can you look? Or are you saying the log viewer doesn't work?

[kenneth]

ok, here is a prt screen. It's when you press View datalog

[jin.patrick]

I saw a lady driving a Laguna Seca Blue M3 today....
the car looked familiar

[Pseudo Nim]

Originally Posted by kenneth

ok, here is a prt screen. It's when you press View datalog

Aieee I completely forgot about this. sori sori!!! what happens when you go to view data log?

[kenneth]

Originally Posted by Pseudo Nim

Aieee I completely forgot about this. sori sori!!! what happens when you go to view data log?

As of today, I can datalog. Another member sent me on the right track I needed to create a data folder within the subdirectory where the program is. Datalogs are actually excel files. Before that I guess it wanted to save to a folder that did not exist!!!

Now when I press view datalog, it does nothing! I can always graph using excel functions though!

[kenneth]

No more boost issues!

[Pseudo Nim]

Originally Posted by kenneth

No more boost issues!

details!!

[kenneth]

Checked everything with BT, cleared a few codes, used analog boost gauge, everything is fine, thank god. Seb is great. Using the Procede highjack of gauge is definitely not accurate to read boost.

At LCMT some user error was made, such as driving on Map 2 first session on wet with all nannies off. After sliding around a few laps engaged nannies and accidentlly switched to Map 3 (0 boost Map)

Did not notice for next session (wet) and first afternoon session (first dry session). When 2nd afternoon dry session came by, everyone was flying by me!

Last session, I made sure I was in Map 1 (12 psi) but that lasted a good 8 minutes LOL!

We tried all maps today, and confirmed the slow feel was really the no boost map!

The thing is I did not even remember there was a 3rd map, until I went to read the manual again.

Brain Fart, as they say, not too proud. Okay? is that enough details?

[GewoW]

Originally Posted by Shibalnoma

I saw a lady driving a Laguna Seca Blue M3 today....
the car looked familiar

[kenneth]

http://www.ecstuning.com/BMW-E90-335...012/ES2594189/

What you guys think, for me?

[Pseudo Nim]

Originally Posted by kenneth

http://www.ecstuning.com/BMW-E90-335...012/ES2594189/

What you guys think, for me?

Get the cool electronic one! The one that goes in the left vent.

[kenneth]

Originally Posted by Pseudo Nim

Get the cool electronic one! The one that goes in the left vent.

No! I am newly impressed with the visual precision of an Analog gauge with needle. digital numbers moving is not easy on the eyes.

Any suggestion of those type of gauges, size, placement etc?

[Pseudo Nim]

Originally Posted by kenneth

No! I am newly impressed with the visual precision of an Analog gauge with needle. digital numbers moving is not easy on the eyes.

Any suggestion of those type of gauges, size, placement etc?

bah you're just impressed because seb used one.

stay off it for a week or two. you will change your mind.

[kenneth]

Originally Posted by Pseudo Nim

bah you're just impressed because seb used one.

stay off it for a week or two. you will change your mind.

ha ha! you would have been impressed too. Big 4-5 inch dial = Surgical.....

[Pseudo Nim]

Originally Posted by kenneth

ha ha! you would have been impressed too. Big 4-5 inch dial = Surgical.....

for diagnosis, totally agree. but for driving, those things look awful

[kenneth]

Originally Posted by Pseudo Nim

for diagnosis, totally agree. but for driving, those things look awful

Well then I am looking more for diagnosis than driving, so don't mind awful ...

[jgalaxy]

Originally Posted by kenneth

Checked everything with BT, cleared a few codes, used analog boost gauge, everything is fine, thank god. Seb is great. Using the Procede highjack of gauge is definitely not accurate to read boost.

At LCMT some user error was made, such as driving on Map 2 first session on wet with all nannies off. After sliding around a few laps engaged nannies and accidentlly switched to Map 3 (0 boost Map)

Did not notice for next session (wet) and first afternoon session (first dry session). When 2nd afternoon dry session came by, everyone was flying by me!

Last session, I made sure I was in Map 1 (12 psi) but that lasted a good 8 minutes LOL!

We tried all maps today, and confirmed the slow feel was really the no boost map!

The thing is I did not even remember there was a 3rd map, until I went to read the manual again.

Brain Fart, as they say, not too proud. Okay? is that enough details?

All is well that ends well. A simple test against the zero map and then with a boost gauge will always tell the tale. I'm glad that it was just a simple error.