3200 is a decimal value.
If it is represented in a hexadecimal system, it looks like this: 0xC80
So more familiar?
You can use both recording methods …
Hello, guys…
Sorry, but I still do not understand anything in this protocol …
you can write with a simple example what XML should look like for a standard Engine-RPM request
CAN 11 bits.
engine ECU x7E0 - x7E8
Pid of RPM - standard - 01 0C
I need make request (id, Len, Data1, Data2): x7E0 02 01 0C
I need get answer (id, Len, Data1, Data2): x7E8 02 01 02
and yes, I watched your example with arduino, where the ecu is emulated to 3200, 3201, 3202… .
therefore, I ask how to change your example from an ECU-emulator to a real ECU.
that’s what I don’t understand.
the fact that in the can monitor you can see frames that are part of the OBDII protocol does not mean that it is possible to implement this using the CAN protocol., More precisely, it is just possible to implement it. But for this, you still need a symbiosis from the sender and the listener. This is not implemented using the CAN.XML file.
It’s easier to use OBDII, in your case you turn to the engine ECU 7E0, and expect a response from it 7E8
Hi guys, excuse me again, but I didn’t understand anything.
Does this mean that the RealDash does not know how to accept the most ordinary RawCAN?
there are so many different connection methods, but there are no RawCAN?!!!
or am I misunderstood something?
Just, How RealDash can work with RawCAN data? What SourceConnection I must select?
The feeling is mutual, I don’t understand what you are saying.
If you are reading the CAN frames on your custom hardware, use the ‘RealDash CAN’ protocol to transfer the ‘raw’ CAN frames over serial to RealDash. Arduino examples are here:
I read your example a week ago. and I wrote to you in the first post that I did NOT understand ANYTHING in it …
I am not a professional programmer.
I just ask for specific help. I wrote the CANID of my engine block (7e0-7e8) and the desired pid (010C) and please give an example of RealDash-CAN XML for it. this is just three lines from you.
my HW just must recieve from RD
7e0 02 01 0C
and send answer
7e8 02 xx xx
but you send me to read something that I can’t figure out …
great advice !!!
Again all your example addesses are ELM327 OBD2, not CAN. There is no concept of ‘PID’ in CAN bus. I believe that we have tried to explain this to you and you have basic concepts of OBD2 and CAN mixed up and that makes it very difficult to give you any advice.
7e0 and 7e8 from the first plst is OBDII, it is not RAW-CAN.
Study the documentation on Wikipedia on protocols, it is very difficult to explain everything from the very beginning.
RealDash can do absolutely anything.))) But this requires knowledge and practice.
I once started this topic because I thought, that I don’t understand the protocol.
Well, apparently, my problems started with some hardware mistakes, and now when I improved that, I can receive messages, and I don’t have difficulties with matching addresses and factors/offsets etc.