Advanced Search

In hal, add the air output pin to spindle-on signal
No remap required.

If it only needs to be on when the spindle is on,
you could do it all in hal with  single statement:

net spindle-air spindle.0.on air-solenoid-drive

(with names other than spindle.0.on changed as desired)


 

Hi,

I do have a ATC spindle that requires bearing air. For this, I can enable the solenoid via M64 P05 and disable it via M65 P05. How can I automate it so that it activates the air when the spindle is active (as I understood, every time the M3 command is run)? 
My first idea is remapping the M3 command and add the M64 in it but I do not know how to enable the spindle then in the remapped M3...

I'm not worried about detecting a manual bit change. ToF sensor on ModBus sounds good.

Does the HAL have access to the lowest Z in the loaded file? I know AXIS parses what you load and displays it in the workbox. That will tell you if the loaded job with the current offsets will go outside the boundaries (such as lower Z limit)

But AXIS and LinuxCNC are not the same thing. Isn't that parsing something AXIS does? Does the HAL get that info?

The real benefit would be in protecting against the bit slipping.  Again, this is a makerspace- you and I know how to tighten a bit and inspect collets for damage like prior interior galling that would make it slip.  But in a makerspace, you don't have that much control and threatening users with consequences tends to intimidate them into not wanting to use the equipment at all more than actually reducing spoilboard gouging. 

So far the only viable thing I could picture would be making the spoilboard conductive, putting a 10k pullup on it, and watch to see if the bit contacts and grounds it (you still get conductivity through the spindle bearings in my experience).  But a) it's a vacuum bed, so gluing on tinfoil would defeat the vacuum function.  Conductive paint or even glue can seal off the vac too.  And b) it's a large bed, it might take a whole gallon or more of conductive paint even if we find a type that won't impede the vac flow.  Hmmm.... not only will salt water swell the MDF grain apart, once it dries, a pile of dry salt isn't conductive so that path is not going to work.

I thought of metal window screen mesh, like to keep out bugs.  Still kind of expensive, and gluing may seal the vac.  Also it's allowable- actually necessary- to cut into the spoilboard by a very small amount.  You'd either glue a 1mm layer of shaved MDF on top of the detection mesh- which gets pretty tough to handle spoil board replacement-  or code it so it only checks for a problem when it starts and stops making contact by calculating how much deeper the file would travel into the Z if allowed to continue.  But that would not detect bit slippage until it Z lifts into a new cut, because we said it's allowed to contact and ground the spoilboard surface during a cut, not knowing how deep it actually is.

Can't keep touching off between cuts.  Well, you could, but it would be an extremely annoying waste of time and, again, would still fail to see bit slippage until gouging has already happened.

It's not essential to have a solid detection layer.  If there were a grid of conductive traces spaced 3" apart, 1mm below the surface, that would still  work, generally.  Not effective at accidentally drilling holes too far, but the touch-off usually detects that prob.  Deep drill marks are not that bad for leaking vac in later use, and you can fill them with a putty of MDF dust and wood glue too

David, thank you! That worked.

If you edit your ini file and set the step_scale to be what you had as steps per in Mach, the scale should be correct. Well same as what you had.

If you have a shared home/limit switch you need to add a HOME_OFFSET to move off the switch during homing. During normal operation including jogging, the limit switch should never be triggered unless Oh Sh#t happens.

Thank you Peter,

I don't think I understood much of that

Mike

Hi...sorry for delay...thought I submitted response..


So tried smaller piece...yes..less off...

Rechecked calibration (experimentation)...was off a bit...I will keep trying.. I made this machine...used mach 3 for many years...never had a problem that you would not hear motors banging from stall ....maybe here missing steps would be silent....
Thanks for your help!

Rick

Thanks for the answer
The PIN for HAL is what I'm looking for.
The whole thing should be monitored by my comp. file mentioned above.
The spindle support is only retracted when the axle passes, and this is exactly when I want to monitor whether the cylinder is retracted.
I have no idea how to implement this in the comp. file.
I think it should be an abreage which checks whether the cylinder is really in the end bearing after the command to retract the cylinder.

The CoC was just the thing edge of the wedge, just testing the waters to see what will be accepted.

But misinformation doesn't apply to the gimbernment, they can say what they like, and they have been.....funny how they start saying the quiet bit out loud after the election.
A bit of history regarding free speech Down Under, when they were writing the constitution down on the back of a beer coaster over a few beers, they all decided that free speech didn't need to be included as it was such a basic right no Aussie in their right mind would infringe on it. Look now, we're being run by a mob not in their right mind put there by voters not in their right mind.
There's no conspiracy, once the majority of the population started thinking for themselves it was deemed time to flood the west with a population that can be manipulated by superstition, the gumbernments are doing a deal with the devil thinking they'll get a seat at the table, as always when you deal with the devil he just brings his people with him.
Enoch was right, just its a different group.

Gmoccapy for Linuxcnc 3.4.6

Another way that I've used is to create a couple of hal pins (an input and an output) that control the output in the gui python script. Then useing a couple of user defined M-codes to setp the value of input pin to setp the value of the input pin. This was able to allow the either the gui or the G-code to override the other like your flipflop example. Essentially the same thing, except the flipflop lives in the gui code instead of using a hal component.

That particular drive (80 AST ...) does not seem to be EtherCAT
but they may have an EtherCAT model.