Echelon Neuron C - Manual (Page 207)

Neuron C Programmer’s Guide 195
Sets the number of network buffers available for outgoing priority messages
and network variables.
Incoming Network Buffers
These compiler directives set the size and number of buffers between the MAC
and network processors for incoming explicit messages and network variables.
See Table 14 on page 196 for a list of default and allowable non-default values.
#pragma net_buf_in_size
n [ , modifier ]
Sets the network buffer size (in bytes) for incoming application messages and
network variables. A minimum size of 50 bytes is required to receive
network management messages from network tools.
#pragma net_buf_in_count n [ , modifier ]
Sets the number of network buffers available for incoming application
messages and network variables.
Incoming Application Buffers
These compiler directives set the size and number of buffers between the network
and application processors for incoming application messages and network
variables. See Table 14 on page 196 for a list of default and allowable non-
default values.
#pragma app_buf_in_size n [ , modifier ]
Sets the application buffer size (in bytes) for incoming application messages
and network variables. A minimum size of 22 bytes (34 bytes if explicit
addressing is used) is required to receive network management messages
from network tools.
#pragma app_buf_in_count n [ , modifier ]
Sets the number of application buffers available for incoming application
messages and network variables.
Number of Receive Transactions
The number of incoming transactions that can be handled concurrently by the
network processor is determined by the receive transaction array. The following
compiler directive sets the number of entries in the array. The size of a receive
transaction entry is 13 bytes. See Table 14 on page 196 for a list of default and
allowable nondefault values.
#pragma receive_trans_count
n
Sets the number of entries in the receive transaction array. The size of a
receive transaction block is 13 bytes.
A receive transaction entry is required for any incoming message that uses either
unacknowledged repeat, acknowledged, or request service. No receive
transaction entries are required for unacknowledged service. A receive
transaction entry is required for each unique source address/destination
address/priority attribute. Each receive transaction entry contains a current
transaction number. A message is considered to be a duplicate if its source