TransSECS PLC

TransSECS PLC

Example project • Build and deploy directly from TransSECS
• Wet Bench • Omron CJ (FINS)
• Wafer Washer • OPC UA Serveur/Mitsubishi Q
• Replacement des capteurs• Omron NX (EtherNet/IP)
• Rétrofit complet d'un équipement (Tool) • OPC UA Client/Modbus
• Wet Bench • Modbus

In the TransSECS editor, you simply define your variables in a tree structure and link them to an API by the device and tag name. You just need a registry card which is a list of variables that you want to make available to the host (VID), a list of alarms (ALID) and events (CEID). If you are not very familiar with SECS/GEM, VIDs are values that you allow the host to read and ALIDs are alarms. CEIDs are "collection events", something that happens in the tool and that might be of interest to the host. Usually, the most important of these were the integrity of the batch, the batch loaded, the batch unloaded, the beginning and end of the batch and the change of processing program (recipe). It's also useful to provide events as the batch is processed, moving from station to station, the door opens/closes, and so on. If you are SECS/GEM and you activate a metrology tool, indications that the data are complete are common.

You define the PLC(s) and registers within the interface:

Data sheet