Advanced Search

Maybe this is 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?

@Lcvette:

It's a DIY XZC slant-bed gang-tool configuration

• Based on a Dunham 5C spindle headstock w/Hardinge taper
  • Step-dir AC servos on all axes, plus 1 micron scales on X & Z
  • Main spindle motor is 3.7kw 8kRPM 'servo-spindle' from SZGH
  • 10kPPR encoder on spindle (40k post-quad) for decent C-axis resolution
• It has a scratch-built 5C sub-spindle mounted to the main XZ slide
  • Both the main and sub have pneumatic collet closers
  • Sub driven by 1kw 5kRPM servo
• Parting slide mounted to headstock (think Omniturn-style)
  • Can be controlled/programmed as a V-axis or X-axis (to permit CSS)
  • Permits main to sub hand-off for back-work
• Main XZ mounted live tool (24k VFD-powered spindle w/ER11)
  • Suitable only for light work, 1/4" or smaller cutters

Regarding the GUI & Probe Basic, here's my wishlist

• Extremely large DRO for XZ, smaller for V/C. Gmoccapy's DRO style is nice.
• On-screen parts counter of some sort.
• Large G-code window, with adjustable font size
  • Don't need/want large preview screen, but do want easy buttons to 'flip' the preview between front tool, back tool, and sub-spindle front/back tools.
• 3 spindles displayed (RPM & load), or at least two at once.
  • I won't have the main and sub turning at different speeds at the same time, but I do want live-tool speed/status at the same time as main/sub spindle
• No on-screen machine controls, or ability to disable
  • No jogging buttons, cycle-start, stop, etc.
  • No on-screen sliders, up/down spin-box buttons, etc.
  • No way to move the machine except via MDI, probing macros, or external physical controls
  • No keyboard control of machine, period.  Keyboard is for data input only.
• Need some GUI real estate for a number of LED indicators (or similar)
  • Main-sub synch active/off
  • Parting slide in V-axis or X-axis mode
  • I have three 'mist/air blast' sources, plus 4 spare air valves for clamps or future automation fixturing/loading.  Need indicators for what's on/off.

Everything is working now, but I haven't built the back-working tools or mount - nor am I 'fluent' with the lathe.  Can't quite figure out how or where to mount more than one tool without causing massive interference with main-slide tools.  I was starting to work on a design with I got side-tracked switching my mill over to Ethercat servos a month or so ago.
 

While the 5i22 is marked as "obsolete" on Mesa's web site. I think that has more to do with the fact that they can no longer be purchased new, and that new one's can't be made due to components being out of production. Functionally I think they are still supported by Linuxcnc, and the most difficult part of using one would be finding a motherboard with a PCI slot (not that hard). I don't know that the 5i22 was ever very popular with Linuxcnc due to the fact that they were rather expensive, a bit overkill, and there were/are much cheaper options from Mesa. (I never used one.)

If you want to draw a line on a pipe, it does not matter if you rotate the pipe or rotate the pen.

Here is your homework. I've already done this. Google coping calculator and review the maths and graphics for a notch in a pipe to be butt joined to another tube. print it on light card and cut the outline out. Wrap it around your tube, trace it with a felt pen and cut that notch out with an angle grinder. 90 deg join is easy to cut. 45 deg is a bit harder (as its deeper) with the angle grinder but it can be done fairly easilly. The maths creates the desired outline and won't care how you cut it! Options 1 & 2 are identical.

If you are cutting a length of RHS, it still has a standard profile defined in an engineering standard so you can still follow the surface to cut it with similar maths.

I think Its predominately a CAM problem but when you want to angle the torch, some kinematics might help. Not sure if it will help but 2.10 now includes some tangential headings which may assist. I think the full 6 axes may let you cut I beams