RomRaider

What information do you need to know? How can I help?

I need to know how Nissan implemented their logging protocol over CAN. Did they just replace the protocol headers and keep the same PID/CID structure? Is there any special session starting and closing sequence? Any security?
A capture of a functional CAN logging session would be helpful.

Mode 22 extended OBD service.
The same way as Subaru Mode 22 ( it is not SSM over CAN ).
There is no Mode 23 for direct RAM reading,
Probably there is a "window" for RAM\ROM reading over mode 22 similar to Nissan Consult k-line commands.
Maybe original Nissan equipment use additional protocol besides OBD mode 22.

viewtopic.php?f=65&t=13566

No start\closing is required.

Thanks.
Then I need a CAN enable ECU to test with. Very hard to write a protocol handler without a test bed. What ECU would you recommend I could get in North America?

There are two options for Subaru minded developers:

- use Hitachi MY08-10 Forester\MY08-10 Exiga\MY10 Legacy NA ecu and download compatible NA Nissan ROM. Probably those Hitachi ecu's are not available in North America.
- use MY07-MY12 Denso ecu and download compatible SH7058\SH7058S Nissan Navara \ Pathfinder ROM.

Petrol and diesel ecu have different extended PIDs. Scaling is evident in Denso ROM similar to Subaru.

You may verify Denso ecu "compatibility" by primary bootloader code comparison.
And download the ROM under test in bootmode.

Any MY08+ Nissan ecu provides extended OBD communication. Thus you may simply use any Nissan NA MY08+ for testing.

Some logs CAN tx/rx consult to ecu.

My analysis of ZY70D would indicate that's exactly what they did. The code for the SIDs is identical to CM31C/CF43D. From my inept position, it seems like it would be as simple as swapping the K-line protocol for CAN.

I now have in my possession an '09 Altima ECU for CAN logging development.

I haven't seen much feedback on the k-line Logger, it can't be perfect after the first release...

Nice to see all these developments taking place. Since I am still not able to connect to my 350z HR using nisprog over k-line I am cheering on the development of the CAN protocol @dschultz! I now have another solution for writing to the ECU but still am looking for logging capabilities. If I can help testing it please let me know.

Friends of mine have been using the k-line logger on one or two cars already without issues (EU CD700 models). Can't say it's a non-perfect release so far

Not a Nissan related issue, but when I resort the loggable parameters the hover over descriptions don't change position. So the descriptions only work for the default sort order.

I noted that and fixed it already, thanks.

Thank you!

The logger works pretty good, within the confines of K-line. I haven't had very good success resetting a logging session. For example, if my laptop goes to sleep or I close the lid, when I return I can't just re-connect. I have to close the logger entirely and re-open it. The "re-connect" isn't working for me.

great logger work for k-line, of course I would like to see can logger support.
i can read ram addr so simple)))

Big thank you for this software!

I've been meaning to try for a couple of months on my jdm v35 skyline am900 ecu and decided to give it a go, and it works great.

I can even log my techedge wbo sensor.

I had an innovate lc-2 + nds2 but the wbo reading was erratic so pulled it out. nds2 does't support non-innovate wbo so I was stuck until now.

Cheers

Great point to start


this is, what we are waiting for logging the GEN4 E6 Diesels and new petrol Subarus.
Lists for Subaru Diesels PIDs are allready here in the forum.

AND:
at the end, SSM-IV, as well as Nissan or VAG or some chinese cars, Mode 22 is UDS, witch is used by a lot OEM for workshop diognosic.
So if we (you) implementate Mode 22 for logging, we can be open for OBD and OEM specific logging.
We only need to define PIDs in the logger deffintions.

So RR-logger can be traied-open logger, if we know PIDs addresses
For ME a gread new staring point for "next-generation" RomRaider Logger..

Only OEM-specific logger deffinitions are a point to think about, because with only one deffinitonfile, the size and infos are too mutch IMO