untimely firmware downgrade of NI9862 cards

[gael_aw]

I have 2x NI-9862 CAN cards in a win7 64 bits computer.

I have a recurring problem : every now and then they return this error message when trying to use them 

NI-XNET: (Hex 0xBFF63001) An internal error occurred in the NI-XNET driver. Please contact National Instruments and provide the information from the file %ALLUSERSPROFILE%\Application Data\National Instruments\NI-XNET\niXntErr.log’ (Windows XP file location). On Windows Vista or Windows 7, the file can be found at %ProgramData%\National Instruments\NI-XNET\niXntErr.log. Please note that this location may be hidden on your computer.

Here is the contents of this file :

Current Row: 0070 Max Num Rows: 001000
(1000) - Log Options: (Internal Errors, User Errors, Internal Warnings, User Warnings)
Date and Time Format YYYY-MM-DD HH:MM:SS (24-hour time)

Row Date and Time Severity Type Component File Line Code (hex) Info (hex)
------------------------------------------------------------------------------------------------------------------------------
0001 2013-10-07 09:53:53 Error System Service 1 203 1239 0xffff3988 0x84cbc4d7
0002 2013-10-07 09:54:04 Error System Service 1 203 1239 0xffff3988 0x84cbc4d7
0003 2013-10-07 09:56:15 Error System Service 1 203 1239 0xffff3988 0x84cbc4d7
0004 2013-10-10 11:45:59 Error System Service 1 2 826 0xffff34ca 0x8402c33a
0005 2013-10-10 11:45:59 Error System Service 1 2 826 0xffff34ca 0x8402c33a
0006 2013-10-10 11:46:00 Error System Service 1 2 826 0xffff34ca 0x8402c33a
0007 2013-10-10 11:46:00 Error System Service 1 2 826 0xffff34ca 0x8402c33a
0008 2013-10-17 11:02:02 Error Internal 1 100 172 0x00000001 0x846480ac
0009 2013-10-18 11:54:05 Error Internal 1 100 172 0x00000001 0x846480ac
0010 2013-10-18 11:55:06 Error Internal 1 100 172 0x00000001 0x846480ac
0011 2013-10-18 12:02:46 Error Internal 1 100 172 0x00000001 0x846480ac
0012 2013-10-18 12:10:31 Error Internal 1 100 172 0x00000001 0x846480ac
0013 2013-10-18 14:27:17 Error Internal 1 100 172 0x00000001 0x846480ac
0014 2013-10-18 14:40:50 Error Internal 1 100 172 0x00000001 0x846480ac
0015 2013-10-21 14:06:02 Error Internal 1 100 172 0x00000001 0x846480ac
0016 2013-10-21 14:07:31 Error Internal 1 100 172 0x00000001 0x846480ac
0017 2013-10-21 14:27:40 Error Internal 1 100 172 0x00000001 0x846480ac
0018 2013-10-21 14:27:50 Error Internal 1 100 172 0x00000001 0x846480ac
0019 2013-10-21 14:29:49 Error Internal 1 100 172 0x00000001 0x846480ac
0020 2013-10-21 14:29:49 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0021 2013-10-21 14:30:20 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0022 2013-10-21 14:30:20 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0023 2013-10-21 14:30:20 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0024 2013-10-21 14:31:07 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0025 2013-10-21 14:31:07 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0026 2013-10-21 14:31:07 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0027 2013-10-21 14:31:07 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0028 2013-10-21 14:31:07 Error System Service 1 203 1239 0xffff3c4b 0x84cbc4d7
0029 2013-10-23 11:48:39 Error Internal 1 100 172 0x00000001 0x846480ac
0030 2013-10-23 11:49:54 Error Internal 1 100 172 0x00000001 0x846480ac
0031 2013-10-23 11:51:09 Error Internal 1 100 172 0x00000001 0x846480ac
0032 2013-10-23 11:52:24 Error Internal 1 100 172 0x00000001 0x846480ac
0033 2013-10-23 11:53:40 Error Internal 1 100 172 0x00000001 0x846480ac
0034 2013-10-23 11:54:55 Error Internal 1 100 172 0x00000001 0x846480ac
0035 2013-10-23 11:56:10 Error Internal 1 100 172 0x00000001 0x846480ac
0036 2013-10-23 11:57:25 Error Internal 1 100 172 0x00000001 0x846480ac
0037 2013-10-23 11:58:40 Error Internal 1 100 172 0x00000001 0x846480ac
0038 2013-10-23 11:59:55 Error Internal 1 100 172 0x00000001 0x846480ac
0039 2013-10-23 15:42:21 Error Internal 1 100 172 0x00000001 0x846480ac
0040 2013-10-23 15:52:32 Error Internal 1 100 172 0x00000001 0x846480ac
0041 2013-10-23 15:53:00 Error Internal 1 100 172 0x00000001 0x846480ac
0042 2013-10-23 15:53:53 Error Internal 1 100 172 0x00000001 0x846480ac
0043 2013-10-23 15:54:34 Error Internal 1 100 172 0x00000001 0x846480ac
0044 2013-10-23 15:54:55 Error Internal 1 100 172 0x00000001 0x846480ac
0045 2013-10-24 14:04:23 Error Internal 1 100 172 0x00000001 0x846480ac
0046 2013-10-24 14:05:38 Error Internal 1 100 172 0x00000001 0x846480ac
0047 2013-10-24 14:06:53 Error Internal 1 100 172 0x00000001 0x846480ac
0048 2013-10-24 14:08:09 Error Internal 1 100 172 0x00000001 0x846480ac
0049 2013-10-24 14:09:03 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0050 2013-10-24 14:09:17 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0051 2013-10-24 14:09:41 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0052 2013-10-24 14:10:15 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0053 2013-10-24 14:10:49 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0054 2013-10-24 14:11:23 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0055 2013-10-24 14:11:57 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0056 2013-10-24 14:12:31 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0057 2013-10-24 14:13:05 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0058 2013-10-24 14:13:39 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0059 2013-10-24 14:14:13 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0060 2013-10-24 14:14:47 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0061 2013-10-24 14:15:21 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0062 2013-10-24 14:15:55 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0063 2013-10-24 14:16:29 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0064 2013-10-24 14:17:03 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0065 2013-10-24 14:17:38 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0066 2013-10-24 14:18:12 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0067 2013-10-24 14:18:46 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0068 2013-10-24 14:19:20 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0069 2013-10-24 14:38:47 Error System Service 1 203 402 0xffff3b50 0x84cbc192
0070 2013-10-24 14:38:58 Error Internal 1 100 172 0x00000001 0x846480ac

When I go into NI Measurement and Automation Explorer, and try a slef test on the CAN cards, the result is that the firmware in the card does not match the current NIXNet version and asks me to update.

I have already updated the cards once, but now the problem has occured once again.

Any ideas how to solve this ?

Thanks

[ThiCop]

Hello Gael,

Hmmm, that (the firmware update issue) is indeed very weird behaviour.

Maybe NI MAX is returning an incorrect message concerning the Firmware, because it would seem quite unlikely (never say that something is impossible) that the firmware would revert back to its old firmware version.
Does performing the firmware update always repair the issue?

Can you double-check the following KB for me?

In general this is the source for the error you're encountering and I just want to make sure we  can exclude it.

http://digital.ni.com/public.nsf/allkb/A2434DB7238D8774862579AE004EA9F8?OpenDocument

If this does not help, then please post a MAX Report of your system:

http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4?OpenDocument

[gregopher]

Hello, I have also experienced the XNET driver returning the same internal error when trying to create a session.  However, I'm running a real-time app on a 9068 chassis with both a 9862 module and a 9881 CANopen module installed.  I don't seem to get the error when the 9881 is removed, and sometimes even with it installed it will run fine.  

I was thinking the problem is that there is a conflict with the two modules, but now maybe it is a firmware issue with the 9862.

I've already started an SRQ with NI (#7396162) and shared some code that reproduces the problem. Hopefully it will get resolved soon.

Edit: Also, since I'm running on the Linux RTOS, I have not clue if and where the XNET driver would place the error log file mentioned in the error message.

[ThiCop]

Hello Gregopher,

I have been out of office this week.

I wanted to check if you have any updates concerning the issues you were seeing.

[gael_aw]

Hi ThiCop, thanks for your reply.

I noticed that a simple reboot of the computer, without performing any firmware update, solves the problem (until the next time it occurs).

About the KB you suggest, we are not replaying frames from a log file. Our issue occurs during real-time CAN communication. So does it apply all the same ?

Anyway our software expert (Bruno O.) is currently discussing the issue with NI support in Paris.

I have informed him about this thread, maybe it can help him.

We will update this thread when we have a solution.

Regards

Gael

[ThiCop]

Hello Gael,

Do both NI 9862 C Series modules have their own USB-cable connecting them to the pc?

Or in other words, are you using a 9171 one-slot chassis for both for them?

Do you have any possibility to do troubleshooting?

If yes, do you see the same behaviour when they are being used in a different pc?

[Gibson]

a Selftest of your 9862 device should help, rather then doing a PC reboot

[gael_aw]

-> they both have their own 1-slot chassis (9171). Each is connected to a USB hub (along with 2x 6525 and 1x 6008), which itself is connected to the PC.

-> we have the problem on many different PC's, running XP, win7 64.

One PC does not have the problem. It's running NI XNet 1.4 instead of 1.6.

I will try downgrading NI Xnet on the problematic PCs when I have enough time to do it, see if that solves the problem. But I'd prefer to be able to run the latest NI drivers.

[ThiCop]

Hello Gael,

Maybe a question a bit to general, but I just would like to know to have a full scope of the issue.

I assumed from the beginning that you were using the USB-9171 from inside a specific application.

Is this a LabVIEW, LabWindows/CVI, Visual Studio or other "type of application"?

If yes, are you able to provide background information about which version of this development system you are using?

In general I wouldn't advise to revert back to earlier versions.

The most recent version at this moment of NI-XNET is version 1.8:
http://www.ni.com/download/ni-xnet-1.8/4166/en/

This left aside, the first thing we should be able to do is pinpoint where and how it is going wrong.
IO Trace should be a very useful tool to determine how and where it is "going wrong".

Most likely my colleagues at NI France have already described which steps should be followed to get more information.

If they have not, then please lete me know, so that I can provide some more information.

[ivan.valles]

I had the same problem, and the only solution was rebooting the computer. I tried rebooting the cDAQ, replacing the CAN module, upgrading/downgrading the CAN module firmware and none of these option seems to fix the problem.

Ivan Valles

CLA, CTA