[happy4nk8er]

Mine is an 07 with MSD80 and a version of progman 28. Not sure which version, I had one upgrade from the original progman 25. I can't remember if I had the surging with the version 25, cause I did not notice it till sometime after the progman update to 28. Had Procede on throughout both versions of progman.

[Jeller]

Originally Posted by luca335i

Was it an install problem u think. Might as well wait for v4 maps

Double checked everything prior to removing actually just to make sure, nothing found.

Originally Posted by Mr. 5

There are so many variations of programs and DMEs that some engines work fine with the newer maps and some don't.

I agree this completely and its impossible for shiv/vishnu to test, but frustrating for the end user/consumer spending money.

Originally Posted by jpsimon

Everyone with the problem should find out what dme version they have and what software version they have and post about it to see if there are any similarities there.

Where do I get my DME version from? assuming it printer on the actual DME correct?

No way to tell the software without the dealer telling me or having a bav-tech tool correct?


Side note*

I ran this REVII prior to the canbus harness update with no issues. Ever since the can bus harness update/new canbus maps & firmware it has not liked the maps at all. (the canbus was added correctly fyi, I double checked before you say anything lol ) Problem is... I really like the can-bus features

[jpsimon]

all of the issues you folks are having will probably be solved with v4, it's coming soon don't worry!

[cn555ic]

He stated something like New Years for some more beta testers, which is only a couple of days away!!

[Dr_Dirt]

This reminds me of an issue with PID settings, not sure if the proceed uses this mechanism to smooth out hysteresis (overshooting targets)...

[J x K]

darn. this is making me think twice about purchasing a procede.

[Mike@N54Tuning.com]

Originally Posted by Mr. 5

Just for the record, this isn't just happening with the procede maps.
It happened with the JB3 that I had as well.
The N54 is a tricky monster.
There are so many variations of programs and DMEs that some engines work fine with the newer maps and some don't.
I believe these oscilations have to do with models with the older V80 DME.

FWIW this was finally fixed in 1.4, the problem was too much or less of a solenoid duty offset under some conditions. Very much a PID related problem. With 2.0 some additional user fields have been added should BMW make future software changes that require a PID tuning change.

Mike

[Mr. 5]

Originally Posted by Mike@N54Tuning.com

FWIW this was finally fixed in 1.4, the problem was too much or less of a solenoid duty offset under some conditions. Very much a PID related problem. With 2.0 some additional user fields have been added should BMW make future software changes that require a PID tuning change.

Mike

That's good to know. I'm glad it was fixed.

[jpsimon]

Originally Posted by J x K

darn. this is making me think twice about purchasing a procede.

many/most people don't have issues, don't fear! especially with v4 coming up, everything is changing (for the best). the only reason a new v3 map to fix the random issue hasn't come out is because v4 is right on the horizon

[happy4nk8er]

Originally Posted by Dr_Dirt

This reminds me of an issue with PID settings, not sure if the proceed uses this mechanism to smooth out hysteresis (overshooting targets)...

+1
I do tuning on occasion for HVAC system loops and I agree with your statement.

[cn555ic]

Originally Posted by jpsimon

many/most people don't have issues, don't fear! especially with v4 coming up, everything is changing (for the best). the only reason a new v3 map to fix the random issue hasn't come out is because v4 is right on the horizon

I hope he comes out with this already...I hate teasers

[M3EST]

Originally Posted by jpsimon

many/most people don't have issues, don't fear! especially with v4 coming up, everything is changing (for the best). the only reason a new v3 map to fix the random issue hasn't come out is because v4 is right on the horizon

Thats not the point.Shiv stopped developing v3 because he makes v4.A lot of people still have rev1 computers.As he mentioned v4 will run only in rev2 owners because of the canbus based development.He has to fix the v3 oscillation issue for all the rev1 owners who gave him not long ago some good money and they will not be able to use v4.Not fair for these people.By the way i am a rev2 user.