Note, this is an iS issue…. I’m trying to resolve why when I connect my Level 2 BUDS dongle to the data port, the software will not recognize the ECU. I first tried to download a friend’s data logs from his 12iS and BUDS couldn’t see the ECU. No recognition of the engine serial number and no Lane indicators - engine page never changed after powering up the ECU. LED on the dongle is solid when plugged into the USB pots and flashes when BUDS opens, just like it should. I’ve successfully used the dongle for over two years on mine and another friend’s 12iS. I always plug the dongle into an unpowered ECU after starting the software. Here are all the things I’ve tried:
I’ve posted the issue to the Rotax Owners forum without anyone offering having experienced the same issue. I’m running out of ideas having exhausted all my substitutional troubleshooting options, except possibly one…
Have any of you 12iS guys had your ECU logs downloaded since replacing your HIC modules? It’s a stretch, but running out of common denominators. Anxious to hear what you guys say.
- Tried two different 12iS aircraft
- Tried two different pcs
- Tried two different serial extension cables
- Tried BUDS v3.0 and v4.0
- Tried all three USB ports on the pc
- Verified there is voltage at the pins at the end of the extension cables
- Sent the dongle to Lockwood and it worked fine for them on pcs running Windows 10 & 11. Both of our pcs are running Windows 10, and ours and Lockwood’s are up-to-date on patches.
I’ve posted the issue to the Rotax Owners forum without anyone offering having experienced the same issue. I’m running out of ideas having exhausted all my substitutional troubleshooting options, except possibly one…
Have any of you 12iS guys had your ECU logs downloaded since replacing your HIC modules? It’s a stretch, but running out of common denominators. Anxious to hear what you guys say.
Last edited: