ECM Droid gurus...a couple of quick questions

Buellxb Forum

Help Support Buellxb Forum:

Phone is turned off now. It's something like:

BUE2D_20170604_xxxxx.xpr

Where the xxxxx is something else...
 
I get you want to go to sleep so no worries, my time is extremely limited so don't know when I can get back on here to help you. I'm sure someone will lend a hand.
 
I was going to try to use my Kindle Fire to try another device.

Problem is that I had to install ecmdroid through the website...it says it is 'installed', but it is *no where* to be found on the Fire....

I can't find it to save my life...even using ES explorer.

This is getting frustrating...
 
Try the OG device and rename the file you want to use that isn't working simply as BUE2D.xpr and give it a try... something isn't adding up. It was for sure a .xpr originally right? You didn't change it to .xpr on your own right? Link where you got it from.
 
No worries lowkey. We can disagree:angel:. I'm not limiting its range beyond compensating for normal issues, I just feel it's range is drastically way and well beyond any possible circumstance (it goes to eleven!) haha. In a 'perfect world' why limit it at all? We are both finding solutions out our own way and I appreciate the discussion:up:

Vicenzajay: The file you saved from your ECM is the one you're trying to re-install right? So firmware shouldn't be an issue, and file location shouldn't either. Even if it was you would get a different error message if you were trying to burn an incompatible firmware, I believe you can still load anything without a warning but before you burn, it won't let you.
The second dialog box that asks you which ECM (BUE2D or BUE3..) is unimportant as long as you hit BUE2D. It's not that action thats throwing the error message.
ECMDroid doesn't like that file for some reason. Dunno why.
 
The link to the file is this one:

http://www.buelltooth.com/maps.html

Half way down the page is the specific file link (XB12 Drummer SS 2008-2009 for BUE2D)

Lowkey: No - I haven't tried to re-load any file that I originally pulled from the ECM. The map on the ECM *is the same map that's been on there for at least two years. I'm trying to upload a .xpr file from the buelltooth site that purports to be made for my specific configuration (and firmware). ECMdroid isn't having it.
 
The link to the file is this one:

http://www.buelltooth.com/maps.html

Half way down the page is the specific file link (XB12 Drummer SS 2008-2009 for BUE2D)

Lowkey: No - I haven't tried to re-load any file that I originally pulled from the ECM. The map on the ECM *is the same map that's been on there for at least two years. I'm trying to upload a .xpr file from the buelltooth site that purports to be made for my specific configuration (and firmware). ECMdroid isn't having it.

I understand, I was just double checking you didn't relabel a downloaded file labeled say BUE2D.txt and relabeled it to BUE2D.xpr for instance is all. I thought about it and maybe came up with why you have the error only trying to "burn". You need to go into ECMDroid settings and put a check on the first two choices "hide EEPROM variables" and "enable EEPROM burning", I choose to leave "optimized burning" unchecked as I had an issue with corrupted data not being written over but it's up to you if you want that checked or not. Try that and report back.
 
Will do - I have enable EEPROM burning selected, but not the 'hide variables' selected. I'll try that this evening.
 
I don't think it will help.... I was just letting you know how I set up that page. Issue is something else if "enable burning" is on.



EDIT: Cooter also has the BUE2D ECM so he can better help you I think, I'll chime in if I can give a hand. One other thing is you said is your ECM is a "race" ECM so maybe the issue is something to do with that? Maybe download and try another BUE2D.xpr to rule out the one you want to use isn't the issue. Just throwing out some ideas...
 
Last edited:
I sounds like an issue "loading" the map onto ECMDroid, not an issue "burning" the map from ECMDroid onto the ECM. Thats why I don't even think the firmware matters (yet).

You could try the ultimate fix. Delete that file and re-download it from their site again? I'll try that link later and see if it works on my tablet.
 
Yes I've seen that issue before with another member I was helping, his device (LG?) could run ECMDroid and change data on the bike but was unable to load .xpr's to the device. I had him borrow a Samsung device from a friend and he got the .xpr to flash without issue. I guess I thought he was past this point and trying to burn the file already but you are probably right.

OP for clarification is the issue getting the .xpr to the device or from device to ECM? And what brand/model of device is it?
 
That sounds like my issue.

My device is a HTC M8 cellphone. The Fire tablet will *not run ecmdroid (for me, I know Cole gets it to work somehow).

Yes - the issue is getting the .xpr into ECMdroid...I never get to the place where I can press the "burn" button.
 
The link to the map you put works with my crappy $32 RCA android tablet. I can load it into ECMDroid and burn it onto a BUE2D ECM. Sounds like you have a hardware issue:(
I'm going to get a new $60 android phone from AT&T to do the same thing and datalog even easier. That interface should be much less aggravating than the terrible RCA touch screen.
 
Well I know for sure the Samsung devices work with those files as long as it's on a compatible android version for ECMDroid. Note-2, Note-3 etc.. and whatever Samsung device the guy I was helping borrowed. Maybe someone will let you borrow an android device to try again?


EDIT: Cooter, you just outed yourself as an iPhone user...:black_eyed:
 
Well I know for sure the Samsung devices work with those files as long as it's on a compatible android version for ECMDroid. Note-2, Note-3 etc.. and whatever Samsung device the guy I was helping borrowed. Maybe someone will let you borrow an android device to try again?


EDIT: Cooter, you just outed yourself as an iPhone user...:black_eyed:

I was using a Motorola and having issues burning the eeprom until trying a Samsung..But the biggest problem was the maps I downloaded from Buelltooth.com was not .xpr...Once you emailed me the proper map I was able to burn it.
 
I was using a Motorola and having issues burning the eeprom until trying a Samsung..But the biggest problem was the maps I downloaded from Buelltooth.com was not .xpr...Once you emailed me the proper map I was able to burn it.

Ok that clears that up except the buelltooth.com files should be .xpr as that is the format for ECMDroid. I thought you couldn't get the device to allow the .xpr to transfer to it, only the Samsung device would allow the file? Maybe another member I'm thinking of? Not to sure.
 
Okay - used my wife's halfway broken, old Samsung tablet and it worked. Go figure.

Weather is not good until Friday. I assume I need to do a TPS reset and a training ride to start, no? Should I at least start it statically and see if all is well through to warm idle?

Jay
 
The map I loaded *was a .xpr file. Since Cooter loaded it just fine, I'm fairly confident that the format is good.

I did the stuff covered earlier in the thread - afv set to 100 on rear cylinder, unchecked exhaust valve enabled box, unchecked speed-based fan control box.

Hopefully that covers the stuff I need to check. Cooter - any thoughts (since you've now looked at that eeprom)?
 
Well - here's an update.

The weather cleared up all day today, so this afternoon I did the TPS reset and then rode for 120 miles. It was quite a ride, with mostly no interruptions (about 10 minutes or so in traffic that I can't avoid). It ranged over 1600 feet of altitude and anywhere from 0-75 MPH (mainly steady driving, though). It also included about 25-30 miles of Blue Ridge Parkway.

Got to Floyd and stopped for a needed break. Then rode home (another 30 miles or so).

Once I parked the bike, I checked the EEprom....the rear AFV has already adjusted to 85.5.

The fan didn't come on the entire ride (not that I noticed, anyway), and the bike cooled down very quickly. It just doesn't show any signs of running lean at all. I should also note that the bike ran very well with the Buelltooth map. It wasn't noticeably 'better' than before, but I've already remarked on how smooth and nice this bike runs. It pulled great - accelerated and decelerated beautifully...no jerkiness at all.

I suppose the next step is to replace the O2 sensor. Bluntly, I want to ask if that's *absolutely necessary right now or can it wait until after the main riding season? I have zero desire to tear a bike apart that is running this good.

Not least - thanks to Cooter and Lowkey for the help thus far....
 
You are one lucky SOB to have the Blue Ridge parkway as a test ride loop!! Color me jealous!

Your ride was long enough for the ECM to adjust so you should be fine. I am very curious why it's trying to pull that much fuel out though. An old O2 could do that, you can check it's function in the "live data" section to see if it's operating properly before buying the part.

I never looked at the eeprom data, just checked to see if it would load.

Glad you're up and running:up:
 
Back
Top