Need help doing vanos test with INPA

[Tomba]

It’s indeed slow. Try to drive it for a while and repeat the test.

[BimmerFan85]

I know this thread is a little old, but would someone be able to give some feedback on these values? It seems my VANOS is a bit slow to adjust on both intake and exhaust. I just finished the entire seals, disk and rattle kit preventative maintenance a couple of days ago. I haven't driven the car yet, just testing in the garage.

Any insight is appreciated.

[avusblue]

^^ those results are fine.

what I did not see are the leak test values. I don’t remember the name of the job, but in this forum there are posted the different jobs including the leak test

I appreciate it, the car seemed to run great and I'm glad I don't have to mess with the timing again.

[maupineda]

^^ those results are fine.

what I did not see are the leak test values. I don’t remember the name of the job, but in this forum there are posted the different jobs including the leak test

[avusblue]

I just ran the test, can someone help me check the results, if it passes the standard or not?

[Tomba]

Thanks Tomba. I appreciate you putting the test file together as that kind of stuff goes way over my head. Nice to have a simple point and click way to do multiple vanos tests. My test is attached below. I still don't really understand the dichtheit test. If, as heinzboehmer suggests, the okay doesn't refer to a pass or fail determination I'm wondering how do you make that determination. Using Tomba's tst file my test indicated, using google translate, that the unit drifted away prematurely for both the intake and exhaust test. Does that mean the vanos actually failed the leak test? When I did the individual dichtheit test it showed my intake had a 4 degree change from the setpoint to the actual value and the exhaust had a 1 degree difference. I guess ideally the setpoint and actual values would be the same but at what point does the difference become a problem and what would that problem be?

Those numbers are perfect. It reached the right end stops and your activation speed is also within specification.

I have added an educational pdf file for BMW VANOS systems to this post. Take a moment to read it as this might clear up your question. Especially if you look the at the hydraulic diagrams.
For instance, on page 46 you can see the hydraulic system of the S50B32 engine. OK not an S54 but hydraulic wise I don't expect much differences.
You can see that the piston to move the shaft has 2 diameter. A small area which is pressurized all the time and the big area that is controlled by 2 valves. Instead off routing the oil fluid from 1 to another side the choice is to release oil or add oil on the bigger side.
Since the "controlled" side is bigger more force will be applied against the other side.

I suspect that the "dichtheid" test sets the camshaft to 1 position and doesn't actuate the control solenoids for a certain amount of time. If you look at the hydraulic diagram no fluid should escape and the position should be maintained under ideal conditions. It might be possible that the seal(s) within the shaft/piston are not sealing perfectly causing oil to escape from one to another "chamber". Another option is that one of the solenoids is not perfectly closed. If you look at the solenoids in the S62 engine (E39 M5) these have filters around them. They tend to break by time and the debris of the filter can get stuck in the solenoid. This will continuously feed oil or release oil fluid. With the "dichtheid" test this can be checked.

For your test, did you do it with hot or cold oil? Cold oil can "seal" more as it is thicker. In your case you could opt to replace the sealing(s) around the shaft(s). I believe this is the easiest. If this doesn't solve the issue one or more solenoids might not seal properly. The S54 has a solenoids block. You can remove it and ultrasonic clean it while "activating" the solenoids with a magnet. I personally wouldn't care to much with the "dichtheid" test as long as the activation time is within <300ms. But if you want to test to pass you could do the things I mentioned.

Hope this clears things a bit up

[boadly]

Thanks Tomba. I appreciate you putting the test file together as that kind of stuff goes way over my head. Nice to have a simple point and click way to do multiple vanos tests. My test is attached below. I still don't really understand the dichtheit test. If, as heinzboehmer suggests, the okay doesn't refer to a pass or fail determination I'm wondering how do you make that determination. Using Tomba's tst file my test indicated, using google translate, that the unit drifted away prematurely for both the intake and exhaust test. Does that mean the vanos actually failed the leak test? When I did the individual dichtheit test it showed my intake had a 4 degree change from the setpoint to the actual value and the exhaust had a 1 degree difference. I guess ideally the setpoint and actual values would be the same but at what point does the difference become a problem and what would that problem be?

[heinzboehmer]

I guess the test has certain built in parameters and when it shows okay it means you are within those parameters. If not, would it say fail or the German equivalent?

I'm pretty sure JOB_STATUS is referring to the routine having been completed successfully (i.e. the program on your computer ran through all the tests it had to perform) and not to the test having passed. If you just want to find an okay or not okay then you probably want to be looking at E/AVAN_STATUS instead. E is for intake and A is for exhaust (comes from the German words).

For example, if you look at AVAN_STATUS from Tomba's bench setup results, it says "AVANOS-1-Einheit vorzeitig weggedriftet". Plugging into Google translate gives "AVANOS-1 unit drifted away prematurely", meaning that the actual position was not inline with the desired position after the allotted amount of time had passed (of course none of this makes sense on a bench setup but you get the point).

[Tomba]

Unzip the attachment,
place it in C:\EDIABAS\ECU
start Tool32
Click the 2nd [OPEN] icon
open MSS54_VANOS_Test.tst
Press F8 to run all tests
A result screen similar to the quoted code text below should appear *tested only with bench set up! Not with a running engine

Test file : C:\EDIABAS\ECU\MSS54_VANOS_TESTS.TST
Start : 18.06.2020 19:57:00.5
Nr 1( 1) : 18.06.2020 19:57:00.6
apiJob("mss54ds0","STEUERN_EVANOS1_FRUEHANSCHLAG", "","")
JOB_STATUS = OKAY
EVAN_ISTWERT = 60 00 3C .<
EVAN_SOLLWERT = 52 00 34 .4
EVAN_ISTWERT_EINH = Grad KW
EVAN_SOLLWERT_EINH = Grad KW
Nr 2( 1) : 18.06.2020 19:57:06.0
apiJob("mss54ds0","STEUERN_EVANOS1_SPAETANSCHLAG", "","")
JOB_STATUS = OKAY
EVAN_ISTWERT = 60 00 3C .<
EVAN_SOLLWERT = 52 00 34 .4
EVAN_ISTWERT_EINH = Grad KW
EVAN_SOLLWERT_EINH = Grad KW
Nr 3( 1) : 18.06.2020 19:57:11.3
apiJob("mss54ds0","STEUERN_EVANOS1_VERSTELLZEIT"," ","")
JOB_STATUS = OKAY
EVAN_VERSTELLZEIT_FRUEH = 0 00 00 ..
EVAN_VERSTELLZEIT_SPAET = 0 00 00 ..
EVAN_VERSTELLZEIT_FRUEH_EINH = ms
EVAN_VERSTELLZEIT_SPAET_EINH = ms
Nr 4( 1) : 18.06.2020 19:57:17.5
apiJob("mss54ds0","STEUERN_EVANOS1_DICHTHEIT",""," ")
JOB_STATUS = OKAY
EVAN_STATUS = EVANOS-1-Einheit vorzeitig weggedriftet
Nr 5( 1) : 18.06.2020 19:57:32.0
apiJob("mss54ds0","STEUERN_AVANOS1_FRUEHANSCHLAG", "","")
JOB_STATUS = OKAY
AVAN_ISTWERT = 0 00 00 ..
AVAN_SOLLWERT = 0 00 00 ..
AVAN_ISTWERT_EINH = Grad KW
AVAN_SOLLWERT_EINH = Grad KW
Nr 6( 1) : 18.06.2020 19:57:37.3
apiJob("mss54ds0","STEUERN_AVANOS1_SPAETANSCHLAG", "","")
JOB_STATUS = OKAY
AVAN_ISTWERT = 0 00 00 ..
AVAN_SOLLWERT = 0 00 00 ..
AVAN_ISTWERT_EINH = Grad KW
AVAN_SOLLWERT_EINH = Grad KW
Nr 7( 1) : 18.06.2020 19:57:42.5
apiJob("mss54ds0","STEUERN_AVANOS1_VERSTELLZEIT"," ","")
JOB_STATUS = OKAY
AVAN_VERSTELLZEIT_FRUEH = 0 00 00 ..
AVAN_VERSTELLZEIT_SPAET = 0 00 00 ..
AVAN_VERSTELLZEIT_FRUEH_EINH = ms
AVAN_VERSTELLZEIT_SPAET_EINH = ms
Nr 8( 1) : 18.06.2020 19:57:48.9
apiJob("mss54ds0","STEUERN_AVANOS1_DICHTHEIT",""," ")
JOB_STATUS = OKAY
AVAN_STATUS = AVANOS-1-Einheit vorzeitig weggedriftet
Stop : 18.06.2020 19:58:03.3
Dauer : 62.9 s

[Tomba]

I was just wondering what the desired result should be. I guess the closer to 45 the better. Don't know what an acceptable range would be. I guess the test has certain built in parameters and when it shows okay it means you are within those parameters. If not, would it say fail or the German equivalent?

The desired result would be that the actual position keeps constant with the desired while not activating the VANOS solenoids. I suspect 1 or 2 degree error is acceptable but I don't know for sure. Just like you said its built in to the program, I suspect the diagnostic tester monitors the actual position and observes the position for xx seconds and based on its actual position after xx seconds decides if its acceptable or not.

[boadly]

I was just wondering what the desired result should be. I guess the closer to 45 the better. Don't know what an acceptable range would be. I guess the test has certain built in parameters and when it shows okay it means you are within those parameters. If not, would it say fail or the German equivalent?

[Tomba]

Thank you. That worked. I really do appreciate it. I've spent way too much time trying to figure out what I thought would be a pretty simple vanos test. It obviously is if you know what you're doing. I've never used Tool32 and didn't even know what it could do. Especially since its in German. I'm assuming there's not an English version?

You can select English from the settings menu I believe, but doubt it will work. The *.prg file might only have german language in it.

I'm pretty much a noob when it comes to these kind of things. I didn't understand what the second and third tests would do so I didn't try those two. I did do the STEUERN_EVANOS1_DICHTHEIT test and is says okay so I guess it passed but I'm not sure what the baseline should be. There were two numbers but I don't know what they represent. One was 40 and the other was 45.

SOLL is Sollwert = desired
IST is Istwert = actual

I believe the camshaft position is moved to 45° from the beginning of the test and then for xx seconds no actuation from the VANOS solenoids is performed to observe if the camshaft angle drifts away. In your case 5°.
Once one of the seals of the VANOS control shaft is worn, oil and thus pressure might escape. This would result in a drift and in my opinion the ECU needs to continuously activate the solenoids to keep its desired position. From OEM perspective this was not how the system was design to be operated.

Do you know how this compares to a typical reading like reaction times should preferably be <300ms?

Sorry I don't know what you mean with this. Please explain it.

I still don't understand if something is wrong with my INPA or if it just has very limited functions for E46 M3's. For example, I'm unable to do the brake bleeding where it activates the ABS and I'm pretty sure it's not operator error. I've searched all over the program and it's just not there on mine. Can anyone else confirm that they are able to do brake bleeding and many other functions with INPA on an E46 M3 that I know people with non M E46's can do?

You might be able to perform such tasks in Tool32 as well. From my understanding BMW makes *.ipo files which are (correct me if I am wrong) generated from *.prg files. *.ipo files can only be handled with INPA -> more user friendly version for the end user over tool32.
If you enter the ABS/DSC module and press F1, F2 or F3 from memory in INPA there should be somewhere listed which *.prg file is used. Let me know and we will look through it.

Unfortunately I am currently not able to create my own *.ipo files otherwise I would implement the VANOS function my self.

[boadly]

I always use Tool32, Seems the ipo file for the M3 was not covered with these functions.
- open (F3) [mss54ds0.prg]
- select [STEUERN_EVANOS1_VERSTELLZEIT]
- hit the [1=>] button on top. Idle speed will be increased and your engine may sound a bit wierd during the operation
- If OK, you will see a time in miliseconds, for EVANOS (Einlas VANOS = intake) I would say reaction time needs to be below <300ms. For exhaust (AVANOS) times may be a bit less as it has a angle to cover <250ms

with, [STEUERN_EVANOS1_FRUEHANSCHLAG] you can force the end points of the VANOS. It will demand for instance 70 degrees while it should do a maximum of 60 +/-2 degrees.
Run [STEUERN_EVANOS1_SPAETANSCHLAG] and it will run the opposite direction. Target -10 while 0 +/-2 degrees should be reached.
Intake 0-60
Exhaust 0-45
with [STEUERN_EVANOS1_DICHTHEIT] you can see if the current position is maintained (leak free).

I can make a *.tst file for you if you prefer that. You just load in that file and run it (F8). It will do things more automatic and prints the results in the Results screen.

Thank you. That worked. I really do appreciate it. I've spent way too much time trying to figure out what I thought would be a pretty simple vanos test. It obviously is if you know what you're doing. I've never used Tool32 and didn't even know what it could do. Especially since its in German. I'm assuming there's not an English version?

I'm pretty much a noob when it comes to these kind of things. I didn't understand what the second and third tests would do so I didn't try those two. I did do the STEUERN_EVANOS1_DICHTHEIT test and is says okay so I guess it passed but I'm not sure what the baseline should be. There were two numbers but I don't know what they represent. One was 40 and the other was 45. Do you know how this compares to a typical reading like reaction times should preferably be <300ms?

I still don't understand if something is wrong with my INPA or if it just has very limited functions for E46 M3's. For example, I'm unable to do the brake bleeding where it activates the ABS and I'm pretty sure it's not operator error. I've searched all over the program and it's just not there on mine. Can anyone else confirm that they are able to do brake bleeding and many other functions with INPA on an E46 M3 that I know people with non M E46's can do?

[Zekarus]

I always use Tool32, Seems the ipo file for the M3 was not covered with these functions.
- open (F3) [mss54ds0.prg]
- select [STEUERN_EVANOS1_VERSTELLZEIT]
- hit the [1=>] button on top. Idle speed will be increased and your engine may sound a bit wierd during the operation
- If OK, you will see a time in miliseconds, for EVANOS (Einlas VANOS = intake) I would say reaction time needs to be below <300ms. For exhaust (AVANOS) times may be a bit less as it has a angle to cover <250ms

with, [STEUERN_EVANOS1_FRUEHANSCHLAG] you can force the end points of the VANOS. It will demand for instance 70 degrees while it should do a maximum of 60 +/-2 degrees.
Run [STEUERN_EVANOS1_SPAETANSCHLAG] and it will run the opposite direction. Target -10 while 0 +/-2 degrees should be reached.
Intake 0-60
Exhaust 0-45
with [STEUERN_EVANOS1_DICHTHEIT] you can see if the current position is maintained (leak free).

I can make a *.tst file for you if you prefer that. You just load in that file and run it (F8). It will do things more automatic and prints the results in the Results screen.

Awesome! Thanks! That file would be great and it would help a lot of people here.

[Tomba]

I always use Tool32, Seems the ipo file for the M3 was not covered with these functions.
- open (F3) [mss54ds0.prg]
- select [STEUERN_EVANOS1_VERSTELLZEIT]
- hit the [1=>] button on top. Idle speed will be increased and your engine may sound a bit wierd during the operation
- If OK, you will see a time in miliseconds, for EVANOS (Einlas VANOS = intake) I would say reaction time needs to be below <300ms. For exhaust (AVANOS) times may be a bit less as it has a angle to cover <250ms

with, [STEUERN_EVANOS1_FRUEHANSCHLAG] you can force the end points of the VANOS. It will demand for instance 70 degrees while it should do a maximum of 60 +/-2 degrees.
Run [STEUERN_EVANOS1_SPAETANSCHLAG] and it will run the opposite direction. Target -10 while 0 +/-2 degrees should be reached.
Intake 0-60
Exhaust 0-45
with [STEUERN_EVANOS1_DICHTHEIT] you can see if the current position is maintained (leak free).

I can make a *.tst file for you if you prefer that. You just load in that file and run it (F8). It will do things more automatic and prints the results in the Results screen.