Cannot read file filename??.in. The input file has incorrect formatting or has been corrupted.
Cannot open file filename??.in. Check spelling and ensure the file is in the correct directory.
These errors indicates the input file specified by the user does not exist. Check for spelling mistakes, and that Netfabb Simulation has been executed in the correct directory.
File filename?? does not exist. Check the input files are correct and ensure filename is in the correct directory.
This error message occurs when the specified input, PRM, or STL file cannot be found in the current directory.
Command-line argument *???? was unable to be read. Check input files and ensure usage is accordance with the user manual.
Cannot read file filename due to error argument in card: *????. Refer to the user manual for correct spelling and usage.
Cannot read file filename??.in due to error in card: *????. Refer to the user manual for correct spelling and usage.
These error messages are displayed when an unknown line is read from the input file. This is commonly due to accidentally uncommenting a comment line, typing errors, or using a non-basic text (ANSI or ASCII) format.
Command-line argument ???? was truncated. Correct in the input file and rerun.
This error message indicates one of the control cards has been truncated. Fix the input file and rerun.
Could not read dependent analysis files. The file may be missing, the wrong file type, or corrupted.
This occurs when one or more files required to run a simulation are missing. For a mechanical analysis, ensure the correct dependent thermal analysis is listed under *DEPE and that the thermal analysis completed correctly.
End of input file filename??.in. One or more input cards are incorrectly formatted. Check each card has the correct usage specified by the user manual.
This error indicates the input file read to the end of the file without encountering the *END card, or with one or more formatting errors in prior control cards.
Could not read restart file example.bin. Check the restart file name specified by *REST.
This error indicates that the .bin file specified by the *REST card is not a valid restart file and may have been corrupted.
PRM file read errors
PRM file example??.prm is not correctly formatted. Ensure the correct file is being used. The PRM file may have been corrupted and needs to be regenerated.
Cannot read prm file example??.prm. Ensure the correct file is being used. The PRM file may have been corrupted and needs to be regenerated.
These errors occur when the PRM file in *PBPF is misnamed, corrupt, or not a prm file. Locate the correct file or regenerate the PRM file.
No PRM file specified by the PRM file card *PBPF. Specify at least 1 PRM file under the *PBPF card.
This error is shown when the *PBPF card is included, but without any PRM files listed.
This PRM file was created by pan2 and is not valid. Regenerate the PRM file using prm gen.
PRM files must be generated with the prm_gen command, not with the pan or pan2 command. Regenerate the PRM file using the prm_gen command. Refer to Example 1 in the Examples section of this Help or in this manual in the PRM File Generation Execution section.
Zero entries found in example.lsr. Check the .lsr file or the *LSRP settings if the file was auto-generated.
This error indicates the .lsr file generated during PRM generation is empty. Correct the settings in the *LSRP card and regenerate.
The number of ambient temperatures are not consistent in the PRM files. Ensure the correct PRM files are being used. You may need to regenerate the PRM files to ensure the specified temperatures are identical in each file.
The number of lack of fusion temperatures are not consistent in the PRM files. Ensure the correct PRM files are being used. You may need to regenerate the PRM files to ensure the specified temperatures are identical in each file.
The number of hot spot temperatures are not consistent in the PRM files. Ensure the correct PRM files are being used. You may need to regenerate the PRM files to ensure the specified temperatures are identical in each file.
The interlayer temperatures are not consistent in the PRM files. Ensure the correct PRM files are being used. You may need to regenerate the PRM files to ensure the specified temperatures are identical in each file.
The lack of fusion temperatures are not consistent in the PRM files. Ensure the correct PRM files are being used. You may need to regenerate the PRM files to ensure the specified temperatures are identical in each file.
The hot spot temperatures are not consistent in the PRM files. Ensure the correct PRM files are being used. You may need to regenerate the PRM files to ensure the specified temperatures are identical in each file.
If multiple PRM files with lack of fusion or hotspot data are used and they have not been generated using the identical number and values for interlayer temperatures, lack of fusion temperatures, and hotspot temperatures, one or more of the above errors will be displayed. Check that the correct PRM files have been specified and regenerate any PRM files as necessary.
File example??.prm does not contain any parameter or lack of fusion entries. Ensure the correct file is being used. The PRM file may have been corrupted and needs to be regenerated.
File example??.prm does not contain any parameter entries. Ensure the correct file is being used. The PRM file may have been corrupted and needs to be regenerated.
These errors indicate that the PRM file does not contain standard PRM data. This may be due to the PRM generation process not completing, the file being corrupted, or accidentally using a non-PRM file.
Number of prm files exceeds 100. Increase the value of *NMAT.
By default a maximum of 100 PRM files may be entered. Use *NMAT to increase this limit.