User`s guide
116
K
A
DAK
KwikNet System Construction
3.7 Using KwikNet with AMX
3.7.1 AMX System Configuration
KwikNet includes its own interface to the underlying operating system. The KwikNet OS
Interface for AMX is ready for use without modification or customization.
KwikNet makes few demands for AMX resources. Consequently, there are few changes to
your AMX System Configuration Module required to accommodate KwikNet.
KwikNet Task
A single KwikNet Task drives the KwikNet TCP/IP Stack. You must add this task to your
list of predefined tasks in your AMX System Configuration Module. You can use the
AMX Configuration Builder to do so. The task's definition is as follows:
Tag KNET
Procedure name kn_task
Priority Above all tasks which use KwikNet
Task stack size AMX minimum plus 1024
Queue 0 0
Queue 1 0
Queue 2 0
Queue 3 0
With AMX 86 and some toolsets, you may have to add a leading or trailing underscore
( _ ) character to the task procedure name. Note that the KwikNet Task must execute at a
priority above all tasks which use KwikNet services.
The task stack size requirement will vary with the particular version of AMX you are
using. As a good rule of thumb, choose a stack size which is approximately 1024 bytes
more than the minimum stack size required for an AMX task. Add more stack if any of
the following conditions exist.
Target is a RISC processor with increased stack demands
KwikNet options are used which make use of file system services
KwikNet debugging aids are enabled in your KwikNet Library
For all versions of AMX, the
KwikNet Task is a simple task with no AMX message
queues.
KwikNet uses private messaging blocks for internal communication with the
KwikNet Task. The total number of available messaging blocks is defined by you on the
Target property page when you create your KwikNet Network Parameter File. You may
have to grow the number of messaging blocks if any of the following conditions exist.
You have many tasks using network services
You service several networks concurrently
You expect high levels of network packet activity