| Author | Message | ||
     Sagehawk |
I wanted to ask the board if out of all the tps resets done and the few times the afv has been reset to 100, has anyone rode their bike to reset the afv for some time and distance to recheck and find the afv still at 100 exactly as set? I've been doing the square idle thing and had a 105.3 afv. With a tps reset, setting tps for the square idle, set afv to 100 and watching the ego at idle which now bounces 98.5 - 102.5. Nothing else has been changed in the Fuel maps. I would expect the afv to change somewhat different as I haven't done datalogging to change anything else. After 3 rides close to 50 miles total it still is at 100. Before motor roll, AFV mostly at 102.5 which was fine. After motor roll, it wound up at 105.3. that number hasn't varied one iota either until I changed it a week ago. My maps aren't that good for a 100 value all the time. One point that I will share, I used the older version of spy before motor roll and at that time to bring bike up, I used the new "paid for" version, of which I am still learning about. Thanks for any views or experiences you all may have had. | ||
| Readyxb |
Hi Sagehawk, yes I have seen that on several occasions and there are multiple possible causes. Recording a sufficiently long datalog session would tell us everything needed to answer your specific AFV mystery! Is that a possibility? A log, combined with the EEPROM image used for the log, means no guesswork involved. I'd be glad to take a look. FYI: You have the ability to dial in a more exact Idle base fuel map; no need for a square idle map modification! Also, as you likely know, closed loop idle O2 feedback does not affect the AFV. | ||
| Sagehawk |
Readyxb: glad to hear from a real person on this subject. Havent had a huge amount of trouble out of bike, but after the motor roll and different spy to set basics, it just isnt as snappy as it was before. Ive only done one short data log in driveway to understand how software works and the file management and nomenclature of it. Ill get lined out to do what you asked and get that to you then. What type of file .ext do You need ? And the current eeprom used? Thanks guy! | ||
| Readyxb |
For the log, if you can, start the recording before cranking the bike, and then get as many different conditions as possible including idle cold, driving around town, driving at highway speeds, idle hot, etc. Be sure to get some steady-throttle driving at around 60-70 mph. The log format can be as recorded from ECMSpy for Mono but the extensions are .xdl, .msl, .csv, .log, .xls, or .dat. The current eeprom (not just the maps) as a .bin/.xpr/.epr or any binary format. (Message edited by readyxb on September 06, 2014) | ||
| Jstav2012 |
Hi Sage, this also happened to me. After I did some tuning, I turned off my O2 sensor, and I discovered that it took me all the way from my house (near Lake Houston), all the way to the beltway near JFK before the CEL would come on (it was telling me it couldn't adjust AFV because the O2 was disabled.) I was very surprised about this, BUT, from 59N to the toll road was the only place I could go 60-70MPH for an extended period of time. | ||
| Sagehawk |
I tried a data log this eve tween rain storms and all I got was frustrated. I've set laptop screen off to 20 minutes and shutdown to one hour. I killed motor and restarted at a stop sign. so two miles down road I pulled over and rechecked to see if log still rolling. nope, transmission interrupted. stopped logfile and restarted it, packed up and got on road again. got no info at all. so, do you fire up spy, key on bike, retrieve eeprom and activate start runtime series, then activate log icon? then start bike? What little bit of info in messages was 14 possible mishaps with air temp or cylinder head temp sensors. message was full of transmission interrupted messages. | ||
| Readyxb |
Does your laptop have any disk "parking" software? Some models have an accelerometer that will temporarily spin down the hard disk if it senses that the laptop is being dropped (or in your case, going over bumps or accelerating). Just a thought. Does the log record successfully if the bike isn't in motion? Maybe try recording just at idle but also close the laptop screen to try and recreate your interrupted log scenario. >> so, do you fire up spy, key on bike, retrieve eeprom and activate start runtime series, then activate log icon? then start bike? >> Yes, you want to key on the bike (key and run/stop switch), start the log, then start the bike. Also, you would only need to save the eeprom image once, such as after you stop recording | ||
| Jstav2012 |
I have done the logging with a laptop in a backpack, and a usb extension cable to my ECM cable, but only once or twice with success. If I ever have to do it again, I'll get the bluetooth version of the dongle. | ||
| Sagehawk |
I got a short log other day in driveway that wasnt to complete either. Went over my notebook today and changed up several options on sleep, lid down, etc. So ill give it another try soon. Got home from ride, and wife had den moved around, then shoulder was hurting. Duh! 6 weeks out of rotator cuff surgery, she is. Then she says, i didnt know it was going to be a damn espnspy buell day. Sometimes a fellow cant win. | ||
| Sagehawk |
tried to log again today. Transmission error occurred Failed to send data, FI_IO_error. So I have to get that out of the way first. I have no problem hooking up to bike, starting process to get ready, and pretty quick it comes up with that message. until that goes away, can't log. Maybe it's the mosquitos. Is anyone else being carted off right now on the gulf coast? | ||
| Readyxb |
Sagehawk, that error suggest a communication error at the USB level. Are you using ECMSpy for Mono's built-in FTDI D2XX DLL interface, or have you installed the FTDI USB hardware drivers from http://www.ftdichip.com/Drivers/VCP.htm ? ECMSpy creates an extensive log file to aid in troubleshooting. Look under the "Messages" tab. Can you send that my way if you get the error(s) again? | ||
| Sagehawk |
I installed ftdi drivers. I didnt know mono had built in driver. Ill look and see if yesterdays message is still filed and get that to you. I just rode yesterday without stopping cuz of mosquitos. Stop n your bled dry. I come up on com 4 with this notebook. Perhaps a software setting? | ||
| Readyxb |
If I could choose between getting $100K or never being bitten by a mosquito again, well.... I'd have to give it serious thought! The little buggers love me. Installing the FTDI drivers is fine. Next time you launch ECMSpy, instead of selecting COM4, choose "FTDI TTL232..." as the serial port and see if that gets rid of your communication issues. | ||
| Sagehawk |
Before I send you anything , I will try that tonight. not much time as soa starts on fx tonight. Will let you know. | ||
| Sagehawk |
Readyxb, i sent a pm your way more on connwction issues than anything. Ill get a print of the messages and send to you tonight. Connection timeout and errors are abound now. Dont know where this is coming from. Take care. | ||
| Readyxb |
Replied to pm. I'll be glad to help if I can! Sounds like a gremlin somewhere. | ||
| Sagehawk |
Readyxb: sent you 3 files tonight. finally got everything line out for a data log today. hope its enough info for you. funny thing, after I got drivers reloaded and hopefully fixed com port issues, now the afv did change. a lot. anyhow please look them over and share your thoughts. life got in the way again is delay excuse. take care. |
