0

Sanity Check - Hardware Only

• These tests assume 'root' access but most commands can be performed with 'sudo'.

1. List USB Devices
Simply plugging in your CommandIR mini to your PC via USB should make it at least 'visible' as a USB device. As a basic test, plug it in and run:

• lsusb

• Cygnal Integrated Products, Inc.
• • If this fails and the CommandIR power indicator is on:
  • If the 'lsusb' command is not available on your system, look for USB devices in /proc
  • If no devices are listed, check that you have a USB driver loaded - for example usbohci - most modern Linux distro's pre-configure USB, but custom kernels and home-brew installations may not.

Sanity Check - CommandIR Hardware and Driver

2. Test Driver (No LIRC needed)

• Compile and load the CommandIR driver (insmod ./commandir.ko or modprobe commandir)
• Check your syslog for a message that the driver has detected a CommandIR:
• COMMANDIR USB device now attached to commandir0
  Receiving on #1 Transmitting on #1 2 3 4

Sanity Check - Basic LIRC Setup

3.1 LIRC View Raw Signals
With CommandIR attached and the drivers for CommandIR and LIRC loaded, you should be able to view raw signals detected by CommandIR from any remote without having to configure LIRC in any way.

• Run: mode2 -m

• Note: Some distros like MythBuntu use /dev/lirc0 by default instead of /dev/lirc - an error message like "mode2: error opening /dev/lirc", means an additional parameter is required: "mode2 -m -d /dev/lirc0"

• Aim any remote at CommandIR's receiver and press any button
• mode2 should display a series of raw IR codes. This shows CommandIR and lowlevel dependancies (like USB drivers) are functioning correctly and detecting your remote's raw signals, all ready for LIRC to decode.
  

Example mode2 output (Hauppauge_pvr remote):

      993      797      970      796      968      825

      968      797      968      825      968      797

      968      825     1836      826      943     1718

     1840      822      943      850      943    91310

      969      824      968      797      968      825

      966      799      966      827      966      799

      965      828     1834      827      943     1719

     1839      823      942      851      942    91344

If the hardware sanity check and CommandIR driver sanity checks pass but this fails - check that:

• The only LIRC modules running are 'lirc_dev' and 'lirc_cmdir' (no lirc_i2c)
• CommandIR is powered on, the remote has batteries, and is directed at CommandIR's front receiver.

3.2 LIRC Sanity Check - transmit to self
With the above checks passed and LIRC installed:

• Make sure your lircd.conf is configured with at least one remote
• Attach an IR emitter to any CommandIR channel, and place the transmitter by CommandIR's receiver
• With lirc_cmdir loaded, run: lircd, which will folk to the background
• In one terminal window, run: irw, which should run until Ctrl+C is pressed
• In a second terminal window, run: irsend send_once your_remote_name any_key_name
• CommandIR will transmit and receive the remote-control command
• The 'irw' window should display which remote command was transmitted and received

• CommandIR Mini is transmitting on the channel with the emitter - set CommandIR to transmit on all channels by: irsend set_transmitters 1 2 3 4
• If the indicator lights do not blink at all, CommandIR is not receiving your Command. Check the LIRC installation and Hardware sanity check.