Don't see a way to contact you

request: 7e0 10 01
request: 7e0 10 03
request: 7e0 10 c0
request: 7e0 19 02 0f

request: 7e0 21 80
request: 7e0 21 83
request: 7e0 21 fe

request: 7e0 22 1001
request: 7e0 22 1301
request: 7e0 22 1302
request: 7e0 22 1303
request: 7e0 22 1304
request: 7e0 22 1305
request: 7e0 22 1306
request: 7e0 22 1307
request: 7e0 22 1308
request: 7e0 22 1309
request: 7e0 22 130a
request: 7e0 22 130b
request: 7e0 22 130d
request: 7e0 22 130e
request: 7e0 22 1312
request: 7e0 22 1313
request: 7e0 22 1315
request: 7e0 22 1316
request: 7e0 22 1319
request: 7e0 22 131b
request: 7e0 22 131c
request: 7e0 22 131e
request: 7e0 22 131f
request: 7e0 22 1321
request: 7e0 22 1502
request: 7e0 22 1503
request: 7e0 22 1504
request: 7e0 22 1505
request: 7e0 22 1506
request: 7e0 22 1507
request: 7e0 22 1508
request: 7e0 22 1509
request: 7e0 22 150a
request: 7e0 22 150b
request: 7e0 22 150c
request: 7e0 22 150d
request: 7e0 22 150e
request: 7e0 22 150f
request: 7e0 22 1510
request: 7e0 22 1511
request: 7e0 22 1512
request: 7e0 22 1513
request: 7e0 22 1514
request: 7e0 22 1515
request: 7e0 22 1516
request: 7e0 22 1517
request: 7e0 22 1518
request: 7e0 22 df10
request: 7e0 22 df11
request: 7e0 22 df12
request: 7e0 22 df13
request: 7e0 22 df15
request: 7e0 22 df17
request: 7e0 22 dff1
request: 7e0 22 f100
request: 7e0 22 f188
request: 7e0 22 f190
request: 7e0 22 f191
request: 7e0 22 f194
request: 7e0 22 f1a0

request: 7e0 2e df01 00
request: 7e0 2e df12 00

request: 7e0 2f df01 03

request: 7e0 31 01 df03

Looking for where I might be able to find logs or mocks of these UDS $22 data identifiers

For Zavrus

for RomRaider Editor v0.9.2:
Currently, bitwise switches exceeding 8-bits show incorrect bits as being enabled.

On top of this, the bitwise switches aren't following the specified order in the A2L file. This one is potentially a RomRaider bug, but analyze A2L.xml to see if anything can be done first.

Update 1:
Bitwise switches that are 1, 2, or 4 bytes can be specified using sizey="1" and the proper storagetype. RomRaider bug prevents using a sizey that's greater than 1 at this time.

Bitwise switch ordering is being sorted alphabetically rather than being based on order in the definition file. This is entirely on RomRaider's end and an issue has been opened on RomRaider's GitHub.

Update 2:
Any bitwise switch that current uses anything with a sizey > 1 needs to be switched to using uint16/32 instead. The full DTC list will unfortunately have to be split into separate DTC supmasks as there's no way to have a bitwise switch larger than 32-bits anymore.

Hey, how are things going on the defs side...

bradsm87 makes a good point, that it may be more convenient to sort and classify defs according to the more permanent mProgver string instead of ECUID.

https://www.romraider.com/forum/viewtopic.php?p=172370#p172370

(I may someday update my own tools accordingly).

Going to keep this here until I figure out a better place to put it.

Undefined ROMs:

• CD000 (P)
• CD001 (P)
• CD002 (P)
• CD006
• CF010
• CF170
• CS500 (m45)
• AM607
• 6Y303
• EV18A
• Check Stock ROM List for more

Further Defining Needed:

• AC510
• CE860
• AM905
• CF065

Properly utilize the userlevel attribute for all parameters.

CF020 Not Working or Defined

No tables are visible in RR once this ROM is opened with the listed def.
If needed, I can upload the ROM.
Please help.

Car is a 2005 JDM 350Z, VQ35DE, 5AT.

Certain DTC bits are inaccurate inside the DTC template due to errors splitting the Master DTC list into 24 individual longword bitwise switch tables.

when i try to open my dump, it says definition not found please help

Due to altering how I set up the DTCs, every ROM will need to be ran through the DTC offset calculator in order to utilize DTCs.

The updated A2L template will not be pushed until this is done.

bit position 4 & 5 have the same name "Unknown 5 -" causing RomRaider to show only one of them, which makes it impossible to correctly change the bit flags.

Original:
<table type="BitwiseSwitch" name="Cruise Control, PTD Open-Degree Operation Switching Flag" category="Options//Flags" userlevel="1"> 0x80 <bit position ="7" name="Unknown 7 -"/> 0x40 <bit position ="6" name="mfPTDASCD - At the time of ASCD, PTD open-degree operation switching flag // Can't use for autos I don't think."/> 0x20 <bit position ="5" name="Unknown 5 -"/> 0x10 <bit position ="4" name="Unknown 5 -"/> 0x08 <bit position ="3" name="Unknown 3 -"/> 0x04 <bit position ="2" name="Unknown 2 -"/> 0x02 <bit position ="1" name="Unknown 1 -"/> 0x01 <bit position ="0" name="Unknown 0 -"/> <description>Toggle On/Off</description> </table>

Fixed
<table type="BitwiseSwitch" name="Cruise Control, PTD Open-Degree Operation Switching Flag" category="Options//Flags" userlevel="1"> 0x80 <bit position ="7" name="Unknown 7 -"/> 0x40 <bit position ="6" name="mfPTDASCD - At the time of ASCD, PTD open-degree operation switching flag // Can't use for autos I don't think."/> 0x20 <bit position ="5" name="Unknown 5 -"/> 0x10 <bit position ="4" name="Unknown 4 -"/> 0x08 <bit position ="3" name="Unknown 3 -"/> 0x04 <bit position ="2" name="Unknown 2 -"/> 0x02 <bit position ="1" name="Unknown 1 -"/> 0x01 <bit position ="0" name="Unknown 0 -"/> <description>Toggle On/Off</description> </table>

Comparing CF48D & CD415 in winols matches when mMITANDD & mMITANDA are interpreted as uint8[8][8], but they are uint8[16][16] in A2L.xml

Looking in Ghidra, the maps will overlap each other if the size is [16][16] instead of [8][8] which also shows up clearly in RomRaider

Good afternoon brother.

I tried to be able to use the definitions and apparently a correct one for my application cannot be found,

I'm trying to modify a (2) 2004 Infiniti FX35
Hitachi SH7058 EFI 705821N (1CL110)(1CG705)

I would appreciate if you could help me.

I attach the (2) .bin
1CL110-20230126-091542.zip
1CG705-20230126-193944.zip

Ensure Metric scaling is added for all parameters.

• Define O2 Sensor Placement flag

(ROM dump already obtained)

AC610.zip
AC610.zip

Hey mate

Turns out AC610 is 96% the same as AC510 so added the .xml (and the original .bin file) for you to add to your repository.

Thanks a million for these definitions!

Organize Master DTC list in numerical order and add all beneficial Sub-DTC lists.