Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cli:franke:fgd-esa-robot [2023/06/20 00:34] n.bergantino [Items count] |
cli:franke:fgd-esa-robot [2023/06/21 10:28] (current) n.bergantino |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== FGD - Fragranite Machining Cell ====== | ====== FGD - Fragranite Machining Cell ====== | ||
| - | ===== Item count interface ===== | + | We can have more than one Fragranite Machining Cell in the facility, so in the follow it will be mandatory to distinguish each one of them. \\ \\ |
| + | We will use the following codes to identify uniquely the cells: | ||
| + | * FMC001: Cell 1 | ||
| + | * FMC002: Cell 2 | ||
| + | * .... | ||
| + | * FMC00//N//: Cell N | ||
| + | Finally we will assign the name "Cell code" to this field. | ||
| + | ===== Items count interface ===== | ||
| The Fragranite Machining Cell subsystems are: | The Fragranite Machining Cell subsystems are: | ||
| * Robot 1 | * Robot 1 | ||
| Line 11: | Line 18: | ||
| - Robot 2 terminates the task | - Robot 2 terminates the task | ||
| For each terminated process ESA will send data to Next via TCP/IP channel. \\ \\ | For each terminated process ESA will send data to Next via TCP/IP channel. \\ \\ | ||
| - | {{: | + | {{: |
| The data sent by ESA will consist in the following structure: | The data sent by ESA will consist in the following structure: | ||
| ^Field^Description^Example^ | ^Field^Description^Example^ | ||
| |Command|A specific string of 4 characters|ITEM| | |Command|A specific string of 4 characters|ITEM| | ||
| |Product|The code of the product|114.0055.882| | |Product|The code of the product|114.0055.882| | ||
| + | |Cell code|The code of the cell that is producing the item|FMC001| | ||
| |Data of starting task in Robot 1|Data in the format YYYYMMDD|20230430| | |Data of starting task in Robot 1|Data in the format YYYYMMDD|20230430| | ||
| |Time of starting task in Robot 1|Time in the format HH: | |Time of starting task in Robot 1|Time in the format HH: | ||
| Line 24: | Line 32: | ||
| |Data of terminating task in Robot 2|Data in the format YYYYMMDD|20230430| | |Data of terminating task in Robot 2|Data in the format YYYYMMDD|20230430| | ||
| |Time of terminating task in Robot 2|Time in the format HH: | |Time of terminating task in Robot 2|Time in the format HH: | ||
| + | |||
| + | The string must be prepared considering the following rules: | ||
| * Each field is separated by the next one by the character //';'// | * Each field is separated by the next one by the character //';'// | ||
| * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number) | * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number) | ||
| - | In the follow | + | |
| + | Follows | ||
| <code csv> | <code csv> | ||
| - | ITEM; | + | ITEM; |
| </ | </ | ||
| ===== Machine status interface ===== | ===== Machine status interface ===== | ||
| Line 52: | Line 63: | ||
| ^Field^Description^Example^ | ^Field^Description^Example^ | ||
| |Command|A specific string of 4 characters|STOP| | |Command|A specific string of 4 characters|STOP| | ||
| + | |Cell code|The code of the cell where the event is occurring|FMC002| | ||
| |Robot|The robot interested by the event: ROBOT1 or ROBOT2|ROBOT1| | |Robot|The robot interested by the event: ROBOT1 or ROBOT2|ROBOT1| | ||
| |Data of starting the event|Data in the format YYYYMMDD|20230430| | |Data of starting the event|Data in the format YYYYMMDD|20230430| | ||
| |Time of starting the event|Time in the format HH: | |Time of starting the event|Time in the format HH: | ||
| |Reason of the stop|A numeric code that identify the reason of the stop, from a specific list of the available stops|20| | |Reason of the stop|A numeric code that identify the reason of the stop, from a specific list of the available stops|20| | ||
| + | |||
| + | The string must be prepared considering the following rules: | ||
| * Each field is separated by the next one by the character //';'// | * Each field is separated by the next one by the character //';'// | ||
| * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number) | * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number) | ||
| - | In the follow | + | Follows |
| <code csv> | <code csv> | ||
| - | STOP; | + | STOP;FMC002; |
| </ | </ | ||
| ^ STOP-> | ^ STOP-> | ||
| ^Field^Description^Example^ | ^Field^Description^Example^ | ||
| |Command|A specific string of 3 characters|RUN| | |Command|A specific string of 3 characters|RUN| | ||
| + | |Cell code|The code of the cell where the event is occurring|FMC002| | ||
| |Robot|The robot interested by the event: ROBOT1 or ROBOT2|ROBOT1| | |Robot|The robot interested by the event: ROBOT1 or ROBOT2|ROBOT1| | ||
| |Data of starting the event|Data in the format YYYYMMDD|20230430| | |Data of starting the event|Data in the format YYYYMMDD|20230430| | ||
| |Time of starting the event|Time in the format HH: | |Time of starting the event|Time in the format HH: | ||
| |Reason of the stop|A numeric code that identify the reason of the stop, from a specific list of the available stops|20| | |Reason of the stop|A numeric code that identify the reason of the stop, from a specific list of the available stops|20| | ||
| + | |||
| + | The string must be prepared considering the following rules: | ||
| * Each field is separated by the next one by the character //';'// | * Each field is separated by the next one by the character //';'// | ||
| * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number) | * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number) | ||
| - | In the follow | + | Follows |
| <code csv> | <code csv> | ||
| - | RUN; | + | RUN;FMC002; |
| </ | </ | ||