pcmhacking.net

depending what car your logging, if it has a data bus and if the bus is silenced for logging various things wont work while logging. This is not an aldldroid issue, its an architectural limitation of the car, and would also affect tunerpro, or tuning in general.

If its not that, then it might be an issue with the aldl interface, or a noisy electrical system in the car and that 1 extra device on the bus is the straw that breaks the camels back.

Correct, VS V6 (and later model V6) you will lose the low speed fan control while logging. High speed fan kicks in at a higher temp so the temp gauge will be higher than normal.

VL400 wrote:Correct, VS V6 (and later model V6) you will lose the low speed fan control while logging. High speed fan kicks in at a higher temp so the temp gauge will be higher than normal.

So hypothetically, if i were to set the highspeed fan temps to equal my low speed fan temps, the highspeed will still work and allow me to log at the same time? its a really cool app and i love the ability to be able to see what is going on with the car as im crusing around

hoosedamoose wrote:So hypothetically, if i were to set the highspeed fan temps to equal my low speed fan temps, the highspeed will still work and allow me to log at the same time?

Yep, lower the high speed on temp and shouldn't have a problem while logging.

antus wrote:depending what car your logging, if it has a data bus and if the bus is silenced for logging various things wont work while logging. This is not an aldldroid issue, its an architectural limitation of the car, and would also affect tunerpro, or tuning in general.

If its not that, then it might be an issue with the aldl interface, or a noisy electrical system in the car and that 1 extra device on the bus is the straw that breaks the camels back.

Ive never had an issue with logging on tuner pro, drive around for hours at a time, thermofans have always kicked in when they were supposed to. this has only changed with using aldldroid. its a bit weird though

Are you sure its the same ADX? Are you using oseplugin in TP? ALDLdroid does what the asks like it should, and TP will follow the ADX as well when not useing the plugin. But when you are using the plugin it needs to change the logic a bit to share the ALDL bus between logging and emulating, so that could be affecting logging setup in TP+OSEplugin mode.

antus wrote:Are you sure its the same ADX? Are you using oseplugin in TP? ALDLdroid does what the asks like it should, and TP will follow the ADX as well when not useing the plugin. But when you are using the plugin it needs to change the logic a bit to share the ALDL bus between logging and emulating, so that could be affecting logging setup in TP+OSEplugin mode.

Yeah its the exact same adx. I've modified it for the wideband readings. I'm also using the ose plugin too.

yep, its hard for the plugin to man in the middle the detect silence and disable chatter part, so it trys to manage it itself. probably the silence chatter is failing with the plugin. the answer to this is to use the plugins own silence chatter feature -> thats the vehicle type drop down box. Currently it only has VT and later as they're the ones that really need it. Perhaps I need to add support for VS too. ALDL Droid is doing the right thing. Having the bus silenced probably prevents an occasional error here or there when something else talks on the VS bus (although the bus is pretty quiet in the VS, so you should be fine to just keep doing what your doing, too).

Jayme how did you connect the 852 via usb? host mode?

just bought a cheap OTG cable off ebay and plugged the usb from the AVT straight into my S5.