On 10/08/12 19:55, Nick F. wrote:
You can do it either way since unstuffing will never generate a valid
HDLC framing code (“01111110”). Unstuffing before the deframing
For what i understand, bit stuffing never generates framing code (that’s
the whole point), but the bit unstuffing can and will if the payload
contains itself a byte which as the same value as the framing code.
Actually, while dumping data from ais_parse.cc, I found that gr-ais
unstuffing code do generate framing codes. that has fooled
get_tags_in_range (a stop was found because the AIS payload had a
01111110 in it).
Well, I think I found, I’m still scratching my head…
correlators means my tags’ sample numbers don’t have to be modified for
the bits inserted by the unstuffing operation.
Yes, I see the point. But you could unstuff inline, in place of the
memcpy, just before calling parse().
Tel: + 353 (0) 1 236 5990 <tel:%2B%20353%20%280%29%201%20236%205990>
Discuss-gnuradio mailing list
[email protected] <mailto:[email protected]>
Embedded systems engineer.
1 Harbour road
Tel: + 353 (0) 1 236 5990