0

Platform: iOS with TCP/IP comms.

The following is an example of my incoming data stream.

$PLTIT,HV,0.20,M,0.00,D,-58.70,D,0.30,M*71
$PLTIT,HV,1.90,M,0.00,D,-8.30,D,1.90,M*41

A valid message frame looks like this:

$PLTIT,HV,1.90,M,0.00,D,-8.30,D,1.90,M*41

But there could be moments where I get this:

[time n+0]  $PLTIT,HV,0.20,M,0.00,D,-58.70,D,0.30,M*71
[time n+1]  $PLTIT,HV,1.90,M,
[time n+2]  0.00,D,-8.30,D,1.90
[time n+3]  ,M*41
[time n+4]  $PLTIT,HV,0.20,M,0.00,D,-58.70,D,0.30,M*71
[time n+5]  $PLTIT,HV,0.20,M,
[time n+6]  0.00,D,-58.70,D,0.30,M*71
[time n+7]  $PLTIT,HV,0.20,M,0.00,D,-58.70,D,0.30,M*71
[time n+8]  $PLTIT,HV,0.20,M,0.00,D,-58.70,D,0.30,M*71

The result is a broken up message frame in the middle.

What objects/containers can I use under iOS to enable me to collect all the data bytes correctly for parsing and not lose any bits due to some intermittent comms or equipment?

Brian Tompsett - 汤莱恩
  • 5,753
  • 72
  • 57
  • 129
Sebastian Dwornik
  • 2,526
  • 2
  • 34
  • 57

1 Answers1

0

A simple buffer of any variety should do the trick. If your data is always textual then you could even just append to an NSMutableString.

All you'd have to do is append the data, do a check to see if the buffer contains more than a single instance of the $ character (which I assume is your delimiter between entries), and if it does then process each entry except the very last, leaving the last one in the buffer until the next chunk of data arrives.

aroth
  • 54,026
  • 20
  • 135
  • 176
  • This data is always textual and my delimiting markers are '$' and '\n' between frames. Will NSMutableString suffice or perhaps CHCircularBufferQueue might be better? – Sebastian Dwornik Oct 28 '11 at 14:25