Nissan Logger Support

unklejoe · **Joined:** Sun Jul 07, 2019 8:58 pm **Posts:** 10

dschultz wrote:

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....

I'm having some trouble with this. I've defined an ecuparam, but it's not appearing in the list of parameters when I open the logger. I've confirmed that I'm using the correct definition file and that the ECU ID matches (and is the proper case). The ECU ID is "CD002", for reference.

I've even tried to change the "ecu id" of an existing param to match mine, but no luck.

Any suggestions? Is there a way to specify a wildcard ECU ID, maybe just to test?

It's worth noting that the regular parameters can be logged just fine.

I tried to attach the log file, but I'm getting some server error. I did take a look through it and confirmed again that my ECU ID is correct though.

Thanks!

a33b · **Joined:** Sat Jun 24, 2017 2:23 pm **Posts:** 315

Post the except from the logger def of the entire ecuparam your trying to log

unklejoe · **Joined:** Sun Jul 07, 2019 8:58 pm **Posts:** 10

a33b wrote:

Post the except from the logger def of the entire ecuparam your trying to log

I figured out my issue - I added it to the wrong protocol group :roll:

Anyway, here's the parameter. It works now. I compared it to the existing "calculated load" parameter, and they differed by only a few percent at idle.

Code:

                <ecuparam id="JM00" name="vQH0 (Load)" desc="TVO-N flow-quantity vQH0" target="1">
                    <ecu id="CD002">
                        <address>0xFF859C</address>
                    </ecu>
                    <conversions>
                        <conversion units="%" storagetype="uint8" expr="x/2.56" format="0.0" />
                    </conversions>
                </ecuparam>

dangt84 · **Joined:** Mon Aug 26, 2019 9:05 pm **Posts:** 24

Hi, I have a general logging speed question - I've had a go at connecting too and logging some parameters on my 03 G35 (AC011) and although the data seems to give good resolution (data points per second) it is very delayed. I can hit record and do a pull on the Dyno, come back to idle and then I can watch the Engine Speed Pid start to slowly count up (I'm still at idle). A short drive around the block seems to give me minutes of delay.

Is this just a limitation of the K-Line connection or could I be doing something wrong here?

PC is a reasonably quick i7 and using the OpenPort2.0 connector.

Either way it is better to have SOME datalogging than NONE so I thank you for all of your efforts!

a33b · **Joined:** Sat Jun 24, 2017 2:23 pm **Posts:** 315

That is very unusual behaviour. My logging experience exhibits no delays whatsoever. I've logged for hours continuously.

dschultz · **Posted:** Wed Sep 25, 2019 8:35 pm

dangt84 wrote:

Hi, I have a general logging speed question - I've had a go at connecting too and logging some parameters on my 03 G35 (AC011) and although the data seems to give good resolution (data points per second) it is very delayed. I can hit record and do a pull on the Dyno, come back to idle and then I can watch the Engine Speed Pid start to slowly count up (I'm still at idle). A short drive around the block seems to give me minutes of delay.

What's the CPU % when this happens?
Do you have a SSD or spinny drive?
Logging is performed and displayed in real-time.

dangt84 · **Joined:** Mon Aug 26, 2019 9:05 pm **Posts:** 24

I will record a small log tomorrow and video the process. It has been very repeatable so far. I will double check the CPU etc. The PC is still very responsive when it's logging.

Also I should note that the recording matches the screen. If I don't sit and watch the full dyno pull play out on the logger it doesn't save it to the log.

dangt84 · **Joined:** Mon Aug 26, 2019 9:05 pm **Posts:** 24

I figured this out by accident. I was recording a video clip and started to play around with settings.
I unchecked "Enable Fast Polling Mode" and the datalogging become realtime.

I hadn't purposely had that option checked so maybe its from when I've tried logging other manufactures via RR.

Hopefully this info may help someone else that faces the same "issue" that I had. :oops:

a33b · **Joined:** Sat Jun 24, 2017 2:23 pm **Posts:** 315

Still shouldn't have that much effect. Both slow and fast polling work for me, the only downside to fast polling is it takes a while to adjust when you add or remove parameters. Occasionally RR hangs for a bit and has some trouble re-establishing a connection, but while logging, never an issue.

Are you doing this on the dyno tab? Or the main logging screen?

dangt84 · **Joined:** Mon Aug 26, 2019 9:05 pm **Posts:** 24

Main data list and gauges etc were acting the same.
I will upload the video and post a link.

dangt84 · **Joined:** Mon Aug 26, 2019 9:05 pm **Posts:** 24

Video link:
https://drive.google.com/open?id=10be7d ... VkCdyL5-BG

The longer I was recording the more out of sync the data would get.

dschultz · **Posted:** Thu Sep 26, 2019 8:12 pm

I'm not sure what would cause that delay. I use an old dual-core Pentium and my CPU while logging 80 samples/sec is about 4%.
Can you submit the rr_system.log?

RomRaider

Forum rules

Nissan Logger Support

Who is online