Re: BSC Protocol question

[Kevin Hawkins <yahoogroupskh@xxxxxxxxxxxxxx>]

Hi Matt,

Nice application - I have a Leopard - and I almost got an Ocelot on
eBay last week.    IIRC the range of products only supports IR TX and
not IR RX - am I right ?

Re the BSC questions - yes you're correct in your interpretation.
You can name the IR signals should you wish as well eg
Module.Point.Lounge.AIWA.Vol_Up    should you wish - although it may
not serve any useful purpose.

Re the restriction to two hex digits (254 devices as 00 and FF are
reserved) - this was a limitation in xAP v1.2.    There is an updated
version of xAP (v1.3) that increases this to eliminate this restriction
.  Have a search in the posts here and also the xAP Developer list.

Essentially you change the xAP header ver=  parameter to ver=13 and the
UID has a new format
UID=NN.AAAA:SSSS    where
NN=network
AA=application address (must be unique)
SS= sub address

The three segments can be any even number of hex digits so you can have
4 digits (or more) for your sub addresses :-).  You will probably use
the format above.

In the BSC schema your ID= parameter has to match in the number of
digits so typically something like
ID=00F2   or
ID=016E

Also just to clarify another change in xAP v1.3.
The feature allowing you to include a target= parameter within message
blocks has been deprecated.

Any more Q's just ask away and I look forward to seeing the application :-)



Cheers Kevin




mx773406 wrote:
>
> Hi everyone -
>
> I'm working on a xAP interface to the Applied Digital Adicon line of
> hardware. It allows 128 modules, with digital, analog inputs, relay
> outputs, and IR modules with 16 zones and 1024 Stored IR commands. The
> hardware is addressed by Module (the Adicon device) and Point (the
> relay, input, or IR zone) on the module. For the IR you also specify
> an index to a stored IR command.
>
> I'm using the BSC schema and I need a bit of assistance.
>
> The way I understand the BSC command schema to work is this:
>
> You can use the target subaddress to send a command to a particular
> device. I would use it as Module.Point.IRIndex (if an IR command)
>
> You could wildcard the subaddress to send the command to all the
> points on a module (ModuleIndex.*) or the same Point on every module
> (*.PointIndex).
>
> Or, and here's where I need some assistance, you can wildcard the
> subaddress (*.* or *.> or >) and then send commands to the
points
> using the message body using the ID key to specify the device. This is
> a 2 digit hex number. The problem is the 2 digit hex number is not
> large enough, and is not capable of specifying a particular device.
>
> Examples:
>
> Sending several IR commands to same zone
> Subaddress ModuleIndex.PointIndex (zone).* or >
>
> Message Body
> ID=(the IR command to send) I need to specify up to 1024, but 2 hex
> digits are not enough
> State=on (not used here)
>
> Sending different commands to different devices
> Subaddress *.* or >
>
> Message Body
> ID=Module and point here also 2 hex digits are not enough
>
> The point to all this is to make sure A: I correctly understand the
> xapbsc.cmd schema and B: confirm that for this device type (Adicon) I
> need to modify the schema to make it work.
>
> Thanks for your time
>
> Matt
>
>


------------------------------------