No to jeszcze takie cos :
Cytat:
Initialization String. The ECU will not communicate until a valid hex
initialization string message is detected.. (0xff)(0xff)(0xef) must be sent at the
correct baud rate with the clock present on the ECU clock pin.
Once Initialized the ECU responds with (0x10), it is then ready for commands.
2. Command format and sequence (as tested with a laptop and terminal program in
HEX mode).
Consult terminal (or PC) sends a query command whose value determines
function to be performed.
ECU responds with the same command byte but having inverted all bits as an
error check. Data send after a command is echoed same as sent.
E.g. Send (0xd1)(hex), ECU responds with (0x2e). For valid commands only.
Consult terminal sends a go ahead/terminate message byte (0xf0)
ECU responds with result of query starting with a frame start leader character
(0xff), then a byte it indicate the number of data bytes to follow, then the data.
ECU WILL STREAM THE REQUESTED DATA until forced to stop.
Consult terminal then sends a stop byte, Command 0x30
e.g. Send (0xd1)(0xf0) , Ecu replies (0x2e)(0xff)(0x02)(0x55)(0x00). Where 2e
is the inverted command, FF is the frame start byte, 02 is the number of data
bytes to follow, 55 is the fault code (55 = no fault), 00 is fault code MSB.
Read any Register Parameter (Live sensor data stream)
(0x5a)<parameter code to read>(0xf0) for single byte stream
(0x5a)<parameter>(0x5a)<next parameter>(0x5a)<next parameter>(0xf0)
for a multi-byte response stream. Maximum of 20 bytes.
terminate command with (0xf0) to start data stream, stop with (0x30).
i tu np. czytanie obrotomierza
Cytat:
Data Name Byte Register No Scaling
Tachometer MSB 0x00 See LSB
Tachometer LSB 0x01 Value * 12.5 (RPM)
I tera pytanie ... jak ustanowic polaczenie miedzy np Atmega a tym kompem ?
szczerze to dopiero zaczolem programowac uC i jak narazie gryze
bascoma