device has acknowledged the operation but has not completed before the timeout

[mortega65]

Hi!

I'm trying to use labview to gather data over a long period of time, however I keep getting hit with this message:

device has acknowledged the operation but has not completed before the timeout

Is there a way to fix this error?

[GerdW]

Hi mortega,

---

@mortega65 wrote:

I keep getting hit with this message:

device has acknowledged the operation but has not completed before the timeout

Is there a way to fix this error?

---

Yes: you need to handle that error programmatically…

[RavensFan]

Not enough information.

What "device" are you working with?

Is there an error number associated with that message?

[mortega65]

---

@RavensFan wrote:

Not enough information.

What "device" are you working with?

Is there an error number associated with that message?

---

I'm using USB-2416 from measurement computing

[mortega65]

---

@GerdW wrote:

Hi mortega,

---

@mortega65 wrote:

I keep getting hit with this message:

device has acknowledged the operation but has not completed before the timeout

Is there a way to fix this error?

---

Yes: you need to handle that error programmatically…

---

I knew that, I'm asking how do you fix this error

[GerdW]

Hi mortega,

---

@mortega65 wrote:

---

@GerdW wrote:

Hi mortega,

---

@mortega65 wrote:

I keep getting hit with this message:

device has acknowledged the operation but has not completed before the timeout

Is there a way to fix this error?

---

Yes: you need to handle that error programmatically…

---

I knew that, I'm asking how do you fix this error

---

It was a very generic question and you got a very generic answer…

More specific answer:

Read the manual of your device to see what is mentioned in there about that error.

I guess there are several options:

• Retry the read command again as perhaps the device wasn't ready to submit a response.
• Re-Init the DAQ device and restart the request.
• Re-init the communication connection to your DAQ device.

It all comes down to "handle the error programmatically"… 😄