Jump to content

6251M Device Not Present


EJW

Recommended Posts

I have recently run into an interesting problem. I have a new 8105 controller, 1031 chassis, and two 6251 DAQ cards. My labview program on this machine starts up with windows (XPSP2). However, when the program initalizes, it gets a device not present error. If you stop and start the program again, or close it and reopen it, it works fine, the device is there. Similarly , if you take the program out of the startup folder and launch it manually after windows starts, it works fine. It appears to me that windows has not finished recognizing the hardware, or the drivers are not fully loaded by the time my program launches when it is in the startup folder, causing this error.

Unfortunately, this is a gage in a production environment, so it HAS to start up with windows. The only solution i have found so far is to put a delay of several seconds into the beginnning of the program before configuring tasks. This seems to allow windows and nidaq to finish doing their thing so i dont get the error. Anyone else have this problem or know of a workaround other than a time delay??

Link to comment

I've seen stuff like that happen. It seems to be a Windows thing. Lots of stuff is launching at once, and not all drivers and services are initialized before your startup shortcuts are executed. I recommend a little tool called Startup Delayer. It lets you specify a time delay for any number of applications to launch after startup.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.