at mio 64e-3 hangs internally

[rosaldorosa]

I experience occassional card hang ( not responding) for the reason I don't know.
It's happens the computer is  plugged off and on.
The only solution is to turn off the PC and reconnect plug.
Is there any card reset possibility to it's default state?
Looks to me like there is a internall bug

[rosaldorosa]

I must add that hand occurs in standard AI READ.vi. Because this vi cannot be debugged, I have no hint what is wrong.
Any hints?

[Ryan_V[DE]]

rosaldorosa,

At what level is your card hanging? Is it hanging in your application? In MAX? In the Windows Device Manager? If the card is hanging in LabVIEW, I would suggest using the Device Reset.vi. In MAX, I would right click on "Traditional NI-DAQ Devices" and select "Reset Driver for Traditional NI-DAQ." Finally, if the card is hanging in all of Windows, I would find it in the Device Manager under "Data Acquisition Devices," right click and select "Disable," then repeat, selecting "Enable."

In order to prevent this hang, I'll need to know a bit more about the circumstances when it hangs. Are you running an application? Is it that the computer does not find it upon boot up? Please let us know.

Hope this helps,

[Ryan_V[DE]]

rosaldorosa,

If the device is hanging in the AI Read, then I suspect that LabVIEW is just wating for your card to return data. How many samples are you requesting? At what rate are you acquiring? If you want, you can cause this VI to terminate prematurely by specifying a timeout to the input. Otherwise, NI-DAQ will calculate the amount of time the VI should take to return the requested data, and timeout only if it takes longer.

Hope this helps,

[rosaldorosa]

When card hangs with AI read.vi I have no other options, like to reset computer.
After that if I don't replug power the card stays in hanged state in every application(i.e. MAX where Max hangs when testing resources)
I am positive, that hang comes up because card waits for trigger state.I would love to find out what triger signal it waits for?!!
Because with the same AI SCAN.VI setting  I have  ocassional hangs  which take one day to recover.
the main vi is Simple_DTMF_decoder_and_encoder.vi
Robert

[rosaldorosa]

I thought initially, that I have low memory system (160MB,Win XP) but after memory extension to 570MB nothing helps.

robert

[rosaldorosa]

attached is ai cont scan.vi front panel with default values.
As about hardware side I have DAQ output (0) wired to ADC (0)
regards

[rosaldorosa]

Voltage V…

At mio-64e is a traditional DAQ(no DAQMX), and as such doesn't have device reset.vi available. It has ai clear.vi but it doesn't work at all in my case.

[rosaldorosa]

Is it possible that ai waveform scan.vi has a bug?
I mean, that when Ai read.vi subvi hangs for whatever reason (I have timeout set to -1 or 1 sec and it still hangs i suppose), everything after that is waiting (acc to labbview general block logic).
And because after ai read.vi subvi is ai clear.vi which waits for task id and error, the card hangs forever until hard power off

[Ryan_V[DE]]

Robert,

The Traditional NI-DAQ Device Reset is located on the Calibration and Configuration Palette, though this is hardly relevant if the execution is in the AI Read. I noticed that you have an analog trigger set up in your Front Panel image. This would require your signal to transition from below to above 0V before it returns any data. Is the signal that you are measuring doing so? You should also specify on which channel you are expecting this trigger. If you do not intend to use triggering, set the "trigger type" to "no trigger." Please let us know if this fixes the problem.

Regards,