Current Page: NeXtMidas Training X-Midas Interoperability XBC Messages Configured Messages
- - - - | Sending configured messages to a host primitive: When sending a NeXtMidas message to X-Midas, NeXtMidas will automatically convert the NeXtMidas message to an X-Midas message. The data in the NeXtMidas message should be a Table. The keys in the table should match the names in the configured message. Example (message configuration):
            name  msglog
            L:severity              ! 1=Error, 2=Warning, 3=Informational
            S[24]:date_time         ! Timestamp
            S[40]:source            ! Primitive name which initiated message
            S[80]:text              ! message text to be displayed
      - Example (message):
            MESSAGE SEND MSGLOG MSGLOG ^id ^info {SEVERITY=^severity,&
              DATE_TIME="^time",SOURCE="^source",TEXT="^text"}
Receiving a configured message from a host primitive: The message will be similar to the message sent (field names match the message configuration).
X-Midas Users Take Note:
NeXtMidas does not support modifying the name of the `info` field in a message. This means that all info fields will be `info` inside a NeXtMidas message even if the host primitive uses an `infoalias`.