Overview of sdiSMS

sdiSMS is a single server supporting both SECS-I and HSMS. sdiSMS comes with the following components:

• TESTConnect
  
• SMSD Runtime daemon for simultaneous SECS-I and HSMS communication
  
• ActiveX/COM SECS-II API for building SECS-II interfaces
  
• HTML based API reference help
  
• Sample applications and examples

Through the TESTConnect, the user can develop the message definition for the SECS-II interface using intuitive active SECS icons. Subsequently, the ActiveX/COM SECS-II API is used to quickly develop a SECS-II interface using Visual Basic.

SMSD Daemon

The SMSD daemon is used by other applications such as TESTConnect and CIMConnect. SMSD is a single server supporting both SECS-I and HSMS.

• One or more device can communicate SECS-I at the same time that other devices communicate HSMS using the SMSD server.
  
• Switching between SECS-I and HSMS requires only a configuration selection change.

• SMSD's unique configuration allows it to run on a different CPU than the client. This allows for flexibility and expandability in group or cell configurations when adding components that require GEM/SECS communication.

SECS-I - HSMS Configuration Screen

 sdiSMS Competitive Advantages

• Simultaneous SECS-I/HSMS support in one driver. Multiple devices communicating either SECS-I or HSMS can run on one server.
  
• This provides a method to progressively migrate from SECS-I to HSMS with minimum interruption.
  
• Two way, SECS-I/HSMS conversion is also provided without coding
  
• SECS/HSMS driver can run on a separate CPU than the host software and act as a terminal server on an NT PC.
• Group and cluster inline controllers can use one SECS driver and have a '"one wire" SECS interface to host station controller
  
• Daemon configuration changes can be made at runtime without interruption. Users can also obtain port status and statistical data at runtime.
  
• User can reconnect to a given device without restarting and without interruption to any other devices connected to SMSD

SECS-II ActiveX/COM API

• SECS-II and General Utility Libraries provide simplified methods for SECS communication:
  
• Native WindowsNT Technology Uses ActiveX/COM Components
  
• Simplified Access to SECS Message Data Items - Provides random access to data items. No "walking" the message structure to read data items.
  
• Easier to Develop and Maintain - No need to know type and size of data items that you are not interested in or guess the maximum buffer size required.
  
• SDI software automatically allocates memory when it is needed.
  
• Reduce the Amount of Code to Maintain. Only assign the values you need for your program.
  
• Default values are configurable through TESTConnect explorer. Don't "hard-code" values.