I managed to find some time this weekend to fix/update some things as well as update the carwings skin to use numosk properly. I even threw together a basic eLite skin for the more popular PIDs.
Rather than me just posting a possibly buggy release i'd like to try and do some wider scale testing this time around. So anyone who is interested in testing the newest build send me a PM and I'll send you the new files/directions later today. Any feedback you can give is appreciated.
Note: There will be no installer for the testing, just the old school dll with a .bat to register it.
well I updated the plugin lastnight, and had to set some INI values to something other than 0 - or else I would get a divide by 0 error, makes sense. We'll see what happens when I do a reset tonight, as a trial as I already filled up
I think the overall calculations are better - at least it's showing L100km(mpg) to what I would more expect.
I'll take a look into the other functions after the holiday and report back to see how they're working. Will have to integrate them into my skin to test it out - as I can't use the 'standard' skins on my build.
I'd appreciate it if you could send me a PM with your .ini configuration, as well as what values you had to change from zero to get things to work.
I'm trying to fullproof things as much as possible so the plugin can adapt to an unexpected input instead of just throwing an error.
I like how the trip FE keeps calculating while standing still...
Would there be a way to have some calculations from a standstill? no speed. Like how a factory system does it, based off the RPMs, or is that getting too complicated and specific to each vehicle?
Originally Posted by sargeants
I'm not exactly sure what you mean. Can you be more specific?
Fuel consumption is currently calculated based on the MAF value, whether it is synthetic or real, so that is being calculated while at a standstill. Since you aren't covering any distance while stationary both distance and instant fuel efficiency remain zero.
Is there something else you would like calculated? I'm always open to adding more useful data.
well I know that if I'm parked with the car running the onboard computer is calculating fuel efficiency.
Okay - I guess I just confused myself... the car wouldn't be calculating instant, but overall. So likely if I actually look at things the obdmpg overall should be around equal to the car. Maybe I was thinking of the previous version.
so if you wanted to to add the ability to erase codes, this is what you have to do. i can't code, but i know how this stuff works.
step 1. delete this everywhere it shows up in the plugin code
If bMode = 4 Then
send_to_OBD = False
updatestatus "Won't send mode 4 by design."
2. then write something like this "If bMode = 4 Then"
3. write some codey stuff that does the following things.
3a. pull current sensor values for the Throttle Position sensor. if this value is greater than 0, proceeed to 3b.
if not, use the updatestatus command to say "please have ignition set to run position and engine off". maybe have a popup box or something stating the car has to be in accessory 2 (aka the "run" position) with just a simple "ok" box. then "exit function".
3b. pull current sensor value for engine RPM. if this value is greater than 0, pop up same box described earlier. if value is 0, proceed to step 4.
4. send a mode 4 request. this would probably be
If bMode = 4 Then
send_to_OBD = True
or somehow otherwise send a "04" to the ECU. this erases any codes and turns the light off.
5. either popup box or statusupate saying "codes cleared. engine may run poorly momentarily while ECU recalibrates" or something.
then exit or return to main screen.
the short version of how this all works is a mode 4 request (04) erases all the codes. in order for this to happen, the car has to be in the RUN position with the engine off. when the TPS shows a data value greater than zero, the car is in the run position (or the start position). when the engine RPM shows zero, the car is not running. that's the point when you're supposed to erase codes. otherwise just send a "04" command and it does it all for you.
i can't write code, so please do this for me. thanks.
I'll look into it when the time comes. At the moment I'm just trying to get a solid stable release out the door for everyone to use without some error boxes popping up. Once all that gets squared away I'll start adding extra features if needed.
Just a heads up to those of you doing testing, I haven't forgot about you! I'm still trying to track down the real source of the Error 13, Type Mismatch as I'm unable to reproduce it on my development machine and debugging in the car isn't very practical.
On the plus side there is now a debug function built into the plugin so hopefully when things go wrong the debug log will help me fix them faster. I'm also about 50% done with a configuration app that will let you choose which pids you want to retrieve and how often you want to retrieve them. I still need to add all the supporting code into the plugin though and the type mismatch error hold precedence at the moment.
One thing I've noticed is that if I'm driving for a while, then stop and turn the car off; but keep the carpc on (so from on to aux with the key). The plugin is still calculating even though there's no OBD information. So if you're sitting in the parking lot for a while your fuel usage such will still be calculating. Small thing that's not a real bug. It's still working.
still using the initial test code.