Issues with new flexlogger setup and looking for ideas -> Logging raw CAN frames and initilizing XNET 9862 cards

[ARBaker]

Hi,

I've setup a new test system in a vehicle utilizing:

Hardware:

• cdaq 9189
• NI 9862 quantity of 4
• A few other analog input cards that may vary based on need (thermocouples, voltages etc)
• Used 2 different Dell laptops one is I5 8GB RAM and another I7 32GB RAM

Software:

Flexlogger 2020 R4

Drivers pretty much up to date; XNET ver 20. Daqmx ver 20

I have several problems/questions:

1.) For the 4 CAN modules, user wishes to "log raw frames" and capture everything on the networks. I clicked the radio button "log raw frames" in the CAN module setup and then log data but raw frames are not logged, only any individual signals setup are logged. Once I saved and restarted Flexlogger then extra groups are added to the tdms file with raw frames. Questions.....

• Why do I have to restart Flexlogger before raw CAN frames are logged? Anyone else experience this?
• I'm assuming all frames are logged once logging starts; is it lossless? Just wanting to make sure its not logging raw frames based on the sample rate setup for the module or something. Is the sample rate setting only for individual signals setup? I can't find this confirmation anywhere in documentation.

2.) Initializing or re-initializing the XNET 9862 cards takes forever. When starting a Flexlogger project it takes like 5 minutes to discover devices. Then once devices are discovered it takes another 3-5minutes before any CAN parameters are showing live values and the RUN button can then be pressed. If I make some setting change then seems like the cards reinitialize and have to wait another 5 minutes again before I can log. Is this normal? Anyway to make flexlogger faster to initialize. Maybe its lower level software? Happens with different computers with plenty of performance. Ive used other manufactures CAN products and don't experience any initialization delays like this.

Thanks for any input for these issues.

Adam Baker

Cummins Inc.

[Devin_K]

Hi Adam,

1) Needing to restart FlexLogger in order to log raw CAN frames is definitely not expected behavior.  I was able to reproduce this behavior (although I could also get it to work by closing and reopening the project, and not fully restarting FlexLogger).  This issue seems to have been introduced in FlexLogger 2020 R4, although at this time we don't know the root cause yet. We'll work to investigate and fix the issue, and if we find any information that may be helpful in the meantime I'll let you know.

2) There was a FlexLogger performance issue related to C Series XNET modules in network cDAQ chassis that was addressed in the most recent version of FlexLogger (2021 R1).  I believe that this is likely what you're running into, and I expect that if you update to the latest version you should not encounter these long delays.  Please let us know if you continue to experience these issues after upgrading to 2021 R1.

Regards,

Devin

[Devin_K]

Sorry, I just realized I missed you question about the sample rate setting for the port.  This applies only to signals added for the port, and is used to resample the value into a uniform waveform that's logged alongside all of the other channels in FlexLogger.  Raw frame logging will be lossless and log all the frames observed during the logging session.  There is a small note about the effect of the Sample Rate setting on the "Configuring an Auotmotive Bus" page of the manual stating "The sample rate will be applied to all signals on the associated port.", but I agree it could definitely be more descriptive.

[ARBaker]

Thank you for the input!. I'll update to 2021 and keep an eye out for the raw logging fix.