apalrd wrote:
I found this forum from the old O5E forum. I'm a controls developer on a university SAE Collegiate Design Series program.
We use 'charge' as our primary engine load and 'pedal load' for driver load. They are treated differently in different parts of the software. We use electronic throttle control, so they are not directly tied together.
........
Welcome.
Hopefully the o5e forum isn't dead yet...just holding on the new HW design.
I was on an FSAE team too many years ago, great project.
What are you guys using for hardware/firmware/Tuner (user interface)?
I'll have to think about what you're doing a bit as it's similar but I think backwards from what I'm doing....but I might not be understanding properly which gets me to the need to think about it.
I'm calculating Mass Air flow and fuel require with the same math you are of course.....but I don't consider that load, I calculate it from the load. Currently load % is MAP/Baro*100, but as John as talking about on an ITB setup I'll most likely need to include TPS in some way because vacuum tends to disappear fast on ITB setups.
Mass for and VE are global, cylinder info (which I haven't added yet) will be local meaning a correcting from the global value. My thought here is its easier to tune the engine then correct the cylinders than it is to tune each cylinder from the beginning, especially when there are 12 cylinders and my expectation after all the flow matching I did is that all 12 will be the same....or so I hope, but cylinder corrections will be available.
I'm not sure about bank correction. In enginelab the bank info is entered directly into Engine Description function and is not available outside that function....so you'd need to enter it twice which opens the door to errors. I can setup a "wizard" that would make them match, but I haven't played with those yet. If I decide to go the path of twin ECUs, then doing banks would work better with ECU1=bank 1. I'll have to see where this goes.
The DBW I haven't done any actual work on yet but the plan is to do basically what you're describing using a tranfer table to convert pedal position to desired TPS....I hadn't thought about tying in MPG or gear selection I guess...maybe.....another thing for me to think about.
I'm sure this will all get much better with time and I'm waiting a bit to see what EngineLab releases for their generic model because I'd like to use as much of their stuff as possible to leverage community work instead of just my own work.