Edit packet content in benchmark

Hi everyone,

In benchmark, the packet is 23-byte long, inclues preamble, access code,
header, payload, crc, and ‘x55’. Now I want to add a one-byte flag after
the header. I changed the packet_utils.py make_packet block, add a flag
when form the new packet. And changed the header length to 9. However,
in terminal, when I run benchmark, it shows the new packet is 24-byte
long now, including the flag byte. But in the file_sink after the
byte2chunks and the chunks2symbols, the file is not longer than before.
In these two files a packet is still 23 bytes without the new flag byte.
So though in tx terminal, it looks like I’ve successfully changed the
packet format, but actually, the transmitter didn’t send this out, it
still sends the original packet format.

Has anyone come across this problem before, and could give me some kind
suggestions on this? Thanks in advance!

Ada

On Mon, Jun 24, 2013 at 12:08 PM, yeran [email protected] wrote:

terminal, it looks like I’ve successfully changed the packet format, but
actually, the transmitter didn’t send this out, it still sends the original
packet format.

Has anyone come across this problem before, and could give me some kind
suggestions on this? Thanks in advance!

Ada

In the receiver, the deframing strips the header, so you’re only
getting the payload out. You’ll need to look at what the receiver code
is doing to read the header and return the packet length. You can
update that code to also include your flag from the header.

Tom