Testing in NX CAE (repetative)

[ateeroyal]

Hi,

I do my engineering finite element analysis in NX and ANSYS and ABAQUS

For engineering analysis, we have a series of test cases.We run these test cases during every version release of the software.

In each test case, we do a series of steps, these include: click several menu buttons, hit on a particular location in the window, let the program perform a task by hitting a menu button (this takes some minutes), once the program has completed the task, I again hit some buttons.

That is, carry out a number of tasks: meshing, boundary conditions application, analysis.

The steps are repetitive.

Can't all these tasks be recorded and then instead of the end user doing it, we just run the record and thus automate it (that is, I do not physically run these test cases each time after every release).

Are there any external tools available which anyone has used ?

The problem is not restricted to NX but other software's as ANSYS,ABAQUS for finite element analysis.

Now, I have been doing all the tasks (in the bold above) by hand.

I want a tool that can completely automate the above.

Is it possible by an external application / tool to do this?

Sorry for a naïve question.

Regards,
Ann

 

[Tuw]

Hi Ann,

Below link is an example of automated customed cae application capable in NX.

https://www.youtube.com/watch?v=zr9fxoZlMps

Regards,
Tuw

 

[ateeroyal]

Hi Tuw,

Thanks a lot. Can you upload any document concernign this? Unfortunately, videos don't open for me in the institute due to a problem.I will have a look after going home in a few hours.

Also, does the automation use any external tool / application?

I have been thinking of having a generic auomation suite which (with some minimal modifications) be utilised in other CAE softwares as well.

Thanks again,
Ann

 

[Tuw]

Hi Ann,

Please find attached fact sheet.

By the way, there is a 'guru' in this forum, by the name cowski. He is the expert in this. You also can check his website at

http://www.nxjournaling.com/

Hope this help.

Tuw

 

[ateeroyal]

Hi Tuw,

Thank you very much for the information. It is useful

However, before diving into NX Open/ utilising jornaling capability in NX to record my analaysis sequence , edit and create automated test scripts, I would like to fundamentally assess some things. This is because I would like my work be used in creating automated test scripts in other softwares (like ANSYS, etc. as well).
The pdf you attached mentions of the integration of Knowledge Fusion (which is an external tool/application) into NX which permits the knowledge based extension of NX by the user.

My question is;

1) IS Knowledge fusion an product of Siemens / NX ?
2) IF I procure Knowledge Fusion, how can it help me to produce automated scripts of NX and another software?

I just do not want to dive in customizing NX , producing test test scrips through journaling, editing but understand how the process works so that I can apply it to a wider scope than just NX CAE.

Any guidance how the integration of Knowledge fusion with NX be useful in automatic test scripts in other softwares (if at all) will be extremely useful.

Thanks again,
Ann

 

[Tuw]

Hi Ann,

Knowledge fusion is one of Siemens NX's module. But I think the module that you are looking for is not that, but NX Open, which provides the API libraries, documentation to create custom applications.

I cannot judge on other software because I am only working with Siemens NX. Anyway, based on my experience with customizing application in NX, you can use many generic computer languages such as C, visual basic, java, python and so on. Therefore, in NX, we have different module of NX Open for .NET, GRIP, Python, SNAP, C++, Java.

Other CAE software might be using the same computer languages as well. The good thing is if these software can be programmed using same language, then probably you can save the time by using the same language template for the next CAE software tool, such as Ansys or Abaqus. This is the advantage of it. Any how, I believe all CAE software will be using different keyword command for similar functions (for example a function to define a material), and this is inevitably a time consuming effort which could not be avoided.

Regards,
Tuw

 

[ateeroyal]

Hi Tuw,

Thanks, yet again.

You say that in in NX,you have different module of NX Open for .NET, GRIP, Python, SNAP, C++, Java.

But, NX CAE (I believe) is written in C++.

Why, then, you have different modules for NX Open fro .NET, GRIP, Python, SNAP, C++, Java ? IS it because, you have intenced that NX Open may be sued by the users for different softwares (than only NX CAE)?

I'm not familiar with NX Open (not familar at all) to eb frank.

Can you please atatch the simplest tutorial (say of a single simply supported beam)- let us say the tutorial automates a test case comprising of: creating geometry, applying boundary condition, meshing, FE aanlsysis and post-processing?

Thanks a lot,
Ann

 

[ateeroyal]

Hi Tuw,

In addition to my above post, what do you think are the advantages of using NX Open over other open source (or paid / license tools) tools over NX Open;

For example, see the list of tools avaialble here for creating an automated test suite

Tools for automated testing

Looking forward to your reply,
Ann

 

[ateeroyal]

Hi Tuw,

Looking forward eagerly to your response

Ann

 

[Tuw]

Hi Ann,

I have no knowledge what language NX CAE is written. We don't have legal issue by having multiple choice of languages to customizing application. The main purpose of having multiple choice is simply to promote the openness and freedom of NX software.

The workflow of NX Open for CAE is generally as below:
1. Record a journal, obtain the code.
2. Since the journal is selection specific, we need to remove the selection specific by applying a selection option. For example, the journal is selecting polygon face ID5, this pre-selection from the journal is then replace with a selection option, to interact with the user, so that the user can do selection during the automated custom process.
3. Creating the custom dialog box. From the dialog box, the codes are obtained.
4. The dialog box code and the journal codes are combined and connected into a complete set of code.
5. From NX software, run the complete code to launch the custom dialog box.

There are a lot of example in

http://www.nxjournaling.com/

You can find my final work at link below:

http://www.nxjournaling.com/comment/839#comment-839

If you would like to know more about NX Open, you can refer to NX Documentation (UGDOC) installation, be sure to install NX Online Help and NX API Manuals. The default installation does not include the installation of NX API.

I have scrolled through your link on the open source code. Sorry but I dont recognized anyone of them, probably because I am not an IT programmer but from engineering background.

Regards,
Tuw