RomRaider

viewtopic.php?f=65&t=13566

11xx 14xx response has one byte data
12xx 13xx response has two bytes data

Data availability response has 4 bytes as usual.

Internally the ECU could be using a word for higher precision calculations, but to the external world it's only sending the MSB which would result in a lower precision value.

The logger would complain if the number of bytes expected, and actually received from the ECU don't match.
In the Logger def, the parameter conversion attribute storagetype="uint16" tells the Logger to expect a word response, otherwise expect only a byte.

Pls tell me about supmask cid - for what first 32bit address. And how programs know what sid is support?

There is a usual test availability procedure.
Request 1100, 1120, 1140 .. 1200, 1220, 1240.. etc.
4 bytes response will tell what data requests are applicable.

A33b, thank you so much. If i correctly understand, i can agree support check different cid number. For example cid221223 not support but ram address have, can we change bit 0 to 1 and see parameter?

Yes, you can, but it will not necessarily contain valid data.

If you want to log arbitrary RAM addresses, there's no need to hack CID support bits.

Just create a new logger.xml entry for the address(es) of interest. For example, to log a byte from RAM:
To log a word from RAM:
Items to note about custom RAM address entries in the logger.xml

• ecuparam id - must be unique within the <ecuparams> list
• ecuparam name - the name to display in the parameter list
• ecuparam desc - a more detailed explanation of the parameter and the hover over Tool Tip string
• ecuparam target - 1 for ECU, 2 for TCU and 3 for both
• ecu id - required, must be the ID of the ECU your are logging from, can also be a comma separate list of ECU IDs if the RAM address is valid for each ECU ID
• address - must be 6 characters long, excluding the 0x
• address length - 1 for byte (if omitted this is assumed), 2 for word, 4 four float or integer
• conversion - you can have as many as you want/need
• conversion storagetype - if omitted the value is assumed to be uint8, if a word is requested (length 2) this must be set to unit16 or int16 whichever is appropriate for the data, other values supported, int8 (length 1), int32 or float if address length is 4.
• conversion gauge min/max/step - these are optional, if provided they describe the values on a dial gauge

For additional conversion examples you can can look at parameters in the SSM and OBD protocol sections of the Logger.xml file. You will find examples of 'bitwise' and 'if x='.

I have some problem with use RR windows xp. How can i start app? Dont support choise.exe..

Choice.exe was first made available in the Windows XP resource kit. Can you load it?

Otherwise, just make you own run.bat file to start the Editor, such as this:
And replace <JAVAW_EXE_PATH> with the full path to javaw.exe

It's working for me. If i copy choise i have errror. Thank you.

Hello. I try connect to the nissan tiida 705519n ecu EM63B with RR logger and i have no result, dont connect. Maybe ecu have something different. Can you help me?

Send the rr_system.log.
http://www.romraider.com/index.php/RomRaider/HowToDebug

I recently wrote that I can not connect. forgot to specify that ecu can-only. how can i add support for can-ecu. Is it possible to add addresses, because its right addresses. But will it work?

<transport id="iso15765" name="CAN bus" desc="CAN bus logging.">
<module id="ecu" address="0x000007E8" desc="Engine Control Unit" tester="0x000007E0" />
<module id="tcu" address="0x000007E9" desc="Transmission Control Unit" tester="0x000007E1" />
</transport>

may still need another adapter? like vag k + can?

There is currently no Nissan CAN support in the Logger. If you can define the Nissan specific implementation details then it can be added in the future.