Differences

This shows you the differences between two versions of the page.

--- cli:franke:fgd-esa-robot [2023/06/20 00:21]
n.bergantino [Machine status interface]
+++ cli:franke:fgd-esa-robot [2023/06/21 10:28] (current)
n.bergantino
@@ Line 1: / Line 1: @@
 ====== 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:
   * Robot 1
@@ Line 11: / Line 18: @@
   - Robot 2 terminates the task
 For each terminated process ESA will send data to Next via TCP/IP channel. \\ \\
-{{:cli:franke:franke-esa-interface.png?600|}}
+{{:cli:franke:franke-esa-interface.png?600|}} \\ \\
 The data sent by ESA will consist in the following structure:
 ^Field^Description^Example^
 |Command|A specific string of 4 characters|ITEM|
 |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|
 |Time of starting task in Robot 1|Time in the format HH:MM:SS|00:03:17|
@@ Line 24: / Line 32: @@
 |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:MM:SS|00:08:40|
+The string must be prepared considering the following rules:
   * 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)
-In the follow an example of a string that ESA can send at the end of the process:
+Follows an example of a string that ESA can send at the end of the process:
 <code csv>
-ITEM;114.0055.882;20230430;00:03:17;20230430;00:06:12;20230430;00:06:24;20230430;00:08:40\04
+ITEM;114.0055.882;FMC001;20230430;00:03:17;20230430;00:06:12;20230430;00:06:24;20230430;00:08:40\04
 </code>
 ===== Machine status interface =====
@@ Line 39: / Line 50: @@
 ESA will send to Next via TCP/IP a specific message for each of the two state transition. \\ \\
 {{:cli:franke:franke-esa-stop.png?700|}} \\ \\
-In the case of RUN->STOP transition the sent data are:
+Considering a STOP event for one of the two robots, it is necessary to send the 2 messages in a specific order, in particular:
+  - RUN -> STOP transition
+  - STOP -> RUN transition
+Next will not consider any different sequence, for example:
+  - RUN -> STOP transition
+  - RUN -> STOP transition
+or
+  - STOP -> RUN transition
+  - STOP -> RUN transition
+In the follow the data structure for the 2 transitions.
+^  RUN->STOP data structure  ^^^
 ^Field^Description^Example^
-|Data|
+|Command|A specific string of 4 characters|STOP|
-===== Robot interface =====
+|Cell code|The code of the cell where the event is occurring|FMC002|
-==== Items count ====
+|Robot|The robot interested by the event: ROBOT1 or ROBOT2|ROBOT1|
-In the follow the machine subsystems:
+|Data of starting the event|Data in the format YYYYMMDD|20230430|
-  * Robot 1
+|Time of starting the event|Time in the format HH:MM:SS|00:03:17|
-  * Robot 2
+|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 //';'//
+  * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number)
+Follows an example of a string that ESA can send when a STOP begins:
+<code csv>
+STOP;FMC002;ROBOT2;20230430;00:03:17;20\04
+</code>
+^  STOP->RUN data structure  ^^^
+^Field^Description^Example^
+|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|
+|Data of starting the event|Data in the format YYYYMMDD|20230430|
+|Time of starting the event|Time in the format HH:MM:SS|00:03:17|
+|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 //';'//
+  * At the end of the string it will be placed the exadecimal code 0x04 (4 as a number)
+Follows an example of a string that ESA can send when a STOP terminates:
+<code csv>
+RUN;FMC002;ROBOT2;20230430;00:08:17;20\04
+</code>
-Each row refers to a complete process
-.0055.882 # 06/04/2023 00:03:17 # 06/04/2023 00:06:12 # 06/04/2023 00:06:24 # 06/04/2023 00:08:40
-.0055.882 # 06/04/2023 00:06:24 # 06/04/2023 00:09:19 # 06/04/2023 00:09:31 # 06/04/2023 00:11:48
-.0656.768 # 06/04/2023 00:30:57 # 06/04/2023 00:34:23 # 06/04/2023 00:34:35 # 06/04/2023 00:36:27
-.0198.674 # 06/04/2023 00:34:35 # 06/04/2023 00:37:50 # 06/04/2023 00:38:02 # 06/04/2023 00:39:57
-.0266.040 # 06/04/2023 00:38:02 # 06/04/2023 00:40:58 # 06/04/2023 00:41:09 # 06/04/2023 00:43:18
-.0198.674 # 06/04/2023 00:41:10 # 06/04/2023 00:44:25 # 06/04/2023 00:44:37 # 06/04/2023 00:46:32
-.0656.768 # 06/04/2023 00:54:40 # 06/04/2023 00:58:06 # 06/04/2023 00:58:18 # 06/04/2023 01:00:11