It seemed that the RCIN app generally read 1 frame(25 bytes data) at a time and process the frame.
But it is programmed that it is possible that it can read multiple frames at a time and process the frames at a time.
And it detected the RcLost from the frame and increased the StrikeCount.
When the app received 10 frames(10 frames of 25 bytes data) at a time
mixed with 1 NoHdr frame and 1 NoFooter frame and Nominal frames,
the app detected the RcLost only from the last frame that it received.
If the last from of the 10 frames is a nominal frame,
then app didn't detect the RcLost and didn't increased the StrikeCount.
If this is not intended, this should be fixed.
Test case: Test_RCIN_ReadDevice_10Msg_1NoHdr1NoFooter()
It seemed that the RCIN app generally read 1 frame(25 bytes data) at a time and process the frame. But it is programmed that it is possible that it can read multiple frames at a time and process the frames at a time. And it detected the RcLost from the frame and increased the StrikeCount.
When the app received 10 frames(10 frames of 25 bytes data) at a time mixed with 1 NoHdr frame and 1 NoFooter frame and Nominal frames, the app detected the RcLost only from the last frame that it received. If the last from of the 10 frames is a nominal frame, then app didn't detect the RcLost and didn't increased the StrikeCount.
If this is not intended, this should be fixed.