Serial Device Monitoring

 

InSight can monitor reads and writes between the application and serial devices and “pseudo-serial” devices.  The following list characterizes InSight’sserial device monitoring capabilities:

 

• Serial devices are often associated with data that needs to be secure such as credit and debit card data.   InSight’sdefault installation will not monitor any serial device by default.  Furthermore, to enable tracing, an end date that is within 30 days of the current date must be specified in the insight configuration file (InSight.cdi).
• Application interface monitoring is supported for up to 4 devices.
• Device channel monitoring for serial devices is supported.
• A  utility program, DEVCHAN, is provided and supports real-time collection of device channel trace data.  It supports active collection of device channel data from either serial devices or printers or both.  It also supports requesting the terminal to snapshot dump.  Both a .286 versionand .exe version are available.  Source code for the program is also provided -> devchanis one of the sample programs in the InSightSDK.
• The dump formatter supports extracting and formatting serial device information from snapshot terminal dumps and full terminal dumps.
• Required CDI keywords : allowSerial [1|2|34]Monitoring, allowSerialMonitoringEndDate.  Note that full documentation for cdikeywords is available in c:\qsa\cdi\insight.all as part of controller installation.
• Optional CDI keywords: tagentSerial[1|2|3|4] devChBuffSizeKB, tagentDevChLowLevel
• Device channel traces for serial I/O on the 485 channel include extra information.  All data writes to the device channel contain a command byte.  All incoming data from the device channel contains 2 status bytes.  The InSightdump formatter and DevChaninterpret these extra bytes of data.
• Example application interface trace output from formatted dump data:

 

Serial2|msec     826.439|11:39:26|SeqNum 28965|

    Ser2Xmit 0000: 0232 392E 3130 3030 3037 3132 0323       * 29.10000712 #  *

Serial2|msec     826.467|11:39:26|SeqNum 28972|

    Ser2Recv 0000: 06                                       *                *

 

• Example device channel trace output  from formatted dump data:

 

DChnW|S2|msec     826.439|11:39:26|SeqNum 28964|ID 02( xmit  )|Port 11|Addr 65|lCtrl ??|

       Command: 08=Transmit

     xmitdata 0000: 0232 392E 3130 3030 3037 3132 0323       * 29.10000712 #  *

DChnR|S2|msec     826.448|11:39:26|SeqNum 28967|ID 02( xmtACK )|Port 11|Addr 65|lCtrl n/a|

DChnR|S2|msec     826.466|11:39:26|SeqNum 28971|ID 01( recv  )|Port 11|Addr 65|lCtrl ea |

       StatusByte1: 50    StatusByte2: 46     CRC: D431

       StatusByte1: TimerOverFlowRcvBuff2NotEmpty

       StatusByte2: Initialized  RTS   DTS

     recvdata 0000: 06                                       *                *                

 

• Example device channel trace output  from DEVCHAN output file:

 

DChnW|S2|msec     826.439|11:39:26|SeqNum 28964|ID 02( xmit  )|Port 11|Addr 65|lCtrl ??|

       Command: 08=Transmit

     xmitdata 0000: 0232 392E 3130 3030 3037 3132 0323       * 29.10000712 #  *

DChnR|S2|msec     826.448|11:39:26|SeqNum 28967|ID 02( xmtACK )|Port 11|Addr 65|lCtrl n/a|

DChnR|S2|msec     826.466|11:39:26|SeqNum 28971|ID 01( recv  )|Port 11|Addr 65|lCtrl ea |

       StatusByte1: 50    StatusByte2: 46     CRC: D431

       StatusByte1: TimerOverFlowRcvBuff2NotEmpty

       StatusByte2: Initialized  RTS   DTS

     recvdata 0000: 06

                                       *                *             

• Feature verification steps:

1.      Install InSighton the primary 4690 controller by running InSighti.286

2.      Add the required CDI keywords for this feature.

3.      Reload terminal(s)

4.      Go to a 4690 command prompt and run qsa_bin :devchan.

5.      Page to the terminal you’d like to trace

6.      Press F8 to start serial device channel tracing

7.      Run transaction on a terminal

8.      When finished, press ESC.

9.      Review devchan.outfile.