Jump to content
Flirc Forums

Search the Community

Showing results for tags 'raspberry'.

  • 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 6 results

  1. Hey there. I have a Flirc (metal one) and i'm trying to do some automation. I'm trying do send IR signal to my TV box using the Flirc connected to a Raspberry. I have fallow this post http://blog.flirc.tv/index.php/2017/08/06/sdk-release-linux-rpi-ir-transmit-support/ But when i send the signal with send_ir_raw nothing happens. Heres the command output: ~ $ flirc_util send_ir_raw 0,482,204,200,203,205,675,231,236,141,230,204,203,179,229,200,204,249,158,174,230,205,509,231,369,179,535,236,666,231,203,205,675,231,203,174 [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(293): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: [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: 100 [D] lib/libtransport/hid.c list_devs(298): Interface: 0 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 384 [D] lib/libtransport/hid.c list_devs(300): Usage: 0 [D] lib/libtransport/hid.c list_devs(293): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: [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: 100 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 0 [D] lib/libtransport/hid.c list_devs(300): Usage: 0 [D] lib/libtransport/hid.c list_devs(306): --------------------------------------------------------- [V] lib/libtransport/hid.c hid_dev_open(330): 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(293): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: [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: 100 [D] lib/libtransport/hid.c list_devs(298): Interface: 0 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 0 [D] lib/libtransport/hid.c list_devs(300): Usage: 0 [D] lib/libtransport/hid.c list_devs(293): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: [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: 100 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 0 [D] lib/libtransport/hid.c list_devs(300): Usage: 0 [D] lib/libtransport/hid.c list_devs(306): --------------------------------------------------------- [D] lib/libtransport/hid.c hid_find(255): Device Used type: 20a0 0006 path: /dev/hidraw1 serial_number: [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: 100 [D] lib/libtransport/hid.c hid_find(259): Interface: 0 [D] lib/libtransport/hid.c hid_find(260): Usage Page: 0 [D] lib/libtransport/hid.c hid_find(261): Usage: 0 [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: flirc [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 30 74 03 .getversion..0t. 10: 00 e0 c6 d3 76 04 00 00 00 01 00 00 00 00 35 e9 ....v.........5. 20: 7e ~ [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 04 .getversion..... 10: 00 02 00 c5 74 00 d6 72 65 6c 65 61 73 65 00 00 ....t..release.. 20: 00 . [V] lib/libflirc/common/flirc_transport.c transport_new_get_version(40): Version: 4.4.2 0xD60074C5 [release] [D] lib/libflirc/flirc_driver.c determine_iface(113): fw_state: firmware [D] lib/libflirc/flirc_driver.c determine_iface(114): version: 4.4 [D] lib/libflirc/flirc_driver.c determine_iface(231): initializing fw ver4.4 [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(263): device found, state: 2 [V] lib/libcmds/cmds.c run_cmds(251): running command: send_ir_raw [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 69 72 74 72 61 6e 73 65 74 00 00 00 24 00 00 .irtranset...$.. 10: 00 05 00 00 00 00 00 00 00 ff ff ff ff 00 00 00 ................ 20: 00 . [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 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 e2 01 cc 00 c8 00 cb 00 cd 00 a3 02 e7 00 ................ 10: ec 00 8d 00 .... [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 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 e2 .irtransraw..... 10: 01 cc 00 c8 00 cb 00 cd 00 a3 02 e7 00 ec 00 8d ................ 20: 00 . [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 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: e6 00 cc 00 cb 00 b3 00 e5 00 c8 00 cc 00 f9 00 ................ 10: 9e 00 ae 00 .... [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 69 72 74 72 61 6e 73 72 61 77 00 00 e6 00 cc .irtransraw..... 10: 00 cb 00 b3 00 e5 00 c8 00 cc 00 f9 00 9e 00 ae ................ 20: 00 . [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 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: e6 00 cd 00 fd 01 e7 00 71 01 b3 00 17 02 ec 00 ........q....... 10: 9a 02 e7 00 .... [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 69 72 74 72 61 6e 73 72 61 77 00 00 e6 00 cd .irtransraw..... 10: 00 fd 01 e7 00 71 01 b3 00 17 02 ec 00 9a 02 e7 .....q.......... 20: 00 . [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 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: cb 00 cd 00 a3 02 e7 00 cb 00 ae 00 ............ [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 69 72 74 72 61 6e 73 72 61 77 00 00 cb 00 cd .irtransraw..... 10: 00 a3 02 e7 00 cb 00 ae 00 00 00 00 00 00 00 00 ................ 20: 00 . [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 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 . [D] lib/libflirc/flirc_driver.c fl_close_device(421): closing device [D] lib/libflirc/flirc_driver.c fl_close_device(432): freeing iface ~ $ Any help? Best regards.
  2. Is the FLIRC Raspberry PI case that's being sold on Amazon the old version or the updated PI 3 version? The user reviews make it sound like its the old version.
  3. Hi I was wondering if it is possible to use the Flirc IR remote dongle to shut down and power off a Raspberry Pi? Looking on the net I found a python programming to do it by connecting 2 GPIO pins and a push button switch. Ampulex
  4. I'm new at Flirc and am stumbling around a little. I've partially got the Flirc & Harmony One & Rasperry Pi3 working together to play a video through RasPlex on my Samsung TV. Eventually I'll be substituting my Epson projector through an a/v receiver for the TV, but for first steps I'm using this less involved setup. Using information I got from another query on this forum (though maybe only partially understood) I added a new LG TV - which I don't own - to my Harmony One. I then set up an activity including that device plus the existing Samsung TV to a new 'Watch Plex on TV' activity. I should note that there are 2 TVs in that single activity, which didn't bother the Harmony One setup though it looks a little odd. Then I turned to programming the Flirc through the Flirc GUI. First I started the activity, then I started mapping keys to the Flirc using the Kodi Controller (seemed like closest to Plex). This all went well until I hit a little stumbling block, namely the LG TV apparently doesn't have a Play or Stop button. Which makes sense, why should it? It's a TV right? Finished Flirc setup, plugged it into the RPi3, and started the activity again. All is well in that I can move around in Plex, but of course I don't have a way to Stop or Pause the video because those keys weren't mapped. With that long preamble, I finally come to these questions: Should I have picked some non-TV type of device? Like maybe a DVD player or something? Barring that, is there some way to easily add Stop or Pause to my current setup? Thanks, Mark M
  5. I'm considering various options for having both Plex Home Theater (via RasPlex) and Kodi available in the same room to the same output through an a/v receiver. One way is to mess around with dual booting a single Raspberry Pi3 with a Flirc. Another way is to have 2 Pi3s, each dedicated to a separate app. They would of course each have their own Flirc. I'd control them, like everything else, with a single Harmony One remote. Is this 2 Raspberry approach feasible? That is, is it possible to have 1 Flirc respond to a set of commands which will be ignored by the other Flirc? I think maybe yes, if I can somehow associate a separate set of commands for each Flirc. Like maybe I could program the Harmony to associate the commands from some old remote I don't use (or at least don't use in the room with the Flircs) with one Flirc, and another old remote with the other Flirc. Am I on the right path? Or maybe there's some way without having the old physical remotes? Thanks, Mark M
  6. Hi, I have the Firc Raspberry Pi case and I love it. I have a small suggestion if one day you make a new version, it would be to add a thermal pad connected to the case for the lan chip, as it produce some heat (and maybe the RG2?). Taken from a website. I can do the test, I have a thermal laser. Right now I put thermal pad + RAM heatsink that I have in spare, does the work, but would be nice to have it directly to the case :) Thanks for reading and thanks alot for the case, It is the best one I've seen so far :)
×
×
  • Create New...