Hi Guys,
What is meant by "reserve PAYLOW_BUFFER_SIZE (0x08G4 is defined as default value) bytes as a reception buffer" , PAYLOW Length , Paylow data. How to write the C code for this.
Can anyone please help me on this.
-------------------------------------
Remember Amateurs built the Ark, Professionals built the Titanic !
What does it mean when someone asks about a variable or constant name, but forgets to mention where he/she found the name in the first place? That they do not know what processor they are using or where they found the source code?
What number base is that??
I figure the same Google link that describes the PAYLOW_BUFFER_SIZE constant also describes the number base.
i want answer for my qestion
0x08G4
Oh, yeah.
Hello sam,
It seems you're writing some communication code.
PAYLOW_BUFFER_SIZE - Total amount of ram reserved as Receive Buffer PAYLOW Length - It's total size of 'actual data' within 1 frame. PAYLOW Data - It's the actual data of interest within 1 frame.
If you've written code for communications (typically asynchronous i.e. only data is transmitted & receiver generates it's own clock as per baud) you know that - 1) Receiver can get data at any time. 2) Received data may be out-of-order, corrupted, incomplete. 3) Data may be too large to transmit in one go. 4) Receiver may not be able to cope with all the incoming data at the rate of transmission. 5) There may be more than one receiver, more than one transmitter. etc.. etc..
So you've what are known as 'Communication Protocols'. They define the rules which are adhered to by transmitter as well as receiver to successfully communicate with each other.
Typically these communcation protocols define, How data is transmitted as FRAMES. That's chunk of data+additional data. This additional data may include receiver address, frame no., crc, time-stamp, transmitter id, data id etc. This helps receiver(s) to correctly identify data addressed only for them, decode it, ask resend if it was corrupted.
Receiver seperates data within frame as 1) PAYLOW that's the data we actually interested in & 2) Additional data. You can see any introductory book on TCP/IP or other comm. protocols, you'll get this in much more details.
As for defining them in C it is just as array - either of simple bytes or of some struct defined. This depends on protocol you're implementing.
I may add that please be more elaborative with your questions so that you may get more detailed answers.
Hope that helps,
JEREMY SWAN
"PAYLOW that's the data we actually interested in"
Are you sure you are not thinking about payload?
PAYLOAD == PAYLOW
thats my assumption.
can sam confirm?
I don't think we should assume to much until the OP do return and actually gives us a bit of explicit information to work on.
Don't know where the second o went in my "too"...
Hi Agin,
Thankx for the answer.
Note that the question was vague in the extreme, and lacking a great number of important details.
Therefore the answer was based on a great deal of assumptions and guesswork - so there is a high risk that it is not (quite) right for your particular situation...