Re: [LHA-misc] Sample Commands (was Line parsing routine)

[Jay H. <jh...@fa...>]

At 10:12 PM 11/28/00 -0500, Neil Cherry wrote:
>Jay Hogg wrote:
> >
> > Ok,
> >     This is from memory and reviewing code since I can't find
> > my paper copy of this and my HD died in March...
> >
> > I've included 2 things inline:
> > - Command/Response document
> > - Sample XML configuration for some of my devices. This is the
> >    "Master" defintion that controls the what/where of all devices
> >    that can be access by the control server.
> >    - Currently called '/usr/local/ha/conf/interface.conf'
> >    - Used by every agent. Start the agent with an 'id' code that is
> >      xrefed in this file to get port/address/device/password/etc.
> >    - The "id" is the prefix to addresses from the server application
> >       (ie  ADDR="napco9600:device.domain.point")
> >
> > Sorry it is so long...  I considered it as an attachment but I
> > know how this group likes to debate inline.  If you want it as
> > an attachment next time just say so.
>
>I think this is fine (but I have a cable modem).
>
>BTW, it is evident that you put a lot of thought into the entire doc.
>Good work! I have some questions (of course).

Thanks. It has been a long time in the works and coincides with stuff
at work that is unrelated except the need for a simple protocol,
*lots* of programs talking, and configs.


> >     <interface
> >        id="ocelot"
> >        desc="Ocelot #1 - Main"
> >        device="//1/dev/cti4"
> >        address="localhost:2004"
> >     />
>
>I noted that the ADICON relay device is seperate from the Ocelot. Is the
>relay controller controled by the Ocelot or is it seperate?
>  The reason I
>ask is that I was wondering about sub devices.

This is an *interface* level definition - specifically defined
by the fact that it is physical (not logical).

The addressing handles the sub-devices.
Ocelot axample:
Addr=0.*  is the Ocelot itself (sub unit); further subdefined by:
      0.0.*    is X10
      0.0.A1   is X10 device A1
      0.1.*    is IR
      0.1.1    is IR code 1 from the ocelot (xmit or recv)
      0.2.*    is Inputs (none on Ocelot)
      0.3.*    is Outputs (none on Ocelot)
      0.4.*    is Keytouches
      0.100.*  is Parameters
      0.101.*  is Timers
      0.102.*  is Variables
Now if I want the relay module off the Ocelot @ address 1:
      1.3.*    is Outputs
      1.100.*  is Parameters
or SECU16 @ 2
      2.2.*     is Inputs
      2.3.*     is Outputs
      2.100.*   is Parameters

The same *exact* format carries to the ADICON RS-485 direct
devices except that address 0 is actually on the network and
not the Ocelot... or if they ever get the Ocelot to fully support
RS-485 access then you could have a Leopard or Ocelot at an
address on the ADICON RS-485 bus and all the X10/IR/KEYTOUCH
domains are valid.

>  Also I noticed that each
>device has a seperate port are these seperate agents (daemons)?

Yes. They can all be on one machine, separate machines, on
remote networks through firewalls...  It also makes adding/
changing or creating brand new interfaces real easy...


>I'm working on an XML definition for the HCS and I need to get this
>straight in my head (this while learning about Frame Relay/ATM switches,
>hand off through online docs :-).

Always fun. I'm having to learn IE messages on ISDN PRI at the moment
and doing some advance work on G729 channel banks over ATM without
the hardware in hand. I can relate fully :)

Jay


>--
>Linux Home Automation           Neil Cherry             nc...@ho...
>http://members.home.net/ncherry                         (Text only)
>http://meltingpot.fortunecity.com/lightsey/52           (Graphics)
>http://linuxha.sourceforge.net/                         (SourceForge)
>_______________________________________________
>http://lists.sourceforge.net/mailman/listinfo/linuxha-misc
>To unsubscribe, send "unsubscribe Linuxha-misc"
>in the body of a message to  Lin...@li...