linuxcnc trajectory planner
21 Oct 2024 09:38 #312727
by Grotius
Replied by Grotius on topic linuxcnc trajectory planner
Hi Arciera,
Nice you can start lcnc now.
So how would I now make it load the gcode file through the optimizer? Everything looks just like it always does.
Start lcnc with open terminal, so you can verify the optimized gcode file is written trough the terminal output.
The gcode is optimized when you press the program run button.
This then starts the optimizer and saves a file in the ~/linuxcnc_trajectory_planner/cmake directory, named validate_xx.ngc. xx=random integer value.
Best worked for me is use a gcode file included a G64 P5 Q0. Then in next line a G61.
Then load the new produced file, and verify content.
I guess this is what made you comment that the install does not work?
Yes that is wrong filepath. The relative attached path"../../rtlib/motmod.so" is ok.
I think I may have found the underlying issue, something in the installation process of your repo seems to point motion.so to the 'lib' directory in the root folder (ie where a deb install would put them).
Maybe, the system would find them always in root lib dirs. I can remember me doing a "export" terminal command adding a
search dir to the system. Something like "sudo ldconfig".
In the link you can set your settings for the G64 P & Q values. With some more settings.
This is now compiled as fixed. To avoid confusion for me in earlyer stages of writing and testing the code.
Link
Good luck. I hope you can get something out.
Nice you can start lcnc now.
So how would I now make it load the gcode file through the optimizer? Everything looks just like it always does.
Start lcnc with open terminal, so you can verify the optimized gcode file is written trough the terminal output.
The gcode is optimized when you press the program run button.
This then starts the optimizer and saves a file in the ~/linuxcnc_trajectory_planner/cmake directory, named validate_xx.ngc. xx=random integer value.
Best worked for me is use a gcode file included a G64 P5 Q0. Then in next line a G61.
Then load the new produced file, and verify content.
I guess this is what made you comment that the install does not work?
Yes that is wrong filepath. The relative attached path"../../rtlib/motmod.so" is ok.
I think I may have found the underlying issue, something in the installation process of your repo seems to point motion.so to the 'lib' directory in the root folder (ie where a deb install would put them).
Maybe, the system would find them always in root lib dirs. I can remember me doing a "export" terminal command adding a
search dir to the system. Something like "sudo ldconfig".
In the link you can set your settings for the G64 P & Q values. With some more settings.
This is now compiled as fixed. To avoid confusion for me in earlyer stages of writing and testing the code.
Link
Good luck. I hope you can get something out.
Please Log in or Create an account to join the conversation.
21 Oct 2024 12:25 #312737
by Aciera
Replied by Aciera on topic linuxcnc trajectory planner
Ok, so just so we are on the same page, here is what I get.
It creates the validate_<...>.ngc :
Not sure if 'vector pointer is not valid' is a problem but I notice that when I run the created file it gets hung up after having run the first maybe 500 lines (this changes from one try to another). At this point linuxcnc cannot be recovered and has to be restarted.
Meanwhile more validate_<...>.ngc files have been created:
Are you seeing these hangups as well?
It creates the validate_<...>.ngc :
gcode loaded items: 1
gcode loaded items: 44
gcode loaded items: 135
gcode ready to be processed in thread.
set your gui maxvel to zero. Then the machine won't move when saving the gcode.
init curves done.
trim curves done.
added inbetween segments:178
Gcode file ready, filename:../../../cmake/validate_1048567314.ngc
thread completed.
vector pointer is not valid.
vector pointer is not valid.
Not sure if 'vector pointer is not valid' is a problem but I notice that when I run the created file it gets hung up after having run the first maybe 500 lines (this changes from one try to another). At this point linuxcnc cannot be recovered and has to be restarted.
Meanwhile more validate_<...>.ngc files have been created:
Are you seeing these hangups as well?
Attachments:
Please Log in or Create an account to join the conversation.
Time to create page: 0.123 seconds