Please select To the mobile version | Continue to access the desktop computer version

OrangePi

 Login            
 Register            
Search
Hot search: orangepi
Author: bir8339e

How to: setup wakeup with your IR remote control

[Copy link]

4

Threads

1128

Posts

7469

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
7469
Post time 2016-10-20 00:42:24 | Show all posts
giaur500 replied at 2016-10-19 17:31
What do you mean by reboot? It was booted after sd card inserted after replacing script.bin on PC. M ...

Well, there is more than one way to replace script.bin and not all require to take out SD card. Anyway, try with 0xB24D instead of 0x4D.

13

Threads

199

Posts

791

Credits

Senior member

Rank: 4

Credits
791
Post time 2016-10-20 01:01:50 | Show all posts
Still not working. So, this soultion is not universal. It sometimes may work, sometimes not

4

Threads

1128

Posts

7469

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
7469
Post time 2016-10-20 01:30:25 | Show all posts
giaur500 replied at 2016-10-19 18:01
Still not working. So, this soultion is not universal. It sometimes may work, sometimes not

I don't think there is another one. You may try another key. From what I know, it doesn't need to be KEY_SLEEP. For me, it works as KEY_POWER, but you can try also KEY_0 or any other. As last resort, you can backup lircd.conf and try from scratch again. Did you make some other script.bin change too?

13

Threads

199

Posts

791

Credits

Senior member

Rank: 4

Credits
791
Post time 2016-10-20 01:37:11 | Show all posts
No, no other changes

13

Threads

199

Posts

791

Credits

Senior member

Rank: 4

Credits
791
Post time 2016-10-20 02:26:56 | Show all posts
Edited by giaur500 at 2016-10-20 02:29

Is lircd.conf read during boot? If not, key mapping should not matter. I guess the only requirement is to have hardware in sleep state and make neccesary script.bin changes. Abd then device should wake up, right? Or it's also related to lirc config as well?
Maybe only some amount of codes are supported? Should I try with other remote?

4

Threads

1128

Posts

7469

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
7469
Post time 2016-10-20 04:40:21 | Show all posts
giaur500 replied at 2016-10-19 19:26
Is lircd.conf read during boot? If not, key mapping should not matter. I guess the only requirement  ...

Not in the driver, but systemd service load it, so yes, it doesn't matter. I partly reverse engineered ARISC IR driver and I can tell you that it looks almost the same as original Allwinner IR driver. I would say that codes don't matter really.

Definetly try with another one, as long as it outputs NEC protocol.

0

Threads

19

Posts

346

Credits

Intermediate member

Rank: 3Rank: 3

Credits
346
Post time 2016-10-20 06:29:37 | Show all posts
jernej replied at 2016-10-20 00:42
Well, there is more than one way to replace script.bin and not all require to take out SD card. An ...

I'd be interested in knowning those other ways as I just installed everything on the build-in emmc and I think changing the script.bin might be a pain now :S

4

Threads

1128

Posts

7469

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
7469
Post time 2016-10-20 13:26:56 | Show all posts
andreq replied at 2016-10-19 23:29
I'd be interested in knowning those other ways as I just installed everything on the build-in emmc ...

First make flash folder writable:
  1. mount -o remount,rw /flash
Copy the Code
and then copy script.bin with scp, for which you have to have ssh enabled. For example, on host PC for command line tool on Linux:
  1. scp script.bin root@192.168.0.10:/flash
Copy the Code
For Windows, there is graphical tool WinSCP.

0

Threads

19

Posts

346

Credits

Intermediate member

Rank: 3Rank: 3

Credits
346
Post time 2016-10-21 04:46:29 | Show all posts
jernej replied at 2016-10-20 13:26
First make flash folder writable:and then copy script.bin with scp, for which you have to have ssh  ...

Thanks a lot!
I'm using a samba share to copy to my windows pc already hehe.
Cant wait to have sunxi tools are included in the build, I won't be needing to go back and forth  Kodibox -> Window PC -> Linux VM -> Windows PC -> KodiBox

1

Threads

2

Posts

13

Credits

Novice

Rank: 1

Credits
13
 Author| Post time 2016-10-23 03:39:39 | Show all posts
glaur500,

Unlike mine,  your lircd.conf indicates that the key streams are not of a constant length. Please follow these instructions so we can find out what your remote is sending out:

1. Connect to the board through SSH.
2. Kill the lircd process and record just the stream for the POWER key like this:

  1. killall lircd
  2. irrecord -f test.conf
Copy the Code

3. Follow the instructions carefully but record just the POWER key.
4. Once you're done copy the 'test.conf' file out through the Samba share (or a USB pen drive) and post it here.
5. Reboot the board from the SSH prompt (type 'reboot' and press ENTER) to restart everything again (just don't unplug it without any kind of controlled shutdown).

This is the file I got:

  1. begin remote

  2.   name  test.cfg
  3.   flags RAW_CODES
  4.   eps            30
  5.   aeps          100

  6.   gap          129815

  7.       begin raw_codes

  8.           name KEY_SLEEP
  9.              9040    4528     552     560     576     560
  10.               528    1728     544     608     504     624
  11.               536     568     568     584     504     632
  12.               528     568     576    1712     536     560
  13.               576    1696     552    1704     520    1728
  14.               544     608     504    1728     576     560
  15.               520     616     552    1696     520    1728
  16.               576    1704     544     568     568     568
  17.               520     632     528    1704     520    1728
  18.               576     576     504     616     552     560
  19.               576    1696     552    1704     520    1728
  20.               568   75543    9016    2256     576
Copy the Code


What's represented are times in microseconds for logical level pairs (one followed by zero). So the first two are the header and the next read as (check the NEC protocol definition on the first post):

0 0 1 0 0 0 0 0 = 0x20
0 1 0 1 1 1 0 1 = 0x5D
0 0 1 1 1 0 0 0 = 0x38
1 1 0 0 0 1 1 1 = 0xC7

The last line is the time until and the key release and can be ignored. This is where those codes in my 'lircd.conf' are coming from. Please share your file so we can find out why your remote is not recognized.
You have to log in before you can reply Login | Register

Points Rules

Archiver|Mobile edition|Darkroom|OrangePi En ( 粤ICP备14086627号-2

2019-12-13 08:58 GMT+8 , Processed in 0.031126 second(s), 20 queries .

Powered by Discuz! X3.2

© 2014-2015 orangepibbs en.

Quick Reply To Top Return to the list