| Applies To | |
| Product(s): | AutoPIPE |
| Version(s): | ALL; |
| Area: | Library |
| Date Logged & Current Version |
Aug 2022 12.08.01.010 |
Problem:
The following is displayed when opening a model in AutoPIPE:
---------------------------
Error
---------------------------
E31-63: Invalid code material(s) detected. Please use "Modify/Properties of Pipe Identifier" to update all pipe-ids.
---------------------------
OK
---------------------------
How to fix this issue?
Solution:
If the model has PipeIDs where Pipe Material = "NS". Please note that AutoPIPE's material libraries do not have a record for 'NS' materials, so the error will always popup.
An easy way to duplicate the issue would be to:
-
-
- Open WALKTHRU and change the pipe code edition from 2018 to 2020. Click OK. Notice no error
- Change 8SCH40 material from A53-A to NS
- Change the pipe code edition back to 2018. Click OK. There is no code material named 'NS' in B313-18. Notice error
-
In addition, the program performs a check on the hot allowable and hot yield values for all Pressure and Temperature points that use the NS material and resets the values to cold, but only if the values were zero in the first place.
This error message is a clear indicator to the user that one or more PipeID's in the model may contain a Material selection that is not available in the newly selected material Library. Or that material information may have been updated. This error message and should be taken seriously.
Avoidance:
Open the Pipe Properties input grid and confirm all the PipeID's have a material currently available in the drop down listing. If no, then press on the material drop down listing for a specific PIpeID and select an appropriate Pipe material from the listing. If the model contains PipeIDs with Pipe Material = "NS" before the triggering event, again, this error will always appear. Please review all of the material settings to be correct.
A check is performed anytime the a. pipe code, b. edition, c. material library name, or d. ambient temperature changes in the model. It runs even if the material library does not change. The triggering event is whenever a material name used in the model does not match one from the 'new' library.