NefMoto

Hey guys,
I generated an ecu file from a bin I read from my car.
I can connect with Me7Logger + GUI, and start logging when the car is off, ignition on. Most of the values are 0.
When I start the car, logging stops, and the car also turns off.
If I do it a couple of times, I get a "Start blocked by immobilizer error.

I can't connect when the car is already running. ecu is 4B0906018BD, on a 1.8T Passat APU (narrow band)

Found that this is a common issue with the 1.8T, something about the instrument cluster. I'll keep reading the other threads

Yup.  Start the car and then pull the cluster fuse so the needles die.  Should be able to connect then.  The immo thing is probably the logger overflowing the k-line and the cluster can't see the ECU, so blocks the start.

I've wired a relay to the front fogs (as R32 headlights don't have them), so I can kill the cluster without pulling a fuse. :)

Isn't a solution running a direct k-line?

And then disabling the original at the same time?  Seems a bit convoluted.

What I am thinking to do is add a secound obd port with just k-line positive and ground.

But the k-line is just a bus, so all you're doing is just adding another OBD in serial and you'll still have the same issue.  No?

something like this

Alright, will try this tonight. Although wiring up a new OBD isn't something I'm thinking of right now -- unless pulling the cluster fuse fails.
Also, nefmoto flasher logger works, but I'm not sure if there is a tool to convert the logs to csv so they can be read by ecux

has anyone ever got this error?

sorry to hijack the thread i've just never managed to get mine connected at all.

tried different cables and laptops xp win7 etc always get the same error....

2013_v1.20\ecus\1.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261206795"
SWNumber           = "1037360313"
PartNumber         = "8N0906018H"
SWVersion          = "0004"
EngineId           = "1.8L R4/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S, I,  A         ,   B, unit
#------------------------------------------------------------------------------------------------------------
#001: nmot_w              , EngineSpeed                     , 00F89C, 2, 0000, 0, 0,        0.25,   0, 'rpm'
#002: gangi               , SelectedGear                    , 380997, 1, 0000, 0, 0,           1,   0, 'gear'
#003: vfil_w              , VehicleSpeed                    , 381BC8, 2, 0000, 0, 0,   0.0078125,   0, 'km/h'
#004: wub                 , BatteryVoltage                  , 3808B2, 1, 0000, 0, 0,      0.0704,   0, 'V'
#005: tmotlin             , CoolantTemperature              , 38489F, 1, 0000, 0, 0,        0.75,  48, '░C'
#006: tanslin             , IntakeAirTemperature            , 384899, 1, 0000, 0, 0,        0.75,  48, '░C'
#007: wped_w              , AccelPedalPosition              , 381C00, 2, 0000, 0, 0,   0.0015259,   0, '% PED'
#008: wdkba               , ThrottlePlateAngle              , 3809AD, 1, 0000, 0, 0,    0.392157,   0, '% DK'
#009: ti_b1               , FuelInjectorOnTime              , 381F18, 2, 0000, 0, 0,  0.00266667,   0, 'ms'
#010: te_w                , EffInjectionTime                , 381F16, 2, 0000, 0, 0,  0.00266667,   0, 'ms'
#011: zwist               , IgnitionTimingAngle             , 00FA04, 1, 0000, 1, 0,        0.75,   0, '░KW'
#012: dwkrz_0             , IgnitionRetardCyl1              , 380A79, 1, 0000, 1, 0,        0.75,   0, '░KW'
#013: dwkrz_1             , IgnitionRetardCyl4              , 380A7A, 1, 0000, 1, 0,        0.75,   0, '░KW'
#014: dwkrz_2             , IgnitionRetardCyl2              , 380A7B, 1, 0000, 1, 0,        0.75,   0, '░KW'
#015: dwkrz_3             , IgnitionRetardCyl3              , 380A7C, 1, 0000, 1, 0,        0.75,   0, '░KW'
#016: wkrm                , AvgIgnitionRetardKnockControl   , 00F9D4, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#017: rkrn_w_0            , KnockVoltageCyl1                , 384B52, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#018: rkrn_w_1            , KnockVoltageCyl4                , 384B54, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#019: rkrn_w_2            , KnockVoltageCyl2                , 384B56, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#020: rkrn_w_3            , KnockVoltageCyl3                , 384B58, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#021: fzabg_w_0           , CountMisfireCyl1                , 381844, 2, 0000, 0, 0,           1,   0, '#'
#022: fzabg_w_1           , CountMisfireCyl4                , 381846, 2, 0000, 0, 0,           1,   0, '#'
#023: fzabg_w_2           , CountMisfireCyl2                , 381848, 2, 0000, 0, 0,           1,   0, '#'
#024: fzabg_w_3           , CountMisfireCyl3                , 38184A, 2, 0000, 0, 0,           1,   0, '#'
#025: fzabgs_w            , CountMisfireTotal               , 381842, 2, 0000, 0, 0,           1,   0, '#'
#026: fr_w                , LambdaControl                   , 382708, 2, 0000, 0, 0, 3.05176e-005,   0, '-'
#027: fra_w               , AdaptationPartial               , 381F58, 2, 0000, 0, 0, 3.05176e-005,   0, '-'
#028: frm_w               , LambdaControlAvg                , 382704, 2, 0000, 0, 0, 3.05176e-005,   0, '-'
#029: lamfa_w             , TargetAFRDriverRequest          , 384AC2, 2, 0000, 0, 0, 0.000244141,   0, '-'
#030: lamsbg_w            , AirFuelRatioDesired             , 381F46, 2, 0000, 0, 0, 0.000244141,   0, '-'
#031: lamsoni_w           , AirFuelRatioCurrent             , 381B00, 2, 0000, 0, 0, 0.000244141,   0, '-'
#032: pu_w                , BaroPressure                    , 384A5E, 2, 0000, 0, 0,   0.0390625,   0, 'mbar'
#033: fho_w               , AltitudeCorrectionFactor        , 384A56, 2, 0000, 0, 0, 6.10352e-005,   0, '-'
#034: ldtvm               , WastegateDutyCycle              , 380ABE, 1, 0000, 0, 0,    0.390625,   0, '%'
#035: mshfm_w             , MassAirFlow                     , 00F9A4, 2, 0000, 0, 0,   0.0277778,   0, 'g/s'
#036: plsol_w             , BoostPressureDesired            , 381E60, 2, 0000, 0, 0,   0.0390625,   0, 'mbar'
#037: pvdks_w             , BoostPressureActual             , 381E00, 2, 0000, 0, 0,   0.0390625,   0, 'mbar'
#038: rl_w                , EngineLoad                      , 00F9B6, 2, 0000, 0, 0,   0.0234375,   0, '%'
#039: rlmax_w             , EngineLoadCorrected             , 382330, 2, 0000, 0, 0,   0.0234375,   0, '%'
#040: rlmx_w              , EngineLoadSpecified             , 382332, 2, 0000, 0, 0,   0.0234375,   0, '%'
#041: rlsol_w             , EngineLoadRequested             , 381EB6, 2, 0000, 0, 0,   0.0234375,   0, '%'
#042: tabgm_w             , EGTModelBeforeCat               , 3849CE, 2, 0000, 0, 0,   0.0195312,  50, '░C'
#043: tats_w              , EGTSensor                       , 384B16, 2, 0000, 0, 0,   0.0195312,  50, '░C'
Logged data size is 74 bytes.
Really logged are 41 entries with 74 bytes.
FTDI library version 30207
Start connecting to ECU at 02.02.2016 18:17:10.077
try connect slow(11)
try connect slow(11)
Could not connect
try connect slow(11)
18:17:15.582-216,3 os_setspeed(speed=10400)
18:17:15.583-136,3 os_receiver_off()
18:17:15.884-386,5 os_setbreak()
18:17:16.084-386,7 os_clrbreak()
18:17:16.284-386,8 os_setbreak()
18:17:16.484-387,0 os_setbreak()
18:17:16.684-387,1 os_setbreak()
18:17:16.884-416,6 os_clrbreak()
18:17:17.084-387,4 os_setbreak()
18:17:17.284-387,6 os_setbreak()
18:17:17.484-387,7 os_setbreak()
18:17:17.684-387,8 os_clrbreak()
18:17:17.685-329,9 os_receiver_on()
18:17:17.686-477,2 ftdi_purge_rx() flushed 3 bytes
18:17:18.187-339,0 os_rcvbyte(timeout=500) -> TIMEOUT
try connect slow(11)
18:17:18.188-733,4 os_setspeed(speed=10400)
18:17:18.190-940,9 os_receiver_off()
18:17:18.492-109,7 os_setbreak()
18:17:18.692-109,1 os_clrbreak()
18:17:18.892-109,2 os_setbreak()
18:17:19.092-109,4 os_setbreak()
18:17:19.292-109,5 os_setbreak()
18:17:19.492-109,7 os_clrbreak()
18:17:19.692-109,8 os_setbreak()
18:17:19.892-110,7 os_setbreak()
18:17:20.092-110,8 os_setbreak()
18:17:20.292-110,3 os_clrbreak()
18:17:20.292-981,2 os_receiver_on()
18:17:20.294-101,4 ftdi_purge_rx() flushed 3 bytes
18:17:20.795-246,9 os_rcvbyte(timeout=500) -> TIMEOUT
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...

Try a lower baudrate, unplug cluster fuse, disconnect cluster, or a dedicated k-line for logging

do you have the laptop powered from the car , Ie , inverter or anything ? I seen this when I had an old laptop running in the car through an inverter charger , but because my new laptop runs for hours on its own batter , I have never seen the problem.

cheers nyet tried slower rate, never did try pulling fuse as everything else works fine through obd, if that works i'll run a dedicated k-line.  :)

Didnt have laptop powered nope just on battery. thanks.

Thanks Nyet, removed fuses 11 & 15 and now i can connect  ;D i will attempt the dedicated k-line over the weekend so i can see my speed while logging lol.

My Euro passat doesn't have fuse 11. And fuse 15 doesn't turn off the cluster (as in the fuel, temp, tachometer don't drop). Any specific other fuses? I've removed all the ones that look like cluster fuses on the fuse card, and nothing still. I'm probably going to have to wire up a second OBD port.

Any specific instructions for wiring up another OBD port? Like best place to join the wire from, etc?

You don't need another OBD port, just use the one you have. What you need to do it take the K-line from the ECU directly to the port and bypass everything else on the bus, like the cluster, to be able to log and flash with no issues.

Now I'm not saying what I did is correct, but the post below details how I tackled the problem. I was tired of pulling the fuse and messing around to log and flash and wanted a more permanent solution. I had the soldering iron out for another project and a few beers in me and this is what I came up with. It has worked flawlessly so far. I put the switch behind my fuse door in the trim panel for easy access. Want to log, switch to bypass. Want to scan something else on K-line, switch on normal. All you need is one double pole/double throw switch and some wire:

http://nefariousmotorsports.com/forum/index.php?topic=6679.msg70602#msg70602

I wound up wiring up a second OBD port under the steering wheel, like this: http://nefariousmotorsports.com/forum/index.php?topic=9741.msg86271#msg86271

Also, I noticed when the switch is open, car can't start (must be the immo), and also when there is a cable in the second OBD port (switch open/closed, have no idea why). But was finally able to take logs using me7logger.

Also, I think the runway needed to do a WOT pull in third gear is quite long. Our roads are not that straight. Can I do a 1st or 2nd gear pull instead?

Yes but you won't get EGT up to where to need to to judge if you have it under control, and your boost PID really needs to be tuned at all gears (you don't really have to run it to redline, but you do need boost spike under control).

Also, if you are using LAMFA to do primary fueling, the time constant will cause fueling to behave differently in every gear.