No worries, that's what the forums are for. You are not alone, there are enough other people asking questions if you do some searches you can sometimes even find the answers quicker than posting questions.
To answer your questions, what I mean by 'bytes to control the message' are the bytes that are not part of your payload. For this bursting example that would refer to the first two bytes in each of the two packets we send [50][00] and [50][A0]. 0x50 is the burst message id and the second byte contains the channel number and burst sequence bits. In the example you give the packets starting with [03][4e][00][01] are events you will
receive, from the ANT device not that you send. The event code is the last byte; you will receive 0x0A (signifying the burst started) sometime after you begin sending the burst packets to the chip, and you will receive 0x05 (signifying the burst completed) after the chip has sent the final closing packet in the burst.
So, if you look at the script I supplied earlier, the only thing you write is two packets to burst the 16 bytes.
For your second question, the document ANT Message Protocol and Usage here
http://www.thisisant.com/images/Resources/PDF/1204662412_ant_message_protocol_and_usage.pdf describes the burst sequence byte and everything else about bursting in section 9.5.5.3.
The mask for the sequence bits is 100000 (only the upper 3 bits). The first sequence number is 0, followed by a rolling counter 001,010,011 looping, the last packet is setting the first bit high and the latter two bits should be whatever the counter would be if it was another packet. (See the doc for an example and more explanation)
