1. Update Item
1) Added CIVIL NX connection information
2) Plate press load not being entered
3) Get node component issues with undefined information
4) Change to maintain Get Property component information
5) Change the static load case component's ID and No. to be unset
2. Description
1) Added CIVIL NX connection information
Added to the Setting component is the ability for CIVIL NX and API to check the connection status.
The function reviews the connection with the product every 5 minutes and provides error information if the product is disconnected or the API Key does not match.
2) Plate Pressure Load Component bug fix
[Issue]
When the Type of Plate Pressure Load Components is Load Type, there is a problem that the load is not input.
[Modification]
Load Data has been changed to enter normally.
When the Type of Plate Pressure Load Components is Load Type, there is a problem that the load is not input.
[Modification]
Load Data has been changed to enter normally.
3) Get node component issues with undefined information
[Issue]
When the Node was not created in the CIVIL NX, the Get Node component generated temporary Node information.
This resulted in a situation in which Node ID information that did not match the modeling information was displayed.
When the Node was not created in the CIVIL NX, the Get Node component generated temporary Node information.
This resulted in a situation in which Node ID information that did not match the modeling information was displayed.
[Modification]
If there is no node information in CIVIL NX, the statement that there is no node information appears.
4) Change to maintain Get Property component information
[Issue]
Connecting a new parameter to Get Property had the inconvenience of disconnecting the connected data.
Connecting a new parameter to Get Property had the inconvenience of disconnecting the connected data.
[Modification]
When a new parameter is connected to Get Property, the information that is connected behind it remains uninterrupted.
5) Change the static load case component's ID and No. to be unset
[Issue]
When creating the Load Case, we found an issue that was not created, such as the value entered by the ID and Index No.
When creating the Load Case, we found an issue that was not created, such as the value entered by the ID and Index No.
Therefore, there was a problem that the input information and the generated information did not match each other, so the connected load was not input.
[Modification]
For the Static Load Case, the order in which users are created has been changed to prevent them from being randomly modified using the API.
Therefore, We deleted it so that I could not enter No. in the component.
In addition, for IDs, CIVIL NX is required to rearrange the IDs internally.
Therefore, even if the user enters the ID randomly, CIVIL NX will convert the data randomly, so the ID cannot be entered automatically to be generated by CIVIL NX.
Therefore, updating to a new version will change the number of input data in the existing Static Load Case Component, and you will need to change it to a new version of Static Load Case.