| > Generally speaking,how would I go about managing a device with a serial
> (RS232) console interface.
If you just want to open a terminal emulator session to the device and
use the device's 'native' command line interface then that's trivial:
- register the deivce a REFERENCE object,
- write a quicky launched application that picks up one of the
objects identifiers,
- create a file somewhere (a priori) that maps the objects
identifier to a TTY (or LTA) port,
- create a decterm do a set host/dte <port name> voila.
If you have kermit installed on the system, that might be a little more
robust that the "set host/dte" option. also Kermit's dialling
procedures would be a little more straightforward if the devices you
want to talk to are dial-up in nature.
If you want to do more integrated things, then you'll need to do more
sophisticated things like parse the ascii strings (or whatever the
protocol is) etc. [The less-defined the protocol, the uglier it
gets...] You may also be able to do some interesting things via the
Script AM, but I haven't sat down and thought that one out very well...
/doug
|
| Thanks,
I do indeed wish to do some more sophisticated stuff than the standard
CLI of the device,but wondered if there was some "vanilla" code that
would help me get the Command Strings to/from the Box to MCC,thus
simplifying the issue.
Kev.
|
| Check out the conferece UFP::MODEM, that tool might do the trick. It supports
scripts that can conditionally do various things based on input received. Also,
it supports sending out 'canned' character sequences.
MODEM is the internal product but it is availale as an ASSET tool for customers
as well.
Lee (long-time MODEM user)
|