**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 |
| S2F25 | S2F26 Loopback Diagnostic Request (LDR) |
| 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) |
| S2F43 | S2F44 supported if spooling is enabled, this the "EnableSpooling" SVID is set to true |
| S2F45 | S2F46 LIMITS monitoring.  Any VID with Limit Min, Limit Max and CEID properties defined can be used in LIMITS Monitoring|
| S2F47 | S2F48 Variable Limit Attribute Request (VLAR) |
| S5F1 | S5F2  Alarm Report Send (ARS) |
| 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 |
| S6F1 | S6F2  Trace Data Send (TDS)|
| 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 |
| S6F23 | S6F24 supported if spooling is enabled, this the "EnableSpooling" SVID is set to true |


Many of the Stream 7 messages  are also handled if you add Recipe Handling to your solution.  See [[recipe_management]]).

| S7F1 to S7F6 | Process Program Load / Request / Acknowledge |
| S7F17 | Delete Process Program Send |
| S7F18 | Delete Process Program Acknowledge |
| S7F19 | Current EPPD Request |
| S7F20 | Current EPPD Data |

Stream 9 (Error Reporting) messages will be sent automatically if the message is not handled within the software.
| S9F1 | Unrecognized Device ID.  Sent if a message is received with a device ID that does not match the configured value |
| S9F3 | Unrecognized Stream ID. Sent if no messages of this stream are implemented |
| S9F5 | Unrecognized Function Type.  Sent if messages of this stream are implemented but this function is not handled |
| S9F7 | Illegal Data.  Sent if the stream and function are implemented but the message does not match the required structure |
| S9F9 | Transaction Timer Timeout.  Sent if the T3 timer expires without a response |


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