Need new Race ECM!

[bmacarthur]

So apparently after the sad demand see of EBR, their online store is no longer up. I have an 04 XB12s with the race can and ecm, and recently it's been a single random stutter, sometimes soft, and sometimes hard enough to almost buck me off the bike. It would set the CEL, but ecmspy showed no codes stored. Finally today, it saved the code. 53, ECM failure. I've looked into it, and the general consensus is that I need a new ECM. so, my question is if anyone has any idea where to find a race ecm? I do NOT want a stock one with the race map flashed on it, or a used one where someone could have dinked around with the maps. Like I said, they used to be available from ebr's online store, but it's gone. I've emailed them and yet to get a response. Thanks in advance!

 

[ReadyXB]

I am not aware of anyone whose ECM has recovered from a code 53.

With the EBR products website offline, the only viable sources are forums and ebay. They do show up on ebay. Also, you might keep checking at http://buellsterparts.com/ as they occasionally carry a few ECMs. Right now, they have a Buell factory Race ECM but for the XB9.

Once you source another ECM, I would be interested in purchasing your old one. I have been trying to get my hands on an ECM with code 52, 53, 54, or 55. Please do not throw it away!

 

[bmacarthur]

Awesome, I'll keep an eye out, and if you would do the same that would be great! And for sure I'll let you know when I get a new one. Out of curiosity, What Interest Do you have with an ecm with a failure code?

 

[ReadyXB]

Will do!

I build and sell Buell data link cables and bluetooth modules (https://readyxb.wordpress.com) and I am working on a datalogging product (along with other projects) that requires lots of testing on a variety of Buell models. Testing is the key. I have long been curious what shows up in a datalog trace during runtime when an ECM fails with codes 52-55. My ideal situation is to find four ecms showing each type of failure, or any combination thereof.

I also want to cut one open, particularly with code 54, and do a bit of chip-level diagnostics.