-50405 error on cDAQ 9188

[BonbonBLou]

Hi there,

I am having a problem with my 9188 cDAQ chassis'.

I have 7 chassis' all with thermocouple modules in, recording a temperature from 800 thermocouples once a second.

On my 9188 chassis' I keep getting the following error - "-50405 Error -50405 occurred at DAQmx Stop Task.vi:6
Possible reason(s):
NI Platform Services:  No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified.
Task Name: CDAQ-2"

The error occurs randomly. Sometimes I'll do a test and get no errors. Sometimes one chassis will error, sometimes several of them will fail. It always seems to be a different chassis every time, but I get the error pop up on about 50% of the tests I run.

I have tried stopping the tasks, clearing the error and trying to restart the task but the same error will still come up. I reserve the chassis and self test them programatically before starting the DAQmx task, and before the task stats there is no error.

I am running DAQmx 9.6 and have updated the firmware on the chassis to 1.4.

Both me and my colleague have tried everything we can think of to fix this and we're both still left scratching our heads.

Any ideas or advice would be appreciated,

Thanks,

Lou

[ShalimarA]

Hey Lou!

Sorry it's taken so long for someone to get back to you.

My initial thought on this issue is that, due to the particular error message, that this might be a network issue. The cDAQ 9188 is ethernet connected and because your VI seems to be dropping out randomly, it implies that your connection to the network is dropping also out randomly, potentially causing it. This may not neccesarily be due to your network itself, though. Faulty ethernet cables or improper connection could cause the connection to drop as well.

I've found this knowledge base article that relates to the error -50405 : http://digital.ni.com/public.nsf/allkb/ACDC4A9DDB0FEA12862574F7006DC1C6

It basically goes through the error and some potential solutions. Why don't you have a look through it and let me know if it helps? If you need anything else, whether to do with the article, the issue if the article doesn't help, or any other issues, let me know!

[ShalimarA]

Hey,

Just wanted to check if you've had any progress?

[BonbonBLou]

Hi Shalimar,

Sorry about the delay in replying. I am still having the problem.

I looked at the information you sent and as for the first solution, I think my network is fine, as all of the chassis are wired up, rather than using wireless and it's a different one that fails everytime, so I don't think it's one dodgy wire that's causing the problem - I can't imagine that all of my ethernet cables are breaking!

I have to admit, I don't really understnad how to go about trying the second solution - any idea on how to access the windows registry?

Thanks,

Lou

[ShalimarA]

Hi Lou,

I'm sorry the first method didn't work. 

As for the second, are you working on Windows 7 or Vista? If so, type 'regedit' into the search bar when you open the start menu and select 'Yes' when it asks when prompted to accept changes. The rest is straightforward from the article. 

[BonbonBLou]

Hi Shalimar,

Just tried the sceond solution, no joy with that either I'm afraid.

Any other ideas?

Regards,

Lou

[ShalimarA]

Hi Lou,

Based on a little more research, I've found that similar issues have come up before. Here are some more troublshooting steps you can take to continue to try to solve the issue.

When running the VI, can you keep refreshing MAX (hit F5) to see, when the error pops up, if the chassis/modules disappear?

Can you try using cross over cables to connect the chassis? 

As you're running several chassis over several cables, you can also try just plugging one chassis directly into the host computer to see if it runs without error. 

[Brian_A]

Crossover cables are not going to change the behavoir and are mostly for use when directly connecting devices (although most new NI products that I know off do not need a crossover anymore)

Also checking MAX by refreshing isn't going to solve the issue since the 50405 error is most likely indicating a communication error. 

Lou,

Can you describe your network topollogy. What brand of switch/router are you using and how are each of the devices and the computer connected to eachother? Is the setup on it's own private network or is it sharring a network with other devices? Have you been able to identify any corelation between an event, such as same time of day or when another application is also run, and getting an error? Also can you post a snapshot or a VI of the aquisisiton part of your code?

Brian A

R & D Product Support Engineer | WSN/Network DAQ/Academic

National Instruments

[ShalimarA]

Hi Brian,

Thanks for responding, I appreciate having someone from R&D looking into this as well. The reason I suggested refreshing MAX was that I thought one of the devices would have disappeared intermittently, showing that the connection was lost between the device and computer. It was more of a sanity check than a solution. 

[BonbonBLou]

Hi Brian,

My 7 chassis' are connected to a Netgear 8 port switch via Ethernet, and the 8th port is used to connect the switch to my computer via the Ethernet port. It is a private network with no other devices and I have given the computer and each of the chassis a static IP address.

As far as I've seen there doesn't seem to be any pattern as to when the error occurs. I'll get it on most of my test runs, but sometimes it'll be one chassis, sometimes 3 etc. It doesn't usually affect all of them at once, though it is always a different one every time that fails. I don't usually run the tests with any other applications open, so I don't think they will be affecting it.

I have included the sub VIs used for acquiring the chassis and reading data. I have also included a screenshot of the main VI, as the whole thing is a bit large and the data acquisition is just one part of it. I'll apologise now, it'sa tad messy, due to me trying several things to try and correct the error, but the basic functionality is simple enough.

Regards,

Lou