gem300

Differences

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

Link to this comparison view

gem300 [2021/07/12 12:21]
wikiadmin created 		gem300 [2024/09/19 14:07] (current)
wikiadmin
Line 3: Line 3:
 === Easy Integration of E39, E40, E87, E90, E94 with PLCs, Programmatic, OPC and more... === === Easy Integration of E39, E40, E87, E90, E94 with PLCs, Programmatic, OPC and more... ===
  
 +300mm Standards (E40, E87,E90, E94, E88 etc.) are based around state models.  These models are defined in the standards and implement in the 300mm wrapper of TransSECS.  The architecture for the 300mm standards is similar for each.
  
 +E39 is also a 300mm standard but it defined data access and doesn’t define any state models – it’s completely transparent in the TransSECS wrapper implementation
 +
 +In TransSECS, the implementation of each of the standards has two components - the //service wrapper// and the //callback interface//.  
 +
 +==== Service Wrapper ====
 +
 +The service wrapper provides services that are used by the implementation to indicate an action taken in the control system, for example, a carrier arrived, process job started or completed, or a substrate moved from one location to another.  It's enough for the control system to indicate these actions for the 300mm implementations to fulfill the requirements of the standards, including state model transition and event generation to the host.
 +
 +==== Callback Interface ====
 +
 +The callback interface notifies the control system of an action taken by the host.  This might be a request to create or start a process job, or a verification of information such as the carrier Id.  This interface is implemented by the control system and methods on the interface will be called appropriately.
 +
 +{{:pasted:20240919-140656.png}}
 +
 +Here're some sample GEM300 scripts for TransSECS
 [[GEM300 Scripts]] [[GEM300 Scripts]]
  • gem300.1626110474.txt.gz
  • Last modified: 2021/07/12 12:21
  • by wikiadmin