This documentation is for an unreleased version of MPF!
This is the developer documentation for MPF 0.51, which is the “dev” (next) release of MPF that is a work-in-progress. Use the “Read the Docs” link in the lower left corner to view the developer docs for the version of MPF you’re using.
Represents a single drop target in a pinball machine.
Args: Same as the Target parent class
Accessing drop_targets in code
The device collection which contains the drop_targets in your machine is available via
self.machine.drop_targets. For example, to access one called “foo”, you would use
self.machine.drop_targets.foo. You can also access drop_targets in dictionary form, e.g.
You can also get devices by tag or hardware number. See the DeviceCollection documentation for details.
Methods & Attributes
Drop_targets have the following methods & attributes available. Note that methods & attributes inherited from base classes are not included here.
Add this drop target to a drop target bank.This allows the bank to update its status based on state changes to this drop target.
Parameters: bank – DropTargetBank object to add this drop target to.
No longer keep up the target up.
Keep the target up by enabling the coil.
Pulse the knockdown coil to knock down this drop target.
raise_config_error(msg, error_no, *, context=None)¶
Raise a ConfigFileError exception.
Remove the DropTarget from a bank.
Parameters: bank – DropTargetBank object to remove
Reset this drop target.
If this drop target is configured with a reset coil, then this method will pulse that coil. If not, then it checks to see if this drop target is part of a drop target bank, and if so, it calls the reset() method of the drop target bank.
This method does not reset the target profile, however, the switch event handler should reset the target profile on its own when the drop target physically moves back to the up position.