pcmhacking.net

denchy wrote:So i pulled out a bunch of fuses and it started working fine, placing the fuses back in while it was running found the one that causes the problem.

7.5A fuse labeled
ECC HTR CONT.
INST. TRIP COMP

got a few copies of the bin now
Thanks for the help

could be your instrument cluster polling the bus. did you have it set to bench mode or in car mode?

Having the mouse issue but the com disable tool doesnt seem to work with windows 10. Was ok but last week it had a few niggles but now wont connect at all on the same car as last week. Any help or ideas would be very helpful.

HI Is it possible to put in custom data for the"send BCM Chatter" under the "Listen to chatter and send custom commands" window.
I would like to send custom chatter to determine the response from the cluster in a Vy

You can do what you need with just "Listen to chatter and send custom commands". Send any commands you need and monitor the bus there.

any chance of updating this or no

It wouldn't be impossible, but also not easy (only VL400 has source). I'm not aware of any bugs and its still easy to run on modern systems. That's the main things.

The FlashTool hasn't got any issues so no point.

Somewhat but not directly related to the FlashTool, there is a bug either with either 12P itself or it's ADX. The Baro never displayed/worked correctly despite VL400 having fixed it apparently.

to include other tools like OBDX Pro tools that support ALDL protocol

All the tuning tools use the standard Serial to ALDL. The OBDX Pro has ALDL for tech2win etc to be able to talk to aldl modules on the bus. They both have their place, but its not something we need, would be a big job and would probably cause more problems that it'd solve to add J2534 or OBDXpro protocol to these tools now.

i dont mind adding it if im allowed too