The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: xAP-Update or config and a tad on discovery - long


  • Subject: RE: xAP-Update or config and a tad on discovery - long
  • From: Ian B
  • Date: Wed, 13 Aug 2003 00:12:00 +0000

I have made an update at the end of this extract from my original message
showing the reply from a status message with a body of type=detail.

Thanks

Ian


All of the following examples are a direct copy of the buffer sent to my
I/O
controller. Note I have not been too picky about sections I don’t analyse
within my embedded chip. These include the bit between the header and body.

Although strings are not case sensitive I retain formatting for the most
part as it is just plain nicer.

<LF> characters (0A) are in the correct places just not printed in
this
message.

My controller is called PROTOTYPE and the output SubInstances are Relay1 to
Relay8. I will be adding Input1 to Input16 in due course as I will be
making
these renamable.


Discovery the RS232 way.
Note here that the schema is RelayControl and the type of message is a
command. The body tells the unit what to do and in this case respond means
send a heartbeat.

<STX>xap-header
{
v=12
hop=1
uid=FFxxxx00
Class=RelayControl.Command
Source=IansINet.RBControl.AnInstance
Target=IansINet.RB3_1Controller.*:*
}
*.
{
Command=Respond
}
----<ETX>

After the heartbeat is received the ‘application’ sends a status request as
follows. We are still in the RelayControl schema and it has a body of
type=detail. This distinguishes it from a standard status message which
gets
an entirely different response. I cannot give an example at the moment as I
re writing the header analysis routine and it is currently broken.

<STX>xap-header
{
v=12
hop=1
uid=FFxxxx00
Class=RelayControl.Status
Source=IansINet.RBControl.AnInstance
Target=IansINet.RB3_1Controller.PROTOTYPE
}
PROTOTYPE.
{
Type=Detail
}
----<ETX>

– OK, fixed the new analysis routine so here is an example of the reply
from
the above message sequence. The unit was completely unconfigured hence the
[00] characters etc. I can now post the reply to the above status=detail
message.

[02]xAP-Header
{
V=12
Hop=1
uid=FF000000
Class=RBController.Status
Source=IansINet.RB3_1Controller.Prototype
}
Status.Detail
{
Serial Number=Hex [00][00][00][00]
Power Recovery=Released
Number Of Inputs=16
Instance=Prototype
Number of SubInstances=8
R1=Relay1
R2=Relay2
R3=Relay3
R4=Relay4
R5=Relay5
R6=Relay6
R7=Relay7
R8=Relay8
}
----[03]







xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.