I am having some strange issue with emu black usb-c version running on v3.
It is running up untill ~4600 rpm and 150kpa and then all the sudden it disconnects laptop, interupts log. sometimes it asks to load tune from computer or retrieve it from ecu, even if I have pressed burn button after changes.
In log it shows rpm rising and then drops to 0. Engine physicaly does not stall or anything, just jerks because of wrong VE map as I try to tune it..
Ecu voltage is stable ~13.6v
Any ideas how to troubleshoot this one ? Except for changing computer and usb cable and running laptop on battery only, not mains power, these I have already tried .
Dyno, in steady state tuning, I did not notice this while on inertia dyno and when I accelerate slowly <120kpa I can rev the engine up to 6k rpm just fine, but once its starts to make boost i get this weird problem..
Engine is vag R36 from 2010 q7, primary trigger vr, secondary hall / hall with vvt on both cams. Dual knock sensor. Using external 4bar map sensor.
Sounds like a ignition problem. Bad spark plug, cable or coil can cause interferance in the complete car. Make sure you use sesistor sparkplugs.
Ground the car to the dyno can also help.
Sometimes I use a longer USB cord, it can happen with bad quality cables.
It has coil on plug, like audi R8 only in diffrent packaging, so I dont think its ignition problem.
I had a problem with usb cable at the beggining, it was too soft and I might have damaged the usb plug itself, have to check this and maybe replace usbc>a pigtail.
So I double checked the grounds, and they are all fine, power gnd goes to engine head and sensor grounds only to sensors.
Yesterday I changed the cable and it mostly solved the issue, but twice i got discconnect anyway, this time a bit higher in VE table. 5-6k rpm and 160-180 kpa. And I think I found out what was causing it.
So wrong knock tables, and ignition table. sequential knock detection is set up. and in ignition table, around the mentioned area 5-6k rprm 160-180kpa is around 15 degree of timing. and when i get false knocking it reduces timing to about 0 +/- 3* and it feels like antilag and engine jerks and pops in exhaust. Computer at the same time gets disconnected and does not connect back immediately, takes some 5 seconds or so, and I noticed that software itself goes to NOT RESPONDING and then starts to respond again.
Maybe my computer is shit for this job..( its an old thinkpad x201 with i5 )