DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

Catastrofic Failure

Hi

 

I have created a couple of functions that apparently doesn't go well along. The first one (AddNewSht.VBS) creates a new sheet and creates 4 plots (2 rows, 2 Cols). The second one (AddYAxs.VBS) creates a new Y axis in the selected plots either on the left or the right.

 

I create the sheet with the 4 plots using the first function and then I try to create a new Y axis using the second function. When I do this I get the Catastrofic Failure PopUp.

 

If I try to do manually over the generated plots Diadem crashes, so apparently the failure is in the generation of the plots.

 

error.JPG

 

The functions are attached.

 

I am using Diadem 2012

 

Thank you

 

Download All
0 Kudos
Message 1 of 5
(5,590 Views)

Hi Dslemusp,

 

Have you already tried in another computer? Does the same crash happen?

 

A thing you can try to do is to reinstall or repair the DIAdem installation.

 

Let me know if it fix your problem.

Plínio Costa
Senior Techinical Support Engineer
National Instruments Brazil



0 Kudos
Message 2 of 5
(5,552 Views)

Hi Plinio

 

Yes, Actually I have tried with 3 different computers, one of them a 64Bit with a fresh Diadem Installation, exactly with the same error.

 

If you use the script I attached and once the axis are created you try to add a new YAxis the crash would appear.

0 Kudos
Message 3 of 5
(5,537 Views)

Hi dsl,

 

I was able run your "AddNewSht.VBS" script to generate 4 empty REPORT graphs, then run your "AddYAxs.VBS" script to add a Y axis on the left side of each of them-- no errors on my DIAdem 2012.

 

Do you have any DIadem events configured or UserCommands registered?  Did you start with an empty REPORT panel?

 

Brad Turpin

DIAdem Product Support Engineer

National Instruments

0 Kudos
Message 4 of 5
(5,467 Views)

Hi Brad

 

I have tried the scripts in a fresh DIAdem installation, with no luck. I have tried running the scripts using a NEW report (empty one), with the same error. The only user command registered is UserCmdExample.VBS.

 

I reported this to Walter Rick in NI Germany and he was able to reproduce the error and said that it seems to be a bug.

0 Kudos
Message 5 of 5
(5,357 Views)