Windows 7 NI-9234 Time Out

[Mark Levine]

I'm getting a 50405 message on the NI-9234 on a Windows 7 machine.

"Error -50405 occurred at Read DAQ 1 and Process Data.vi

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

It runs for 10 - 60+ minutes then it fails.

I'm checking AvailSamplesperChannel and they seem very low with the Maximum value seen as 2000.

Your thoughts.

Thanks,

Mark

[JÞB]

OK I'll shake the magic 8-ball  (Sometimes it works)

Q: ~~~~~Is the CompactDAQ chassis connected by USB through a hub being shut down by Windows Power manager?~~~~~~

A: It seams likely without knowing more.

[Mark Levine]

Jeff,

Thanks for the shot.  It's connected by ethernet to a network switch.

Here's a more interesting tid bit.

The identical program runs fine on a Windows 7 desk top intel core7 (with a great graphics card)

I draw 2 errors about every 90 minutes on the 2X E56202 1U SuperMicro (with a poor graphics capability).

At first I thought it was the poor graphics card but I continued to draw errors even when I eleminated all graphics output.

Mark

[Mark Levine]

Also the card is not in a Compact IDAQ chassis.   Just connected directly to the Ethernet.

Mark

[Luke_W · Accepted solution]

Hi Mark,

The 50405 error is a timeout error. This can occur with internet connections that experience intermittent interruptions. You can try and accommodate for these moments of not ideal connections by increasing the time the read vi waits until throwing the error. 

This developer zone article walks through potential resolutions of the 50405 error.

http://zone.ni.com/devzone/cda/epd/p/id/6172

Hope this helps,

Luke W

[Mark Levine]

Luke,

Thanks.  Based on the article I changed the timeout from the assumed default (2.5s) to 30s and everything works.

Of course I'm a little torqued that spent so much time chasing my tail.

Too bad NI doesn't set up their services to work with their devices or as a minimum put an alert sheet in their installation documentation.   I ran the ENET 9234 on two Windows 7 machines and both exhibited the same "bad" behavior.  Two entirely different hardware configurations.

Mark