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


 

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.

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

@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.)