Server improperly interpreting escaped start flag

[Rowbotronics]

When an escaped start flag is present in a packet, the server correctly identifies the packet, but then also tries to interpret the section starting at the escaped flag as a second packet.

This is unlikely to cause any real issues as the falsely identified packet should always be discarded, but it raises false flags in the logs.

Jul 14 13:08:19 mcp node[27179]: Writing packet : fa1400010102000afefa52fb
Jul 14 13:08:19 mcp node[27179]: RAW Serial : fa,14,0,1,1,2,0,a
Jul 14 13:08:19 mcp node[27179]: RAW Serial : fa,14,0,1,1,2,0,a
Jul 14 13:08:19 mcp node[27179]: RAW Serial : fe,fa,52,fb
Jul 14 13:08:19 mcp node[27179]: Incoming packet: fa1400010102000afefa52fb
Jul 14 13:08:19 mcp node[27179]: RAW Serial : fe,fa,52,fb
Jul 14 13:08:19 mcp node[27179]: Incoming packet: fa52fb
Jul 14 13:08:19 mcp node[27179]: =============================
Jul 14 13:08:19 mcp node[27179]: Bad CRC 65535 vs NaN
Jul 14 13:08:19 mcp node[27179]: =============================