Hi!

Basically you enter the command as-is that you would normally send to an ELM327 based adapter.

So to ask for Speed, you would simply put into the box:

010D

and that's all!

Then '010D' is sent to the adpater every time you press the button (and the adapter then sends this to the ECU)

Thanks for the reply Piemm, point is, this is a custom Toyota PID (SET Hybrid battery fan)and i'm wondering where i can get the direct ELM command. Not from the standard OBD list.

Hi!

If you know the PID, then all you need to do is enter that PID into the box (just like for the mode 01 pid for speed). So if the PID is 220A02 then that's what you enter into the send obd command box. If you need to set any headers then that's a little more complicated but still achievable using the push button using ATSH to set the header first, then '\n' to separate the command and then the mode and pid straight after as per above.

If you don't know the PID yet, then you'll need to find that first before continuing, it's most likely already known on the toyota forums

Yes i know the PID and i already use it with the on/off button.

ModeandPid is 30810606
Equation A
Header 7E2

If you can help for the proper command i'll appreciate. Thanks a lot

Just tested on the car entering the ModeandPid only. It worked.

Problem is that puts ON only and to stop the command you have to change focus on another page. Any idea on how to have a real ON/OFF button?

try to add to your home screen, with devices, for example on the engine 7e0, Send Command button and at least one device for 7e2 block

Hi

The button at the moment isn't on/off, but is equivalent to a 'momentary' switch - the command is sent once when pressed

You can have 2 of them at the moment. One with the 'ON' command and another with the 'OFF' command to turn the fan on/off.

I'll add an on/off capable button once I've finished working on the long PID mods to the app(which are consuming a bit of time completing)

Quote from admin on August 16, 2016
You can have 2 of them at the moment. One with the 'ON' command and another with the 'OFF' command to turn the fan on/off.

I tought to do sometihing like that, cause of course i have the PID for fan off. But the situation must revert to the normal management of the car software, which could be any speed, that is the default auto.

That is, the thing needed is just to *NUL* the command, not to send another set command. Unfortunately a SET AUTO does'nt exist.

Bear in mind for that very interesting enhancement of the Push Button.
Looking to similar app "push button" , it should'nt be a difficult task.

And when you'll work on the PUSH BUTTOn, don't forget that there's no edit of their theme and size, which is not good.

Many thanks for your help.

send command atsh7e2\n30810606
programm does not understand
https://yadi.sk/i/Df9-ffNmuFvb2

Apologies - you can press 'enter' to add a new line (\n in 'code' speak I accidentally said) and this will send multiple commands.

Or If you want to keep it on one line, then use ';' as the separator

cintak, don't add the header change, just the plain 30810606.
It works.

Quote from cintakc on August 16, 2016
try to add to your home screen, with devices, for example on the engine 7e0, Send Command button and at least one device for 7e2 block

Mmmm, can you explain a little better? Are you saying to send whatever else 7E2 command to stop the previous Fan command?

For it to revert to the previous speed setting, you'll need to somehow tell the ECU to re-send it's fan speed setting again - because this is a diagnostic thing it's unlikely to have a facility to do that

On a more hacky side of things, it may be possible to spoof the temperature readings to the ECU, so send 'I'm cold' then 'i'm hot' to the ECU and see if it resends the fan control command. This is pure guesswork though.

Well, what happens when you turn the page and the command is voided? Is the right thing.

If i do that, situation revert to the previous status. What affect the turning of the page, must be simply associated to the OFF feature.

I would add that seems unappropriate that on the push button the change of the colour to red is not permanent and revert to green: this way, theoretically, you don't have a clue if your spoof is working or not.

About the temperature spoofing, you are giving me some idea, because our hybrids have some issue... when the "push on/off" will be ready, i'll think about.

so works
https://yadi.sk/i/B4ZXla2luFy3U

Hi!

Nothing really happens - the command isn't voided as it's already been sent once (when you pressed the button)

It is not continually sent, it's only sent when you press the button, and there is no 'un-command' done

What might be happening when you swap screens is that it could be simply timing out the command on the ECU, *or* you have another PID setup on another screen that's an extended one, that's setting a different fan speed?)

To clarify, the 'send command' push button, only ever sends the command when the button is pressed, and it sends it once. press it again, and it will send the command once more. So if you press the button 3 times, the command is sent 3 times

Quote from admin on August 16, 2016

What might be happening when you swap screens is that it could be simply timing out the command on the ECU,

This is it, timing out; it is already known that the ECU, not receiving instruction for more than 2 seconds, revert to the previous fan setting (auto).

But this doesn't sound to me fitting the single impulse of the command you mentioned. For sure it's me not understanding "timing out" what does it means here.

Ok, that's good - if the ECU times out the command then you just need a 'latching' kind of pushbutton to continually send the command. I can add that easily enough (once we've worked out what weirdness here is going on)

So, correct operation at the moment should be, press the button, and the fan should do whatever is commanded for at least 2 seconds, then revert back to the previous setting defined by the ECU (as I guess the ECU continually sends the fan speed command in this instance every 2 seconds)

That means that, for the fan to be continually at the commanded speed, it will be:

* The command is being continually sent, when it should not be - this shouldn't be happening in the app and the button isn't capable of pushing itself (unlikely, will be testing here just incase)

or

* There is an extended PID somewhere with this command in, and that's on the screen, visible and that's continually sending the command until you swap screens (fairly likely), or a PID/display that is perpetuating the fan speed command somehow by simply being sent

or

* There is another command on adjacent screen that's being sent in an extended PID that puts things back to normal (unlikely)

It's going to be one of the above causing this behaviour. I'm going to test the command button tonight and double check that it's doing what it should be.

If you could send a debug that'd be great. You can send a debug by enabling debugging in the general settings, restarting the app, going to the main screen with the button. pressing it. waiting 5 seconds then going to another screen and then presss menu, send debugging info and put 'fan speed' in the debug (so I can locate the debug). I'll have a look and see what's being sent

No wait, it does'nt need sending continously the command, 1 time is enough and keep working!

The timing out of the 2 seconds comes only when you turn the page!
So only if you turn the page for some second the command is voided and the fan revert to the original speed, otherwise go forever to the speed set by the command.

Hi!

Right! - that means another command is being sent that is cancelling the set condition for the fan, and most likely it is on the second page, or that you have a display on the same page as the pushbutton that's causing this

I'll need a debug to understand further