We still haven't got the pack with the 2 ECU-s to repair (eg. with broken-off Econoseal pins), because it was posted in different way than [instructed]
- recipient was different
- and more importantly declared value was more than max allowed
Following the simple instructions about sending would have been so easy. Suffered delays instead, and now more laborsome and annoying
The pack seems to have bounced between customs offices somehow (for weeks!). Perhaps in some loop
- not sure about that, we are trying to break the loop but it's quite nonsense and laborsome
- even if the pack is in dest district the logistic company cannot hand over until the customs office allows it
- Customs office requests "CN23" paper ("Declaration en Douane") filled and signed by the sender
- (normally included with the shipment of 50 EUR or more value, but was not in this case ? Not needed for 25USD .. 47 EUR or lower)
- on telephone they said they need original signature on paper, but please also scan and send us so we have information, we also try to hand them a color print; but I'm afraid they will insist on the original
- signed CN23 not yet provided by the sender (sender notified, but progress seems to have stalled => returned pack is still in no-man-s-land without chance to move)
Authorize mainboard replacement if necessary
- Apparently repairable, mainboard replacement would NOT technically be needed.
- But now the only chance to send back new ECU in short time
- instead of waiting undefined delay (sender providing CN23 for customs office, customs office delaying for god knows how much more time, and than perhaps requesting sg else...)
We recommend to clarify spec, and if complete spec available on 2017-06-08 we offer new ECU for 200 EUR / ECU (~gut replacement price) and immediate manufacturing and sending)
- any EC10 inputs / outputs used
- exactly ?
- we can assemble new ECU extremely fast if the specs are clarified, but we cannot start (need to wait indefinitely for the sender/customs/ack procedure) if uncertain.
extra functions on EC10 - proposal (to be confirmed) so alternate path of manufacturing 2 new identical ECU-s can progress
- 3rd VR trigger input (best on EC18/12 or EC10/x)
- 2nd wheelspeed in
- 2 * NFET outputs for vanos
- optional: another 2 NFET outputs (inverted)
- 2nd RS232 TX and RX
- GND, +5V
- analog input (if any free pin available)
New ECU can be made immediately if installer can confirm to take care and handle this
- almost certainly suitable, but depending on his harness pinout maybe 1-2 pins need adjustment, or config change
v3/9858 Econoseal, but for S50B32 (original oid9877 order comment says S50B30 - prolly no significance)
- two broken pins in the EC36 connector
- just curiuos, did they bend first, and than was connected with "some force" ?
- VR,VR,VR three triggers needed, MembersPage/GunnarReynisson/VariableVanos single variable vanos S50B30 engine
- good comment
- "Also please make all stepper outputs low side drivers"
- usually NFETs are driven from spare S259(/5,6), and p259/2-3 (p259, when driving NFETs are inverted, active after powerup even before firmware activates them => so not recommended for fuelpump).
- Please list all used EC10 inputs / outputs , and anything special about the setup
ECU VEMS V3 VR,VR,VR
- primary_trigger: EC36/27 VR
- secondary_trigger: EC36/13VR
- ignition driver: 8 IGBT
- MAP connection: 400 kPa simplenipple
- Knock input channels: 0
- EGT input: no
- LCD connection: no
- Flyback: HighZ-only 30V flyback
- withSDcard: no
- 1-wire interface: no
v3/11414 (orig oid12126) Econoseal, but for S50B32
- P259 failed. "rectified wiring mistake since then on another ECU." (apparently they fixed harness ground )
- originally: ECU v3/11414 with LSU4.9; VR,VR,VR (yes, third VR trigger input)
1 x ECU VEMS V3 VR,VR,VR
- primary_trigger: EC36/27 VR
- secondary_trigger: EC36/13VR
- ignition driver: 8 IGBT
- MAP connection: 400 kPa simplenipple
- Knock input channels: 0
- EGT input: no
- ETC BridgeOutput_Interface: 0
- Flyback: HighZ-only 30V flyback
- Hi-side PFET outputs: 0
- LCD connection: no
- withSDcard: no
- 1-wire interface: no
- Please list all used EC10 inputs / outputs , and anything special about the setup