topic Re: LSR import error log ? in Netfabb Forum

LSR import error log ?

Anonymous — Thu, 19 May 2022 09:52:07 GMT

Hello,

We often get the following error due to various reasons :

"The LSR file contains z-coordinates or time data that is not in ascending order..."

However there is no indication on where the error is detected in the LSR file, and this file can be huge in our applications.

How can we know where the error got triggered in the LSR file ?

Since it occurs before the project can be saved, I don't know where the log file could be, or if there is one.

Thanks

Re: LSR import error log ?

Chao-LI — Thu, 19 May 2022 18:02:28 GMT

Hi Stephane,

Thanks for the question. The second to the last column in the LSR file is the "Start time" for each laser path, and it should be in ascending order. I would suggest you to check this first.

# POWER, LASER VECTOR, START POINT (X,Y,Z), END POINT (X,Y,Z), RADIUS, VELOCITY, START TIME, LAYER #

Thanks

Chao

LSR import error log ?

Anonymous — Fri, 20 May 2022 10:36:08 GMT

Yes I understand but we would like to know exactly where the error occurs in the LSR file because we use complex trajectories with many points so we generate the LSR file automatically and it's not always trivial for various reasons. The error message doesn't give any clue as to where or why the error is triggered, which would be very helpful to diagnose what went wrong as there can be several causes...So there is no detailed log of the error ?

Re: LSR import error log ?

Chao-LI — Tue, 24 May 2022 21:44:22 GMT

Hi Stephane,

Thanks again for your detailed description of the issue. I did a test run with bad time order in the lsr file. Below is the error message I got in the .out file, the error message in the latest solver will point out the exact location of the error.

ERROR
Code 73
*LASR laser vector card lines are not in time ascending order. Laser line: 22 (%2 with comments). Check and fix .lsr file.

My solver version is: Autodesk AM Process Simulation v23.1.0, Build ID : 23.0.0.99999

Could you share the build information at the very beginning of the .out file? (Like: Autodesk AM Process Simulation v23.1.0, Build ID : 23.0.0.99999)

Also could you share the error code number in the .out file? We are happy to help you find out what might be causing the issue.

Thanks

Chao

LSR import error log ?

Anonymous — Wed, 25 May 2022 12:10:08 GMT

Hello,

Thank you for your feedback.

Regarding the test you ran, were the error generated upon importing the LSR file or later on when launching the solver ?

Because in our case, this error is most often triggered when importing the LSR, i.e. before launching the solver, so no *.out file is generated yet in the project folder...so in this case I don't know where to look for the error code number etc...any suggestions ?

Best regards,

Stéphane

Re: LSR import error log ?

Chao-LI — Thu, 26 May 2022 04:49:55 GMT

Hi Stephane,

The error was received after the solver was launched. I also tried to import the .lsr file (with time order issues) using the user interface, but I didn't notify any errors at this stage.

For now, you can run the case in the command line with an input file and lsr file. I will PM your an example for reference, you can save the text as "test.in". This is a thermal only test, with material IN625. Include your lsr file under *LSRF with "your_lsr_file.lsr". *SBXY and *DDM! define the dimension of the substrate, details can be found here: (https://help.autodesk.com/view/NETF/2021/ENU/?guid=GUID-1E4A055C-4A5C-4C7B-85A0-44C560B57C95) and (https://help.autodesk.com/view/NETF/2021/ENU/?guid=GUID-2CDC160C-B0E8-49F2-B0FB-9A71941C3C7B).
To initiate the run: launch a prompt window and navigate to the folder where the input and lsr files are located, type: pan -b test >filename.out and then hit enter. See the figure below.

The error message should be in the file “filename.out”.
Please let me know how it goes.

Thanks

Chao

LSR import error log ?

Anonymous — Mon, 30 May 2022 15:24:04 GMT

Ok thank you, I've launched the simulation from the commandline with the input file you provided.

For now, the solver is running with the LSR file that causes issues when importing from the GUI.

So at least, through the GUI we know if there is an LSR error but we do not know where, whereas with the commandline the error is signaled to the user when it is encountered but that means we have to wait for the solver to get to this point.

It would be better to know about the error right away through the GUI with the error code and corresponding LSR line.

I'll wait for the simulation to progress until it reaches the error and will keep you posted.

Best regards,

Stéphane