Application specific code for ip 852 interfaces, Selecting the device type, Application-specific code for ip-852 interfaces – Echelon LonTal Stack User Manual
Page 153
LonTalk Stack Developer’s Guide
141
ble.cpp
Stack\LtLayer4.cpp X
X
X
Stack\LtLayer6.cpp X
X
X
Stack\LtMip.cpp X
X
X
Stack\LtMipApp.cpp X
X
X
Stack\LtMsgOverride.cpp X
X
X
Stack\LtNetworkImage.cpp X X
X
Stack\LtNetworkManager.cpp X
X X
Stack\LtNetworkManager2.cpp X
X X
Stack\LtNetworkStats.cpp X X
X
Stack\LtNetworkVariable.cpp X X X
Stack\LtNetworkVariableConfig
uration.cpp
X X
X
Stack\LtNetworkVariableConfig
urationTable.cpp
X X
X
Stack\LtOutgoingAddress.cpp X
X X
Stack\LtPlatform.cpp X
X
X
Stack\LtProXy.cpp X
X
X
Stack\LtReadOnlyData.cpp X X
X
Stack\LtRouteMap.cpp X
X
X
Stack\LtStackClient.cpp X
X
X
Stack\LtStatus.cpp X
X
X
Stack\LtTransactions.cpp X
X
X
Stack\LtXcvrId.cpp X
X
X
Stack\NdNetworkVariable.cpp X
X X
Stack\dedef.cpp X
X
X
VXLayer\VxLayer.c X
X
X
VXLayer\VxLQues.c X
X
X
VXLayer\VxMsgQ.c X
X
X
VXLayer\VxSemaph.c X
X
X
VXLayer\VxTimers.c X
X
X
Application-Specific Files for LonTalk Stack Devices
If you are building an application device that uses a native LonWorks or IP-852
interface, you need to include the LID-generated files that customize your
application interface, and modify the templates as appropriate.
Application-Specific Code for IP-852 Interfaces
If you define an IP-852 interface, you must include a valid, unique ID for the
IP-852 interface. If you are defining an application device, you must register this
unique ID (prior to calling the LonInit() method) using the
LonResgisterUniqueId() method. This method is defined in the
Source\FtxlApi\FtxlApi.h file.
Selecting the Device Type
Your build process must define one of the following preprocessor definitions that
are used by LonTalk Stack to control the type of device that is being built: