Echelon LonTal Stack - Manual (Page 21)

LonTalk Stack Developer’s Guide 9
Notes:
1. ShortStack Micro Servers running on FT 3150 or PL 3150 Echelon Smart
Transceivers support up to 254 network variables. ShortStack Micro Servers
running on FT 3120 Echelon Smart Transceivers support up to 240 network
variables, and ShortStack Micro Servers running on PL 3120 Echelon Smart
Transceivers support up to 62 network variables. A custom Micro Server can
support up to 254 network variables, depending on available resources.
2. ShortStack Micro Servers running on FT 3150 or PL 3150 Echelon Smart
Transceivers support up to 127 aliases. ShortStack Micro Servers running on FT
3120 Echelon Smart Transceivers support up to 120 aliases. ShortStack Micro
Servers running on PL 3120 Echelon Smart Transceivers support up to 62 aliases.
A custom Micro Server can support up to 127 aliases, depending on available
resources.
3. See the ISO/IEC 14908-1 Control Network Protocol Specification for more
information about the extended command set (ECS) network management
commands. This document is available from ISO:
www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=60203
4. An implementation of the L ON W ORKS file transfer protocol (FTP) is not provided
with the product.
5. For more information about the direct memory files (DMF) feature, see Using Direct
Memory Files.
The LonTalk Stack solution provides support for any host processor with the
highest performance and highest network capacity, and it can be used on native
L
ON W ORKS and IP-852 channels. The ShortStack solution provides support for
any host processor, and supports TP/FT-10 and PL-20 channels. The ShortStack
solution supports fewer network variables and aliases that the LonTalk Stack
solution.
Requirements and Restrictions for LonTalk Stack
The LonTalk Stack requires that the application on the host processor use either
an embedded operating system or software that implements a minimum set of
operating system services.
The LonTalk Stack require about 850 KB of program memory on the host
processor, not including the application program or the operating system. In
addition, you must provide sufficient additional non-volatile memory for device
configuration data and any non-volatile data that you include in your application.
You can implement configuration properties as configuration network variables
or in configuration files. To access configuration files, you can implement the
L ON W ORKS file transfer protocol (FTP) or use the direct memory files (DMF)
feature. See Using Direct Memory Files for more information about when to use
FTP or the DMF feature.