As a base rule, for any special customization, URL of editable page (see MembersPage) is required in the order comment.
- it is best to have separate page for each project
- but in very simple cases (when updates are most certainly not needed), URL of a previous project is OK, if the specs is otherwise clearly
Only use the ECU EC10 (any other special features) after DVM testing the relevant outputs / inputs in VemsTune [with 1k resistor connected to 0V/5V] (using the included paper as a hint/starting point).
- EC36: highly standard, usually does not depend on options (other than the IGBT / logiclevel ignition outputs)
- EC18: depends on product options (knock, dual WBO2, ...), but otherwise quite standard, see [RescueKit.pdf]
- EC10: customization, according to exact pinout on URL referred in order comment
- otherwise EC10 might differ from what one might expect, or from similar ECU, or EC10 might not be present at all.
For standard (EC36+EC18) VEMS ECU one ECU EC10 possibility/example (not standard, but as requested, or specified during manufacturing)
- EC10/1 analog input (mc0)
- EC10/2 analog input (eg. mc2)
- EC10/3 analog input (eg. mc3)
- EC10/4 analog input (eg. mc5 or mc6)
- EC10/5 2nd RS232 RX
- EC10/6 3d trigger (HALL) - useful for activation
- EC10/7 2nd wheelspeed
- EC10/8 2nd RS232 TX
- EC10/9 +5V
- EC10/10 GND (measure connectivity to EC36/26 GND, start with this)
For Motronic88, one ECU EC10 possibility/example (not standard, but as requested, or specified during manufacturing) :
- EC10/1 analog input
- EC10/2 analog input
- EC10/3 analog input
- EC10/4 analog input
- EC10/5 +5V
- EC10/6 2nd wheelspeed
- EC10/7 3d trigger (or p259/x or 2nd serial TX)
- EC10/8 power IGBT output
- EC10/9 power IGBT output
- EC10/10 GND (measure connectivity to EC36/26 GND, start with this)
For "ECU VEMS V3 internal CAN", possibility/example (not standard, but as requested:
Notes:
- 2nd RS232 TX is also common nowadays.
- 2nd wheelspeed and 3d trigger can be used as activation inputs (in fw 1.2.38 and newer)