redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 212899861 | Release Date | 2026/04/12 | List Price | $112.62 | Model Number | 212899861 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
DSAI TO MDI IGNITION CONVERSION — KOHLER COMMAND TWINS: Replaces discontinued 12V DSAI (Digital Spark Advanced Ignition) system Converts to magneto-powered MDI (Magneto Digital Ignition) system Changes from 3-wire DSAI to 1-wire MDI while reusing original harness Kit contains (2) MDI modules, duplex lead harness, terminal, cable ties, instructions KOHLER ENGINE APPLICATIONS: CH740/CV740 Command PRO 725cc V-Twin OHV 27HP (DSAI-equipped specs) CH750/CV750 Command PRO 747cc V-Twin OHV (DSAI-equipped specs) CH20 Command 624cc V-Twin OHV 20HP (DSAI-equipped specs) CH23 Command 674cc V-Twin OHV 23HP (DSAI-equipped specs) CH640 Command PRO 624cc V-Twin OHV (DSAI-equipped specs) OEM PART NUMBERS (Superseded by This Kit): Kohler: 25 707 03-S / 2570703S Kohler: 24 584 52-S / 24 584 53-S / 24 584 63-S / 24 584 64-S Kohler: 24 584 89-S / 24 584 90-S / 24 584 30-S / 24 584 31-S Kohler: 24 584 38-S / 24 584 39-S / 24 584 41-S Kohler: 24 755 162-S / 24 755 172-S / 24 755 173-S Bad Boy: 015-2000-00 MDI Module Conversion Kit for Kohler Command V-Twin Engines: Complete conversion kit replaces all DSAI ignition modules with 2 or 3 terminals on Kohler Command Twin cylinder engines. Magneto-powered system eliminates 12V dependency for reliable spark. ⚠️ IMPORTANT: Verify engine model and spec number before ordering. Not all specs within listed models use DSAI ignition.
| Brand | Rareelectrical |
|---|---|
| Model | Aftermarket OEM MDI Module Conversion Kit |
| Exterior | Machined |
| Item Weight | 2 pounds |
| Manufacturer | RAREELECTRICAL |
| Item model number | 055-624A1 |
| Product Dimensions | 8.2 x 5.25 x 3.5 inches |
| Manufacturer Part Number | 055-624A1 |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form