[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: using intranet.ocx to build an application
Yes as Kevin says in xAP v1.2 the subID can be 01-FE (254 endpoints).
The subID of 00 is reserved for the device itself (rather than its
endpoints) and FF is just reserved. If however you move to xAP v1.3
there is no limit to the number of sub addresses
xAP v12 uid=FF1234AB
xAP v13 uid=FF.1234:AB
The three segments in the uid address can be any even number of digits
eg uid=FF.123456.AABBCCDD
should you wish
again all 0's or all FF's in any segment are reserved/special meaning
Now I know James said that his OCX based applications were xAP v1.3
compatible but he didn't actually mention if in the latest OCX you can
send and receive xAP v1.3 messages.
James ??
K
turner228 wrote:
>
> Something not quite right with my reply, so try again...
>
> > is there a subuid limit? up to "FF"?
>
> >From the V1.2 Protocol definition :-
>
> The UID is generated as an upper case ASCII hex number, comprising nn
> dd dd ss where nn is the xAP network and domain identifier (FF by
> default), dd dd is the unique device identifier and ss is a subaddress
> node within the device. For all elements of the UID, the values FF and
> 00 are reserved for future use. Sub addressing is explained in more
> detail below.
>
> http://www.xapautomation.org/index.php?title=Protocol_definition
> <http://www.xapautomation.org/index.php?title=Protocol_definition>
>
> HTH
>
> KevinT
>
>
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|