Binary: [1 1 0 1 1 1 1 1] [1 0 0 0 0 1 0 1]
This unsolicited report reports that the Slink-e received garbage on its serial port which did not form a valid RS-232 character. It was something other than a start bit, 8 data bits, and a stop bit (at the current baud rate).
More precisely, the Slink-e recognizes this error when it fails to receive a stop bit. At some time, the Slink-e's serial port is idle and then it sees the data line level go to Mark. It takes that to be the beginning of a start bit. It then samples the line 9 times, at times determined by the baud rate. It takes the first 8 of those to be the data bits (so any value is valid). It take sthe 9th to be the stop bit, which means it must be at Mark level. If it is not, the Slink-e recognizes a framing error.
One cause of this is corruption in the communication line. A bogus start bit -- a spurious Mark pulse during an idle time on the line -- would cause it. Another cause is improper settings in the UART that is sending data to the Slink-e. The proper settings are 1 start bit, 1 stop bit, 8 data bits, no parity, and the same baud rate that is set in the Slink-e. If the settings are improper, you should see framing errors on virtually every character.
This is always unsolicited. It reports a synchronizing error.