- Posts: 4793
- Thank you received: 1480
Coordinated Motion involving rotary axis
- Todd Zuercher
- Offline
- Platinum Member
-
Less
More
11 years 1 month ago #62982
by Todd Zuercher
Replied by Todd Zuercher on topic Coordinated Motion involving rotary axis
I believe that with the old trajectory planner the naive cam detection is the difference between G64 moves in only XYZ and moves with ABCUVW. If I turn of the naive cam detector (Q0) then the XYZ plot looks the same as moves with ABCUVW.
Please Log in or Create an account to join the conversation.
- Todd Zuercher
- Offline
- Platinum Member
-
Less
More
- Posts: 4793
- Thank you received: 1480
11 years 1 month ago - 11 years 1 month ago #62986
by Todd Zuercher
Replied by Todd Zuercher on topic Coordinated Motion involving rotary axis
I think there is a small bug in the new trajectory planner when the naive cam detection is turned off (Q0). Notice how at the end of the move there is a strange blip in the velocity. That blip is not found in the plots I made using 2.6. I also think I've seen it on some plots on other threads where people where having problems with G33 and G33.1.
I'm not familiar with the processes for reporting bugs, are there instructions somewhere?
I'm not familiar with the processes for reporting bugs, are there instructions somewhere?
Last edit: 11 years 1 month ago by Todd Zuercher.
Please Log in or Create an account to join the conversation.
- dgarrett
- Offline
- Platinum Member
-
Less
More
- Posts: 492
- Thank you received: 297
11 years 1 month ago - 11 years 1 month ago #63012
by dgarrett
Replied by dgarrett on topic Coordinated Motion involving rotary axis
A good way to make a report and not have it lost in
transient conversations is to open a ticket on
sourceforge (you probably need to create a sourceforge
login).
sourceforge.net/p/emc/bugs/?source=navbar
The more information you include, the more likely a
report will be investigated.
For instance, include:
1. system and linuxcnc version info
You can use the output of the command linuxcnc_info
2. sim configuration (a complete tar file if necessary)
2. example gcode file to demonstrate the issue
3. halscope configuration (use halscope File/Save Configuration
to create a halscope config file)
4. detailed instructions to demonstrate behavior
transient conversations is to open a ticket on
sourceforge (you probably need to create a sourceforge
login).
sourceforge.net/p/emc/bugs/?source=navbar
The more information you include, the more likely a
report will be investigated.
For instance, include:
1. system and linuxcnc version info
You can use the output of the command linuxcnc_info
Code:
$ linuxcnc_info ;# outfile is /tmp/linuxcnc.info
2. example gcode file to demonstrate the issue
3. halscope configuration (use halscope File/Save Configuration
to create a halscope config file)
4. detailed instructions to demonstrate behavior
Last edit: 11 years 1 month ago by dgarrett. Reason: add url
Please Log in or Create an account to join the conversation.
Time to create page: 0.547 seconds