-
Notifications
You must be signed in to change notification settings - Fork 9
/
0 - LLAP Reference.mht
executable file
·10702 lines (10650 loc) · 544 KB
/
0 - LLAP Reference.mht
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
From: "Saved by Windows Internet Explorer 8"
Subject: 0 - LLAP Reference
Date: Tue, 24 Jun 2014 11:22:37 +0100
MIME-Version: 1.0
Content-Type: multipart/related;
type="text/html";
boundary="----=_NextPart_000_0021_01CF8F9E.9A8A8DD0"
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
This is a multi-part message in MIME format.
------=_NextPart_000_0021_01CF8F9E.9A8A8DD0
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Location: http://openmicros.org/index.php/articles/85-llap-lightweight-local-automation-protocol/297-llap-reference
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" =
"http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML lang=3Den-gb xml:lang=3D"en-gb"=20
xmlns=3D"http://www.w3.org/1999/xhtml"><HEAD><TITLE>0 - LLAP =
Reference</TITLE>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3Dcontent-type>
<META name=3Drobots content=3D"index, follow">
<META name=3Dkeywords content=3D"">
<META name=3Drights content=3D"">
<META name=3Dlanguage content=3Den-GB>
<META name=3Dtitle content=3D"0 - LLAP Reference">
<META name=3Dauthor content=3DRob>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18448">
<SCRIPT type=3Dtext/javascript=20
src=3D"http://openmicros.org/media/system/js/core.js"></SCRIPT>
<SCRIPT type=3Dtext/javascript=20
src=3D"http://openmicros.org/media/system/js/mootools-core.js"></SCRIPT>
<SCRIPT type=3Dtext/javascript=20
src=3D"http://openmicros.org/media/system/js/caption.js"></SCRIPT>
<SCRIPT type=3Dtext/javascript=20
src=3D"http://openmicros.org/media/system/js/mootools-more.js"></SCRIPT>
<LINK rel=3Dstylesheet type=3Dtext/css=20
href=3D"http://openmicros.org/templates/system/css/system.css"><LINK=20
rel=3Dstylesheet type=3Dtext/css=20
href=3D"http://openmicros.org/templates/system/css/general.css"><LINK=20
rel=3Dstylesheet type=3Dtext/css=20
href=3D"http://openmicros.org/templates/a4joomla-thirty-three/css/templat=
e.css"><LINK=20
rel=3Dstylesheet type=3Dtext/css=20
href=3D"http://openmicros.org/templates/a4joomla-thirty-three/css/grey.cs=
s"><!--[if IE 6]>
<link rel=3D"stylesheet" =
href=3D"/templates/a4joomla-thirty-three/css/ie6.css" type=3D"text/css" =
/>
<script src=3D"/templates/a4joomla-thirty-three/js/suckerfish.js" =
type=3D"text/javascript"></script>
<style type=3D"text/css">
img, div, a, input { behavior: =
url(/templates/a4joomla-thirty-three/iepngfix.htc) }
</style>
<script src=3D"/templates/a4joomla-thirty-three/js/iepngfix_tilebg.js" =
type=3D"text/javascript"></script>
<![endif]--><!--[if lte IE 7]>
<link rel=3D"stylesheet" =
href=3D"/templates/a4joomla-thirty-three/css/ie67.css" type=3D"text/css" =
/>
<![endif]-->
<SCRIPT type=3Dtext/javascript src=3D""></SCRIPT>
<STYLE type=3Dtext/css>#header {
HEIGHT: 80px
}
#allwrap {
MARGIN-TOP: 0px
}
#logo {
WIDTH: 440px; HEIGHT: 80px
}
#logo H2 {
MARGIN-TOP: 0px; FONT-SIZE: 52px
}
#logo H3 {
MARGIN-TOP: -10px
}
#banner {
HEIGHT: 80px
}
#banner DIV.moduletable {
MARGIN-TOP: 10px
}
#headerright {
WIDTH: 530px; BACKGROUND: none transparent scroll repeat 0% 0%; HEIGHT: =
80px
}
#search {
WIDTH: 170px; HEIGHT: 32px
}
</STYLE>
<!-- <script src=3D"/templates/a4joomla-thirty-three/js/equalize.js" =
type=3D"text/javascript"></script> --></HEAD>
<BODY>
<DIV style=3D"WIDTH: 1030px" id=3Dallwrap class=3Dgainlayout>
<DIV id=3Dheaderwrap class=3Dgainlayout>
<DIV id=3Dheader class=3Dgainlayout>
<DIV id=3Dlogo class=3Dgainlayout><A =
href=3D"http://openmicros.org/"><IMG border=3D0=20
alt=3D"" src=3D"http://openmicros.org/images/openmicroslogo.png"></A> =
</DIV>
<DIV id=3Dheaderright class=3Dgainlayout>
<DIV id=3Dbanner>
<DIV class=3Dmoduletable>
<H3>Banners</H3>
<DIV class=3Dbannergroup>
<DIV class=3Dbanneritem><IMG alt=3D"EVE Forum"=20
src=3D"http://openmicros.org/images/banners/evelogo468.png">=20
<DIV class=3Dclr></DIV></DIV></DIV></DIV></DIV>
<DIV class=3Dclr></DIV></DIV>
<DIV class=3Dclr></DIV></DIV>
<DIV class=3Dclr></DIV></DIV>
<DIV id=3Dtopmenuwrap class=3Dgainlayout>
<DIV id=3Dtopmenu class=3Dgainlayout>
<DIV class=3Dmoduletable>
<H3>Top</H3>
<UL class=3Dmenusfh>
<LI id=3Ditem-464><A href=3D"http://openmicros.org/">Home</A></LI>
<LI id=3Ditem-540><A=20
=
href=3D"http://openmicros.org/index.php/documentation">documentation</A><=
/LI>
<LI id=3Ditem-486><A=20
=
href=3D"http://openmicros.org/index.php/component/kunena/?Itemid=3D0">FOR=
UM</A></LI>
<LI id=3Ditem-484 class=3D"current active"><A=20
href=3D"http://openmicros.org/index.php/articles">Articles by =
list</A></LI>
<LI id=3Ditem-490><A =
href=3D"http://openmicros.org/index.php/search">forum=20
search</A></LI>
<LI id=3Ditem-541><A href=3D"http://ciseco.co.uk/" =
target=3D_blank>Ciseco=20
Shop</A></LI></UL></DIV>
<DIV class=3Dclr></DIV></DIV>
<DIV id=3Dsearch class=3Dgainlayout>
<DIV class=3Dmoduletable>
<H3>Search</H3>
<FORM method=3Dpost action=3D/index.php/articles>
<DIV class=3Dsearch><LABEL =
for=3Dmod-search-searchword>Search...</LABEL><INPUT=20
onblur=3D"if (this.value=3D=3D'') this.value=3D'Search...';" =
id=3Dmod-search-searchword=20
class=3Dinputbox onfocus=3D"if (this.value=3D=3D'Search...') =
this.value=3D'';"=20
value=3DSearch... maxLength=3D20 size=3D20 type=3Dtext =
name=3Dsearchword> <INPUT=20
value=3Dsearch type=3Dhidden name=3Dtask> <INPUT value=3Dcom_search =
type=3Dhidden=20
name=3Doption> <INPUT value=3D484 type=3Dhidden name=3DItemid> =
</DIV></FORM></DIV>
<DIV class=3Dclr></DIV></DIV>
<DIV class=3Dclr></DIV></DIV>
<DIV id=3Dwrap class=3Dgainlayout>
<DIV id=3Dpathway class=3Dgainlayout>
<DIV class=3Dbreadcrumbs><SPAN class=3DshowHere>You are here: </SPAN><A=20
class=3Dpathway href=3D"http://openmicros.org/">Home</A> <IMG alt=3D""=20
src=3D"http://openmicros.org/templates/a4joomla-thirty-three/images/syste=
m/arrow.png">=20
<A class=3Dpathway =
href=3D"http://openmicros.org/index.php/articles">Articles by=20
list</A> <IMG alt=3D""=20
src=3D"http://openmicros.org/templates/a4joomla-thirty-three/images/syste=
m/arrow.png">=20
<A class=3Dpathway=20
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol">LLAP=20
- Lightweight Local Automation Protocol</A> <IMG alt=3D""=20
src=3D"http://openmicros.org/templates/a4joomla-thirty-three/images/syste=
m/arrow.png">=20
<SPAN>0 - LLAP Reference</SPAN></DIV>
<DIV class=3Dclr></DIV></DIV>
<DIV id=3Dcbody class=3Dgainlayout>
<DIV style=3D"WIDTH: 988px" id=3Dcontent60>
<DIV id=3Dcontent class=3Dgainlayout>
<DIV class=3Ditem-page>
<H2><A=20
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference">0=20
- LLAP Reference</A> </H2>
<UL class=3Dactions>
<LI class=3Dprint-icon><A title=3DPDF onclick=3D""=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference?tmpl=3Dcomponent&format=3Dpd=
f"=20
rel=3Dnofollow target=3D_blank><IMG alt=3DPDF=20
=
src=3D"http://openmicros.org/components/com_phocapdf/assets/images/pdf_bu=
tton.png"></A></LI>
<LI class=3Dprint-icon><A title=3DPrint=20
=
onclick=3D"window.open(this.href,'win2','status=3Dno,toolbar=3Dno,scrollb=
ars=3Dyes,titlebar=3Dno,menubar=3Dno,resizable=3Dyes,width=3D640,height=3D=
480,directories=3Dno,location=3Dno'); return false;"=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference?tmpl=3Dcomponent&print=3D1&a=
mp;page=3D"=20
rel=3Dnofollow><IMG alt=3DPrint=20
src=3D"http://openmicros.org/media/system/images/printButton.png"></A> =
</LI>
<LI class=3Demail-icon><A title=3DEmail=20
=
onclick=3D"window.open(this.href,'win2','width=3D400,height=3D350,menubar=
=3Dyes,resizable=3Dyes'); return false;"=20
=
href=3D"http://openmicros.org/index.php/component/mailto/?tmpl=3Dcomponen=
t&template=3Da4joomla-thirty-three&link=3D40f4081603eb7d798314948=
95368f7528e35f074"><IMG=20
alt=3DEmail =
src=3D"http://openmicros.org/media/system/images/emailButton.png"></A>=20
</LI></UL>
<DL class=3Darticle-info>
<DT class=3Darticle-info-term>Details</DT>
<DD class=3Dcategory-name>Category: <A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol">LLAP=20
- Lightweight Local Automation Protocol</A> </DD>
<DD class=3Dmodified>Last Updated on Thursday, 06 February 2014 14:13 =
</DD></DL>
<H1>LLAP Reference Guide</H1>
<P>In this document we bring together everything you need to know about=20
LLAP.</P>
<OL>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#intro">Introduction</A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#use">What=20
is LLAP used for?</A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#where implemented">Where=20
is LLAP implemented?</A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#how does it work">How=20
does LLAP work?</A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#personalities">Personalities</A>=
</LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#Programming">Programming=20
Gateways or applications for LLAP Personalities </A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#Generic LLAP Messages">Appendix =
1: Generic LLAP messages</A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#XRF Personalities">Appendix=20
2: XRF personalities</A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#Permissible LLAP message =
characters">Appendix=20
3: Permissable LLAP message characters</A></LI>
<LI><A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#Typing LLAP messages">Appendix=20
4: Entering LLAP messages into a terminal window</A></LI></OL>
<P> </P>
<H2><A name=3Dintro></A>Introduction by the inventor</H2>
<P>LLAP: <A href=3D"http://shop.ciseco.co.uk/llap/">an introduction</A> =
=E2=80=93 LLAP=E2=80=99s=20
inventor, Miles Hodkinson explains why he invented LLAP and why it came =
out the=20
way it did.</P>
<P> </P>
<HR>
<H2><A name=3Duse></A>What is LLAP used for?</H2>
<P>LLAP can be used to convey all sorts of short messages, but in our =
world, we=20
use it to send short human readable messages between sensors, =
controllers and=20
actuators in control systems.</P>
<P style=3D"TEXT-ALIGN: center"><IMG style=3D"WIDTH: 200px; HEIGHT: =
145px" alt=3D""=20
src=3D"http://openmicros.org/images/wirelesscontrolsystem.jpg"><IMG=20
style=3D"LINE-HEIGHT: 1.5; FONT-SIZE: 11.81px" src=3D""></P>
<P align=3Dcenter> </P>
<P><SPAN style=3D"LINE-HEIGHT: 1.5; FONT-SIZE: 11.81px">There are two =
main types=20
of device:</SPAN></P>
<OL>
<LI>Devices that are polled for data at regular intervals or sent =
commands by=20
the controller (similar to MODBUS and the main stay of operation). =
These=20
devices are normally permanently powered or are continually charged =
e.g. via=20
solar power or another form of energy harvesting.</LI>
<LI>Devices that send data when they have something to send. This =
further=20
splits in two common types:</LI></OL>
<UL>
<LI style=3D"MARGIN-LEFT: 40px">Devices that sleep most of the time =
and=20
occasionally wake up and transmit readings. These are usually cyclic =
and=20
repeat their behaviour. They are often battery powered; they sleep to =
conserve=20
energy.</LI>
<LI style=3D"MARGIN-LEFT: 40px">Devices that need to send an alert, =
e.g. a=20
doorbell, smoke sensor, overflow detection etc. Their behaviour is to =
report=20
at the moment the action or detection occurred. These can be powered =
by any=20
means. Some can sleep and wake on an interrupt caused by the external =
event=20
they are monitoring.</LI></UL>
<P>Any message that conforms to the message format rules defined in this =
document is considered to be a valid LLAP message. However, for a =
message to=20
make sense to a recipient, it needs to carry data that the recipient can =
handle.</P>
<P>There are several sets of messages:</P>
<UL>
<LI>Generic messages: all LLAP devices should be able to handle these. =
They=20
are listed in <A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#Generic LLAP Messages">Appendix =
1</A></LI>
<LI>Ciseco defined =E2=80=9Cpersonalities=E2=80=9D: these are specific =
message sets that only=20
certain LLAP devices can handle. There are pre-defined personalities =
for light=20
and temperature sensors, relay control, button and Hall Effect =
sensors, as=20
well as generic analogue to digital conversion and general purpose =
digital I/O=20
tasks. Today we have these personalities in firmware for the XRF. We =
are=20
looking to extend this to the SRF also. See <A=20
=
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#XRF Personalities">Appendix=20
2</A> for details of the XRF personalities.</LI>
<LI>User defined =E2=80=9Cpersonalities=E2=80=9D: you can define your =
own set of messages and=20
use these with your controllers and devices. If you want to use Ciseco =
radio=20
technology, you will probably choose the XinoRF or the Raspberry Pi as =
your=20
controller and the RF=CE=BC328 as the base for your sensor or =
actuator. You will=20
also be able to use our LLAP libraries to make sending and receiving =
LLAP=20
messages a breeze.</LI></UL>
<P> </P>
<HR>
<H2><A name=3D"where implemented"></A>Where is LLAP implemented?</H2>
<P>LLAP messages are simple text messages and completely independent =
from the=20
underlying infrastructure and transmission media used to convey the =
messages.=20
That means that LLAP can be used anywhere you can exchange text.</P>
<P>In particular, a user can type in a LLAP message in a terminal window =
on a=20
Windows, Linux or Mac based computer, or on a Raspberry Pi for instance =
and=20
receive a response from devices in a Ciseco device network to which that =
computer is connected.<BR>Note: The only proviso when working with =
Ciseco radios=20
is that you type fast enough to make sure the LLAP message is sent in =
one data=20
packet. Cut and paste is usually the best approach.</P>
<P>Ciseco have freely available software that uses the LLAP message =
format for=20
communications:</P>
<UL>
<LI>Firmware for the XRF that implements a number of sensors and =
actuators. We=20
refer to this firmware as =E2=80=9Cpersonalities=E2=80=9D. Since all =
XRFs ship with serial=20
pass-through firmware, customers will need to load an XRF that is to =
be=20
configured as a specific sensor or actuator with the appropriate =
firmware=20
using XCM. See the section on personalities for details.</LI>
<LI>Example software for our Arduino based SRF units (XinoRF and =
RF=CE=BC328) to=20
emulate XRF personalities for sensors and actuators.</LI>
<LI>An Arduino LLAP library makes it very easy for customers to write =
their=20
own sensor or actuator software and to define their own messages as=20
appropriate.</LI>
<LI>A Python LLAP library is under construction too and is the best =
base for=20
development of LLAP software on the Raspberry Pi for =
instance.</LI></UL>
<P> </P>
<HR>
<H2><A name=3D"how does it work"></A>How does LLAP work?</H2>
<P>It is assumed that messages either arrive completely and without =
errors or=20
don=E2=80=99t arrive at all. The communication infrastructure should =
provide for message=20
integrity (e.g. via CRC) and messages that get corrupted must be =
intentionally=20
lost by the infrastructure. Ciseco radios have this property.</P>
<P>When you send a message, you should not expect any acknowledgement =
from the=20
communications infrastructure as to whether it was sent or not. The only =
way to=20
know if a message was received is by the recipient sending you a =
response LLAP=20
message.</P>
<H3>Message format</H3>
<P>Each message is exactly 12 characters long and in three distinct=20
sections:</P>
<UL>
<LI>One start byte</LI>
<LI>Two bytes for the device identifier</LI>
<LI>Nine data bytes, padded by dashes if necessary.</LI></UL>
<P><SB> <ID> <ID> <D> <D> <D> =
<D>=20
<D> <D> <D> <D> <D></P>
<P>See <A=20
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/297-llap-reference#Permissible LLAP message =
characters">Appendix=20
3</A> for details of the permissable characters in each field.</P>
<P><SPAN=20
style=3D"LINE-HEIGHT: 1.5; FONT-FAMILY: Arial, Verdana, Helvetica, =
sans-serif; FONT-SIZE: 1.15em; FONT-WEIGHT: bold">Address=20
range</SPAN></P>
<P>With two ID bytes that can each assume 30 different values, it is =
possible to=20
address 900 individual devices. Excluding the special characters, the =
range=20
extends to 26 X 26 =3D 676 devices.</P>
<P>Ciseco radio devices each operate with a specific PANID. Each PANID =
defines a=20
subnet, within which 676 or 900 devices are addressable. The usable =
PANIDs run=20
from 0000 (hex) to EFFF (hex), or 61,439 subnets.</P>
<P>In a single location, it is thus possible to host 41.5 million =
devices.</P>
<H3>Device start-up</H3>
<P>A new =E2=80=9Cout of the box=E2=80=9D device is pre-assigned the =
generic ID=20
of <STRONG>--</STRONG> (dash dash). When it is powered up it =
sends</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a--STARTED=E2=80=94</STRONG></P>
<P>When a controller hears this, it should reply with</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a--ACK------</STRONG></P>
<P>If no response is heard then a further 5 attempts (retries) are made, =
again=20
in the same format.</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a--STARTED=E2=80=94</STRONG></P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a--STARTED=E2=80=94</STRONG></P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a--STARTED=E2=80=94</STRONG></P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a--STARTED=E2=80=94</STRONG></P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a--STARTED=E2=80=94</STRONG></P>
<P>The device now assumes normal operation on the ID of =E2=80=93</P>
<H3>Address allocation</H3>
<P>Assuming the controller did hear the device it begins by allocating =
it a=20
unique address. The controller will send out</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a=E2=80=94CHDEVIDXX</STRONG></P>
<P>where XX represents the ID to allocate to the device. The device =
responds to=20
this by echoing the command</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>a=E2=80=94CHDEVIDXX</STRONG></P>
<P>The controller then requests the device to restart thus applying the =
new=20
ID </P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG> a--REBOOT---</STRONG></P>
<P>The device then resets and starts up by announcing</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXSTARTED--</STRONG></P>
<P>This is repeated at 193mS intervals for an additional 5 times unless =
the=20
controller replies with </P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXACK------</STRONG></P>
<P>This startup message now happens every time that the device is reset =
or=20
powered up and acts to inform the controller that the device is =
available.</P>
<H3>Request/response pairs</H3>
<P>Commands from the controller, are acknowledged by the device by one =
of two=20
methods. Either repeating the command (simple acknowledgment of receipt) =
or=20
replying with the data requested. The response =E2=80=9Cshould=E2=80=9D =
be sent back within 0.1=20
second (100ms). If no receipt message is received then further requests =
can be=20
sent. The number of retries is normally 5, however this can be changed =
within=20
the controller or the device.</P>
<P>Examples:</P>
<P>When a controller requires a device to reboot, it sends:</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXREBOOT---</STRONG></P>
<P>The device sends back a similar message to acknowledge receipt.</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXREBOOT---</STRONG></P>
<P> It then carries out the command (to reboot in this case).</P>
<P>A controller may request the version number of the firmware on device =
with=20
address XX by sending:</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXAPVER----</STRONG></P>
<P>The device then sends back the requested information:</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXAPVER1.01</STRONG></P>
<P>where 1.01 is the version number.</P>
<H3>Announcements</H3>
<P>Some messages are simple announcements and do not require a =
response.</P>
<P>Example:</P>
<P>When a device starts (is powered up, or reset), it should send out an =
announcement to say it is available:</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXSTARTED=E2=80=94</STRONG></P>
<P>A battery powered device will report that its battery is low:</P>
<P style=3D"MARGIN-LEFT: 40px"><STRONG>aXXBATTLOW--</STRONG></P>
<P> </P>
<HR>
<H2><A name=3Dpersonalities></A>Personalities</H2>
<P>A device with a LLAP personality is capable of generating and =
responding to=20
the set of messages that are defined for that personality.</P>
<P>There are two types of personality:</P>
<UL>
<LI>Ciseco defined personalities are available as firmware that a user =
can=20
load onto an XRF to make that XRF into a temperature sensor, an =
actuator for=20
relays, etc.</LI>
<LI>User defined personalities are defined by third parties to create =
their=20
own specific sensors and actuators.</LI></UL>
<P> </P>
<H3>Ciseco defined personalities</H3>
<P>Ciseco provide a range of sensor and actuator personalities. Each is=20
encapsulated in firmware that needs to be written to the radio device to =
give=20
your radio unit a specific predefined function.</P>
<TABLE style=3D"WIDTH: 694px" border=3D1 cellSpacing=3D0 =
cellPadding=3D0>
<TBODY>
<TR>
<TD style=3D"WIDTH: 139px">
<P><STRONG>Personality</STRONG></P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter><STRONG>Type</STRONG></P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter><STRONG>XRF</STRONG></P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter><STRONG>SRF</STRONG></P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter><STRONG>XinoRF =
/<BR>RF=CE=BC328</STRONG></P></TD>
<TD style=3D"WIDTH: 234px">
<P><STRONG>Comments</STRONG></P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Temp. thermistor</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>Beta</P></TD>
<TD style=3D"WIDTH: 234px">
<P>Single thermistor sensor</P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Temp. Dallas</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P>Single Dallas DS18B20 sensor input</P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Button / Hall Effect</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>Beta</P></TD>
<TD style=3D"WIDTH: 234px">
<P>Two button and one Hall Effect input</P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Analog</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P>Single channel analogue input</P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Light</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>Beta</P></TD>
<TD style=3D"WIDTH: 234px">
<P>Single LDR sensor</P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Generic I/O</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor / Actuator</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P>Two digital outputs, one digital and one analogue =
input</P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Relay</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Actuator</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P>Dual relay on/off/toggle</P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>RGB encoder</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Actuator</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Y</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P> </P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Count</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Beta</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P> </P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Tacho</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Beta</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P> </P></TD></TR>
<TR>
<TD style=3D"WIDTH: 139px">
<P>Ultrasonic</P></TD>
<TD style=3D"WIDTH: 92px">
<P align=3Dcenter>Sensor</P></TD>
<TD style=3D"WIDTH: 73px">
<P align=3Dcenter>Beta</P></TD>
<TD style=3D"WIDTH: 51px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 98px">
<P align=3Dcenter>N</P></TD>
<TD style=3D"WIDTH: 234px">
<P> </P></TD></TR></TBODY></TABLE>
<P> </P>
<H4>Personalities for the XRF</H4>
<P>The personalities for the XRF assume the LLAP device XRF pin-out =
described=20
here: <A=20
href=3D"http://openmicros.org/index.php/articles/87-llap-lightweight-loca=
l-automation-protocol/llap-devices-commands-and-instructions/190-llap-dev=
ice-xrf-pinout">http://openmicros.org/index.php/articles/87-llap-lightwei=
ght-local-automation-protocol/llap-devices-commands-and-instructions/190-=
llap-device-xrf-pinout</A></P>
<P>The firmware for these personalities is available on github (<A=20
href=3D"https://github.com/CisecoPlc/XRF-Firmware-downloads/downloads"=20
target=3D_blank>https://github.com/CisecoPlc/XRF-Firmware-downloads/downl=
oads</A>).</P>
<P>All you need to do is select the function required, buy the =
appropriate=20
sensor or actuator and combine it with an XRF, perhaps conveniently =
using one of=20
our boards. Using the XRF Configuration Manager (XCM) software you then =
program=20
the XRF with the chosen personality and you are done.</P>
<P>Instructions on how to update the firmware on an XRF are available =
here: <A=20
href=3D"http://openmicros.org/index.php/articles/84-xrf-basics/111-firmwa=
re-updating-how-to"=20
target=3D_blank>http://openmicros.org/index.php/articles/84-xrf-basics/11=
1-firmware-updating-how-to</A></P>
<P>(This doc needs to be updated with the Explorer Plus method of =
firmware=20
upload).</P>
<P>LLAP commands for Ciseco radio personalities must be issued over the =
air not=20
via the Serial</P>
<H4>Personalities for the SRF</H4>
<P>Personalities for the SRF are pending demand from our users. Most of =
the XRF=20
personalities will also work on the SRF, but since the SRF does not have =
exactly=20
the same pin-out as the XRF, some parts may not work as expected. We =
currently=20
do not support ruuning LLAP personalities on SRF's, try it ar your own =
risk.</P>
<H3>Creating your own sensor / actuator personality</H3>
<P>Any developer worth their salt wants to make sensors and actuators do =
something a bit different from the pre-defined Ciseco provided =
personalities. So=20
we got loads of requests for customisation, which we found hard to =
respond to=20
(due to the volume in demand).</P>
<P>Allowing anyone to create their favourite sensor personality and =
allowing=20
these to be uploaded to the XRF proved too painful. Programming the =
CC111x chip=20
is a professional job and the increased chances of end user software =
interfering=20
with the correct operation of the radio would mean our products would =
soon be=20
seen as unreliable.</P>
<P>We needed a solution which allows you to program the personality =
yourself=20
without compromising the reliability of the radio. Our solution is to =
add a=20
separate end-user programmable processor to our radio unit in serial=20
pass-through mode. This combination is now available in two form =
factors:</P>
<UL>
<LI>RF=CE=BC-328 combines an Arduino 328 with our SRF on the same Xbee =
form factor=20
that is used by the XRF</LI>
<LI>XinoRF places our SRF on an Arduino Uno compatible board</LI></UL>
<P>RF=CE=BC-328 is ideal for low power deployment scenarios, whereas =
XinoRF is more=20
suitable for development. Both units are software compatible, so =
software=20
developed on one can be run without change on the other.</P>
<P>We are developing the sketches to cover the personalities we have for =
the=20
XRF. They will be placed on github as they become available.</P>
<P>The Arduino LLAP library (<A=20
href=3D"http://openmicros.org/index.php/articles/85-llap-lightweight-loca=
l-automation-protocol/266-arduino-llap-library-for-user-devices">http://o=
penmicros.org/index.php/articles/85-llap-lightweight-local-automation-pro=
tocol/266-arduino-llap-library-for-user-devices</A>)=20
is the base against which we develop these. We recommend users who wish =
to code=20
their own Arduino based sensors, actuators and controllers, to use this =
library=20
also.</P>
<HR>
<H2><A name=3DProgramming></A>Programming Gateways or applications for =
LLAP=20
Personalities </H2>
<P>At some point many users want to develop some application or gateway =
to talk=20
to our XRF Personalities.</P>
<P><BR>Before writing any code we recommend that you try out you LLAP =
commands=20
first using your favourite serial terminal program. This way you =
see what=20
messages you need to send an what messages you might receive in =
reply.</P>
<P> </P>
<HR>
<H2><A name=3D"Generic LLAP Messages"></A>Appendix 1: Generic LLAP =
messages</H2>
<P>LLAP devices should be able to handle messages from the set of =
generic=20
messages defined in this section.</P>
<P> </P>
<H3>Message request/response pairs</H3>
<P><STRONG>APVER</STRONG> =E2=80=93 Request the LLAP version</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXAPVER----<BR>Requests the =
supported LLAP=20
version number =E2=80=93 response from the device is aXXAPVER9.99 where =
9.99 is the=20
version number. The current version at present is 1.0</P>
<P> </P>
<P><STRONG>BATT</STRONG> - Request battery level in=20
Volts </P>
<P style=3D"MARGIN-LEFT: 36pt">aXXBATT----- will reply aXXBATT3.43- =
(3.43V)</P>
<P style=3D"MARGIN-LEFT: 36pt"> </P>
<P><STRONG>CHDEVID</STRONG> =E2=80=93 Change device ID</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXCHDEVIDDD<BR>Request that the device =
change its=20
device ID to DD. The change will only take place when the device is =
rebooted or=20
powered on/off.<BR> </P>
<P><STRONG>CYCLE</STRONG> =E2=80=93 Start cyclic mode (only applies =
to cyclic=20
sleeping devices) </P>
<P style=3D"MARGIN-LEFT: 36pt">aXXCYCLE---<BR>Request that the device =
starts a=20
cyclic sleep =E2=80=93 the device should sleep for the sleep interval, =
awaken and send=20
any reading. The device wiull then go back to sleep. Every (default 10) =
times it=20
will send aXXAWAKE---- aXXBATTv.vv- wait for 100mS incase there is a =
command for=20
the unit and then send aXXSLEEPING-. This is configurable by using =
aXXWAKECnnn-=20
whenre nnn is the count of transmits before it will wake and send the =
battery=20
reading.</P>
<P style=3D"MARGIN-LEFT: 36pt"> </P>
<P><STRONG>DEVNAME</STRONG> =E2=80=93 Request the manufacturer =
device name</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXDEVNAME--<BR>Request the device name. =
Response=20
is a nine character =E2=80=9Cfriendly=E2=80=9D name.<BR> </P>
<P><STRONG>DEVTYPE</STRONG> =E2=80=93 Request the device type</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXDEVTYPE--<BR>Request the device type. =
Response=20
is a nine character device type e.g. aXXU00000001 Device types beginning =
with U=20
are reserved for users to assign to their own prototype devices. All =
other=20
device types will be kept on a register by CISECO Plc., that can be used =
to=20
update hubs on a regular basis. In APVER 1.1 this will change to a eight =
character field e.g. aXXU0000001-</P>
<P> </P>
<P><STRONG>FVER</STRONG> =E2=80=93 Request the manufacturer =
firmware version</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXFVER-----<BR>Request the device =
firmware=20
version. Response is aXXFVER9.99- e.g. aXXFVER0.32-</P>
<P> </P>
<P><STRONG>HELLO</STRONG> =E2=80=93 Request the device to =
acknowledge it=E2=80=99s=20
there.</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXHELLO----<BR>Request the device to =
confirm it is=20
receiving, response is<BR>aXXHELLO----<BR> </P>
<P><STRONG>INTVL</STRONG> =E2=80=93 Sets the sleep interval between =
=E2=80=9Cactivities"=20
(only applies to cyclic sleeping devices)</P>
<P style=3D"MARGIN-LEFT: 36pt">XXINTVL999P<BR>Set the cyclic sleep =
interval to 999=20
=E2=80=9Cperiods=E2=80=9D<BR>Periods can be S(seconds), M(minutes), =
H(hours), D(days)</P>
<P> </P>
<P><STRONG>PANID</STRONG> =E2=80=93 Change PANID</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXPANIDFFFF<BR>Requests that the device =
change its=20
PANID to FFFF(the id of the channel the device listens to). PANID is a =
four=20
character hexadecimal number on XRF or XBee wireless networks. All =
devices=20
within the same PANID can communicate with each other. The change will =
only take=20
place when the device is reset or powered on/off.</P>
<P> </P>
<P><STRONG>REBOOT</STRONG> =E2=80=93 Force a restart</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXREBOOT---<BR>Request that the device =
reset=20
itself.</P>
<P style=3D"MARGIN-LEFT: 36pt"> </P>
<P><STRONG>RETRIES</STRONG> =E2=80=93 Set the amount of messages to =
retry to get an=20
ACK from the hub</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXRETRIESRR<BR>Set the amount of retries =
that=20
uninitiated =E2=80=9Csends=E2=80=9D should try before giving up, default =
is 5 (number can be=20
00-99) this is set by RR</P>
<P style=3D"MARGIN-LEFT: 36pt"> </P>
<P><STRONG>SER</STRONG> =E2=80=93 Request the manufacturer serial =
number</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXSER------<BR>Request the device serial =
number,=20
response is a 6 character serial number, e.g. aXXSER000001<BR> </P>
<P><STRONG>SLEEP </STRONG>=E2=80=93 Requests the device go into low =
power mode=20
(only applies to sleeping devices)</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXSLEEP999P<BR>Request that the device =
sleep for=20
999 =E2=80=9Cperiods=E2=80=9D, the response echos the command, the =
device will then send the=20
notification aXXSLEEPING- when going to sleep, and the announcement =
aXXAWAKE----=20
when the device reawakens. Periods can be S(seconds), M(minutes), =
H(hours),=20
D(days) T(milliseconds)</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXSLEEP---- (only applies to interrupt =
sleeping=20
devices) . Sleep until an interrupt is received. Only the Button =
firmware=20
behaves like this at present.<BR>Every (default 10) times it will send=20
aXXAWAKE---- aXXBATTv.vv- wait for 100mS incase there is a command for =
the unit=20
and then send aXXSLEEPING-. This is configurable by using aXXWAKECnnn- =
whenre=20
nnn is the count of transmits before it will wake and send the battery=20
reading.</P>
<P> </P>
<H3>Device related announcements</H3>
<P> </P>
<P><STRONG>AWAKE</STRONG> =E2=80=93 Device has re awoken (only =
applies to devices=20
that support sleep)</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXAWAKE---- Device is now awake,=20
<Possible addition: if the device is a cyclic sleep device then the =
device=20
should now remain awake for at least 100mS listening for hub requests. =
Such a=20
device does not need to announce that it is awake at each cycle, but is =
expected=20
to do so at least every 5 minutes.</P>
<P> </P>
<P><STRONG>BATTLOW</STRONG> - Device battery is low (only applies =
to=20
battery powered devices)</P>
<P style=3D"MARGIN-LEFT: 36pt">aXXBATTLOW--</P>
<P style=3D"MARGIN-LEFT: 36pt"> </P>
<P><STRONG>ERROR</STRONG></P>
<P style=3D"MARGIN-LEFT: 36pt">aXXERRORnnnn - This is to notify that =
something=20
unexpected happened at the device and that should be investigated. The =
nnnn can=20
be used by the manufacturer to denote what type of error occurred.</P>
<P> </P>
<P><STRONG>SLEEPING</STRONG>- Device is going to sleep (only applies to =
devices=20