Using direct memory files, Using direct memory, Files – Echelon FTXL User Manual

Page 108: 96 for mor

Advertising
background image

96

Developing an FTXL Application

utility, might not be able to communicate with a device that is in the extended

mode.

To return an FTXL device to the legacy mode, rather than the extended mode,

perform one of the following tasks:

• Re-run the LonTalk Interface Developer utility to generate a new

signature for the device, and rebuild and load the application image.

• Send the NM_NODE::NM_INITIALIZE extended network management

command to the device.

• Erase the non-volatile memory for the device.
• If the device is currently commissioned in an LNS database, de-

commission it.

You should not need to perform any of these tasks often because most network

management tools use LNS or are compatible with ECS.
For more information about the LonTalk extended command set (ECS) network
management commands, see the

LonTalk Control Network Protocol Specification

,

EIA/CEA 709.1-B-2002. This document is available from the IHS Standards

Store:

http://global.ihs.com/doc_detail.cfm?item_s_key=00391891&item_key_date=9711

31&rid=CEA

.

Using Direct Memory Files

To use configuration properties in files, your host application program must
implement a method that allows the network management tool to access those

files. You can support either one of the following:

• The L

ON

W

ORKS

FTP protocol

• The host direct memory files (DMF) feature

The FTP protocol is appropriate when large amounts of data need to be

transferred between the host processor and FTXL Transceiver. The host DMF

feature is appropriate for most other cases.

By supporting direct memory files, your application allows the network

management tool to use standard memory read and write network messages to

access configuration property files located on the host. Direct memory files
appear to the network management tool as if they were located within the FTXL

Transceiver’s native address space, but the FTXL LonTalk protocol stack routes

memory read and write requests within the DMF memory window to the
LonMemoryRead() and LonMemoryWrite() callback handler functions provided

in the FtxlHandlers.c file. These functions use the LonTranslateWindowArea()
support function, which is generated by the LonTalk Interface Developer utility

to translate between FTXL Transceiver addresses and host addresses.
If the model file contains a network variable of type SNVT_address, the LonTalk
Interface Developer utility automatically generates all necessary code and data

for the memory read and write requests, including code in the LonInit() function

to register the virtual memory window with the FTXL LonTalk protocol stack.

Advertising