[OpenFlash]

Originally Posted by supracg

I don't thnk there is a knock 'sensor' per say, depending on how much timing is pulled at a given point i believe the PROcede considers whether it is knock or not and then makes timing adjustments

Correct. The Procede monitors actual timing and compares it to the dme's advance setpoint. The difference is considered knock induced ignition trim/retard.

Shiv

[ciomas]

Originally Posted by shiv@vishnu

Yes, very near future

[D.B.S]

Originally Posted by shiv@vishnu

Yes, very near future

Excellent... As I may have to upgrade to an X5 in the next year or two, would love to move the PROcede to it.

Unless I get the X5m... in which case the PROcede may not work... unless you have something in the works for that too...

[OpenFlash]

If it's got a turbo (or two) and it's a BMW, the Procede will work. We can't wait until the new //M engines come out

[TMR]

Can I try this yet!!!!?

[M3_WC]

Originally Posted by shiv@vishnu

If it's got a turbo (or two) and it's a BMW, the Procede will work. We can't wait until the new //M engines come out

What about the new 550i?

[AltecBX]

Shiv, I'm really hoping you start looking into the N63. It has so much potential as it already starts at 407 hp 442 lb-ft. Peak power is at 1750rpm which is 350rpm higher than the N54 & 550rpm higher than the N55. Properly tuned, same way you have the N54, I think you can make this baby into the 550 hp 600 lb-ft beast to compete with the '12 M5 578 hp just like a current Procede N54 competes with a M3. Can you bring down the time it takes to peak power?

Glad you see the future in engine is turbo. Even the '12 Ferrari Enzo will go from a V12 to a V8 twin-turbo setup. The N55 is all about efficiency. Most of us here in the tuning section don't care about that so the N54 suits us just right and would think the N63 is the next step up in twin-turbo technology.


Change the name to BMW M5 Procede

[MKE_M3]

Originally Posted by cn555ic

Adrian. You guys do some good work down under!!!

That's what she said!

[adrian@vishnu]

Originally Posted by vasillalov

Adrian,

In a binary system like PCs, embedded systems like ECUs, etc etc things work this way:

signal passes through gate -> one
no signal through gate -> zero

In a binary system things are either ON or OFF, i.e. there are no gray areas. For an example: lets say someone created database of the IATs of an N54 engine measured every 5 seconds over the period of 4 hours. Lets say you were interested in the following range 60F - 100F. A binary system will select ALL entries from that database that are EXACTLY 60.00 degrees Fahrenheit and all the way to EXACTLY 100.00 degrees fahrenheit.

What about all the measurements that were 59.98 F, or 100.04F. Those are very very close to the above specified range, but the the binary system excluded them. A trully fuzzy system will accommodate those values that are so close to the range as technically they are the same. There are mathematical algorythms that allow you to specify a deviation from the ranges that you are permitted to have.

Also, all binary system follow the Von-Neuman computer architecture where lines of binary code are executed in a top-down fashion. The system has absolutely no idea what it will do in the next step until it actually reaches the next step.

In a fuzzy system, a completely different method is used. All variables and values are preloaded as "facts". A set of rules is then added to manipulate those facts. The system is then started. The way the system runs is by considering ALL rules at the same time. It can, on its own, choose how to organize the facts, choose which facts to eliminate from its facts list and it can on its own extrapolate new facts which are then re-inserted back into the mix.

I won't bother you with any more of this since fuzzy logic and fuzzy programming is an advanced topic in artificial intelligence. A lot of serious work has been done in this field from DARPA, MIT, MOTOROLA and a whole lot of universities and research centers.

In the end, the consensus of all the Ph.D's in the world is that a truly "fuzzy" system is not possible in a computer system based on the von-Neumann's architecture. It simply is not.

So, if I were you, I'd be very careful when making claims about an embedded computer product that contains "fuzzy" logic. You must understand that some of us here on this forum are also engineers and bright minds and we are not easily fooled.

Wow... never knew what I was getting into!! As stated by Shiv, he never made any claims of fuzzy logic, and neither did I. We have a complex control system that is more than up to the job, and I will leave it at that.

I only responded as I thought it amusing, and I initially assumed it was someone who had read a paragraph on wiki and then was claiming expertise which seems to happen alot around here with some members. However I see your issue is more of semantics of fuzzy logic. I am not going to get into a debate with you, but I will say that I have done fuzzy logic control systems before in binary systems. Binary systems have some quantisation error, but that does not stop them from using fuzzy logic theory withing the limits of quantisation, and modern binary systems have plenty of power (to process many more bits than single bit) to deliver more than enough resolution for great results in the applications I have done.

Anyway, we can argue over bits and bytes, but at the end of the day, the Procede has more than enough capability to do the things we do on the N54 platform. In time people will see that Procede only ever had one minor packaging upgrade from day 1, and there will be many upgrades as our competition reach their capacity with their systems.

That is a great experiment on the dyno Shiv, and really shows how CPS ignition control does make a difference. If it did not, the Procede would not maintain the same agression level with different fuels.

Cheers,

Adrian

[e.n335]

Originally Posted by vasillalov

Adrian,

In a binary system like PCs, embedded systems like ECUs, etc etc things work this way:

signal passes through gate -> one
no signal through gate -> zero

In a binary system things are either ON or OFF, i.e. there are no gray areas. For an example: lets say someone created database of the IATs of an N54 engine measured every 5 seconds over the period of 4 hours. Lets say you were interested in the following range 60F - 100F. A binary system will select ALL entries from that database that are EXACTLY 60.00 degrees Fahrenheit and all the way to EXACTLY 100.00 degrees fahrenheit.

What about all the measurements that were 59.98 F, or 100.04F. Those are very very close to the above specified range, but the the binary system excluded them. A trully fuzzy system will accommodate those values that are so close to the range as technically they are the same. There are mathematical algorythms that allow you to specify a deviation from the ranges that you are permitted to have.

Also, all binary system follow the Von-Neuman computer architecture where lines of binary code are executed in a top-down fashion. The system has absolutely no idea what it will do in the next step until it actually reaches the next step.

In a fuzzy system, a completely different method is used. All variables and values are preloaded as "facts". A set of rules is then added to manipulate those facts. The system is then started. The way the system runs is by considering ALL rules at the same time. It can, on its own, choose how to organize the facts, choose which facts to eliminate from its facts list and it can on its own extrapolate new facts which are then re-inserted back into the mix.

I won't bother you with any more of this since fuzzy logic and fuzzy programming is an advanced topic in artificial intelligence. A lot of serious work has been done in this field from DARPA, MIT, MOTOROLA and a whole lot of universities and research centers.

In the end, the consensus of all the Ph.D's in the world is that a truly "fuzzy" system is not possible in a computer system based on the von-Neumann's architecture. It simply is not.

So, if I were you, I'd be very careful when making claims about an embedded computer product that contains "fuzzy" logic. You must understand that some of us here on this forum are also engineers and bright minds and we are not easily fooled.

Would bright minds argue like this ? This is not a fuzzy logic discussion platform, IMO.

Eugen

[vasillalov]

Ok, Ok, I admit: I got caught up in semantics here.

[Jeff@TopGearSolutions]

Another thread, greatly off topic...

[hun77777]

all i want is new map and new firware... send it on my way RIGHT NOW!!!!

[OneFastE92]

Originally Posted by shiv@vishnu

.

...You'll also notice 2 new datalogging channels for wideband lambda bank1 and bank2...

Cheers,
Shiv

What O2 sensor is it using to read this? How accurate is this in measuring actual AFR? I have an Innovate LC-1 Wideband setup. Also, let say it's not the most accurate. The LC-1 has a 5v analog output that can go to a datalogger (would there be a wire that we could tap into in the Procede harness). The end user would def. have to get a bung welded in their exhaust, but should be very accurate for real time and data logging purposes, might be best for those running nitrous.

[lamia2super]

Originally Posted by hun77777

all i want is new map and new firware... send it on my way RIGHT NOW!!!!

+1

[dcorn]

So lets say after you do your pulls and the car autotunes itself up to peak power, then you go about driving normally for a while, does it autotune itself back to a lower power setting? If someone pulls up to you on the highway, are you going to have to tell him to do 3-4 races and only the last one counts? Is the new BMW ricer excuse going to be "my autotune didn't get enough time to fully work"?


Oh, and with all the autotune discussion, have you gotten any trademark flak from T-pain?

[Pry]

Why would it autotune to a lower power in normal driving?
At the moment it does just the opposite.
Shiv said that this false learning will be fixed so it won't autotune to overly aggressive settings in normal city driving. So it'll keep the settings it made with the pulls.

[stealth-twntrbo]

The procede is going to tune its self to the target agression level, even during normal driving the peak power settings will stay the same unless conditions change and you go full throttle and knock is induced then it will adjust the settings to the selected agression level. So with normal daily driving its not going to detune its self.

[A4rings]

when is this gonna be available?

[supradriver]

Shiv, did you get a chance to finish up the wiring diagram so the rest of us can wire our bottles up to the procede?

[OpenFlash]

Hi guys.. been busy with the new updates I hope to release tomorrow to the beta group mailing list. Just need to do some 6AT testing tomorrow morning first. A few days after that, I'll post it on the forum publicly.

WHAT'S NEW:
1) Ignition Correction AND Boost AutoTuning is now active
2) Revised fuel pressure mapping (should resolve the hiccup at cruise that some cars experienced)
3) Revised conditionals for AutoTuning. Will prevent the false learning that occurred during light load conditions.
4) Ability to enable/disable AutoTuning functionality in both map1 and map2.
5) Ability to adjust base wastegate position during idle and light load conditions in order to minimize wastegate rattle.
6) Gear compensation for AutoTuning.
7) New logging channels: CAN DME Lambda bank1 and CAN DME Lambda bank2 (from front wideband o2 sensors)
8) Revised warm-up compensations for boost limiting.


After this is out, i'll get back to nitrous documentation as well as a little announcement on the n55

Cheers,
shiv

[ridin135]

Sounds good shiv, will auto tunning adjust boost and timing on map 2 when running methonal?