Please make it possible in future versions for trigger actions to set values from variables obtained in an xml file, so that they can be assigned to text.
For example, in this field. Add the output variable
Use the ‘Select Input’ button and select your custom value from ECU Specific category.
Be aware though that if you set the value via action and value is also received thru RealDash CAN you will get ‘value fighting’ as both are updating the value at the same time.
It’s not what I want, and I don’t get what I need. And I need to get exactly the value when the trigger is triggered, and at no other time.
One of my signals contains 10 different sub-signals. And I only need to display one sub-signal, which I intended to display when an event occurs. And you need to output the value from this signal, not the text.
I’m sorry, I just do not understand what you mean 
See. I get signals at the entrance:
7E8 8 10 43 62 00 01 01 79 00
7E8 8 21 8B 00 00 00 00 00 00
7E8 8 22 01 2E 00 00 10 AA 00
7E8 8 23 00 80 FF 41 FF 80 00
7E8 8 05 6F 00 04 06 00 AA AA
7E8 8 05 6F 00 04 01 00 AA AA
7E8 8 10 43 62 00 01 01 79 00
7E8 8 21 8B 00 00 00 00 00 00
7E8 8 22 01 2E 00 00 10 AA 00
7E8 8 23 00 80 FF 41 FF 80 00
7E8 8 24 3E 00 00 80 00 00 00
7E8 8 25 00 00 73 00 00 00 00
7E8 8 26 04 55 01 8C 00 1F 00
7E8 8 27 00 00 00 8B 00 00 00
7E8 8 28 01 C0 00 04 A4 6C 9B
7E8 8 29 00 1C 1F 00 00 AA AA
7E8 8 05 6F 00 04 01 00 AA AA
I am only interested in the data of the 7e8 signal, which starts at a null byte containing the value 25. In this signal, I need the data contained in 1 and 2 bytes.
I made a trigger to search for a null signal, but I can’t output the data contained in 1 and 2 bytes of this signal to the text.
During the trip, this signal changes very quickly, and I also need to display this value on the screen
57,297000 1 0004 7E8 8 25 00 00 87 00 00 00 00
57,500000 1 0004 7E8 8 25 00 00 87 00 00 00 00
57,656000 1 0004 7E8 8 25 00 00 87 00 00 00 00
57,796000 1 0004 7E8 8 25 00 00 87 00 00 00 00
57,952000 1 0004 7E8 8 25 00 00 87 00 00 00 00
58,405000 1 0004 7E8 8 25 00 00 87 00 00 00 00
58,654000 1 0004 7E8 8 25 00 00 87 00 00 00 00
58,857000 1 0004 7E8 8 25 02 F5 87 00 00 00 00
59,044000 1 0004 7E8 8 25 02 F0 87 00 00 00 00
59,715000 1 0004 7E8 8 25 04 E4 87 00 00 00 00
59,855000 1 0004 7E8 8 25 03 3B 87 00 00 00 00
00,011000 1 0004 7E8 8 25 02 AA 87 00 00 00 00
00,167000 1 0004 7E8 8 25 02 3A 87 00 00 00 00
00,308000 1 0004 7E8 8 25 02 10 87 00 00 00 00
00,464000 1 0004 7E8 8 25 01 EF 86 00 00 00 00
00,916000 1 0004 7E8 8 25 01 D8 86 00 00 00 00
01,057000 1 0004 7E8 8 25 01 D8 86 00 00 00 00
01,213000 1 0004 7E8 8 25 01 D8 86 00 00 00 00
01,369000 1 0004 7E8 8 25 01 D3 86 00 00 00 00
01,556000 1 0004 7E8 8 25 01 DC 86 00 00 00 00
There is no such thing as ‘null byte’ maybe you mean that value is 0. Anyways, maybe somebody with better english could explain to me this case as I still have trouble understanding.
The signal consists of:
7E8-signal ID;
8-number of bytes in the signal;
25 01 DC 86 00 00 00 00 - the signal itself containing the information.
The byte count goes from left to right. In other words:
25 - 0 byte
01 - 1 byte
DC - 2 byte
86 - 3 byte
00 00 00 00 - 4, 5, 6, 7 bytes respectively.
Here is 0 bytes, i.e. where the value is 25 and you need to navigate.
Similarly, in your xml file, the notation B0, B1, B2, and so on
- Make a custom value in XML to read first byte only. In this example named ‘my25’
- In RealDash make a trigger for input ‘my25’ and trigger condition value=37 (which is hex 25)
- Set trigger reset condition to value != 37
Now you have a trigger that fires when this value changes to 0x25. Add any actions you wish to this trigger.
Yes, I did. But I can’t output a value that is contained only in the signal with byte “25”. That’s what I’m trying to convey.
Here is my xml:
Here, make the data source (a variable from xml) and the internal ID. In other words, when the trigger is triggered, a variable from xml is written. And the problem will be solved.
Please try it
In fact, you need to implement something similar to the OBDII protocol using RD CAN.
7E8 is the target identifier
B0- start of title
B1- heading
B2- team name
B3- end of team name
B4 - ECU first byte
B5- second byte of ECU response
B6-usually not counted
B7- usually not taken into account
It is necessary that if “B0” = 0x25, it would be possible
assign the current B4 + B5 = dummy var1, for example.
if B0 "= 0x56, one could
assign B4 + B5 = dummy var2, for example.
if B0 "= 0xFC, one could
assign B4 + B5 = dummy var3, for example.
etc…
to split one package into many different values this way!
One option is to use Hide/Show gauge actions to show your gauge showing the other value only when your 25 is active.
This is what I talked about, Artyom.
I don’t need to show or hide the sensor, I need to display a variable that is only contained in the signal number 25