Advanced Search

Eventually they gave up and adopted USB-C. (Oh well..., so much for all that work)

nope, they did not "adopt" it, they were forced by Europe.

bevins wrote:

You can do it like this.

loadrt toggle count=5
addf toggle.0 servo-thread
setp toggle.0.debounce 50 

net flood-toggle toggle.0.in <= hm2_5i25.0.7i77.0.0.input-29
net flood-control toggle.0.out => hm2_5i25.0.7i77.0.0.output-02

If you need only one toggle, do not use "count=5" as that creates 5 toggles, so that would also need all the addf and setp and inputs and outputs in hal, for all 5, from 0 to 4.

You can do it like this.

loadrt toggle count=5
addf toggle.0 servo-thread
setp toggle.0.debounce 50 

net flood-toggle toggle.0.in <= hm2_5i25.0.7i77.0.0.input-29
net flood-control toggle.0.out => hm2_5i25.0.7i77.0.0.output-02

Thanks for the replies, I should have noted the inhibit logic on the drive itself in my earlier post, but from my interpretation of the datasheet for the 12A8, GND at the input would disable the drive.  Is that correct?
11 INHIBIT IN TTL level (+5 V) inhibit/enable input. Leave open to enable drive. Pull to ground to inhibit drive. Inhibit turns off all power devices.

If so, I would just connect direct to each servo drive with a ground wire connected to the following pins below on the mesa board and then the other side of the floating switch would also go to GND:  
net joint-0-enable joint.0.amp-enable-out => hm2_7i97.0.ssr.00.out-00
net joint-1-enable joint.1.amp-enable-out => hm2_7i97.0.ssr.00.out-01

Alternatively, if I could figure out how to make those into one signal with OR'ed logic for turning ON and AND logic for turning off, I would just drive the 12V relay on the board with one output, however, the Estop approach may be the simplest one to implement when reusing the existing PCB.  

I'm assuming the Mesa board / LCNC don't care if anything is connected to servo enable as long as the motors move when commanded?  Meaning if the servos were enabled externally via Estop for example, the motion control would still work just fine and I could leave out the above two net commands from the HAL file?

No it is not.
FireWire was a very good standard that got killed by corporate greed.
It was also used for networking mainly as interconnect between switches due to it's full duplex speed, besides all DV cameras having it at one point in time.
I liked it and used it plenty, and still have some add on cards rusting away in the shop.

Hi,

I am currently implementing a rack tool changer. My problem is that the Hal Pin "iocontrol.0.tool-prep-pocket" is always Zero. Do I need to activate it in my HAL File? Its currently initialized as following:
My Tool Table looks as follows:
However, even when inserting Tool1 prep-pocket is always 0. Is there something I am missing?