Main.Documentation HAL en 0 Main.Documentation xwiki:XWiki.nkef xwiki:XWiki.nkef xwiki:XWiki.nkef 1233251769000 1257512027000 1257512027000 1.7 1 Hardware Abstraction Layer ---- #toc("" "" "") ---- 1.1 Introduction Using RFID or barcode readers from different vendors, can impose significant complexity to a system. To override this problem there are two possible solutions. First to define a specification that all vendors should implement so that there can be a single way of interacting with such a device. Such specifications exist for RFID UHF readers, namely EPCglobal Reader Protocol ([RP>http://www.epcglobalinc.org/standards/rp]) and EPCglobal Low Lever Reader Protocol ([LLRP>http://www.epcglobalinc.org/standards/llrp]). The problem is that not all vendors implement these specifications. In these cases we have to define an abstraction layer that can translate proprietary vendor system calls to standardised calls (e.g. to RP calls). In the case of AspireRFID, we support LLRP readers,with the use of [Fosstrak>http://www.fosstrak.org] libraries we support RP readers and can support any other reader that supports only a proprietary protocol by building its own HAL. Through the [Reader Core Proxy>ReaderCoreProxy] component we support BRI reader protocol and the Fosstrak's simmulator. 1.1 Developers Guide To add support for non-RP or LLRP compliant readers, the most important action that need to be taken is to implement a HAL class that extends the BaseReader interface at ALE layer ( [Building a HAL Adaptor>http://www.fosstrak.org/fc/docs/developer-adaptor.html#A]) <h2 class="heading-1"><span id="HHardwareAbstractionLayer">Hardware Abstraction Layer</span></h2><p class="paragraph"/><hr class="line"/> <ul> <li><a href="#HIntroduction"> Introduction</a> <li><a href="#HDevelopersGuide"> Developers Guide</a> </ul> <hr class="line"/> <h3 class="heading-1-1"><span id="HIntroduction">Introduction</span></h3><p class="paragraph"/>Using RFID or barcode readers from different vendors, can impose significant complexity to a system. To override this problem there are two possible solutions. First to define a specification that all vendors should implement so that there can be a single way of interacting with such a device. Such specifications exist for RFID UHF readers, namely EPCglobal Reader Protocol (<span class="wikiexternallink"><a href="http://www.epcglobalinc.org/standards/rp">&#82;P</a></span>) and EPCglobal Low Lever Reader Protocol (<span class="wikiexternallink"><a href="http://www.epcglobalinc.org/standards/llrp">&#76;LRP</a></span>). The problem is that not all vendors implement these specifications. In these cases we have to define an abstraction layer that can translate proprietary vendor system calls to standardised calls (e.g. to RP calls). In the case of AspireRFID, we support LLRP readers,with the use of <span class="wikiexternallink"><a href="http://www.fosstrak.org">&#70;osstrak</a></span> libraries we support RP readers and can support any other reader that supports only a proprietary protocol by building its own HAL. Through the <span class="wikilink"><a href="/xwiki/bin/view/Main.Documentation/ReaderCoreProxy">Reader Core Proxy</a></span> component we support BRI reader protocol and the Fosstrak's simmulator. <h3 class="heading-1-1"><span id="HDevelopersGuide">Developers Guide</span></h3><p class="paragraph"/>To add support for non-RP or LLRP compliant readers, the most important action that need to be taken is to implement a HAL class that extends the BaseReader interface at ALE layer ( <span class="wikiexternallink"><a href="http://www.fosstrak.org/fc/docs/developer-adaptor.html#A">&#66;uilding a HAL Adaptor</a></span>)