User`s guide

the second approach places the burden on the host application.
The first is more
direct and is likely to result in the information getting to the host more quickly.
The
second approach has the primary advantage that no special Neuron Chip application
code is required; also, since the call initiation and host application launch may
require minutes, the time it takes the host application to poll several network
variables is not significant. In the best scenario, upon being launched the host
application would first check with a datalogging node on the network that records
alarms and also the system state, mode, or health information.
Monitoring: L NS Application Design Issues
A well-designed LNS monitoring application using the SLTA-10 Adapter through
modems should use the correct version and layer of LNS, should handle initialization
of the application with the correct LNS database and device driver name, and should
have a phone call session termination and an application termination strategy.
The remote monitoring application is based on LNS Object Server of LNS 1.5 or
higher. Applications based on the LNS 1.0 and LNS 1.01 do not behave well by
default and do not allow for certain dial-out scenarios. Applications written at the
NSS layer are not supported for use with the SLTA-10 Adapter across a pair of
modems.
The remote monitoring application should open the appropriate LNS and device
driver. Specifically, the mapping of the Remote ID to the LNS database should be
handled by the application. We suggest using the command line arguments with the
information available from the SLTALink Manager. Note LNS capacity keys may
need to be hard-coded in the monitoring application.
Finally, the LNS application needs to implement a termination strategy that meets
the needs of the application and the system.
Good Practices / Schemes that Work
Use these guidelines to avoid the system-level failures detailed above:
l When expecting the SLTA-10 Adapter to dial-out from the network to a remote
PC, dedicate one SLTA-10 Adapter to dial-out and always have that SLTA-10
Adapter connect to the same remote PC. Make sure that the NSI EEPROM is
configured correctly. See figure 7.11.
l If an LNS-based application is connected to the network through modems,
dedicate one SLTA-10 Adapter in the network to handle dial-out and dial-in with
this PC that has the LNS server. Make sure that the SLTA-10 adapter’s
EEPROM is configured correctly. See figure 7.12.
l Several PCs can share one SLTA-10 Adapter as long as the calls are all initiated
on the remote PC hosts (i.e., dial-in only) and each remote LNS application
removes the bound connections to its host before terminating.
See figure 7.13.
SLTA-10 Adapter User’s Guide
7-19