cli:franke:fgd-esa-robot

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cli:franke:fgd-esa-robot [2023/06/20 00:37]
n.bergantino [Items count interface]
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 ======
 +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 ===== ===== Items count interface =====
 The Fragranite Machining Cell subsystems are: The Fragranite Machining Cell subsystems are:
Line 16: Line 23:
 |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:MM:SS|00:03:17| |Time of starting task in Robot 1|Time in the format HH:MM:SS|00:03:17|
Line 31: Line 39:
 Follows 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> <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> </code>
 ===== Machine status interface ===== ===== Machine status interface =====
Line 55: 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:MM:SS|00:03:17| |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| |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 an example of a string that ESA can send when a STOP began:+Follows an example of a string that ESA can send when a STOP begins:
 <code csv> <code csv>
-STOP;ROBOT2;20230430;00:03:17;20\04+STOP;FMC002;ROBOT2;20230430;00:03:17;20\04
 </code> </code>
 ^  STOP->RUN data structure  ^^^ ^  STOP->RUN data structure  ^^^
 ^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:MM:SS|00:03:17| |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| |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 an example of a string that ESA can send when a STOP began:+Follows an example of a string that ESA can send when a STOP terminates:
 <code csv> <code csv>
-RUN;ROBOT2;20230430;00:08:17;20\04+RUN;FMC002;ROBOT2;20230430;00:08:17;20\04
 </code> </code>
  
  
  • cli/franke/fgd-esa-robot.1687214278.txt.gz
  • Last modified: 2023/06/20 00:37
  • by n.bergantino