SECS GEM

[paul.r]

Hi All,

I am wondering if anyone has ever implemented a SECS GEM interface in LabVIEW, and if so, if they could share some information about the scale of the project - estimates on man hours required to implement, major hurdles etc.

I am just starting to really dive into the protocol, but from what I have seen so far, while it does seem like a lot of work, everything seems pretty straightforward. There are a lot of 3rd party tools, but none are specifically targeted at LabVIEW, and I would prefer to keep everything in LabVIEW/in house if possible. I know sometimes using an external tool ends up being more pain than it is worth, which I am trying to avoid.

Thanks!

[paul.r]

Anyone?

[TylerC1123]

Hi paul.ross,

I don't personally have any experience with implementing this type of protocol but I was able to find a KnowledgeBase article of ours that should help out. LabVIEW doesn't support this natively but, as I believe you've found, there are third-party tools, such as OPC Servers, that can be used to accomplish this.

Can LabVIEW Communicate Via the SECS-I or SECS-II Protocol?

[paul.r]

Hi Tyler, 

Thanks for the link - I had seen that, however I am really just looking to get information from anyone has implemented an interface(or is fairly familiar with the standard) so that I can get a better idea on the scope of work.

Thanks!

[mateomiller]

Hello 

SECS (SEMI Equipment Communications Standard)/GEM (Generic Equipment Model) are communication interface protocols for communication between a semiconductor equipment and a fab host.  More information https://www.einnosys.com/introduction-secs-gem/ 

[Marc-Agileo]

Hi Paul,

We have recently interfaced Agil'GEM from Agileo Automation with LabVIEW. It is very straightforward since LabVIEW can natively call .NET Assemblies using .NET 4.0 and Agil'GEM is a full .NET assembly that implements SECS-I, HSMS, SECS-II and GEM SEMI standards.

It is just required to pay attention to a few limitations in the .NET API supported by LabVIEW but this can be easily overcome.

Marc

[ixuyay]

Is the problem solved? Could you share some examples and learn from each other

[Marc-Agileo]

The solution is to create a wrapper as described here: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PA8QSAW&l

Thanks to the wrapper, you can hide to LabVIEW the things that it doesn't support.