11-20-2008 10:06 PM
Hello Matt:
This is a 32-bit OS VISTA as I checked it on my properties.
I hope to get a solution soon since I would be using DIAdem for a 1,200,000 points noise analysis - let see how this fare with Origin 8.0.
Thanks.
Berns B.
11-22-2008 05:35 PM
Hello Matt:
I've attached here the screenshot of what happens at start-up and when I attempt to use the example from within LabVIEW. I hope this also gives a clear picture of what actually happens.
Thanks.
Berns B.
11-24-2008 09:40 AM
11-24-2008 10:12 AM
Hi Dr. Burns,
I noticed that both the screenshot files you posted show a running LabVIEW program. Would you please post a screenshot of the error you get when DIAdem launches after you have rebooted and NOT run the LabVEW program at all?
Also, would you please post that LabVIEW VI so that we can see what it is doing? The error message you posted claims that the LabVIEW VI passed DIAdem the ActiveX command "". I would expect an empty command to cause trouble, but not the crash that you are experiencing.
Dr. Turpin
DIAdem Product Support Engineer
National Instruments
11-24-2008 04:57 PM
Hello Dr.Turpin:
The screenshots I did was when everything seemed to stall after many minutes of waiting (5 minutes and more) that all I see is this (see attached). When however, after I launched LabVIEW (concurrently with a stalled boot of DIAdem) and calls *any supplied example in search example for DIAdem* this consequently happens - it loads its GUI performs what ever example I launch to the end! (say format and print a report in PDF) - then I could navigate around the GUI sub-tabs but can't make any new layout, buttons appear but they can't be pressed or activated. If I exit the example all the rest of DIAdem GUI also diminishes. I have also tried to repair/reinstall MS Office 2007 for possible Excel errors.I have tried to examine the behavior of it and taken a look at the processes at this state (see more attachments).
By the way? Does this software have any conflicts with VC++ and VB Express Editions by the way or in anyway with other Microsoft programming modules? Is this known?
Thank you for your attention.
Berns B.
11-25-2008 10:08 AM
Hi Dr. Berns,
I would like to debug the problem you're seeing by trying a much simpler test than what you actually want to do. I understand that you want to call DIAdem programmatically from LabVIEW in order to create some reports. This extra ActiveX connction you are using from LabVIEW is adding a lot of complexity and unknowns to the situation and is making it harder for me to help you. If you would like me to help you, please follow the below debugging steps. Once we have a better idea what the source of the trouble is, we can go back to calling DIAdem from LabVIEW via ActiveX and fix any problems that persists on that end. I want to find out whether the problem occurs inside of the DIAdem launch or because of the LabVIEW ActiveX connection.
1) Please send me the LabVIEW VI that is communicating with DIAdem (the one in all the screenshots).
2) Please reboot your computer, then start DIAdem from the Windows START menu, and take a screenshot of any error message that appears during this simple, stand-alone DIAdem launch. Please then tell me what happened and send me the screenshot if an error occurred.
Talk to you again soom,
Brad Turpin
DIAdem Product Support Engineer
National Instruments