- Posts: 40
- Thank you received: 1
Making M62/M63 codes failsafe
- Limedodge
- Offline
- Senior Member
-
Less
More
4 years 3 months ago #247197
by Limedodge
Making M62/M63 codes failsafe was created by Limedodge
Is there a way to modify any settings to make M62 failsafe (revert to low) in the event of a program crash or emergency stop? for example, a "following error" or something.
I'm using M62/M63 it to fire a laser and it works great until you manually stop motion or hangup. Then the digital out stays high and the laser continues to fire. Only after a deliberate (non zero) motion with M63 does it shut off. For safety reasons, not ideal.
I'm using a 7i96 digital output pin if there's hardware solution someone is aware of
Thanks
I'm using M62/M63 it to fire a laser and it works great until you manually stop motion or hangup. Then the digital out stays high and the laser continues to fire. Only after a deliberate (non zero) motion with M63 does it shut off. For safety reasons, not ideal.
I'm using a 7i96 digital output pin if there's hardware solution someone is aware of
Thanks
Please Log in or Create an account to join the conversation.
- tommylight
- Offline
- Moderator
-
Less
More
- Posts: 22011
- Thank you received: 7491
4 years 3 months ago #247201
by tommylight
Replied by tommylight on topic Making M62/M63 codes failsafe
Sending it through an AND component with the other input wired to machine-is-enabled or PWM-enable or mode-is-auto or.... should do the trick just fine.
That will stop the laser when any of those pins stops.
This is all in HAL.
That will stop the laser when any of those pins stops.
This is all in HAL.
Please Log in or Create an account to join the conversation.
- Limedodge
- Offline
- Senior Member
-
Less
More
- Posts: 40
- Thank you received: 1
4 years 3 months ago #247234
by Limedodge
Replied by Limedodge on topic Making M62/M63 codes failsafe
Brilliant. I'll give that a try. Thanks
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
- Limedodge
- Offline
- Senior Member
-
Less
More
- Posts: 40
- Thank you received: 1
4 years 3 months ago #247334
by Limedodge
Replied by Limedodge on topic Making M62/M63 codes failsafe
Not the correct forum, but since I started the topic here, I'll continue
The problem with wiring to "motion.motion-enabled" is that if you hit stop, motion is still enabled and the output continues to be high. If i stop the program mid path, it continues to be high.
I think I need to do some digging and find a pin/signal to tie to that is only high when there is commanded motion. It get more complicated because in this case I'd need to make sure it's motion in X OR Y (galvos). Just in case it's a straight X or Y move. Unless anyone can think of one?
I'm not sure what pin is "mode-is-auto". Is that an "axis" pin?
The problem with wiring to "motion.motion-enabled" is that if you hit stop, motion is still enabled and the output continues to be high. If i stop the program mid path, it continues to be high.
I think I need to do some digging and find a pin/signal to tie to that is only high when there is commanded motion. It get more complicated because in this case I'd need to make sure it's motion in X OR Y (galvos). Just in case it's a straight X or Y move. Unless anyone can think of one?
I'm not sure what pin is "mode-is-auto". Is that an "axis" pin?
Please Log in or Create an account to join the conversation.
- tommylight
- Offline
- Moderator
-
Less
More
- Posts: 22011
- Thank you received: 7491
4 years 3 months ago #247335
by tommylight
Replied by tommylight on topic Making M62/M63 codes failsafe
A quick search through pins results in:
halui.mode.is-auto <<<< can be used as is
motion.teleop-mode <<<< is inverted so requires inversion
I would use the first one.
halui.mode.is-auto <<<< can be used as is
motion.teleop-mode <<<< is inverted so requires inversion
I would use the first one.
Please Log in or Create an account to join the conversation.
- MaHa
- Offline
- Platinum Member
-
Less
More
- Posts: 542
- Thank you received: 241
4 years 3 months ago #247340
by MaHa
Replied by MaHa on topic Making M62/M63 codes failsafe
I had the similar problem but a different application. Solved with a small component. net x-vel-cmd and net y-vel-cmd to this component, and check if there is any movement (non-zero). Or use 2 wcomp, out to or2 will do the same.
And have look at motion.motion-type 1: Traverse , 2: Linear feed, 3: Arc feed
And have look at motion.motion-type 1: Traverse , 2: Linear feed, 3: Arc feed
Please Log in or Create an account to join the conversation.
Time to create page: 0.261 seconds