Boost Compensation - Possible Implementation
Originally Posted by Evo23IG
Is Shiv incorperating this into the new stuff he is working on or does he atleast approve of it? Is this something we get from you or Vishnu?
Originally Posted by Donour
PPS- What input are you using now for MAP? I want to add it to pyxede. I just realized it's been 5 months since the last version and there's lots of features in the development branch that nobody has even seen.
Originally Posted by Ludikraut
Sign me up for one .
Originally Posted by freedom
Also PM your email address and I'll send the manual. I would like feedback...

PM sent.
l8r)
I would be interested in one as well. temp's here vary from 30 deg. in the winter to 105 on a hot day in the summer, and I only want the lc, not interested in the nls feature. looks to be a great product.
bump... updates?
Also, after reading through this thread again... if you have boost compensation, how do you actually set your boost? How does the Xede know what to do with the PWM input? I don't fully understand the logic behind this. Does the box have a memory of what the boost was the day you installed it, and it will output offsets from that point on when the weather changes?
Also, after reading through this thread again... if you have boost compensation, how do you actually set your boost? How does the Xede know what to do with the PWM input? I don't fully understand the logic behind this. Does the box have a memory of what the boost was the day you installed it, and it will output offsets from that point on when the weather changes?
PM me your email address and I'll send you the full manual as it is too large to attach here.
I attached the explanation of how the module works with the Xede for boost comp. Sorry for the four zip's pdf pages, but that is the only way I could get them to post given the size limit of 100k per file.
I think that the manual pages should be helpful, but I'll give direct feedback here.
Boost is still set by modifying the normal smart boost map. The module only compensates for environmental changes such that what is in the boost map applies for any temp, etc. I wanted to hold on to as much of the Xede's way of doing things to make things easy for people.
The PWM input is just another input for the Xede which to the user is represented as a value between 0 and 100 percent. Instead of a voltage, pwm represents the value as the percent of time that the signal is at 5v versus 0v. Thus if the pwm input to the Xede is 0v all the time, the pwm value is 0%. If the signal is 0v for say 1 second and 5v for 1 second, then the pwm value is 50%. And so on. Note that the time periods quoted are only an example. The real numbers are much smaller. Also note that the period of time is doesn't matter, only the ratio.
There is no memory in the implementation. I wanted to keep the thing as simple as possible. Basically the offsets are from the baseline map. In the attached pages are offsets are for a map that is baselined for ~70F. In other words it should work for the maps which Vishnu has on their web site.
And the update question... I built up ten units plus extras and they have been sitting around for several weeks. Shiv and I talked about selling them through Vishnu several weeks ago, but we haven't touched base given everything that has been going on (e.g. I got busy and he went on a trip.)
I attached the explanation of how the module works with the Xede for boost comp. Sorry for the four zip's pdf pages, but that is the only way I could get them to post given the size limit of 100k per file.
I think that the manual pages should be helpful, but I'll give direct feedback here.
Boost is still set by modifying the normal smart boost map. The module only compensates for environmental changes such that what is in the boost map applies for any temp, etc. I wanted to hold on to as much of the Xede's way of doing things to make things easy for people.
The PWM input is just another input for the Xede which to the user is represented as a value between 0 and 100 percent. Instead of a voltage, pwm represents the value as the percent of time that the signal is at 5v versus 0v. Thus if the pwm input to the Xede is 0v all the time, the pwm value is 0%. If the signal is 0v for say 1 second and 5v for 1 second, then the pwm value is 50%. And so on. Note that the time periods quoted are only an example. The real numbers are much smaller. Also note that the period of time is doesn't matter, only the ratio.
There is no memory in the implementation. I wanted to keep the thing as simple as possible. Basically the offsets are from the baseline map. In the attached pages are offsets are for a map that is baselined for ~70F. In other words it should work for the maps which Vishnu has on their web site.
And the update question... I built up ten units plus extras and they have been sitting around for several weeks. Shiv and I talked about selling them through Vishnu several weeks ago, but we haven't touched base given everything that has been going on (e.g. I got busy and he went on a trip.)
Originally Posted by SuperHatch
bump... updates?
Also, after reading through this thread again... if you have boost compensation, how do you actually set your boost? How does the Xede know what to do with the PWM input? I don't fully understand the logic behind this. Does the box have a memory of what the boost was the day you installed it, and it will output offsets from that point on when the weather changes?
Also, after reading through this thread again... if you have boost compensation, how do you actually set your boost? How does the Xede know what to do with the PWM input? I don't fully understand the logic behind this. Does the box have a memory of what the boost was the day you installed it, and it will output offsets from that point on when the weather changes?
While I understand how it should work, I'm still not sure HOW it works.
The SMART boost table is simply solenoid duty cycly in a table of RPM vrs. load. Your box shoots for a target load at each RPM rather than a target solenoid duty. I don't know, I need time to digest this and try to sort it out before I post more stuff that really probably makes no sense.
The SMART boost table is simply solenoid duty cycly in a table of RPM vrs. load. Your box shoots for a target load at each RPM rather than a target solenoid duty. I don't know, I need time to digest this and try to sort it out before I post more stuff that really probably makes no sense.
The box modifies the solenoid duty cycle as a function of the measured environmental conditions. And it does that by applying different scaling factors from a table where the scaling factor is chosen based upon the measured temp/pressure values.
Originally Posted by SuperHatch
While I understand how it should work, I'm still not sure HOW it works.
The SMART boost table is simply solenoid duty cycly in a table of RPM vrs. load. Your box shoots for a target load at each RPM rather than a target solenoid duty. I don't know, I need time to digest this and try to sort it out before I post more stuff that really probably makes no sense.
The SMART boost table is simply solenoid duty cycly in a table of RPM vrs. load. Your box shoots for a target load at each RPM rather than a target solenoid duty. I don't know, I need time to digest this and try to sort it out before I post more stuff that really probably makes no sense.
God. Just Finished reading this whole thing. Absolutly amazing work.
I can tinker around with computers & software all day long (programmer). But I really want to know how to make my stuff have stuff happen in the real world.
Somebody teach me! (aka freedom!)
I can tinker around with computers & software all day long (programmer). But I really want to know how to make my stuff have stuff happen in the real world.
Somebody teach me! (aka freedom!)
A quick update on this project. In short I'm stll trying to find a way of selling these modules in a manner that doesn't require paying the site for vendor status at a rate where the fee exceeds the profits on the module.


