| Author | Message | ||
     S21125r |
I figured out why my RPM range was screwed up in version 5... Took some screen shots from v4 and compared them to v5 for some of the table settings. This is what worked for me - individual results may vary: - Right click on your fuel table map in the parameter tree and select "Edit Parameter XDF info" - Once the edit interface pops up click on the "Column" tab, and tick the box "LSB first" I haven't a clue what the hell this is, but it was the only difference between v4 and v5 that I could see, and by having it checked it did fix my RPM scale in V5. | ||
| Xoptimizedrsx |
its alread posted its the beta on the eeprom side. thats still out of order. see above. the new beta is not released to the public yet and has that fixed. just use the v5 to run the datalogs that side of it is correct. use the v4 for the eeprom xpr/xdf files till posted or you get an update available from tunerpro. I believe all we have out of line in the v5 is the rpms in the tables on the buell ecm/xpr/xdf. (its fixed but not released just yet on a new build) it has more to be put in it still. Hope this helps... we are working hard to get you guys something as an all in one program. mike | ||
| Xoptimizedrsx |
s2 I will FWD that fix(rpm xdf) to Mark(Tunerpro owner) to see if its a correct thing to do or not. He always gets back same day so I should have an answer soon. I do know the adx is correctly labeled now. I just need to corralate it to match the MLV and thats the last it needs in that dept. next the historgrams need to be built for each ecm type/bike type so the tps and rpm values match. it edits the same way. Have fun with the tool... new tool coming soon with more fixes and ect to the public. | ||
| M1combat |
I'm assuming we should use DDFI1 for the DDFI2 bikes? | ||
| Smoke4ndmears |
mike, minor thing, but could you put in a request to have the 3d maps flipped for the timing tables? | ||
| S21125r |
Smoke - not sure if this is what you are referring to but I did see a configuration setting under preference where you can flip both columns and rows. My fuel maps came in with full throttle high rpm at the bottom left so I flipped column and row to put it top right. | ||
| Xoptimizedrsx |
this is the joy of this setup going beta. its allowing all of us to slowly improve the setups. the next release of the tunerpro has changes that are allowing many new things. use the edit to flip the columns to your liking. as thing go we will eventually get uploads and a circle of guys improving this to upload to one central server for everyone. I am so glad to see more involved in locating things and posting for everyone. I can only do so much alone. especially since i dont have a ddfi3 bike. The ddfi1 and ddfi2 uses the same adx file. I have not sat down to hand mark off every offset to be 100% on that one yet. I also have not started the history table based on actual Injector fuel for suggested values to run over current map numbers from the datalog. as you guys are already seeing this setup is much better. load a rides datalog then open the fuel maps. next load the datalog and run it with the history open. now look at these numbers compared to the actual fuel map. it will add some here and remove some there. this is the actual injected value in the history. use the avg setting on this. like I said this is going to be the biggest break through by far. Glad you guys like it so far... | ||
| Xoptimizedrsx |
M1 use the ddfi 1 file it will save as ddfi1 &ddfi2. Its a beta to view whats going to happen. let me verify every offset before you trust it 100%. The offsets have been verified in the ddfi3.. | ||
| Xoptimizedrsx |
I will verify this tonight and post a new ddfi 1 & 2 tonight. | ||
| Xoptimizedrsx |
done verified the offsets and built the history tables to see what the injectors are putting down the TB per cylinder. Loaded to the server now. Its free to download. use this and build to it. To fix the rpms visual readings in the actual xpr/bin maps read above post. (Message edited by xoptimizedrsx on July 11, 2010) (Message edited by xoptimizedrsx on July 11, 2010) | ||
| Xoptimizedrsx |
all newer versions will continue to be posted but it will be at the server side of things from this point. | ||
| Curve_carver |
I was playing with my calibration and I could not find the area that disables the 02s . I currently unplugged mine for now and added a little fuel with the afv areas. It definately smoothed the bike out to the point where chugging at 2700 wasn't so chuggy anymore. Very smooth. Can anyone point out what area/ function that disables the o2s. Thanks for your hard work. | ||
| Smoke4ndmears |
s2115r -moving the columns around unfortunately does not affect how the 3d map is displayed. curve -set the 'closed loop feature minumum rpm' outside of the bikes rev range. | ||
| Curve_carver |
Isn't there a minimum rpm to enter and max rpm to exit .I would think I would have to set both outside the max rpm on the bike. Does this sound right? (Message edited by Curve_carver on July 11, 2010) | ||
| Smoke4ndmears |
just think about it for a second  | ||
| Smoke4ndmears |
and i figured out how to swap the timing table around in the graph by switching the xdf data per respective x/y axis. going to have to re transcribe the entire cell data tho  | ||
| Xoptimizedrsx |
there is no need to disable the o2's program the value to run at the desired afr. the O2 is just a report tool the ecm is what uses the values. the respected best arf set in the ecm is well within the usable range of the O2. If you look at the logs in the history and open data. compare the history log to the actual map. we already have improved the bikes a lot by using the data provided by the tunerpro history avg based on the ve and ect. as you guys see the tunerpro allows you to adjust everything to your need once the main files were loaded. This is the glory on this software and why i pushed so hard to get all data in xdf and adx into it as a base starting point. as xdfs are remade and adx's added to we can load to a file for anyone to host as per ecm firmware and bike type. I will gladly load these to the website for everyone for free once the files are adjusted. Please note the Tunerpro is going to release a update so the xdf data currently will read differently once this goes public. anyone running datalogs yet? if so the historygraph page it is your friend. look at the setup as per data. The x/y can be adjusted to your ecm type rpm's and tps values. just save as a new file once adjusted... How do you guys like this stuff now compared to what use to be available for the Bikes? | ||
| Xoptimizedrsx |
curve tunr them on and use the history graph to see what the datalog ride is saying should be in the cells. there is a front and rear map on this. now compare this history run to the actual map and make changes . re-ride for a few mins then redatalog and see what its doing then. I did this test... i have dual widebands with afr xd16 gauges. if i set the afr front cyl and rear cyl almost exactly the same the bike is smooth at low afr (13.0) to high afr (15.7). If I set one cylinder differently by 1 afr or more the bike chugs. I did this test on three different ECM'S (firmware) If you do this check you will find the same results. overall its not a lean surge its a imbalanced afr between cylinders. because i can run very lean and still be smooth as long as its balanced. high afr is just less power. so stage the ecm map tables. you can do this with tunerpro where you cant with other systems. my cruise afr is 15.5 where my openloop hits 13.2 and wot hit 13.0 on demand. i now get 62 mpg while retaining max hp/TQ when needed. you dont need max hp/tq at no load cruise you can run a lower afr. fuel at 14.7 burns the hottest and above that to 16.0 its cooler above 16.0 getting hotter again. below 14.7 it cooler. all of this is in the weather conditions and fueling post.http://www.hotrod.com/techarticles/engine/hrdp_040 6_density_altitude_tuning/index.html | ||
| M1combat |
So as long as we tune the defined closed loop area to 14.7 (with a stock O2), we can tune everything else where we want it AND retain AFV functionality right? This is important to me as I live in a mountainous area. One road I like takes me from about 1500' ASL to about 6000'ASL. (Message edited by m1combat on July 12, 2010) | ||
| M1combat |
So lemme see if I have this straight ... Hook TunerPro to the bike and start a data log. Go ride, and save the log. Use ECM Read to grab the ECM data (maps etc). Plug both of those into mlv, make sure you like where your AFR's are set in MLV and let it do it's magic to the fuel maps. Aside from grabbing more data in the log... Is there a benefit to doing it this way as opposed to using ECM Spy for the logging? | ||
| S21125r |
I Frogged around for a few minutes before work this morning, but was unable to make a connection between Tuner Pro and the ECM. Tried Spy and Read and had a com error as well, although I have pulled an xpr off before this. So looks like I'll have to spend some time getting my ports straightened around before I try Tuner Pro direct again. Anybody else have success? | ||
| Xoptimizedrsx |
not in MLV. The history table in tunerpro. you can do this with MLV but you dont have the MSQ program yet to make those map files. I have that program but Have not released it yet. It will be free as well. on connecting to tunerpro it will read hardware not found thats ok. Thats a emulator side not used in the buell ecm. load your adx file. then click the two blue arrows. from there you wil see the middle of the screen say connected. if its not click tools,then preferences. on the left side click the bottom box. set your comport to the value used in any other program for the bike. now click save or Ok. now click the two blue arrows. it will connect. used the dash button to see gauges. right click any gauge to select a different value. use the data to see all data. use the history to see a running history. click acquisition and record to record the log. to run or save as a file for MLV you have to export this log as a csv file. then delete row 3 and add a name to the A,2 cell. Note all values are not names ad MLV data names so some things are not read. but most are done. I dont use the MLV any longer I am doing everything in tunerpro and with ecmread. its got plenty power to handle all your needs. If needed I need to do a viedo screen capture to show how to do this with a mic on I guess. I need to locate a screen capture program to save the run as a file. remember to set the laptop to do nothing when closing the lid or it shuts off. mike | ||
| M1combat |
So Tuner Pro will adjust maps for you based on your chosen VE tables and the data it gets from the O2 in the log? Like what MLV does? If we can talk on the phone for a bit (after I re-make a cable that I let a friend borrow... long story) and if you'll walk me through the steps you've found work well I'd be HAPPY to write a basic tutorial on how to operate the software. Tuning itself should be left to reading the tuning guide V2, but I'd be happy to throw something together to get people hooked up and headed in the right direction. | ||
| Blk09r |
M1combat, that would be great. I'm still trying to figure out how this all works. | ||
| Avc8130 |
M1combat, That would be totally awesome! ac | ||
| Smoke4ndmears |
just to clarify a question i have mike -the setup you are running is that your bike has the stock narrow band switches/sensors in the original locations and you have dual widebands plugged in further downstream in the headers. you are letting the bike sort out its closed loop region and separately logging/tuning the wideband output in the open loop region? | ||
| Xoptimizedrsx |
I am tuning the whole thing. I have ran the NB and the wb. I do adjust my NB voltage to a lower point afr on race bikes and actually leaner on street bikes for more MPG. you now have the tunerpro and have the power to set the ecm this way also. much easier than any other system that was produced before. My widebands are downstream just to verify the afr. I log off the NB output of the lc1 feed directly to the ecm. if i switch the WB to the front O2 I just flip a switch and it then feeds the Nb output of the O2 into the ecm. The openloop area is based on settings not in the map alone but many sensor and data feed backs. over time the adjustments made on the bike with the WB and dyno/mlv (oldway) took a while. now with the new systen i can start with a stock ecm and stock map and be done in a few hours. from what i did on the dyno and many datalogs with the old system verifying it on the dash gauges its accurate. and now with this way its getting the same results. so to do this with the Nb or wb its actually very accurate. More accurate with wb reception feed to nb dataline but not actually needed on the newer bikes because you have many other sensors coming into play to make the finale vecorr1/2 values which is what the history graph is based on independently. I have tuned this thing many ways to get one final answer balanced closedloop area afr rich or lean is smooth. (set O2 target voltage .6 to .4 max with NB) and with wb only. the end maps set to the afr of choice gives me the aprox same fuel table depending on weather conditions. M1 PM me I'll give you a buzz. | ||
| Smoke4ndmears |
got it. btw i think the xdf definition for the IAC setpoint map is not correct. its a celsius/voltage axis but the celsius numbers are three to four digits. | ||
| Xoptimizedrsx |
it could need a set point correction offset to convert the number. do you have my last file? i did find a few changes in that its on my server. free to down load. a new version of tunerpro v5 is about ready also. it will use the current xdf from ecmspy as a good file. no having to make all those lsb first changes. plus a few other changes for us. all buell data is LSB first. Mark has started the script to read the ecm and write to it. so its not too far out we will have a all in one program. I have to test the read write section on spare ecms at first... No need in frying a unit i use. once written and fetched with new data i have to run good old compare differences in tunerpro and in Excel to see if the changes are locked and true. if all three of my ecms are good then we test the 2008 up stuff. I have a couple test bikes working with me in the IT field to help do this section to speed things up. Gotta love computer geeks...I want to be one one day... Mike | ||
| Fastcarr |
The correct formula for the Rows->Conversion for Idle Air Control Setpoint Map is (X*1.000000)+(-40.000000) |
