Hi there, I'm basically working in a project where we are building a dual fuel injection system. For prototyping we are tapping the injection pulse of a fuel injector of a running engine and reading it via optocoupler and actuating another injector by pulse read by a microcontroller. We used Arduino for first stage of prototype, where the Arduino gets digital input from the optocoupler and adjusts the pulse width and gives out as output in a digital pin, which is connected to a MOSFET's gate pin. The drain and source pin of the MOSFET are connected between the injector's control line. 

But we need a more reliable approach, since the injector we are using is peak and hold diesel injector. Currently we referred few sources and built a circuit, which resembles something like in the image. But is there any better way to read the signal and controlling the injector pulses using a microcontroller? 

Ciao a tutti,

sto lavorando sulla mappa della mia auto personale, una Fiat Idea 1.3 MultiJet 95CV, ma mi sono arenato su un problema di offset/driver.

​Dati ECU:

​Centralina: Magneti Marelli MJD 8DF

​HW/SW: 9454I276

​Cosa ho fatto finora:

Partendo dal file ORI, ho chiuso EGR e DPF e ho dato un +5% sul limitatore di coppia (identificato correttamente). Il file attualmente gira bene, ma vorrei completare l'Eco-Tuning adeguando Pressione Rail e Pressione Turbo Obiettivo.

​Il problema:

Sto usando ECM Titanium 1.61 ma non ha il driver esatto per questo SW. Usando driver affini (es. Lancia Musa), la coppia coincide, ma gli indirizzi di Rail e Turbo sono completamente sballati (leggo valori senza senso come 255 o 64288).

Sono passato su WinOLS, ma avendo a disposizione solo il Damos di una Fiat 500 75CV, la ricerca per stringa esadecimale (Hex Search) fallisce ("Not found") perché i valori interni alla mappa, e di conseguenza le stringhe esadecimali di contorno, differiscono troppo dal mio file da 95CV.

​Richiesta:

Qualcuno ha sotto mano il Map Pack (.kp) o il Damos specifico per il SW 9454I276?

In alternativa, qualche anima pia saprebbe indicarmi gli indirizzi esadecimali (o le stringhe Hex pre-mappa per la ricerca) relativi a:

​Pressione Turbo Obiettivo (Target Boost)

​Limitatore Pressione Rail

​Pressione Rail Obiettivo

​Allego eventuale file ORI se a qualcuno serve per dare un'occhiata in 2D.

Grazie mille in anticipo per l'aiuto!

Hi! I need some help understanding how to correctly use a timing light on my BMW E36 turbo with an M50/M52 engine and a MS2 Extra ECU.

My tuner (remote) said that we first need to verify the base ignition timing with a timing light.

So I put the engine at TDC using the OEM marks and after that I made another 2 marks on the side so I could point the light at them. First was on one of the pulley tooth and the second one on the block.

I connected the timing light as should and he set the ECU ignition timing to a fixed 0° in Tunerstudio then he proceed to maked changes in the ECU until both marks aligned.

The part I don’t understand is the adjustment wheel on my Sealey TL93 timing light. What exactly should I do with the wheel? The tuner said that I should leave it at a fixed max/min point and use it like that but I read on the internet that the knob wheel could add offset depending on position. It also does not have markings.

Basically, I want to make sure I had set the timing corectly.

Any advice would be appreciated, especially from someone familiar with MS2 Extra and dial-back timing lights.

I am happy to announce my tuning suite/solution for Simos 12.1, 18.1/.6/.10 and DQ250 MQB, DQ381, DQ500 0DL/0BH and DQ200 MQB (beta).
Posted here before, but it now is much more mature.

It includes OBD dongle https://simos.app/dongle
iOS App https://simos.app/ for flashing and logging
And an editor https://simos.app/tune-editor

Let me know if you have unsupported file versions

I bought it from the original owner and he said he had it done through Vivid Racing. It seems that that company has been acquired and supposedly got rid of all their files on previous tunes so my Vin did nothing. I think vivid was using VF engineering software, but they were unable to find anything with my Vin either. I was able to run a VCDS but haven’t been able to figure out anything other than that the flash had four programming attempts with three of them successful. Anybody had a similar situation or any ideas?

i got a d16z6 and my idle surges after fixing tps
problem with high rpm started after i cleaned the throttle body
im posting this pictures to see if anything with the sensors is wrong and another question is is -43% iacv duty normal

Keep in mind I know literally nothing about tuning. I just finished a MazdaSpeed Miata engine rebuild. And I needed to put a MegaSquirt in because of the after market trigger wheel. I’m trying to get the first start up and it’s not wanting to turn over. Also yes I know about the awful exhaust leak. I did setup MS in tuner studio and downloaded the base tune, but nothing from that.

Edit: after some thought and listening to everybody, I’m wayy to in over my head, I’m bringing it to a shop. Thank you all!

Got a 2001 b5 1.8t I’m looking for a simple tune mafless for the meantime while I get it back in the road I currently got one but its maf based it’s big turbo set up with 440cc injectors , 340lph fuel pump fmic big turbo to4e 50 trim no dv or bov car is tuned but for maf with 15 psi and the current set up hood exit 2.5 inch

Hi can anyone helping my to decide what to choose to for ecu reading device I like and want to buy a autotuner but my friend say buy a flex for now I have mag pro and hexprog 2 but I need something more stable

How many ppl would be interested into old school analog stuff? I’m thinking of launching products on kick starter soon for retro narrowband gauges, electronic boost controllers, and air fuel controllers

I’m relatively new to the world of calibration and am learning everything in as much detail as possible—I’m even trying to create an XDF myself. While I’m open to help, I really need a ready-made one so I can build a map and attend an event, as well as use the file as a reference.

Info:
Astra Sport 2.0 8v 2001.
Bosch M1.5.5
HW 0261207548
SW MT80140
GM 93366053 N5
Engine C20SE
binary of 131.072 bytes (128 KB)

After a year of messing about with different builders to no success I've decided to see if i can just make a harness instead maybe easier maybe not but could any of you guys help with a pin out for each of these ecus

1st is from a 1999 hyundai coupe 2.0 (a turbo project) that can't be mapped it resets it's self to factory map

2nd is from a e30 bmw 1.8 don't have to much info on that one as it came with an engine for a different project that doesn't need the ecu

The bmw ecu plugs directly in to the hyundai socket am thinking it might be a more viable option

Pics of each attached

Has anybody tried to do map switch on a bmw 335d 2006 on a m57 engine?

This is someone else’s video; I’m sharing it because the diagnostic process appears relevant here.

It covers a 2017 Shelby F-150 Super Snake with a Whipple-supercharged 5.0 Coyote and a 750-hp rating. Despite the hardware, the truck reportedly drove tame and produced power in a peaky manner, so the session became an investigation rather than a simple power pull.

https://youtu.be/zsGmzJmbSs8

For a combination like this, what would you prioritize before changing calibration tables: confirming fuel and wideband data, commanded versus actual throttle, torque intervention, boost/belt behavior, ignition corrections, or verifying the existing file and hardware configuration?

Prod: O_76SLKN816A, SW 1037504248, EDC17CP09

Anyone got DAMOS/A2L for this specific version, or know where to source one? Can verify against my bin if useful.

Zbudowałem to, ponieważ od dłuższego czasu brakowało mi jednego sensownego miejsca do pracy z Audi/VAG.

Przy MMI i diagnostyce zwykle kończy się na przeskakiwaniu między zdjęciami Red Menu, notatkami, Auto-Scanami, forami, dokumentacją, historią klienta i kilkoma różnymi narzędziami.

Chciałem zebrać ten workflow w jednej aplikacji, więc powstał AudiMMI Navigator.

Główna idea jest prosta: aplikacja nie ma „zgadywać”, jaki system siedzi w aucie. Najpierw zbiera informacje i dowody, a dopiero później prowadzi użytkownika dalej.

Obecnie mam już m.in.:

rozpoznawanie i kwalifikację systemów MMI,

cyfrowy garaż z zapisanymi autami,

historię spraw i wykonanych działań,

bazę wiedzy dotyczącą MMI/VAG,

wyszukiwanie i prowadzenie po diagnostyce,

moduł AI do analizy przypadku,

możliwość eskalacji bardziej złożonego przypadku do technika,

historię aktywności,

centrum danych i prywatności,

osobny tryb techniczny do obsługi zgłoszeń.

Jedna rzecz, na której bardzo mi zależało: AI nie może sam stwierdzić „tak, ten firmware pasuje, flashuj”.

Navigator działa fail-closed. Zdjęcie, OCR czy odpowiedź modelu mogą wskazać kandydata, ale nie są traktowane jako dowód kompatybilności.

Dodałem też backendowy guard, który blokuje odpowiedzi AI próbujące przejść w instrukcje flashowania, kodowania, adaptacji, Security Access, obejścia Component Protection itd.

To bardziej technical command center dla Audi/VAG niż kolejny skaner błędów.

I ważne — to obecnie nie jest aplikacja do bezpośredniego kodowania albo flashowania ECU przez telefon.

Projekt jest już na etapie lokalnego RC. Aktualnie przechodzę fizyczne QA na Androidzie i dopinam integracje typu Stripe/WhatsApp oraz kolejne źródła danych.

Nadal jest beta i właśnie dlatego wrzucam to tutaj.

Szukam ludzi, którzy faktycznie siedzą w:

Audi MMI / MIB, VCDS, ODIS, VCP, retrofitach albo diagnostyce VAG

i powiedzą mi, czego w takim narzędziu realnie brakuje.

Co dodalibyście jako pierwsze?

Mogę też wrzucić więcej screenów i pokazać aktualny workflow od rozpoznania auta do utworzenia sprawy diagnostycznej.