No, HSMS is a header/message component in the SECS/GEM protocol for TCP. The header is expected to precede 100K or more of attached data. This could represent a "program", "recipe" or "wafer cassette inventory list". SECS-I is the RS-232 ANSI-type "transport" for SECS/GEM commands/objects, which has to fragment everything into packages of 255 bytes, or fewer. Thus, the big HSMS message must be broken up into multiple SECS-I packets. This kind of fragmentation/defragmentation process is not supported by the Digi One IA RealPort. Most wafer fab MES system are large UNIX or IBM main-frames. Of these systems the majority of them should be able to put SECS-I into TCP via a raw socket, which the Digi One happily supports. Being that HSMS is rarely used protocol component, Customers should evaluate their system to see if they truly need HSMS on Ethernet, rather than SECS-I into TCP. If their MES system can support SECS-I in TCP (or UDP), that would be a better long-term solution. This also has a very useful ability to manage GEM objects larger than 64K by the MES-to-SECS-I direct solution. The SE DR1 solution cannot handle objects larger than 64K, of which most "programs" of complex wafer cells will be larger than 64K. 

Related Information: