Jump to content
Flirc Forums

Search the Community

Showing results for 'SendIR command'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Flirc forums
    • Skip
    • Raspberry Pi Cases
    • Flirc USB
    • Flirc USB Gen1
    • Jeff Probe

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests

Found 25 results

  1. I'm happy with the Flirc so far, but I found the initial set up a bit un-intuitive - so I thought I would document how I got this running on Mint Linux. Ultimately, I want to record all the codes from the huge remote that came with my screen, mount the Flirc near the IR receiver of the screen on a USB extension cable, and then use my PC as the primary control for the screen (transmitting IR via the Flirc dongle with scripts). At that point, I can put the remote in a drawer somewhere, so it's not cluttering up my space. I'm not quite there yet, but I think it's just a matter of learning how to decode the recorded codes and how to feed them to`sendir`. My process Using the commands below, I downloaded the binaries and loaded the libraries I was missing. I also pasted in the recommended udev rules. sudo apt install libreadline7 libhidapi-hidraw0 libqt5xmlpatterns5 wget http://apt.flirc.tv/arch/x86_64/flirc.latest.x86_64.tar.gz tar xvzf flirc.latest.x86_64.tar.gz cd Flirc-3.27.12 After unplugging and replugging the Flirc, I was able to successfully test it: I recorded a key press from my remote, turning it into the 'e' key. Then I pressed the key on the remote again and it typed an 'e'! Flirc-3.27.12$ ./flirc_util record e Press any button on the remote to link it with 'e' Succesfully recorded button Flirc-3.27.12$ e I successfully started the GUI, and upgraded the firmware via the GUI I successfully confirmed the firmware update, the self test, and the stored 'e key' macro. Flirc-3.27.12$ ./flirc_util settings 3.27.12 FW Version: v4.10.3 SKU: Flirc 2.0 [dori] Branch: release Config: release Hash: 0x9E8F9304 Settings: sleep detection: always enabled noise canceler: always enabled inter-key delay: N/A for current firmware variant: Flirc builtin profiles: NA Memory Info: NA product sku: Flirc 2.0 [dori] Recorded Keys: Index hash IK ID key ----- -------- --- -- ------------ 0 F6F39F97 054 01 e Flirc-3.27.12$ ./flirc_util unit_test Flirc Okay Issues encountered Adding the repository, per the docs, did not work at all for me, it comes up as 'insecure' and even using the apt flags for --allow-unauthenticated didn't help. The x86_64 repo doesn't have a Release file. That seemed to be one source of the issues, but I think there are multiple problems that would need to be addressed to allow the repo to work. After initial install, I was still getting the error below, even though the device showed up in lsusb. Ultimately it seems I was encountering an issue where udev rules are not applied until the device is removed and then reinserted. Flirc-3.27.12$ ./flirc_util settings device disconnected, can't run command Running the Flirc self test unexpectedly erased the key I had recorded during testing. I was unable to find a download for the firmware, so I had to use the GUI to update the firmware. I probably would not have loaded the GUI or it's dependencies at all otherwise.
  2. Inside a Flirc USB the IR transmitter and the IR receiver are physically very close to one another so the receiver picks up the transmitter's IR signal. Therefore, if a certain IR signal/pattern is paired with a keyboard key, the flirc_util.exe sendir --pronto/raw=<IR signal/pattern> command will also trigger the paired keyboard key, which is not always desired. Is there maybe a command line switch (or would it be possible to implement one) that would disable the Flirc's IR receiver (or ignore its input) while the sendir command is transmitting the IR signal (e.g. flirc_util.exe sendir --ignore)?
  3. Hi! I've been happy Flirc user, at least until now. After last firmware and Flirc app update on my Windows 11 HTPC, Flirc works only until I use irtools.exe with sendir command. After using it, Flirc shows as connected in the app, but can't read any IR codes. This can be fixed by unplugging and replugging Flirc into USB port, but only until I use irtools again. This is debug output with a few button presses when Flirc doesn't work: po aug 7 2023 20:55:31 Flirc GUI Version v3.27.3 Operating System: Windows -24513000 -510000 -595000 -803000 -620000 -518000 -370000 -43000 This is output ater replugging Flirc when it starts working: po aug 7 2023 20:56:11 Flirc GUI Version v3.27.3 Operating System: Windows *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.7 SKU: Flirc 2.0 [dori] Git Hash: 0x1de23eb8 <1>malloc_addblock(49): Heap Block: 0x20001AA4 - 0x20003BFF (8k) -13389000 +9101 -4406 +635 -474 +579 -500 +637 -450 +631 -474 +578 -504 +635 -448 +635 -492 +591 -1590 +635 -474 +608 -474 +605 -478 +634 -1595 +630 -1595 +608 -474 +635 -1595 +608 -1595 +634 -1590 +635 -447 +635 -474 +609 -473 +646 -1583 +609 -473 +635 -448 +634 -474 +604 -474 +635 -1594 +608 -1594 +635 -1594 +634 -448 +635 -1589 +635 -1594 +609 -1594 +634 -1804000 +9096 -4406 +634 -474 +609 -474 +604 -478 +635 -452 +630 -474 +605 -477 +635 -452 +605 -1616 +634 -452 +631 -473 +605 -478 +635 -1594 +604 -1603 +626 -474 +635 -1572 +630 -1594 +635 -452 +630 -474 +604 -509 +604 -447 +635 -1589 +635 -452 +630 -474 +583 -499 +635 -1594 +579 -1625 +634 -1590 +635 -1594 +579 -504 +635 -1594 +604 -1603 +626 -1594 +635 -1155000 +9100 -4403 +635 -452 +631 -474 +609 -473 +635 -448 +635 -473 +579 -504 +635 -448 +661 -1564 +635 -452 +631 -473 +583 -500 +635 -1594 +579 -1624 +631 -474 +608 -1595 +635 -1594 +635 -448 +635 -474 +604 -474 +635 -448 +635 -1594 +635 -1594 +609 -1591 +634 -474 +609 -1594 +635 -1595 +635 -1590 +609 -1594 +635 -474 +609 -474 +635 -448 +634 -1591 +609 -2326000 +9098 -4406 +605 -477 +635 -452 +631 -473 +631 -454 +633 -452 +630 -469 +609 -474 +634 -1594 +579 -504 +635 -447 +635 -469 +609 -1594 +635 -1594 +634 -448 +635 -1589 +635 -1594 +609 -473 +635 -1594 +578 -1624 +635 -1590 +635 -452 +630 -474 +604 -478 +635 -452 +630 -1594 +635 -447 +631 -473 +579 -504 +635 -1594 +612 -1590 +630 -1595 +634 -1595 +604 I am 90% positive it stopped working after upgrade, but can't be 100% sure because before the upgrade I was using flirc_utils.exe instead of irtools.exe Please help me with this issue. Thanks!
  4. @jason or anyone. Is there a tool or website available that helps me convert the flirc codes to the new format? I have a bunch of flirc codes lying around that need updating to use with the new Pi software. I tried getting phind.com to write a tool for me which resulted in this python code: import math # define constants PRONTO_CODE = '0000' FREQUENCY = '006D' ZERO = '0000' PULSE = 9025 SPACE = 4391 # input sequence (change this to your input) ir_sequence = [0,9025,4391,643,448,617,469,643,443,643,448,638,448,617,470,643,443,643,1568,617,1597,643,1568,643,1572,643,1568,643,1568,621,1594,643,1568,643,448,643,1568,643,443,643,447,617,469,643,444,643,447,639,447,643,444,643,443,643,1568,621,1593,643,1568,617,1598,643,1567,643,1567,647,1568,643] # convert IR sequence to Pronto Code pronto_sequence = [] for i in range(2, len(ir_sequence), 2): space = ir_sequence[i] pulse = ir_sequence[i+1] pulse_hex = hex(int(pulse/PULSE*0x10)) space_hex = hex(int(space/SPACE*0x10)) pronto_sequence.append(str(space_hex)[2:].zfill(4)) pronto_sequence.append(str(pulse_hex)[2:].zfill(4)) print(PRONTO_CODE, FREQUENCY, ZERO, ZERO, ''.join(pronto_sequence)) but it gave me a completely different result from the working expected pronto code that i have for that one command: Expected result: 0000 006D 0022 0000 0159 00AD 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0014 0042 0015 0041 0016 0041 0015 0042 0015 0042 0015 0042 0015 0042 0015 0016 0016 0042 0015 0016 0016 0016 0016 0016 0016 0016 0016 0016 0015 0016 0015 0016 0016 0016 0016 0041 0015 0041 0016 0042 0015 0042 0015 0042 0015 0041 0015 0041 0015 06C3 Actual result: 0000 006D 0000 0000 001000010001000100010001000100010001000100010001000100010001000100050001000500010005000100050001000500010005000100050001000500010001000100050001000100010001000100010001000100010001000100010001000100010001000100050001000500010005000100050001000500010005000100050001 EDIT: I now also tried your tool from above but it says "--pattern" can and can't be used at the same time: blu@automater:/var/www $ irtools help decode 0,9025,4391,643,448,617,469,643,443,643,448,638,448,617,470,643,443,643,1568,617,1597,643,1568,643,1572,643,1568,643,1568,621,1594,643,1568,643,448,643,1568,643,443,643,447,617,469,643,444,643,447,639,447,643,444,643,443,643,1568,621,1593,643,1568,617,1598,643,1567,643,1567,647,1568,643 Help for `decode' command: usage: decode <opts> decode --pattern=143,2123,13... OPTIONS: -l, --listen open the hardware, listen, decode results -r, --read read and decode from a file -t, --time comma delimited timing in microseconds -x, --raw +8248 -1291 +212 ... -p, --pronto pronto comma delimited pattern -e, --elapsed show elapsed time blu@automater:/var/www $ irtools decode --pattern=0,9025,4391,643,448,617,469,643,443,643,448,638,448,617,470,643,443,643,1568,617,1597,643,1568,643,1572,643,156 8,643,1568,621,1594,643,1568,643,448,643,1568,643,443,643,447,617,469,643,444,643,447,639,447,643,444,643,443,643,1568,621,1593,643,1568,617,1598,643,1567,643,15 67,647,1568,643 [W] lib/libcmds/cmds.c handle_longopt(181): `decode' doesn not take '--pattern' option Error: must specify an option EDIT 2: I now found the right command to atleast send the old commands in the meantime: irtools sendir --ik=23000 --repeat=0 --csv="0,9025,4391,..." this will help me until i have all codes converted to pronto. (Quick question: What happens if i send codes from flirc_util and irtools at the same time?)
  5. A little follow up. I have since upgraded to version 3.27.3. It seems that the repeat part of the sendir functionality does not work reliably. I erroneously claimed in my first post that the IR signal is not being sent under certain conditions but that was an observation based on the (non)response from the IR controlled device. I have since found a slightly more reliable (but still far from ideal) detection method: by capturing the output IR signal of the Flirc's transmitter with the Flirc's receiver (inside a Flirc unit the transmitter and the receiver are physically very close to one another so the receiver picks up the transmitter's signal). By using IR receiver logging functionality I can see that in reality the IR signal is sent, but usually not the correct one. In fact different length IR signals are being sent when using the same sendir command if the number of repeats is > 0 (note that when --repeat is omitted, sendir defaults to 1 repeat): Batch 'test.cmd': @echo off for /l %%a in (1,1,4) do ( flirc_util.exe device_log --ir >nul flirc_util.exe sendir --pronto="0000 006d 0022 0002 0156 00ab 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 05d8 0156 0055 0015 0e48" --repeat=2 >nul flirc_util.exe device_log ) Output: C:\Program Files (x86)\Flirc>test -36681 +8925 -4389 +585 -1588 +585 -1596 +555 -1609 +585 -471 +580 -472 +585 -471 +581 -471 +585 -1587 +585 -472 +580 -472 +585 -1587 +585 -1587 +559 -1614 +554 -1622 +559 -1605 +559 -497 +585 -471 +581 -471 +585 -1588 +559 -493 +585 -1587 +585 -4 72 +554 -498 +592 -1580 +585 -1587 +9478 -4368 +585 -9940 +8954 -2126 +585 -2761 +8928 -4387 +585 -1587 +585 -1591 +585 -1583 +585 -471 +559 -493 +585 -471 +559 -493 +585 -1587 +585 -471 +585 -467 +585 -1587 +584 -1588 +585 -1587 +585 -1587 +585 -1588 +585 -471 +581 -471 +585 -472 +580 -1588 +584 -492 +565 -1587 +559 -4 93 +585 -472 +554 -1618 +554 -1618 +554 -1614 +559 -502 +585 -1582 +585 -472 +58 0 -1587 +8930 -4370 +585 -9625 +8951 -2130 +585 -2776 +8927 -4394 +554 -1614 +559 -1627 +524 -1636 +585 -471 +555 -498 +585 -467 +585 -472 +554 -1614 +559 -498 +559 -493 +585 -1588 +585 -1587 +585 -1587 +586 -1596 +555 -1605 +559 -498 +585 -467 +585 -471 +559 -1613 +559 -493 +585 -1588 +585 -4 71 +555 -497 +600 -1573 +585 -1587 +9476 -4368 +585 -9949 +8954 -2130 +585 -2721 +8928 -4392 +584 -1588 +585 -1587 +585 -1587 +585 -471 +580 -472 +585 -471 +580 -472 +585 -1587 +585 -467 +585 -471 +585 -1587 +585 -1587 +585 -1587 +585 -1587 +559 -1614 +558 -498 +558 -493 +559 -493 +585 -1587 +585 -489 +541 -1613 +559 -4 93 +585 -471 +559 -1614 +554 -1614 +9476 -4370 +585 -9927 +8956 -2125 +585
  6. I have a batch script that utilizes flirc_util.exe to send IR commands with Flirc USB. After upgrading Flirc (by replacing Flirc.exe & flirc_util.exe in the install dir) from 3.26.5 to 3.26.8 (because I need support for Pronto IR codes), I am having the following issue. If flirc_util.exe command is inside a for /f loop, for example: for /f "delims=" %%a in ('""C:\Program Files (x86^)\Flirc\flirc_util.exe" sendir --pronto="0000 006d 0022 0002 0156 00ab 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 05d8 0156 0055 0015 0e48" 2>&1"') do echo %%a the IR signal is NOT being sent anymore. flirc_util.exe command output is still displayed though: Transmitting IR Pattern... +8892 -4446 +546 -1664 +546 -1664 +546 -1664 +546 -546 +546 -546 +546 -546 +546 -546 +546 -1664 +546 -546 +546 -546 +546 -1664 +546 -1664 +546 -1664 +546 -1664 +546 -1664 +546 -546 +546 -546 +546 -546 +546 -1664 +546 -546 +546 -1664 +546 -5 46 +546 -546 +546 -1664 +546 -1664 +546 -1664 +546 -546 +546 -1664 +546 -546 +54 6 -1664 +546 -1664 +546 -546 +546 -38000 +8892 -2210 +546 -95000 Done! If flirc_util.exe command is called directly, for example: "C:\Program Files (x86)\Flirc\flirc_util.exe" sendir --pronto="0000 006d 0022 0002 0156 00ab 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 05d8 0156 0055 0015 0e48" 2>&1 the IR signal is still being sent (most of the time anyway*). (both examples can also be verified directly in cmd.exe if you replace %%a with %a) Can somebody please help. Thank you in advance. Regards, Franc * After some experimenting it seems like the longer (more complicated) the command line is, the less likely the IR signal will be sent. Very strange.
  7. The emitter and receiver in Flirc are just millimetres apart, so the receiver is probably picking up the signal from the emitter. There is no (official) command line switch to disable the receiver during the sendir.
  8. I read that Flirc can act as an emitter, and sendir is the way to do it. However, I've found that using sendir causes Flirc to execute on the PC whatever command is bound to the sent code. That's cool, but it's not what I want. I just want it to send the IR code, basically to "forward" it. Also, when I turned on IR debugging, pressing a single key on my remote caused several lines of output, and passing any one of them to sendir works to execute the command on my PC, e.g. "Enter", "Right arrow", etc. For example, this is the output for pressing the Enter key on my remote: +2458 -507 +1261 -508 +658 -503 +1261 -503 +1261 -508 +1257 -507 +1257 -508 +662 -503 +658 -503 +1262 -507 +658 -503 +1261 -509 +1256 -507 +658 -507 +1257 -507 +658 -507 +658 -507 +658 -503 +1261 -508 +1257 -507 +1257 -11000 +2461 -508 +1263 -501 +658 -503 +1262 -503 +1261 -503 +1262 -503 +1261 -508 +658 -503 +658 -507 +1257 -508 +657 -508 +1257 -508 +1257 -507 +658 -503 +1261 -508 +657 -507 +658 -507 +658 -503 +1261 -503 +1261 -508 +1257 -11000 +2460 -508 +1261 -503 +662 -503 +1276 -488 +1257 -507 +1257 -508 +1256 -508 +657 -507 +658 -503 +1261 -504 +662 -503 +1257 -508 +1257 -508 +658 -503 +1261 -507 +658 -507 +658 -503 +662 -504 +1256 -508 +1257 -507 +1257 -11000 +2461 -507 +1261 -504 +657 -504 +1261 -503 +1258 -507 +1257 -508 +1257 -507 +658 -507 +658 -503 +1257 -508 +657 -508 +1257 -507 +1257 -508 +657 -508 +1257 -507 +658 -507 +658 -507 +733 -428 +1257 -508 +1257 -507 +1257 -11000 +2466 -503 +1262 -503 +662 -504 +1261 -503 +1257 -508 +1256 -504 +1261 -503 +662 -503 +662 -503 +1257 -507 +658 -503 +1261 -503 +1261 -503 +662 -503 +1261 -503 +662 -503 +662 -503 +657 -504 +1261 -503 +1262 -503 +1261 -36436000 Sending "+2458 -507 +1261 -508 +658 -503 +1261 -503 +1261 -508 +1257 -507 +1257 -508 +662 -503 +658 -503 +1262 -507 +658 -503 +1261 -509 +1256 -507 +658 -507 +1257 -507 +658 -507 +658 -507 +658 -503 +1261 -508 +1257 -507 +1257" causes Flirc to executed an "Enter" keystroke on my PC. I don't know what the other lines are for. Can you explain to me the proper use of sendir?
  9. Hello, I want to purchase a FLIRC but I want to be sure Ill be able to work out what i need to do before I do. My situation: Have PC (Win10) Stereo Amplifier My requirement is to be able to turn on/off the amp, and control its volume from Windows command line (my whole goal is to go remote-less) I know the FLIRC can send IR commands and can learn them too. But the process of doing this via command line with flirc_utils sendir is confusing. For my amplifier, the RAW IR codes are available in the support manual. But sending that via sendir is where I'm getting stuck. Volume down for example is: 000 006D 0022 0002 0157 00AC 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0689 0157 0056 0015 0E94 But I'm unsure how to 'convert' that info a format that sendir will accept/understand. I found these threads below, which are quite similar to what I'm after - but as above, I don't really know how to convert it. Do I/can I use IrScrutinizer? I asked ChatGPT but it gave lots of incorrect answers. Thanks!
  10. Hi @jason Thanks for your continued efforts on this. I am not 100% sure it's working on the raspberry pi - please see the output below it all looks successful however the IR signal is not transmitted. Also from a usability perspective it would be great if you could have the raw signal as an input for the transmission using irtools rather than having to decode and then add commas into the before issuing a send command. Something like: irtools sendir --raw="..." --repeat=1 pi@raspberrypi:~ $ irtools decode --raw="+9071 -4425 +638 -456 +639 -456 +639 -451 +644 -451 +643 -452 +643 -452 +639 -456 +638 -456 +639 -1584 +643 -1584 +643 -1579 +643 -1584 +643 -1585 +638 -1585 +643 -1584 +639 -1584 +643 -452 +643 -451 +639 -1584 +643 -1584 +643 -452 +639 -456 +664 -430 +639 -452 +643 -1584 +639 -1584 +643 -452 +643 -451 +643 -1585 +638 -1584 +669 -1559 +638 -1585 +643" [V] main(121): Command: irtools [V] main(125): running pre-command function 0 [D] list_devs(254): --------------------------------------------------------- [D] list_devs(255): -----------------------Device List----------------------- [D] list_devs(256): --------------------------------------------------------- [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 0 [D] list_devs(274): Usage Page: 65280 [D] list_devs(275): Usage: 1 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 1 [D] list_devs(275): Usage: 6 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 12 [D] list_devs(275): Usage: 1 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 1 [D] list_devs(275): Usage: 128 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 12 [D] list_devs(275): Usage: 1 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 2 [D] list_devs(274): Usage Page: 65280 [D] list_devs(275): Usage: 1 [D] list_devs(281): --------------------------------------------------------- [D] hid_find(229): Device Used type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] hid_find(231): Manufacturer: flirc.tv [D] hid_find(232): Product: flirc [D] hid_find(233): Release: 200 [D] hid_find(234): Interface: 2 [D] hid_find(235): Usage Page: 65280 [D] hid_find(236): Usage: 1 [V] hid_dev_open(311): Manufacturer String: flirc.tv [V] hid_dev_open(316): Product String: flirc [V] hid_dev_open(321): Serial Number String: E7A3ABA25050323431202020FF101122 [V] hid_dev_open(322): [V] hid_send_packet(79): Report ID: 2 [V] hid_send_packet(80): Report len: 33 00: 02 75 73 62 5f 69 66 00 00 00 00 00 00 01 00 00 .usb_if......... 10: 00 01 04 f5 00 bc 47 9f ff c8 3b 01 00 c8 47 9f ......G...;...G. 20: ff . [V] hid_send_packet(91): hid_write = 33 [V] hid_recv_packet(144): Report ID: 1 [V] hid_recv_packet(145): Report len: 33 [V] hid_recv_packet(155): retval = 33 00: 01 75 73 62 5f 69 66 00 00 00 00 00 00 00 00 00 .usb_if......... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 . found it [V] lib/libcmds/cmds.c run_cmds(251): running command: decode [V] lib/libcmds/cmds.c cmd_getopt(223): opt: --raw=+9071 -4425 +638 -456 +639 -456 +639 -451 +644 -451 +643 -452 +643 -452 +639 -456 +638 -456 +639 -1584 +643 -1584 +643 -1579 +643 -1584 +643 -1585 +638 -1585 +643 -1584 +639 -1584 +643 -452 +643 -451 +639 -1584 +643 -1584 +643 -452 +639 -456 +664 -430 +639 -452 +643 -1584 +639 -1584 +643 -452 +643 -451 +643 -1585 +638 -1584 +669 -1559 +638 -1585 +643, carg = 1 +9071 -4425 +638 -456 +639 -456 +639 -451 +644 -451 +643 -452 +643 -452 +639 -456 +638 -456 +639 -1584 +643 -1584 +643 -1579 +643 -1584 +643 -1585 +638 -1585 +643 -1584 +639 -1584 +643 -452 +643 -451 +639 -1584 +643 -1584 +643 -452 +639 -456 +664 -430 +639 -452 +643 -1584 +639 -1584 +643 -452 +643 -451 +643 -1585 +638 -1584 +669 -1559 +638 -1585 +643 [V] analyze_edge(66): removing decoder: rc5 8182 > 2000 [V] analyze_edge(66): removing decoder: mce 6407 > 2000 [V] analyze_edge(66): removing decoder: xmp 8861 > 2000 [V] analyze_edge(66): removing decoder: ortek 7151 > 2000 [V] analyze_edge(66): removing decoder: sharp 7223 > 2000 [V] analyze_edge(66): removing decoder: sony 6671 > 2000 [V] analyze_edge(66): removing decoder: denon 8807 > 2000 [V] analyze_edge(66): removing decoder: flirc 4171 > 2000 [V] analyze_edge(66): removing decoder: nokia 8659 > 2000 [V] analyze_edge(66): removing decoder: TDC 8756 > 2000 [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] finish_nec(72): nec [V] ir_decode(74): handler match: NEC [V] ir_nec_bytes_to_scancode(72): NEC Scancode: 0x0030 [V] ir_nec_decode(122): Device: 0x00 ~Device: 0xFF Command: 0x30 ~Command: 0xCF ScanCode: 0x00FF30CF :: FLIRC :: NEC - scancode: 0x00FF30CF 0000 006D 0022 0002 015C 00AA 0018 0011 0018 0011 0018 0011 0018 0011 0018 0011 0018 0011 0018 0011 0018 0011 0018 003C 0018 003C 0018 003C 0018 003C 0018 003C 0018 003C 0018 003C 0018 003C 0018 0011 0018 0011 0018 003C 0018 003C 0018 0011 0018 0011 0019 0010 0018 0011 0018 003C 0018 003C 0018 0011 0018 0011 0018 003C 0018 003C 0019 003B 0018 003C 0018 05F1 0156 0056 0015 0E4A [V] DecodeIR(5900): NEC Device: 0x00 SubDevice: 0xFFFFFFFF OBC: 0xFFFFFFFFFFFFFFFFFFFFFFFF000000CF MISC: no repeat ERROR: :: DECODEIR :: NEC - scancode: 0x00CF D:0x0000 S:0xFFFFFFFF [V] analyze_edge(66): removing decoder: rc5 8182 > 2000 [V] analyze_edge(66): removing decoder: mce 6407 > 2000 [V] analyze_edge(66): removing decoder: xmp 8861 > 2000 [V] analyze_edge(66): removing decoder: ortek 7151 > 2000 [V] analyze_edge(66): removing decoder: sharp 7223 > 2000 [V] analyze_edge(66): removing decoder: sony 6671 > 2000 [V] analyze_edge(66): removing decoder: denon 8807 > 2000 [V] analyze_edge(66): removing decoder: flirc 4171 > 2000 [V] analyze_edge(66): removing decoder: nokia 8659 > 2000 [V] analyze_edge(66): removing decoder: TDC 8756 > 2000 [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] get_closest_proto(40): list entry: NEC [V] get_closest_proto(46): choosing: NEC [V] finish_nec(72): nec [V] ir_decode(74): handler match: NEC [V] ir_nec_bytes_to_scancode(72): NEC Scancode: 0x0030 [V] ir_nec_decode(122): Device: 0x00 ~Device: 0xFF Command: 0x30 ~Command: 0xCF ScanCode: 0x00FF30CF :: FLIRC :: NEC - scancode: 0x00FF30CF :: ARDUINO :: NEC - scancode: 0x00FF30CF {32} ++++ [V] main(153): running post-command function 0 [V] flirc_deinit(89): closing serial device pi@raspberrypi:~ $ irtools sendir --pattern="0000,006D,0022,0002,015C,00AA,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,0011,0018,0011,0018,003C,0018,003C,0018,0011,0018,0011,0019,0010,0018,0011,0018,003C,0018,003C,0018,0011,0018,0011,0018,003C,0018,003C,0019,003B,0018,003C,0018,05F1,0156,0056,0015,0E4A" --repeat=1 [V] main(121): Command: irtools [V] main(125): running pre-command function 0 [D] list_devs(254): --------------------------------------------------------- [D] list_devs(255): -----------------------Device List----------------------- [D] list_devs(256): --------------------------------------------------------- [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 0 [D] list_devs(274): Usage Page: 65280 [D] list_devs(275): Usage: 1 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 1 [D] list_devs(275): Usage: 6 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 12 [D] list_devs(275): Usage: 1 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 1 [D] list_devs(275): Usage: 128 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 1 [D] list_devs(274): Usage Page: 12 [D] list_devs(275): Usage: 1 [D] list_devs(267): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] list_devs(269): [D] list_devs(270): Manufacturer: flirc.tv [D] list_devs(271): Product: flirc [D] list_devs(272): Release: 200 [D] list_devs(273): Interface: 2 [D] list_devs(274): Usage Page: 65280 [D] list_devs(275): Usage: 1 [D] list_devs(281): --------------------------------------------------------- [D] hid_find(229): Device Used type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] hid_find(231): Manufacturer: flirc.tv [D] hid_find(232): Product: flirc [D] hid_find(233): Release: 200 [D] hid_find(234): Interface: 2 [D] hid_find(235): Usage Page: 65280 [D] hid_find(236): Usage: 1 [V] hid_dev_open(311): Manufacturer String: flirc.tv [V] hid_dev_open(316): Product String: flirc [V] hid_dev_open(321): Serial Number String: E7A3ABA25050323431202020FF101122 [V] hid_dev_open(322): [V] hid_send_packet(79): Report ID: 2 [V] hid_send_packet(80): Report len: 33 00: 02 75 73 62 5f 69 66 00 00 00 00 00 00 01 00 00 .usb_if......... 10: 00 01 54 d6 01 1c 46 c1 ff c8 3b 01 00 28 46 c1 ..T...F...;..(F. 20: ff . [V] hid_send_packet(91): hid_write = 33 [V] hid_recv_packet(144): Report ID: 1 [V] hid_recv_packet(145): Report len: 33 [V] hid_recv_packet(155): retval = 33 00: 01 75 73 62 5f 69 66 00 00 00 00 00 00 00 00 00 .usb_if......... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 . found it [V] lib/libcmds/cmds.c run_cmds(251): running command: sendir [V] lib/libcmds/cmds.c cmd_getopt(223): opt: --pattern=0000,006D,0022,0002,015C,00AA,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,0011,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,003C,0018,0011,0018,0011,0018,003C,0018,003C,0018,0011,0018,0011,0019,0010,0018,0011,0018,003C,0018,003C,0018,0011,0018,0011,0018,003C,0018,003C,0019,003B,0018,003C,0018,05F1,0156,0056,0015,0E4A, carg = 1 [V] lib/libcmds/cmds.c cmd_getopt(223): opt: --repeat=1, carg = 2 [V] hid_send_packet(79): Report ID: 2 [V] hid_send_packet(80): Report len: 33 00: 02 67 65 74 76 65 72 73 69 6f 6e 00 00 c8 19 d7 .getversion..... 10: f7 d0 06 01 00 00 00 00 00 94 1b d7 f7 00 00 00 ................ 20: 00 . [V] hid_send_packet(91): hid_write = 33 [V] hid_recv_packet(144): Report ID: 1 [V] hid_recv_packet(145): Report len: 33 [V] hid_recv_packet(155): retval = 33 00: 01 67 65 74 76 65 72 73 69 6f 6e 00 00 04 00 09 .getversion..... 10: 00 07 00 b8 3e e2 1d 72 65 6c 65 61 73 65 00 00 ....>..release.. 20: 00 . [E] fl_version_compare(281): Flirc iospirit found version: 4.9.7 0x1DE23EB8 [release] [D] csv_to_buf(44): number of commas in string: 75 [V] hid_send_packet(79): Report ID: 6 [V] hid_send_packet(80): Report len: 65 Transmitting IR Pattern...00: 06 69 72 74 72 61 6e 73 65 74 00 00 00 4a 00 00 .irtranset...J.. 10: 00 01 89 45 df d0 de d3 f7 00 10 05 00 90 61 01 ...E..........a. 20: 00 a8 18 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 10 d7 f7 fc 45 c1 ff d0 08 9e f7 f4 44 c1 ......E.......D. 40: ff . [V] hid_send_packet(91): hid_write = 65 [V] hid_recv_packet(144): Report ID: 5 [V] hid_recv_packet(145): Report len: 65 [V] hid_recv_packet(155): retval = 65 00: 05 69 72 74 72 61 6e 73 65 74 00 00 00 00 00 00 .irtranset...... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: 00 00 06 00 16 00 02 00 0f 00 00 00 12 00 0b 00 ................ 10: 12 00 0b 00 12 00 0b 00 12 00 0b 00 12 00 0b 00 ................ 20: 12 00 0b 00 12 00 0b 00 12 00 0b 00 12 00 03 00 ................ 30: 12 00 03 00 .... [V] hid_send_packet(79): Report ID: 6 [V] hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 06 .irtransraw..... 10: 00 16 00 02 00 0f 00 00 00 12 00 0b 00 12 00 0b ................ 20: 00 12 00 0b 00 12 00 0b 00 12 00 0b 00 12 00 0b ................ 30: 00 12 00 0b 00 12 00 0b 00 12 00 03 00 12 00 03 ................ 40: 00 . [V] hid_send_packet(91): hid_write = 65 [V] hid_recv_packet(144): Report ID: 5 [V] hid_recv_packet(145): Report len: 65 [V] hid_recv_packet(155): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: 12 00 03 00 12 00 03 00 12 00 03 00 12 00 03 00 ................ 10: 12 00 03 00 12 00 03 00 12 00 0b 00 12 00 0b 00 ................ 20: 12 00 03 00 12 00 03 00 12 00 0b 00 12 00 0b 00 ................ 30: 13 00 0a 00 .... [V] hid_send_packet(79): Report ID: 6 [V] hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 12 00 03 .irtransraw..... 10: 00 12 00 03 00 12 00 03 00 12 00 03 00 12 00 03 ................ 20: 00 12 00 03 00 12 00 0b 00 12 00 0b 00 12 00 03 ................ 30: 00 12 00 03 00 12 00 0b 00 12 00 0b 00 13 00 0a ................ 40: 00 . [V] hid_send_packet(91): hid_write = 65 [V] hid_recv_packet(144): Report ID: 5 [V] hid_recv_packet(145): Report len: 65 [V] hid_recv_packet(155): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: 12 00 0b 00 12 00 03 00 12 00 03 00 12 00 0b 00 ................ 10: 12 00 0b 00 12 00 03 00 12 00 03 00 13 00 03 00 ................ 20: 12 00 03 00 12 00 05 00 9c 00 38 00 ..........8. [V] hid_send_packet(79): Report ID: 6 [V] hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 12 00 0b .irtransraw..... 10: 00 12 00 03 00 12 00 03 00 12 00 0b 00 12 00 0b ................ 20: 00 12 00 03 00 12 00 03 00 13 00 03 00 12 00 03 ................ 30: 00 12 00 05 00 9c 00 38 00 00 00 00 00 00 00 00 .......8........ 40: 00 . [V] hid_send_packet(91): hid_write = 65 [V] hid_recv_packet(144): Report ID: 5 [V] hid_recv_packet(145): Report len: 65 [V] hid_recv_packet(155): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . Done! [V] main(153): running post-command function 0 [V] flirc_deinit(89): closing serial device pi@raspberrypi:~ $
  11. Thanks @jason its updated. This was my recording in the device log: *** Device Connected *** Firmware Version: v4.9.7 SKU: Flirc 2.0 [dori] Git Hash: 0x1de23eb8 -19275000 +9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639 -40000 +9095 -2169 +613 <3>record_hash(473): hash exists I believe I should be using the command to send the IR signal - can you please confirm pi@raspberrypi:~ $ flirc_util sendir --raw="+9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639" --repeat=1 Here is the output: [V] util/flirc_util/src/main.c main(123): Command: flirc_util [V] util/flirc_util/src/main.c main(127): running pre-command function 0 [D] lib/libflirc/common/flirc_transport.c fl_open_hid(124): trying to open bootloader device [D] lib/libtransport/hid.c list_devs(280): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(281): -----------------------Device List----------------------- [D] lib/libtransport/hid.c list_devs(282): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 0 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 6 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 128 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 2 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(306): --------------------------------------------------------- [V] lib/libtransport/hid.c hid_dev_open(329): Device 20A0:5 not found [V] lib/libtransport/transport.c dev_open(88): no device found [V] lib/libflirc/common/flirc_transport.c _fl_open_libhid_btldr(56): no hid device found [D] lib/libflirc/common/flirc_transport.c fl_open_hid(130): trying to open main device [D] lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(92): trying to open 0x20A0, 0x0006 [D] lib/libtransport/hid.c list_devs(280): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(281): -----------------------Device List----------------------- [D] lib/libtransport/hid.c list_devs(282): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 0 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 6 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 128 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 2 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(306): --------------------------------------------------------- [D] lib/libtransport/hid.c hid_find(254): Device Used type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122[D] lib/libtransport/hid.c hid_find(256): Manufacturer: flirc.tv [D] lib/libtransport/hid.c hid_find(257): Product: flirc [D] lib/libtransport/hid.c hid_find(258): Release: 200 [D] lib/libtransport/hid.c hid_find(259): Interface: 0 [D] lib/libtransport/hid.c hid_find(260): Usage Page: 65280 [D] lib/libtransport/hid.c hid_find(261): Usage: 1 [V] lib/libtransport/hid.c hid_dev_open(336): Manufacturer String: flirc.tv [V] lib/libtransport/hid.c hid_dev_open(341): Product String: flirc [V] lib/libtransport/hid.c hid_dev_open(346): Serial Number String: E7A3ABA25050323431202020FF101122 [V] lib/libtransport/hid.c hid_dev_open(347): [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 2 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 33 00: 02 67 65 74 76 65 72 73 69 6f 6e 00 00 b4 79 03 .getversion...y. 10: 00 d4 ea 8f ff 04 00 00 00 00 00 00 00 78 ea 8f .............x.. 20: ff . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 33 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 1 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 33 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 33 00: 01 67 65 74 76 65 72 73 69 6f 6e 00 00 04 00 09 .getversion..... 10: 00 07 00 b8 3e e2 1d 72 65 6c 65 61 73 65 00 00 ....>..release.. 20: 00 . [V] lib/libflirc/common/flirc_transport.c transport_new_get_version(35): Version: 4.9.7 0x1DE23EB8 [release] [D] lib/libflirc/flirc_driver.c determine_iface(116): fw_state: firmware [D] lib/libflirc/flirc_driver.c determine_iface(118): version: 4.9 [D] lib/libflirc/flirc_driver.c determine_iface(256): initializing fw ver4.9 [D] lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(113): [Device Found] [V] lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(114): FIRMWARE: 2 [V] lib/libflirc/common/flirc_transport.c fl_open_hid(132): application found [D] lib/libflirc/flirc_driver.c fl_open_device(285): device found, state: 2 [V] lib/libcmds/cmds.c run_cmds(251): running command: sendir [V] lib/libcmds/cmds.c cmd_getopt(223): opt: --raw=+9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639, carg = 1 [V] lib/libcmds/cmds.c cmd_getopt(223): opt: --repeat=1, carg = 2 Transmitting IR Pattern... [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 65 74 00 00 00 44 00 98 .irtranset...D.. 10: 3a 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 :............... 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 ff ff ff ff 00 00 00 00 dc 99 61 f7 c8 fb 80 ...........a.... 40: f7 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 65 74 00 00 00 00 00 00 .irtranset...... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: 00 00 89 23 2f 11 83 02 c4 01 83 02 c8 01 7e 02 ...#/.........~. 10: c8 01 7f 02 c4 01 83 02 c4 01 83 02 c3 01 7f 02 ................ 20: c8 01 7f 02 c8 01 7e 02 35 06 7f 02 35 06 7f 02 ......~.5...5... 30: 30 06 83 02 0... [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 89 .irtransraw..... 10: 23 2f 11 83 02 c4 01 83 02 c8 01 7e 02 c8 01 7f #/.........~.... 20: 02 c4 01 83 02 c4 01 83 02 c3 01 7f 02 c8 01 7f ................ 30: 02 c8 01 7e 02 35 06 7f 02 35 06 7f 02 30 06 83 ...~.5...5...0.. 40: 02 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: 31 06 7e 02 31 06 83 02 31 06 83 02 30 06 7f 02 1.~.1...1...0... 10: 31 06 93 02 20 06 7f 02 34 06 7f 02 da 01 6d 02 1... ...4.....m. 20: c8 01 7f 02 c8 01 7f 02 c8 01 7f 02 31 06 7e 02 ............1.~. 30: c9 01 7e 02 ..~. [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 31 06 7e .irtransraw..1.~ 10: 02 31 06 83 02 31 06 83 02 30 06 7f 02 31 06 93 .1...1...0...1.. 20: 02 20 06 7f 02 34 06 7f 02 da 01 6d 02 c8 01 7f . ...4.....m.... 30: 02 c8 01 7f 02 c8 01 7f 02 31 06 7e 02 c9 01 7e .........1.~...~ 40: 02 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: c8 01 7f 02 c8 01 7f 02 35 06 aa 02 06 06 83 02 ........5....... 10: 30 06 7f 02 34 06 7f 02 ca 01 63 02 4b 06 7f 02 0...4.....c.K... [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 c8 01 7f .irtransraw..... 10: 02 c8 01 7f 02 35 06 aa 02 06 06 83 02 30 06 7f .....5.......0.. 20: 02 34 06 7f 02 ca 01 63 02 4b 06 7f 02 00 00 00 .4.....c.K...... 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . +9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639 -15000 Done! [V] util/flirc_util/src/main.c main(173): running post-command function 0 [V] util/flirc_util/src/prepost.c flirc_deinit(39): closing device [D] lib/libflirc/flirc_driver.c fl_close_device(443): closing device [D] lib/libflirc/flirc_driver.c fl_close_device(454): freeing iface pi@raspberrypi:~ $
  12. Hello, I'm trying to replicate my AC remote using Flirc. I did it a few months ago, but I can't seem to get it back. I captured this log using Flirc GUI: Firmware Version: v4.9.61 SKU: Flirc 2.0 [dori] Git Hash: 0x4b35b711 <3>record_hash(473): hash exists -40481 +8834 -4157 +509 -1534 +510 -494 +509 -493 +507 -495 +508 -1536 +509 -494 +509 -493 +509 -494 +508 -495 +509 -493 +535 -469 +508 -495 +506 -495 +510 -493 +507 -496 +508 -496 +508 -1534 +509 -495 +522 -480 +507 -496 +508 -494 +508 -495 +509 -494 +509 -493 +508 -1534 +509 -494 +508 -495 +507 -495 +508 I'm trying to replicate this command using flirc_util, but I can't get it to work: flirc_util.exe sendir --raw="-40481 +8834 -4157 +509 -1534 +510 -494 +509 -493 +507 -495 +508 -1536 +509 -494 +509 -493 +509 -494 +508 -495 +509 -493 +535 -469 +508 -495 +506 -495 +510 -493 +507 -496 +508 -496 +508 -1534 +509 -495 +522 -480 +507 -496 +508 -494 +508 -495 +509 -494 +509 -493 +508 -1534 +509 -494 +508 -495 +507 -495 +508" [W] lib/libcmds/cmds.c handle_longopt(182): `sendir' doesn not take '--raw' option Error: must specify an option flirc_util.exe sendir --pronto="-40481 +8834 -4157 +509 -1534 +510 -494 +509 -493 +507 -495 +508 -1536 +509 -494 +509 -493 +509 -494 +508 -495 +509 -493 +535 -469 +508 -495 +506 -495 +510 -493 +507 -496 +508 -496 +508 -1534 +509 -495 +522 -480 +507 -496 +508 -494 +508 -495 +509 -494 +509 -493 +508 -1534 +509 -494 +508 -495 +507 -495 +508" Transmitting IR Pattern... (but doesn't work) flirc_util.exe sendir --pronto="0,40481,8834,4157,509,1534,510,494,509,493,507,495,508,1536,509,494,509,493,509,494,508,495,509,493,535,469,508,495,506,495,510,493,507,496,508,496,508,1534,509,495,522,480,507,496,508,494,508,495,509,494,509,493,508,1534,509,494,508,495,507,495,508" [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state' Error getting version device disconnected, can't run command ¿Any idea? Thanks!
  13. Try flirc_util.exe sendir --pattern=0,8834,4157,509,1534,510,494,509,493,507,495,508,1536,509,494,509,493,509,494,508,495,509,493,535,469,508,495,506,495,510,493,507,496,508,496,508,1534,509,495,522,480,507,496,508,494,508,495,509,494,509,493,508,1534,509,494,508,495,507,495,508 --repeat=0 Close Flirc GUI before running the command. --raw and --pronto arguments are not available before version 3.26.8.
  14. i can send you the previous firmware, but would also need to include support for the comma delimited sendir command, is that correct?
  15. Unfortunately the documentation and support is rather lacking on this feature possibly due to lack of dev cycles anyway here is a "how to" of the " SendIR waveform function" from latest git as of feb 8 2021 on Ubuntu 20 x64: ( this guide assumes basic Linux know how, and may be invalidated over time due to updates to git) Side note: There exists other devices I bought like USB-UIRT which do a better job but have their own issues, flirc however I find a little easier to capture IR waveforms so has some uses the issue is the transceiver its not going to work unless your literally sitting the usb unit in front of the device you want to control. Objective: What is Send IR, its a way to remotely send Infrared signals directly outbound, as opposed to what Flirc was designed for which is mainly inbound device control. 1. You will need Ubuntu 20 or equivalent 2. You will need V2 of the Flirc Steps: a. install flirc using the known methods namely: Debian [64], Redhat [64bit], or Raspberry Pi Debian curl apt.flirc.tv/install.sh | sudo bash b. get git, sudo apt install git c. Make a directory and install and compile the sdk Commands from your home directory: cd ~ mkdir buildsdk cd buildsdk git clone https://github.com/flirc/sdk.git cd sdk cd cli sudo apt-get install libusb-1.0-0-dev libreadline-dev libhidapi-dev make all now your tool will be compiled in: ~/buildsdk/sdk/cli/buildresults/Linux_x86_64/x86_64_linux_gnu_gcc_10/flirc_util/debug/ And it is called flirc_util (latest version from git) d. Capture IR command signal Open the traditional Flic setup and control tool, my tool which was installed in step (a) is Flirc v3.25.3 it says connected as my flirc is inserted in the computer, if you cannot find it refer to installation again in step (a). open the app, goto File, drop down: click device log, click on the checkmark (x) Enable IR debugging. This will record all IR signals being sent to the flirc you will need this to create your IR commands. So Example: Mon. Feb. 8 2021 01:51:26 Flirc GUI Version v3.25.3 Operating System: Linux *** Device Disconnected *** *** Device Connected *** So lets say I want to record the power off, power on button for my heater; When I press power on/off button while pointed towards the flirc the waveform command is, captured and immediately shows up in the debugging window as: 0,9073,4414,618,1595,622,470,618,469,649,443,618,470,622,465,623,469,622,466,622,470,617,1596,622,1595,622,1595,618,1595,622,1595,622,1595,622,1594,618,1599,618,1594,622,470,618,1595,626,465,622,466,622,469,618,470,622,470,617,470,621,1595,618,469,622,1595,621,1595,622,1591,622,1595,622 Now you have successfully captured the IR signal. e. Send IR command signal in step C, you created the flirc_util from git so, Point the USB flirc at whatever device you want to control in my case heater now from command prompt goto ~/buildsdk/sdk/cli/buildresults/Linux_x86_64/x86_64_linux_gnu_gcc_10/flirc_util/debug/ and run this command: flirc_util sendir 0,9073,4414,618,1595,622,470,618,469,649,443,618,470,622,465,623,469,622,466,622,470,617,1596,622,1595,622,1595,618,1595,622,1595,622,1595,622,1594,618,1599,618,1594,622,470,618,1595,626,465,622,466,622,469,618,470,622,470,617,470,621,1595,618,469,622,1595,621,1595,622,1591,622,1595,622 Now in my case the heater if turned on turns off, and if the heater is off turns on, You have successfully transmitted the IR signal by the computer. Main use cases would be remote ( ie not even home) control of appliances and some robotics applications. Where you can remote into your computer from away and run scripts to control things, I guess use your imagination. Good luck
  16. No worries, it is a minor complaint compared to a bug! No rush to this below question: I don't see any explanation why 3.26.0 is now broken with fully up to date Win 11 22H2. Testing 3.26.0 using the command line repeatedly verified this on several machines. These machines were minimal-ist machines (Minisforums N40 mostly). No easily accessible method to raise the priority of the command line to see if that would improve. Is there a flirc_util command line switch for verbose that might offer a better error enumeration than >> [E] util/flirc_util/src/cmds/ir_transmit.c sendir(96): Error: invalid length, must be even
  17. I found a way to do sort of do this in case you are comfortable using the CLI. (I'm also surprised this is not a native feature!) First, go to Flirc GUI and there go to File > Device Log. Turn on the Enable IR debugging checkbox and press a key on your remote against the Flirc receiver. There will be a number of new lines. Ignore the ones starting with a colon and look for a line with a long sequence of numbers separated by commas. Note that this line will most likely be wrapped around into multiple lines and it usually (maybe always?) starts with a zero - the zero is the first number of that sequence but the line will likely break right after it. Cope the whole sequence into your keyboard. Next up, find where the Flirc CLI is on your system, on macOS it is in /Applications/Flirc.app/Contents/Resources. Use your terminal to enter this directory and in it, run this command substituting your actual pattern from the Flirc GUI: ./flirc_util sendir --pattern="0,…" This will replay the recorded sequence using the IR transmitter in Flirc. I was able to verify this works by using a remote-controlled LED strip and recording one of the color buttons and then changing the color to something else with the remote and replaying the original color IR sequence using Flirc CLI and the LED strip consistently switched back to the recorded color. Hope this helps anyone! And also hope Flirc will kick the support up a notch, it almost seems like the product is abandoned :/ Which is a shame, because it is genuinely great.
  18. I have a Flirc V2 running on a raspberry pi headless. Using the device log when I press the increase temperature button I get this (I just press the button one time but get what looks like to me to be two outputs): :e:0 371,454,375,454,372,453,372,453,372,423,406,424,405,424,406,484,354,454,375,454,371,454,376,454,371,454,1226,484,353,454,1226,454,371,458,371,454 :e:0 376,454,371,449,380,458,371,429,396,453,372,453,371,450,384,454,371,454,375,454,371,454,371,454,371,424,1264,454,371,454,1230,450,379,454,376,423 I am now trying to use the sendir command like this: flirc_util sendir --pattern="371,454,375,454,372,453,372,453,372,423,406,424,405,424,406,484,354,454,375,454,371,454,376,454,371,454,1226,484,353,454,1226,454,371,458,371,454" --repeat=1 --ik=40000 and I get this error: [E] util/flirc_util/src/cmds/ir_transmit.c sendir(101): Error: buffer should lead with zero But if I add a zero at the beginning like this, I get a different error: flirc_util sendir --pattern="0,371,454,375,454,372,453,372,453,372,423,406,424,405,424,406,484,354,454,375,454,371,454,376,454,371,454,1226,484,353,454,1226,454,371,458,371,454" --repeat=1 --ik=40000 [E] util/flirc_util/src/cmds/ir_transmit.c sendir(96): Error: invalid length, must be even I also tried recording the on/off button with similar results. I noticed the codes are always a little bit different everytime. Do you have any suggestions? Is controlling a minisplit something the Flirc can do? Thanks for the help!
  19. hi thanx i knew of sendir but it still didnt send via that theres a few posts that might help you if you can actually send from flirc app i cant never mind trying cmd but heres some links for you http://forum.flirc.tv/index.php?/search/&q=SendIR command &search_and_or=or&sortby=relevancy theres 4 diff links there only 3 did as posts
  20. Hello! I am about to use the SDK for that purpose. If the CWD could do it, it would be just wonderful - but my research so far suggests: No, only possible by calling API-function: fl_transmit_raw() I hope I am wrong and somebody knows a trick how to send using CMD. Thanks! UPDATE: Just found that a recent version of the CMD-tool does have some (slow?!) sending-command: flirc_util.exe help sendir But this is new (great) info for me and I need to test. I think slow does not matter in my case. So that would be great if it worked. Somebody knows more?!
  21. Need Help When I try to use the flric_util.exe on any option I get corrupted data. here is an example: c:\Program Files (x86)\Flirc>flirc_util.exe record escape Press any button on the remote to link it with 'escape' [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' Error, button exists I can program keys from GUI and have use the sendir command all works. here is a dump using kodi config c:\Program Files (x86)\Flirc>flirc_util.exe Version: flirc_util.release.v3.25.3-16-g28e8a01+ [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: The parameter is incorrect. [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout [E] lib/libtransport/hid.c hid_recv_packet(167): hid_recv_packet: wrong report id [E] lib/libtransport/hid.c hid_recv_packet(168): hidapi: The parameter is incorrect. [E] lib/libtransport/transport.c _recv_packet(126): _recv_packet: recv packet error = -1 [E] lib/libtransport/transport.c _dev_send_cmd(201): recv timeout FW Version: v4.9.3 SKU: Flirc 2.0 [dori] Branch: master Config: release Hash: 0xCB185BDE
  22. Trying to figure out how to use the flirc to send IR commands is pretty daunting. For starters, the blog post won't load: http://blog.flirc.tv/index.php/2017/08/06/sdk-release-linux-rpi-ir-transmit-support/ I've tried to cobble together various ways to do it, but I have seen three different flirc_util commands mentioned that don't work, finally finding the one that currently works with software version 3.25.3, which is the "sendir" command. My use case I would think is common, I want to use a remote to control a device the remote doesn't support, so I want Flirc to receive one command and transmit another. I'll program my remote to control some arbitrary device it supports, then have the Flirc send a different command that controls my actual device. In my case it's my LG TV remote that I want to use to control the volume on an amplifier, but the LG remote doesn't support it nor does it have a learning function to control arbitrary devices. To get started on a proof of concept, I can use the GUI device log to capture the IR sequence I want to transmit. I press a button on my remote and the device log will show something like: :e:17031 0,9008,4393,614,475,615,470,615,470,615,1584,615,474,615,470,615,470,615,1584,619,1584,614,1584,619,1584,614,470,615,1588,614,1584,614,1589,614,479,605,470,615,1584,618,1584,615,470,614,474,615,480,605,1583,615,474,616,1583,617,472,610,474,615,1584,614,1588,625,1573,615,474,615,1584,615 :e:40 0,9007,2157,614 The long string there is the IR code I guess (I really don't know what I'm doing here). I can then transmit this code by doing something like: flirc_util.exe sendir --ik=23000 --repeat=3 --pattern="0,9003,4390,619,470,614,470,614,470,614,1588,614,470,614,474,614,470,614,1588,614,1582,614,1588,614,1587,614,470,614,1588,614,1583,614,1587,615,469,615,474,610,1587,615,1587,615,469,615,470,614,474,615,1583,614,474,614,1583,614,474,610,474,614,1584,614,1587,615,1587,614,470,614,1583,618" This is enough for me to write a simple script that can be triggered with a keyboard press, but I suspect it will be slow and I'll need to dust off my ancient or now non-existent C skills and see what I can do. What would be end game for me is if I could flash the flirc with my own custom firmware and then connect the flirc to power and use it standalone without any PC. Is something like this possible? Assuming it's not possible, I have a Raspberry Pi Zero W on the way to control the flirc instead. I'll report back when I've got my setup in production, but hopefully the above will save someone some time.
  23. I have been using Flirc for my application for almost 2 yrs now, and I have have no issues with both Flirc devices to receiving commands from my remote controls. I wanted to try sending an IR command and the device doesn't seem to send anything. I have 2 Flirc devices with the latest release (Firmware Version: v4.9.3, SKU: Flirc 2.0 [dori]). (BTW, I am working on Windows 10) When I execute the command line: flirc_util.exe sendir --pattern="0,1,2,3,4,5" --repeat=3 (the content of the pattern is irrelevant) Output is : "Transmitting IR Pattern...Done!" The GUI log states: *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde <3>ir_transmit_set(140): error, ik delay: 0 < 13000. Defaulting to 40000 The outcome is the same whether I have "enable IR Debugging" set or not. Since I have 2 Flirc devices, I connected them to 2 different computers and positions the flirc devices within inches of one another. I started the Flirc GUI on the second machine, and the log view never displays anything when the above command line is executed from the first computer (regardless of whether "enable IR Debugging" is set or not.) When I point any remote control directly at either Flirc devices, then there is an output generated in the log (when "enable IR Debugging" is set). Therefore, I seems that my devices are clearly able to receive input, but don't appear to be transmitting. Is there suppose to be any visual indicator when a Flirc is transmitting? Is there any other permission or setting I need to set? Perhaps, the version of the devices that I have don't support IR send? Any advice? Thank you
  24. Sure, no problem. First of all, just for future reference, the FLIRC command-line utility has built-in reference for all commands it supports. To view a list of all supported commands, use the "help" command: flirc_util.exe help Please note that I am on Windows, hence the ".exe" part. You may not need it if you are on macOS or Linux. To view reference for a specific command, use the same "help" command, but after it specify the command you need reference for, like this (without the <> brackets): flirc_util.exe help <command> So, when you run: flirc_util.exe help sendir here's what you get: Help for 'sendir' command: usage: sendir <opts> sendir --pattern=0,153,1231,131 --repeat=3 --ik=32000 OPTIONS: -i, --ik set the interkey delay between rep. frames -r, --repeat number of times to repeat pattern -k, --kill kill any currently running transmission -p, --pattern send the comma delimited pattern Which means the correct way of sending out your code, provided that you only need to repeat it once, would be as follows: flirc_util.exe sendir --pattern=0,8978,4384,608,469,608,1592,608,469,608,464,613,1592,608,469,608,464,612,478,608,469,608,464,612,1589,612,465,612,1592,608,1593,612,464,613,473,612,1588,612,465,612,464,612,465,612,465,612,464,608,465,612,477,613,464,608,1592,612,1588,612,1588,612,1588,612,1589,612,1592,612,1592,612 --repeat=1
  25. I am wondering the same. Would have been nice to share your solution once you figured. I am always getting "Error: must specify an option" when I am trying to send the ir signal using e.g. based on the above log file the following command: flirc_util sendir 0,8978,4384,608,469,608,1592,608,469,608,464,613,1592,608,469,608,464,612,478,608,469,608,464,612,1589,612,465,612,1592,608,1593,612,464,613,473,612,1588,612,465,612,464,612,465,612,465,612,464,608,465,612,477,613,464,608,1592,612,1588,612,1588,612,1588,612,1589,612,1592,612,1592,612 What am I doing wrong?
×
×
  • Create New...