Advanced Search

Note that 'genhexkins' is meant for hexapods, which may or may not be what you are using.
linuxcnc.org/docs/html/man/man9/kins.9.h...Hexapod%20Kinematics
 

PS. If I happened to have a 5i22 and daughter/breakout boards to go with it, I would be more inclined to try to use it than to try to sell it. Especially if I were planning a Linuxcnc related project.

hello gentelmen,

Does somebody have time to help me tested some behaviour of the actual trajectory planner(trapeziodal)? maybe there is bug in the TP and I need more independent observations ... 

Its just regular simulation setup with some precise steps to replicate ... the post the picture of the watched scope please

I need help from you please...

If you are ready, create axis.ini sim OR sim axis_mm.ini trivkins simulation UI ... then

• Start Lcnc
• Enable
• home all
• hal scope
• observation time as long as possible but period is fine 40ms
• add joint.0.vel-cmd.. scale 20
• add joint.1.vel-cmd.. scale 20
• split them to they own space
• Load Gcode program(from attachements but watched behaviour is present everywhere)
• hit play button alias program run
• observations the spline created by gcode (nice smooth steady - the first one)
• wait program end OR stop program by program stop/stop radio button
• break point 1(only for repeat command)
• return home G28 or rehome everything
• I press start button again at same code no change, no position change nothing just return to row 1 of gcode
• start program with play radio button
• observations the spline created by gcode (clingy - every other)
• wait program end OR stop program by program stop/stop radio button
• go to breakpoint 1(only for repeat command)

Please paste your scopes ... I hope your velocity splines will be exact same at rerun the gcode!!!

My scope is at rerun different each time ... 

many thanks


 

For a simple example of a switchable kinematics component see:
github.com/LinuxCNC/linuxcnc/blob/master...onents/millturn.comp
This is the kinematics used in the simulation config at 'configs/sim/axis/vismach/millturn'

For a more complex but fully documented example that might even cover your use case this might be of interest:
forum.linuxcnc.org/show-your-stuff/49103...-head?start=0#271334
The two kinematic models presented in the zip folder attached to the above post can do a fair bit more than what you need but together with the documentation it will give you an in depth introduction on how to build your own kinematic components.



For documentation on building linuxcnc on your local machine (RIP):
linuxcnc.org/docs/html/code/building-linuxcnc.html

Hi Stepperonline Thank you very much for the guide, and a warm welcome to the forum. I hope you’ll be able to help us with any questions we have on the forum.

If you are using Gmoccapy then you can use the 'gmoccapy.program.progress' halpin which is created by the GUI.

 

This was my thinking to get the program length if it was not being computed.

Is there a way of accessing "program.length" to set a global # parameter, say #1100 (#1100 = halcomp["program.length"] or is there a way to access halcomp["program.length"] inside of gCode?

Or better yet, is program progress being computed by gmoccapy which can be connected to an analog output, say motion.analog-out-01? This would be preferred since no additional lines need to be added a gcode file to track progress., just a HAL connection to the display widget.

Thanks for that @rodw. your contributions in this forum is a godsend. I am still a newbie, nonetheless plan on contributing as much as i can.

The geometry makes sense, i didn't struggle with that. i always unfolded the pipe in my head. the geometry of the pipe is the same but i guess the g-code produced by the CAM is different.

In option 1, where the pipe is on a chuck its a mere single axis rotation command of -60 degrees, and then a movement along the x-joint for notch.

In option 2, the torch would have to maneuver along the pipe which is both a y-axis, z-axis movement, and also c-axis rotation, then a movement along the x-axis for a notch.

Writing all of this has made me realize it is CAM dependent as you said. so nothing would change but I would need to use the genhexkins for full 6-axis. I'll have a go at it then.

Hello Aceiera,

Can you help modifying this Kinematics which I can compile as .comp file, I'm Total noob to understand RIP installation.

Any documentation or guide, for RIP in 2.9.8.


Thanks in advance

Good used PC's with PCI slot:
HP Z400
HP Z600
There are others, but these are very, very good, and very cheap.
Edit:
Z400 here still goes for around 100Euro, while Z600 i got last year for roughly 35 Euro a piece, despite being a dual Xeon machine with more RAM and more everything. Z400 is still called "gaming PC" here, hence the price.
Both are very high quality workstations and worth every penny.

Gmoccapy simply counts the lines of the loaded file:

@Lcvette

Fingers crossed, in 2 to 4 weekends.

Not sure how much "commissioning" will be required, this is my first time setting up a cnc-lathe.

I am planing to make the Z limits movable so they can be adjusted to the type of chuck being used and where the tailstock is positioned.

Timeline depends a bit on the weather, it's currently very hot here in West London, UK.

Thanks.

I dont have an answer, but i know its possible - there are interfaces with progress bars.

It worked, THANKS! )))

I changed the scale as well, the speed is not so precise, probably it depends on the milling machine board as well. I will add an encoder in the future, but for now, it's ok!

Thanks, have a nice day!

Examining the linuxcnc.stat() module I see that there is "current_line"  method. Is there a way to get the total number of lines in a loaded gcode file to drive a progress meter?