Advanced Search

Hello David
Thanks for writing. As far as I know the hydraulic tool changers were both working until I interfered with them. Now the horizontal one is not working and been like that fo two years. I suspect the springs are broken but I don't know haw to pull the unit apart. There is hydraulic pressure in the lines but maybe the lines need bleeding. I cant see how best to do that.
I need to send you some photos. I tried once before (years ago) and failed.
I am going to be away for a few days. Promise some action on my return
Cheers Chris McMullen
Auckland New Zealand

There is a guy who sells flexihal boards in aus.....i dont know what his site is, but he goes by Jaymis

Some of Mesa's cards have dedicated inputs for hand-wheel encoders.
But this is so slow counting that you can use normal pins and the encoder component to get the hand-wheels inputs.
"normal pins" means parallel port pins, mesa input pins or some other digital io in pin.
linuxcnc.org/docs/html/man/man9/encoder.9.html

This is a weird-ish question, but LinuxCNC is so vast, I thought I'd ask:

I have a build where I'm making a trunnion inside the same area where the XYZ axis operates. Now that trunnion is growing up to have parts attached to it...

Is there a way to define a "no go zone" within the XYZ build box so that I don't accidentally crash into it?

It would need several different sections, ie, a series of boxes could be defined within which the controller is supposed to know that's not OK and send that 'move would exceed limitations' message if I tried to violate it.

I'm thinking the answer is "with great complexity comes great responsibility..."

But I thought I'd ask.

Cheers. 

Hi all,

* Note, the topic name was changed up to 2 times by someone, haha.

Today i added look ahead. This took almost half a day. It's a tiny file, but took a lot off time.
Here is the look_ahead_source_code_file

Now i did a test run tonight using a line fillet algo :  file_path_standard_subseg_line_fillet
This is a simple optimizer algo, that is handy for simple runtests.

The test is done on the extreme  spiral_on_surface file. With tiny segments 0.001mm and deviation P0.0001 Q0.0

Some hal values:

• incements_a_cycle = 2   (planner skips extra gcode segment to keep up with scurve new position)
• ring buffer size = 10
• total loaded segments from program start = 15117
• future buffer, items that are ready to perform, including fillet segments = 3
• cycle dist, is the distance in mm for current servo cycle = 0.0078 mm
• hal traject buffer dist, total todo segments length. ( sum off future buffer ) = 0.1544764 mm

This file run's quite nice for what it is.

 

Git sources are updated.
The first donation is recieved. Thanks ! See the github readme file for more info !