Advanced Search

Pretty sure this is all you need
net spindle.0.on hm2_7i76e.0.7i76.0.0.output-11
or this
net solenoid-bearing_air spindle.0.on hm2_7i76e.0.7i76.0.0.output-11

Did you add new limit switch to monitor the cylinder extended position? 

if not, right now you are activating a relay when the cylinder position is in between

(cylinder-position < 900) and (cylinder-position > 1600)

And you would like to stop any axis movement when the above statement is true AND the cylinder-position < 1600?

please upload you hal file and I will add for you some hal code that you can test.

Ah, even easier. Thanks!

Like so ( I would also like to use manually using code, thus mapped to motion pin)?
net solenoid-bearing_air spindle.0.on hm2_7i76e.0.7i76.0.0.output-11 <= motion.digital-out-05

在相同的电脑配置下版本对比2.94版本哪个实时性能更好？
我的电脑配置如下；
cpu i3 9300
主板微星b360M直击炮
内存双通道16G
M.2 256G固态
关闭了睿频，隔离了2—3个内核。
整机配置不到100美元（我是来自中国的数控爱好者）

There is no wiring between the motors and controller: all power and signals pass through the drives. The wiring diagram doesn't help: communication to the control, whether data or discrete signal, isn't explained (i.e. wire xxx connects terminal y1 to x1, but you don't get to know what it does).

Given that I can't actually test the questionable motor properly, I think it may make more sense to replace the motors with modern servo systems.

Thanks for pointing to the Manual, I was not aware that this document changed.

I got it working now. One thing I added was the Airblast when picking up / putting away the tool by rewriting M24 and M25.

However, there is also the Airblast Button in the GUI. Is it actually connected to something?

Another point is that the ATC seems to forget the traverse Feedrate every time I start linuxcnc. When picking up a tool I get the error "Cannot do g1 with zero Feed rate" and have to go into the Rack Setup and click "Update rack parameters" (although the Feedrate is stated correctly here).

I now know that clicking "Ref Rack data"  loads the Tools that are stored in the Rack. Unfortunately, It doesn't use the Tool Table "Rack" coloumn as I understood. 
I assume this would require a Python script to read the tool table and make it usable via Gcode?

Thank you for your patience by the way, really appreciated!

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.