i sure did. it all works fine with no logged error codes but the cel light is on when running?

i have been running the ose12 code in my 355ci vs man ute for 6 months or so it has been awesome no probs. and now i have just put my new comms board in the 808 for a vn/vp and it works great but i am having trouble with the nvram possibly. i have burnt the ose12 to the ram module and the car runs a...

It wont allow me to connect to the emulator while logging is connected i have to disconnect from the logging by pushing the logging button and then i can detect attached hardware otherwise it does not pick it up

Disabling the bcm first via flashtool worked thanks jayme the adx did not work it showed some correct values but others jumped around i could not have the emulation going and the logging going at the same time is that normal?

sweet i will give it a try on a s/c vt tomorrow and report back!

thanks for your time jayme. yes i have tried most of the things you mention apart from the disabling the bcm chatter which i will try tomorrow the flashtool works fine as long as i select f5 so maybe the tp 5 plugin does not like the bcm.

no i have not that looks like a great adx though! i am unable to get tp 5 to pick up the ecu with the nvram to emulate so i can start tuning i have no idea what is wrong?!

yeah, i have the nvram installed in the vt ecu and tp5 with the plugin will not pick it up so i cannot do any realtime tuning it works fine with my vs and vr but not with the vt?

hi antus, the update allows the new tunerpro to pick up the plugin but it does not work on the vt v6 s/c ecu with the nvram installed still tp 5 will not pick up the nvram as an emulator i have tried both echo on and off not sure what else it could be? any ideas

the one supplied in the realtime tunes section is that not the correct one to use?