Getting started
Copyright IXXAT Automation GmbH
38
IEM Manual, 1.5
use the initialization data
as_MapTableInit[]
. This array contains the generic
members.
The unique variable identifier
dw_reference
is set by the module, so it has to
be initialized by host with 0. The protocol specific addresses are
not
part of
this structure initialization. Inside
APPdemo_ChannelConfigureGeneric()
the
generic members are copied to the map table now.
The second step is to fill in the protocol specific addresses in this map table.
This has to be done individually by each protocol.
The Figure 2-16 should clarify the relationship between the structures
t_MAP_ENTRY_INIT,
APP_t_MAP_ENTRY,
COM_t_ADDRESS
and
COM_t_SPECIFIC
.
APPdemoGenMain.c
Generic attributes
Specific attributes
t_MAP_ENTRY_INIT
APPdemoxxx.c
COM_t_ADDRESS
COM_t_SPECIFIC
EMI_cmdChannelConfigure()
APP_t_MAP_ENTRY
APP_as_MapTable[i]
APP_xx
xMapTa
blePrep
are()
Chann
elCon
figureG
eneric
()
Figure 2-16: Example of object mapping from the demo application
The registering of a single variable will be done by means of the
function. In our demo application we are using a
loop to acquire the registration of all needed variables. Please have a look at
the function code of
APPdemo_ChannelConfigureGeneric()
which should
clarify the process.
To add variables by modifying the demo application do the following steps:
1. Adapt the variable count
APP_cfg_NUM_OF_VARIABLES
at
APPint.h
2. Add generic entries and initialize its members at
APPdemoGenMain.c
3. Edit protocol specific address part at
APPdemoxxx.c