TransSECS Message Matching - GEM Tool Messages
A TransSECS GEM Tool will be automatically handle the messages below that are part of the SECS/GEM standard. These should not be added to your project:
Host Message | Tool Response Message |
---|---|
S1F1 | S1F2 with SVID value(s) automatically inserted in reply |
S1F3 | S1F4 with SVID value(s) automatically inserted in reply |
S1F11 | S1F12 with SVID list automatically inserted in reply |
S1F13 | S1F14 with MDLN and SOFTREV automatically inserted in reply |
S1F15 | S1F16 with OFLACK |
S1F17 | S1F18 with ONLACK |
S1F21 | S1F22 with VID list automatically inserted in reply |
S1F23 | S1F24 with CEID list automatically inserted in reply |
S2F13 | S2F14 with ECID value(s) automatically inserted in reply |
S2F15 | S2F16 with EAC automatically inserted in reply |
S2F17 | S2F18 with date/time of tool automatically inserted in reply |
S2F23 | S2F24 with TIAACK automatically inserted in reply and trace started if appropriate |
S2F29 | S2F30 with ECID list automatically inserted in reply |
S2F31 | S2F32 with TIACK and date/time of tool automatically reset |
S2F33 | S2F34 with DRACK automatically inserted in reply and listed report(s) enabled/disabled (if not error) |
S2F35 | S2F36 with LRACK automatically inserted in reply and listed report(s) linked/unlinked to events(s) (if not error) |
S2F37 | S2F38 with ERACK automatically inserted in reply and listed event(s) enabled/disabled (if not error) |
S2F45 | S2F46 LIMITS monitoring. Any VID with Limit Min, Limit Max and CEID properties defined can be used in LIMITS Monitoring |
S5F3 | S5F4 with ACKC5 automatically inserted and alarm(s) enabled/disabled |
S5F5 | S5F6 with alarm list automatically inserted |
S5F7 | S5F8 with enabled alarm list automatically inserted |
S6F11 | Event messages with report data automatically inserted |
S6F15 | S6F16 with report data automatically inserted |
S6F17 | S6F18 with report data automatically inserted |
S6F19 | S6F20 with report data automatically inserted |
S6F21 | S6F22 with report data automatically inserted |
Many of the Stream 7 messages are also handled if you add Recipe Handling to your solution.
For host application, TransSECS will also automatically handle event messages (S6F11 and S6F13) and alarm messages (S5F1) and will respond to multi-block request notifications. Even those these are part of the SECSI (serial port) standard many HSMS tools will erroneously send these messages. TransSECS will always respond accepting the request. The following messages are handled:
S2,F39/F40 S3,F15/F16 S4,F25/F26 S6,F5/S6,F6 S7F1/F2 (Process Program Load Inquire) S13,F11/S13,F12 S14,F23/F24 S15,F1/F2 S16,F1/S16,F2 S19F19/F20