After 10+ years of watching businesses come and go in the realm of Ducati EFI tuning/etc, I think the time is right that We got involved. That's the Royal We. Me, you, Cycleworks, all in the ""  spirit of sharing useful knowledge to help people better enjoy their motorcycles.

I'm not the first one to this particular party, but historically, I didn't want to throw my efforts into R&D because each time a company approached us, the business model was such that they were the ones to make the large share of money -- and then there is always the presence of hiding "how easy" all this is from the customers. Can't have them finding out. That's what got me started with in the first place. In 1995, the mechanics I approached asking the first couple dumb questions about my new-to-me 1991 900SS laughed in my face and said just pay them for service.

My long time heroes of Ducati EFI are Doug Lofgren, Brad Black, and JHP Ducati. And now there's a new breed of knowledgeable people in the community contributing, you can find them on the forums sharing info: 
How to: GuzziDiag/Tunerpro for Ducs
OFFICIAL: Closed Loop ECU mods
Non-linear TPS readings vary between ECUs
There is so much you can learn there -- and also discover even more resources and more people helping.

So this thread (Ducati ECU Tuning Resources) is the most applicable to my recent R&D work... Historically, "scan" tools would connect to the diag port on Ducatis with weber-marelli ecus and communicate via K line (KWP2000). 

With the Seimens ECU on the new Monsters, the diag port gets two data line pins: the CAN bus. I've been watching CANbus in the industry and think it is kind of exciting. And after my experience using powerful small processors on Arduino-like platforms, I'm starting to poke my nose in the world of Ducati EFI...

We've got a chipKIT Max32 which has two CAN controllers inside its PIC32 processor. I finally have my hardware set up on the CAN bus in such a way as to not interfere with our Stupidly Expensive Efi Tools ( SEET ) talking to a Monster 696's diag port. This is actually kind of cool because it took more than a few attempts to make this happen. I was getting worried because every attempt previous to put my hardware on the bus would result in comms failure in SEET's software. I read the mcp2551's data sheet and it suggested a 60 ohm resistor for testing ... and the 80-something ohm resistor was the 1st one I grabbed within 50% of 60 ohms...

CAN sniffing on M696


I still haven't convinced the Max32 to actually sniff traffic, but this was the 1st configuration where the SEET could still communicate with the M696 while the chipKIT hardware was connected to the CAN bus. So that's some progress at least. It's also the 1st time my test software said "can bus modules initialized". Now it's back on the software to finger out how to make the CAN stuff in the PIC32 work.


In a parallel development, we got in a NXP dev board with CAN controller and transceivers built in. I was successful in making it "blink" ... however, I have no idea how nor how to make code happen in the IDE software. Normally my 2nd step after making something blink is to make it do SOS in morse code. Kinda of backwards, as I'm quite SOS and SOL until I actually make it blink dot dot dot dash dash dash dot dot dot. Just a bit frustrating how the NXP IDE is supposed to be “easy” but the hobbyist-oriented Arduino stuff actually is easy.


Speaking of Arduino, we also ordered some CANbus shields, where the transceiver and controller are on-board and the MCU (microcontroller unit – “computer”) only needs to shuffle the data coming out of it. But they're lost in the hybrid UPS+USPS delivery system. Rather than it being twice as cheap, it just introduces more people to lose the package – and more other people to blame it on. I'm told we can report it lost after 4 weeks.