IRPyro TO unit test console using the IRPyro API
Functions for single and multiple sensor configurations in a Unit test format
IRPyro TO unit test console using the IRPyro API
Date
March 2018
Version
Release 1.0.6

Introduction

Note
The TO-CAN is a four pin sensor with no CS nor INT lines. As a result the device is controlled only via I2C. Power control should be independently supplied.

This is important in two ways:

  • Stabilization of the device should be allowed.
  • I2C address collision should be controlled externally.

The IRPyro TO unit test demonstration firmware shows in a simplified manner how to:

TO_test01(); 02 Initialize a single IRPyro TO device

TO_test03(); 08 READ DATA FROM a single IRPyro TO and detect frames missing

TO_test05(); 14 Change IRPyro TO POWER CONFIGURATION

TO_test06(); 15 Configure the IRPyro TO WAKE UP EVENT, SEND TO SLEEP, DETECT WAKE UP

TO_test07(); 16 Change IRPyro TO PARAMETERS on the fly

Multiple Sensor Test

TO_test02(); 05 Initialize multiple IRPyro TO devices

TO_test04(); 11 READ DATA FROM MULTIPLE IRPyro TO SENSORS and detect frames missing

IRPyro API Unit Test structure

Attention

© COPYRIGHT 2018 _KEMET, Ltd

    Copyright (c) 2018, _KEMET, Ltd 
    All rights reserved.

    THIS SOFTWARE IS PROVIDED BY _KEMET, Ltd ''AS IS'' AND ANY
    EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
    WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
    DISCLAIMED. IN NO EVENT SHALL _KEMET, Ltd BE LIABLE FOR ANY
    DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
    (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
    LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
    ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
    SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.