made a custom PID to log boost, after upgrading to 2.24 now the function doesnt work. I have tried every configuration but to no avail. Please help
made a custom PID to log boost, after upgrading to 2.24 now the function doesnt work. I have tried every configuration but to no avail. Please help
And all but 2 tabs in the Histogram are showing Unsupported Parameter, including the preloaded ones. And I'm not seeing a MAP signal in the Chart display. WTF ?
post your scanner log.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
dont know what went wrong
update ?
You aren't logging map, you need to log it in the table display to actually see it in the other displays.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
You need to ad MAP to MAIN TABLE.
If you are saying you can not find MAP to be able to ad to MAIN Table then goto your Documents/hptuners/vcm scanner/vehicle and delete your vehicle .os file.
Then reconnect and it should repoll your vehicle to get them back.
have 3 Bar MAP in the table, that doesnt satisfy the requirement ?
do I delete the entire file or just the ".os" portion of the file ?
I am not seeing any Map in your primary table, delete the whole file.
it was there before I uploaded the log file, i'll check when I get home
Double checked the Table Settings and it's showing 3 Bar MAP as a parameter, I also deleted the .os files and reconnected to the vehicle but still not fixed. Everything was working fine in 2.22
Uploaded the wrong file, but it wont matter it still doesnt work
seems to be working fine. You aren't logging RPM so histogram #2 can't work but other than that the software is doing what its told.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
All parameters are loaded in the Main Table, when scanning some drop off, i.e. RPM. Also all tabs in the Histogram are now showing Unsupported Parameter
I switched laptops and everything works fine, not sure why the hardware problem all of a sudden