OrangePiOne LIRC over GPIO

Mritke · Published in 2016-7-30 05:43:01

Anyone did that? Generally Arbian works great for my purposes (vivarium controller), wifi, gpio, hw RTC timer, etc, work like a charm(after little search). I have spare IR receiver and I would like more use it. I tried to change the pin in scripts.bin on PD14 (hw 12). But it did not work(i would be too easy

). I was following few threads on this forum(for example http://www.orangepi.org/orangepi ... &extra=page%3D5). but nothiong make the trick. Should i know something more? There is RPi(lirc_rpi, option gpio_in_pin=x) module for gpio use but i cant find one for H3.

nopnop2002 · Published in 2016-7-30 07:34:56

Edited by nopnop2002 at 2016-7-30 08:24

There is How to use IR with gpio.(without LIRC)

http://feijoa.jp/laboratory/raspberrypi/infrared/

This is a Japanese page, but I think you can probably understand.
If you use Google Chrome, it's translated into your national word.

I tried my OPI-ONE.(OPI-ONE doesn't have IR receiver)

It's work fine my OPI-ONE.
TV power on/off.
TV channel change.
TV volume up/down.

I have only a remote control of the NEC format.
It may not work by the other formats.

If you don't understand Japanese of this page, please ask an author or me using very very easy English.

Mritke · Published in 2016-7-30 08:23:52

I found this link earlier, and the program runs in my setup. Saves some data. But as far as i understand it makes only copy of IR signal, not interpret it. And I need OPi to be controlled from IR pilot. Not to controll tv.

nopnop2002 · Published in 2016-7-30 08:32:29

Edited by nopnop2002 at 2016-7-30 08:58

Mritke replied at 2016-7-30 08:23
I found this link earlier, and the program runs in my setup. Saves some data. But as far as i unders ...

I tried the following shell.
It couldn't be compared correctly.

#!/bin/bash
sudo ./scanir tmp.ir
files="./*.ir"
for filepath in $files; do
echo $filepath
cmp tmp.ir $filepath
done

How is lirc comparing the IR pattern?

nopnop2002 · Published in 2016-8-2 21:51:01

Edited by nopnop2002 at 2016-8-3 21:19

Mritke replied at 2016-7-30 08:23
I found this link earlier, and the program runs in my setup. Saves some data. But as far as i unders ...

I could control using external IR receiver by combining with ATtiny.
My RPI-ONE (This have No IR) can control using a remote control.

1. A sketch is written in ATtiny85.
The sketch is as follows.
ATtiny85 sends a received infrared code using UART.
This can distinguish only the NEC format.
Original is here.
http://www.technoblogy.com/show?V6F

/* ATtiny85 IR Remote Control Receiver
David Johnson-Davies - www.technoblogy.com - 3rd April 2015
ATtiny85 @ 1 MHz (internal oscillator; BOD disabled)
CC BY 4.0
Licensed under a Creative Commons Attribution 4.0 International license:
http://creativecommons.org/licenses/by/4.0/
http://www.technoblogy.com/show?V6F
*/
#include <SoftwareSerial.h>
#define rxPin 0 // PB0
#define txPin 1 // PB1
SoftwareSerial mySerial(rxPin, txPin); // RX, TX
volatile int NextBit;
volatile unsigned long RecdData;
// Demo routine
void ReceivedCode(boolean Repeat) {
// char buff[64];
// sprintf(buff,"%d,%x",Repeat,RecdData);
// mySerial.println(buff);
mySerial.print(Repeat);
mySerial.print(",");
mySerial.println(RecdData,HEX);
}
// Interrupt service routine - called on every falling edge of PB2
ISR(INT0_vect) {
int Time = TCNT0;
int Overflow = TIFR & 1<<TOV0;
// Keep looking for AGC pulse and gap
if (NextBit == 32) {
if ((Time >= 194) && (Time <= 228) && (Overflow == 0)) {
RecdData = 0; NextBit = 0;
} else if ((Time >= 159) && (Time <= 193) && (Overflow == 0)) ReceivedCode(1);
// Data bit
} else {
if ((Time > 44) || (Overflow != 0)) NextBit = 32; // Invalid - restart
else {
if (Time > 26) RecdData = RecdData | ((unsigned long) 1<<NextBit);
if (NextBit == 31) ReceivedCode(0);
NextBit++;
}
}
TCNT0 = 0; // Clear counter
TIFR = TIFR | 1<<TOV0; // Clear overflow
GIFR = GIFR | 1<<INTF0; // Clear INT0 flag
}
// Setup **********************************************
void setup() {
// Set up Timer/Counter0 (assumes 1MHz clock)
TCCR0A = 0; // No compare matches
TCCR0B = 3<<CS00; // Prescaler /64
// Set up INT0 interrupt on PB2
MCUCR = MCUCR | 2<<ISC00; // Interrupt on falling edge
GIMSK = GIMSK | 1<<INT0; // Enable INT0
NextBit = 32; // Wait for AGC start pulse
mySerial.begin(4800);
mySerial.println("IR demo start");
}
void loop()

Copy code

2.Wiring ATtiny85 and RPI-ONE.
A wiring diagram is this.
It don't have a part image of OPI, so I substituted a part image of RPI.
If someone have a part image of OPI, please share.
http://nopnop2002.webcrow.jp/OrangePiONE/OrangePiOne-2.html

**ATtiny operate 5V.
**So you need level shift.
**When ATtiny operate 3.3V,It can't receive IR.

3.Download sirw and sirexec.
Source code of sirw is this.
http://nopnop2002.webcrow.jp/OrangePiONE/ir/sirw.c

Source code of sirexec is this.
http://nopnop2002.webcrow.jp/OrangePiONE/ir/sirexec.c

$cc -o sirw sirw.c -lwiringPi
$cc -o sirexec sirexec.c -lwiringPi

4. Execute sirw.
$sudo ./sirw

When you push any remote,sirw indicates a remote control code.
When you'd like to use ttyS2 or ttyS3:
$sudo ./sirw /dev/ttyS2
$sudo ./sirw /dev/ttyS3

5. You take notes of an IR code.
The first 1 character is indicator whether repeat or not.
1,E619FF00:This is repeat code
0,E619FF00:This is not repeat code
E619FF00 is IR code.

6.Stop sirw.
Create config file in $HOME.
Everything is good for the file name.

Example:
#ok
EA15FF00,uname -a
#menu
BC43FF00,ls /boot

When receive EA15FF00,[uname -a] is executed.
When receive EA15FF00,[ls /boot] is executed.

7. Execute sirexec.
$sudo ./sirexec /dev/ttyS1 $HOME/config debug
When you'd like to use ttyS2 or ttyS3:
$sudo ./sirexec /dev/ttyS2 $HOME/config debug
$sudo ./sirexec /dev/ttyS3 $HOME/config debug

When you push remote, sirexec execute a command.
**Last argument "debug" is for test.
**When including in your /etc/rc.local, please remove the last argument "debug".

DoubleHP · Published in 2018-2-18 23:40:38

I have not been able to use LIRC on Orange/Armbian. It failed on many levels. The whole story is explained here:
https://forum.armbian.com/topic/ ... s-on-orangepi-zero/

The problem varies with the exact version of distribution you use. I am using µUbuntu 5.35 with kernel 4; and IR is now handled via the cir overlay; the cir driver has gone away.

My solution is explained here, for reception and emission:
http://www.orangepi.org/orangepi ... amp;extra=#pid22197
the whole work is done in bash and C; emission is done by my C code on PA6. I don't need any external chip; I can wire the IR receiver and emission diode directly on my opi0; my method does not require Atmel or anything like this. My solution is specific to my use case (I have hardcoded the 400us timing everywhere), but this can be tuned by editing the sources.

If you read about "lirc_rpi" driver on rpi forums, just run away; this is Raspbian specific.