From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
System crash after unhandled exception during pending A/D conversion
UnCrashMySys
Member
11-22-2004 09:39 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Anybody experienced similar phenomena and/or has a fix ?:
I'm using the DAQ components (6.0) for ActiveX (subset delivered with the NI-DAQ driver-CD) from VB 6.0 (SP6) to control measurements with a 6040/6070 E-series card.
The application starts a delayed (with CWpulse) A/D conversion and waits for the "acquired data" event. In the meantime, several other application-handled events can happen (mouse, kbd, timer, network link).
We have a watchdog application which monitores the main application, but...:
If there occurs an unhandled exception while the A/D conversion is pending, the system crashes after the "serious error..." message / error reporting of the O/S is confirmed - both on Win2000 and XP (SP1a). One can here the HDD retract and the (mostly) reboot. Two times, the system locked up so bad, it won't even restart until a complete power-cycle - of course at the customer's site... 😞
That kind of behaviour is reproduceable when I force an exception (e.g. div-by-zero) after the CWAI component was started.
I tried that on systems with NIDAQ 6.9.3 and also with 7.1, but both give me no chance to return to the O/S after the application failure.
Does anybody know about the reason for such unfriendly behaviour or can help me to solve that problem?
Any help will be much appreceated!
I'm using the DAQ components (6.0) for ActiveX (subset delivered with the NI-DAQ driver-CD) from VB 6.0 (SP6) to control measurements with a 6040/6070 E-series card.
The application starts a delayed (with CWpulse) A/D conversion and waits for the "acquired data" event. In the meantime, several other application-handled events can happen (mouse, kbd, timer, network link).
We have a watchdog application which monitores the main application, but...:
If there occurs an unhandled exception while the A/D conversion is pending, the system crashes after the "serious error..." message / error reporting of the O/S is confirmed - both on Win2000 and XP (SP1a). One can here the HDD retract and the (mostly) reboot. Two times, the system locked up so bad, it won't even restart until a complete power-cycle - of course at the customer's site... 😞
That kind of behaviour is reproduceable when I force an exception (e.g. div-by-zero) after the CWAI component was started.
I tried that on systems with NIDAQ 6.9.3 and also with 7.1, but both give me no chance to return to the O/S after the application failure.
Does anybody know about the reason for such unfriendly behaviour or can help me to solve that problem?
Any help will be much appreceated!
Michael Sallaberger
NI Employee (retired)
11-26-2004 06:57 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hello,
First of all please try to use the NI-DAQ 7.3. I can not promise that it leads to a solution.
The problem is that when the unhandled exeption occurs the daq-driver is not stopped and the acquisiton continious. This behavior can lead to the crash.
The only solution I can think of is to prevent the unhandled exception.
Regards
Michael Sallaberger
First of all please try to use the NI-DAQ 7.3. I can not promise that it leads to a solution.
The problem is that when the unhandled exeption occurs the daq-driver is not stopped and the acquisiton continious. This behavior can lead to the crash.
The only solution I can think of is to prevent the unhandled exception.
Regards
Michael Sallaberger
reddog
Active Participant
11-26-2004 03:47 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
If unhandled exceptions are a concern, I would recommend switching over to the DAQmx API and driver. The DAQmx driver does a much better job of gracefully handling abnormal program termination and shutting down any ongoing acquisitions.
11-29-2004 02:14 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I'd prefer this, too - also for some other reasons, like shared ADC access by different applications.
But, as NI states, NIDAQmx can not be used under VB6... or is there a (undocumented?) possibility to use the mx API also with non-.NET development systems?
But, as NI states, NIDAQmx can not be used under VB6... or is there a (undocumented?) possibility to use the mx API also with non-.NET development systems?
reddog
Active Participant
11-30-2004 07:11 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
While DAQmx is not officially supported through Visual Basic 6.0, it can be done. I am not a VB6 user and haven't tried it, but you can look at the following Knowledge Base explaining how to accomplish this. You can also look at the following MSDN article explaining how to access DLLs and the Windows API through VB. Essentially you end up making DLL calls as you normally would through VB using the DAQmx C API. I hope this helps.
