Moving to feeder location when not homed

97 views
Skip to first unread message

Mark Patton

unread,
Apr 2, 2023, 4:31:01 PM4/2/23
to OpenPnP
I just discovered that if I turn my PnP machine on and start Open PnP but not home the machine, then go to one of the feeders and move the head to reference hole location, the head will move from wherever it happens to be.  This new location could be anywhere.

Can anyone think of a reason why popping up an error with "Machine not homed" or some such error would be a bad idea? 

I could home the machine when the host connects, but I can think of reasons why that could be ill advised.  Unexpected head motion, for instance. 

mark maker

unread,
Apr 3, 2023, 2:26:37 AM4/3/23
to ope...@googlegroups.com

That's a valid concern.

It is one of these functionalities that are so "primal" that we don't think much about them anymore, i.e. quite out of place, now that bar for adequate safety is much higher than back in the beginnings.

Because these functions with motion are virtually everywhere, this needs some thinking... I have an idea, though.

_Mark

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/5def69f6-d3ae-44ea-a62a-99790ccbc424n%40googlegroups.com.

Mark Patton

unread,
Apr 3, 2023, 10:48:31 AM4/3/23
to OpenPnP
Thanks Mark!

ma...@makr.zone

unread,
Apr 5, 2023, 4:21:43 AM4/5/23
to OpenPnP
Hi everybody

NOTE: this affects everybody, please read.

From the description:

On unhomed machines the current position is not known by the controller, they often power-up/reset to zero coordinates at the position the machine randomly happens to be. Positioning the machine to a prerecorded location can therefore lead to a crash. Only few actions in OpenPnP check if the machine is homed and prevent that. Most notably the generic Position to Location buttons do not.

This PR makes this safer. In doing so, it distinguishes two types of motion:

  • Jog motion is allowed, when the current controller machine position is positively known to OpenPnP. It is assumed that the user observes the true machine position and will avoid jogging into obstacles.
  • Non-jog motion is generally disallowed on unhomed machines.

The machine homing safety checks are centrally administered inside the motion planner, so motion generated from all sources is covered.

The behavior can be overridden on the driver, in case it proves too restrictive, e.g. for controllers where absolute linear encoders are available and homing is simply not required, or where homing is inherently and safely done when powering up. This option can be controlled per driver, i.e. it can be treated differently if multiple drivers/controllers with different capabilities are involved. The drivers assigned to axes determine which drivers are relevant for a certain motion.

This is now in the OpenPnP test version. Please allow some minutes to deploy.

_Mark
Reply all
Reply to author
Forward
0 new messages