Feeder InterLocking#
Feeder Interlocking is accomplished by the Setup Center Feeder External Control API to prevent usage of certain feeders. Setup Center calls the Feeder External Control Service in the following cases:
- Online Area: If the feeder is placed in the machine on a changeover table If table management is active the feeder is checked only if a changeover table has already been registered for the location where the feeder is placed. A changeover table with feeders is registered for a location in the machine (if the changeover table management is active).
- Offline Area(Pre-Setup Area): If the feeder is placed on a docking station or feeder rack. -The offline setup verification is started scanning the setup report, docking station ID and changeover table ID. Setup Center composes a list of the feeder IDs. The list is sent to the External Feeder Control Service for approval. The service checks the feeder IDs and reports a status “Feeder is OK” or “Feeder is not OK” and a reason why the feeder should not be used. Rejected feeders which are placed in online area are locked on the machine (component pickup not possible). The error message is displayed on the station GUI. The feeder LED will only be set to red color if the feeder is used in the recipe.Otherwise the feeder LED is off. Rejected feeders which are placed in pre-setup area show “locked” in their display if present and the LED is turned to red color. The feeder status is also updated in the Setup Center GUI to “Error” (red color). Subsequent Setup Center operations for verifying packaging units with a scanner (setting, refilling packaging unit and activation of tracks) checks the feeder status set by the External Control Service and deny verification if the feeder was locked. A corresponding message is shown on the display of the scanner.
Communication Parameters#
| Name | Type | Possible Values | Default Value | Description |
|---|---|---|---|---|
| enableMode | Enum | NoneOnePerEnterpriseOnePerSiteOnePerLine | None | How should activate Feeder Interlocking instance:None - No instance will be usedOnePerEnterprise - One Instance for all Lines (Enterprise level)OnePerSite - One Instance for all Lines (Site level) OnePerLine - One Instance per Line |
| callbackPort | Integer | 0 | What port to use to receive events from Feeder Interlocking. Use 0 to use a free port at callbackBasePort + 400 | |
| statusReplyTimeout | Integer | 60000 | Number of milliseconds to wait for a FeederInterlockingStatus reply |
Events#
FeederInterlocking.Event.InterlockingRequest#
Setup Center requests the MES System to validate feeders maintenance.
| Property Id | Data Type | Possible Values | Description |
|---|---|---|---|
| FeederInterlocking.Property.Feeder.IdList | String | Single or multiple feeder Id (comma separated) to validate | |
| FeederInterlocking.Property.Feeder.AdditionalInfo | Object | Attached Feeders additional information |
Commands#
FeederInterlocking.Command.StatusRequestReply#
This command is used to send a reply to the FeederInterlocking.Event.InterlockingRequest event, and is expecting the following parameters:
| Command Parameter Name | Type | Mandatory | Possible Values | Default Value | Description |
|---|---|---|---|---|---|
| Internal.ReplyId | String | Yes | Id of the request that this command is supposed to reply | ||
| FeedersId | String | Yes | Single or multiple feeder Id (comma separated) that | ||
| RequestResults | String | Yes | 0,1 | The result of the board validation returned by MES. Must be:<br> 0: OK: The feeder interlocking status is ok. The feeder can be used. <br> 1: NotOk: The feeder interlocking status is overdue. This is a comma separated value string for all the FeedersId | |
| Reasons | String | Yes | A reason for the return value of requestResults (comma separated values) |