| Author | Message | ||
     T_man |
I quickly skimmed over this post and have a question: am I correct in understanding that you can determine what air-to-fuel ratio your bike is running at various throttle openings and RPM's with this software and the stock narrow band o2 sensors? No need for wideband o2's? If this is the case... it is great news! | ||
| Xoptimizedrsx |
wide bank make it go quicker to get the results but the NB will do it as well it will just take a little longer that all. | ||
| Xoptimizedrsx |
Fast what is that FX relating to in the 119 offset as IAC setp? percent? I dont see it labeled on my data that way but my data can be incorrect. Where did you pull the FX from for the IAC If you can answer that for us. As its posted this is the beta files so some things need to be tweaked and I will update my download link. If anyone see's an error please let me know. this way the next guy downloading this will get correct data. We are all users of this and the more we share the better. | ||
| Xoptimizedrsx |
(X*1.000000)+(-40.000000) is the temp correction FX. The IAC Setpoint to rpm based on offset cell 119 is X*10.000000 which is active rpm value. In order to fix things I need a tad more info. what exactly are you scaling or wanting to see differently? I did just now do a couple changes to the base file i have posted on the website. I also added a date so people can see if they have a old version or a current file. | ||
| Smoke4ndmears |
thanks fast. 22-110 celsius seems like a much more reasonable operating range. | ||
| Fastcarr |
I actually pulled that conversion function from an older BUE2D .XDF file, one of the first versions. I noticed a month or 2 ago it changed to the current incorrect one. I really wish Gunter would put a version number or date on his .XDF files. | ||
| Xoptimizedrsx |
I was in the ADX file looking at my numbers not the xdf file. My bad... If you notice on a few places I stay in contact with a few guys in the ecm circle and I have a lot of ECM data besides whats posted online in different type of program files. I have posted to make sure you have the latest xdf file as things have changed in those across the board. Especially the BUE2D file. For some reason each time you think its 100% well another thing is spotted. in my current from ecmspy directly the Bue2d file was reading my IAC setpoint in the tables correctly. It is reading as Celsius. you will notice in the datalogs i put it in there at a couple different numbers for the same cell as tracking overall function, its done as 8 bit, Celsius, and rpm. Each one of these functions has a relation to another part of the ecm and what it will do. Kind of like a If this do that function. when I see an issue I get into a panic because probably 75% of the people only download something once and dont check back to see if there is a newer version. you may want to go download all the current XDF files peeps.They are better now. Plus its not far out to a new version of V5 tunerpro.(free) | ||
| Avc8130 |
Mike, I think you have the best idea with adding the date to the file names. This will make it super easy for anyone to make sure they have the newest versions. ac | ||
| Xoptimizedrsx |
As people make up different versions I will host those as well. this will keep it all available for everyone. I can even inlay new settings as new file types per ecm firmware and bike type. what we have so far is the list and one history file set set to one firmware and bike type. what we need is the history files set to each bike and firmware to match rpms and tps. Plus we need to get some screen shots and photo shop these to show others how to adjust the rpms and ect in tables so that it will read correctly if they choose to modify there rpms to keep everything matched. This is still early into the connecting the bikes with tunerpro so we have a ways to go. I add the dates to the downloads area on mine already. Mike | ||
| Jayz |
M1combat - how are you going with that tutorial? Quote "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." | ||
| Xoptimizedrsx |
I sent the PM out on walking him through it. No reply yet... I need feedback on how you guys like this so far please. like feedback on how too's in the tunerpro vs the old systems. | ||
| M1combat |
I need to get the cable  , then build it. The friend never gave it back is the short version of the long story. I have a bike side plug though so that's half the hurdle. | ||
| Avc8130 |
Mike, I have a cable and I would LOVE to start playing around. Send me the PM you sent the other guy and let me see if I can help figure this stuff out for the masses. ac | ||
| Xoptimizedrsx |
sent pm to Avc also. the way I see it the more fingers testing and working with data the better. this is at all levels of tuners. this allows Us to see how exactly easy can we make this. the more simple the better. | ||
| Jayz |
Thanks Avc. I'm happy to provide some input as well when I get my cable and start tweaking my ECM. | ||
| M1combat |
Don't mean to hold up the process or anything ... Just need to get my cable built and I'll be on it. Give me time . If anyone else wants to make the general overview of the process document fire away for sure. I won't take it personally but as soon as I get a cable (maybe late next week or so?) I'll get on it. | ||
| Xoptimizedrsx |
new tunerpro version rt v.5.????? on the verge of release. test version is looking good guys no more xdf and rpm issues. as well as faster working. next hurdle has been leaped linked to the ecms loosely with out being on a bike. heheheeh Mark has ordered a ecm to start some hardcoding work now. some of the adx functions that will be loaded will be locked with passwords and ect to keep them from getting messed up. these are codes and ect and for resetting the TPS. thats all so far as of new stuff pending. | ||
| M1combat |
Just ordered an 895_TTL_232R_5V from mouser... When it gets here I'll make the cable and start the connection document . | ||
| Xoptimizedrsx |
M1? Didnt you get the msg from me for the free cable? I keep about 30-100 on hand at all times on AVG. update new files on server. ddfi1 needed to stand alone Update.. mark has a ddfi2 and ddfi3 ecm currently. now the fun stuff starts. also gunter just posted recently a new xdf ecm type I stumbled into for him a bueod ecm. we will keep moving FWD. the beta release 2 has the xdf stuff corrected but more is still to be added before release. I have two weeks and then it back to school. no more play time. I did accomplish the link this summer with Mark and got all the data inlaid for everyone. hope that start helped. I did a cheesy post on youtube on tunerpro. different computer next time so it will process the recorder for a live connection on the bike. search( tunerpro buell ) (Message edited by xoptimizedrsx on July 24, 2010) | ||
| Jayz |
Nice work Mike. Seeing it on video makes it so much easier | ||
| Stimbrell |
Xoptimizedrsx, Followed your youtube post, problem I have is cable detected and working but when I connect it shows "connecting" but does not and when I check the cable is no longer found. Cable works with V4 and Ecmread. Any thoughts most welcome. Steve. | ||
| S21125r |
Been doing some logging for the past week and here are my observations.... The history tables are very nice but beside the average, you will want to keep an eye on your sample count and your standard deviation. On the tuning side of things I found that in the 2-3K chugging range at 10 TPS 8 bit that my standard deviation is crazy for both front and back cylinders - like 20 % of the average. To put this into perspective it means that 68% of the data points fell into a range of 20% leaner to 20% richer than the average. What's even more scary is that the other 32% of the data points wanted something leaner/richer than 20%... Certainly not like the bell shaped distribution I was looking for. Both MAP sensors seems to be all over the board at that range as well so suspect that veCurr is heavily influenced by the Map values. Seems to me that Highscore started an airbox post a few weeks ago that suggested some weird internal airbox harmonics in this range causing the airbox pressures to fluctuate. Might just have to pull the lid off and run another log to see what it looks like statistically. Oh... One more thing... The first set of logs I gather looked like it wanted to pull a considerable amount of fuel out of the WOT region. Almost as it it's trying to correct it back to Stoic. Any body else do any logging yet? Any interesting observations? | ||
| Jayz |
Stimbrell - I have the same issue. Anyone else experienced this? | ||
| S21125r |
Jayz/Stimbrell, Look under tools | preference | Data Acq tab. Middle/Left of the page click Config Plug-in Component and make sure your com port is set properly. | ||
| Jayz |
Thanks S2112r. That's where I was playing with the settings but I got nothing. I'm using the Prolific driver v2.0.13.130. I can make it work with other applications. | ||
| Xoptimizedrsx |
Jay are you on vista? run under administrator. Then set the com port to the same one in the other programs. (apply)ok what bike year? I did just put up a new ddfi1 and two file. plus you may have a variable data compared to standard using a smaller byte count. some ecms do have this but most dont. easy fix below. Go to communications in the edit adx you will see a set of three communications links to click on. click the middle one. now on the bottom you will see two boxes with numbers. ddfi1 99 ddfi2 103 ddfi3 133. what you do is lower this number in each box till your ecm connects ON THE VERY TWO BOTTOM SPACES... do so by lowering one point at a time in each box at the same time and save. then click the two blue arrows. SR I do not have an 1125 but you can change what parameters are used for the correction in the history table by selecting a different data. do this in the edit. in the adx. I think its a weird sound wave issue in the air-box as well. but, I don't have a ddfi3 bike. | ||
| Jayz |
Hi Mike, My laptop is running XP and I'm definitely running under administrator. The bike is a 2010 1125CR (DDFI3?) and it's a BUE1D ECM. Cheers, Jayz | ||
| Xoptimizedrsx |
tps load in the timing tables. in the xdf change a data in the row under timing. open a timing table. view/edit xdf click it under xdf.(up top) click rows tab click edit button. click edit button again (new window) erase all data type this (X*1) save apply close close timing window open back up and you will see correct numbers to 255. re-pete on other table for timing. mike | ||
| Xoptimizedrsx |
Jay lower that byte count as mentioned in the other post and report back what number it took to connect. | ||
| Jayz |
Success! The magic number is 135. Took me a while as i was working backwards from 133 and got really frustrated when i got to the 80 mark. All I was getting were flashes of "Blue Connected" and "Red Error" at the bottom of Tuner Pro screen. Then i decided to start increasing the numbers and got a solid (blue) connect when I configured the decimal number at 135. These were the steps I took: 1. Run TunerPro v5.00.6356.00. On the splash screen, TunerPro reports no hardware found although cable is connected and functioning. 2. On the menu bar, XDF -> Select XDF. Loaded XDF specific to my ECM (BUE1D). XDF obtained from ecmspy.com 3. On the menu bar, Acquisition -> Load Definition File -> loaded ADX file from Mike (http://xoptiinside.com/downloads). 4. On the menu bar, Tools -> Preferences -> Data Acq./Emulation -> Configure plug-in component (left side of screen) and selected the comm port assigned to my cable. This comm port number can be found by: 4.1 Right click My Computer 4.2 Select Manage 4.3 Select Device Manager on the left window pane 4.4 Expand ports on the right window pane. The comm port number you're looking for is the one labled "USB-to-serial Comm Port" 5. On the menu bar, Acquisition -> Edit Definition 5.1 On the left pane, expand Commands and select "Retrieve Live Data - DDFI 3" 5.2 On the right side of the screen modify Body Size (Dec) and Payload Size (Dec) fields from 133 to 135. Click save at the bottom of page. 6. Click the Acquire Data button (2 blue arrows) I hope this helps |
