Advanced Search

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 !

Whoops. Big error on my part!
It's easy to forget stuff at my age. I should have checked stuff before I spouted off..
The missing pressure switch in the hydraulic in the photo is 3F1. It runs the pump directly. Otherwise the pump works as mentioned.
Contactor 5K1, which operates the tool unclamp, solenoid is part of a complex set of interlocks that stop you releasing the tool while the machine is running and stops the machine running if the tool is being changed. It also defeats the gear change jogging.
I'm not sure exactly how it works if you have the Philips controller, but I think that if you pulled any of that wiring by removing the controller the tool unclamp wont work and probably also the auto tool changer.
A lot of the interlocking is relay logic so it's probably possible to sort through the logic and strap it where the controller stuff no longer counts.
If I had an auto tool change on mine it would have been done completely on the back plane of the Heidenhain controller. But even then the relay logic would be involved and 5K1.
A key starting point is: does the hydraulic pressure pump run? It's noisy on mine. It usually runs for about 5 seconds on mine if the machine has been off for a while. On mine the light in the power button illuminates if the hydraulic pump isn't running. It's directly wired to the other contact in the 3F1 pressure switch. Seems an odd way to do it. And the bulb sometimes blows from the solenoid kick.
You will have to change gears using a spanner. On mine the half inch drive extension of a socket set works. The manual has a chart of what the coloured dots on the selector cams mean.
I think I put the logic drawing of this up earlier. It's so complex that it took me days to understand. And as you can see I often get confused by it. I went so far as to draw it in each possible state by erasing the other stuff. And even then I don't know if I got many of the possibilities.
A simple test might be to just press on the tickler on 5K1 contactor and see if the tool unclamps? Make sure to catch the tool if one is fitted.
 

As the message says it's not really an error, I think the only way to stop the message would be to modify the hal_parport code, or I not sure if this would work but add a debug level when loading the driver. First would work but means compiling Linuxcnc one's self the second option is just a guess.
If the machine works I wouldn't bother too much about it. Yeah it is a little annoying. But then again you have the convenience of CNC