Jump to content
Flirc Forums

All Activity

This stream auto-updates     

  1. Yesterday
  2. Also getting the same on linux/macos
  3. I have a bose V30 and I'm trying to use the send_ir_raw function to send a request. I used the app and captured the following "Volume down presses": :e:2989 0,9075,4412,610,484,589,1613,614,484,610,1592,610,1570,636,1591,610,485,610,1591,614,1566,643,1584,614,459,636,1566,635,464,635,459,636,1591,610,459,636,485,614,1592,609,459,636,459,635,464,635,459,662,433,636,484,614,1566,635,459,636,1591,614,1566,635,1566,635,1570,636,1566,635,1566,614 :e:1111 0,9072,4386,635,459,636,1570,609,485,635,1566,636,1566,635,1570,636,459,635,1566,610,1596,635,1566,635,459,662,1540,640,459,635,459,635,1566,635,459,640,459,635,1566,636,459,635,459,640,459,635,459,636,459,635,459,640,1566,636,458,636,1570,635,1566,635,1566,636,1566,640,1565,636,1565,636 :e:890 0,9074,4412,610,485,609,1596,610,485,610,1591,640,1540,636,1566,635,485,610,1591,615,1565,636,1591,614,459,636,1566,635,459,636,463,610,1591,635,459,636,463,635,1566,662,433,635,459,655,440,614,485,635,460,635,459,636,1591,614,459,636,1566,636,1565,640,1566,635,1566,635,1566,640,1561,640 :e:2460 0,9075,4386,635,459,635,1566,639,459,635,1566,635,1566,640,1566,635,471,623,1566,640,1561,666,1540,636,459,635,1566,640,459,635,460,635,1566,640,455,665,434,635,1566,640,455,665,429,665,434,635,459,640,455,639,455,640,1566,635,459,654,1547,640,1565,636,1565,640,1566,635,1566,640,1561,614 :e:911 0,9075,4384,635,459,635,1576,629,459,635,1565,640,1564,636,1564,640,471,623,1565,635,1565,640,1565,635,459,635,1565,640,459,635,458,636,1565,639,459,635,459,635,1566,639,459,636,458,636,459,639,455,640,458,636,459,609,1592,639,459,635,1566,635,1565,640,1565,635,1565,636,1565,639,1565,640 :e:1149 0,9069,4386,640,459,635,1592,609,459,614,1591,636,1565,636,1576,629,459,636,1565,636,1566,635,1570,636,458,636,1565,610,485,640,459,635,1566,635,459,635,459,636,1570,635,459,635,459,636,459,635,459,640,459,635,459,635,1566,646,448,665,1540,636,1566,635,1569,636,1565,636,1565,640,1566,636 I have tried to replay these using flirc_util however the volume doest change, am I missing something?
  4. Last week
  5. I'm also convinced it's a firmware issue as I use the FLIRCs with linux computers without any particular drivers. You're probably referring to Windows computers but I will give you my OS version just in case :) It's xubuntu 18.04 with kernel 4.15.0-48-generic in all cases. These are all USB2 ports (black). Here is what I get from another computer with a FLIRC that was not firmware upgraded, when I reboot (relevant to the FLIRC): > lsusb Bus 005 Device 002: ID 20a0:0006 Clay Logic > dmesg [ 2.192076] usb 5-2: new full-speed USB device number 2 using uhci_hcd [ 2.398139] usb 5-2: New USB device found, idVendor=20a0, idProduct=0006 [ 2.398145] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.398148] usb 5-2: Product: flirc [ 2.398151] usb 5-2: Manufacturer: flirc.tv [ 2.437998] usbcore: registered new interface driver usbhid [ 2.438001] usbhid: USB HID core driver [ 2.448105] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.3-2/input0 [ 2.449274] input: flirc.tv flirc as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/0003:20A0:0006.0002/input/input5 [ 2.508426] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1d.3-2/input1 Here is what I get from the computer with the upgraded FLIRC when I reboot: > lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub (nothing connected to any USB port, and there is nothing else than the FLIRC connected) > dmesg [ 2.664308] usb 2-6: new full-speed USB device number 2 using ohci-pci [ 2.745144] ACPI Warning: SystemIO range 0x0000000000004D00-0x0000000000004D3F conflicts with OpRegion 0x0000000000004D00-0x0000000000004D04 (\IP2) (20170831/utaddress-247) [ 2.745168] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 2.745177] ACPI Warning: SystemIO range 0x0000000000004E00-0x0000000000004E3F conflicts with OpRegion 0x0000000000004E00-0x0000000000004E3F (\_SB.PCI0.SM00) (20170831/utaddress-247) [ 2.745194] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver ... [ 7.900173] usb 2-6: device descriptor read/all, error -110 [ 8.088072] usb 2-6: new full-speed USB device number 3 using ohci-pci [ 23.704066] usb 2-6: device descriptor read/64, error -110 [ 39.320058] usb 2-6: device descriptor read/64, error -110 [ 39.428080] usb usb2-port6: attempt power cycle [ 39.932058] usb 2-6: new full-speed USB device number 4 using ohci-pci [ 50.604058] usb 2-6: device not accepting address 4, error -110 [ 50.792058] usb 2-6: new full-speed USB device number 5 using ohci-pci [ 61.612059] usb 2-6: device not accepting address 5, error -110 [ 61.612096] usb usb2-port6: unable to enumerate USB device Now, when I unplug and replug the FLIRC while the computer is powered on: > lsusb Bus 002 Device 006: ID 20a0:0006 Clay Logic > dmesg [ 743.920674] usb 2-6: new full-speed USB device number 6 using ohci-pci [ 744.162676] usb 2-6: New USB device found, idVendor=20a0, idProduct=0006 [ 744.162683] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 744.162687] usb 2-6: Product: flirc [ 744.162690] usb 2-6: Manufacturer: flirc.tv [ 744.348840] hidraw: raw HID events driver (C) Jiri Kosina [ 744.409404] usbcore: registered new interface driver usbhid [ 744.409411] usbhid: USB HID core driver [ 744.508490] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:04.0-6/input0 [ 744.516430] input: flirc.tv flirc as /devices/pci0000:00/0000:00:04.0/usb2/2-6/2-6:1.1/0003:20A0:0006.0002/input/input7 [ 744.573280] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:04.0-6/input1 [ 744.574269] hid-generic 0003:20A0:0006.0003: hiddev1,hidraw2: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:04.0-6/input2 I think this should give you a few good hints as to what is happening here. :-) Cheers, Daniel
  6. I'm positive it's a firmware issue, but I can't for the life of me reproduce this. Can you guys post your OS version, your hardware version, whether it's USB 2.0 or 3.0 ports? Any other information. A picture of device manager when it boots into this 'bad state'. Etc. Here is the latest firmware, upload the correct sku for your hardware. Once I see the problem, I'll have a fix pushed in seconds, but there is no reason for you guys to keep waiting anymore. I'm really sorry. nemo.release.bin dori.release.bin
  7. I've seen a couple minor patches to the driver in the last few weeks but that has not worked. When this started, it was after a firmware and driver upgrade. Could be a firmware issue.
  8. Hello, I'm having issues with my FLIRC Gen 1. I'm setting up my keys with Full Keyboard presets and a remote and testing with my Raspberry Pi with LibreELEC and everything works fine... for some minutes. After like 3 minutes my FLIRC not only stops aswering the keys, but also "forgets" all the keys that i mapped and i have to map everything again. Whenever i map, i straight test with my Macbook Pro and the keys are working just fine, then i put it in my Raspberry Pi and after some minutoes it stops working, and when i plug it again in my Macbook Pro, the keys also doesn't work on the mac anymore. Is there anything that could be causing my FLIRC to just forget the keys i'm mapping? I tested both with and withoud an extension cable. Anyone can point me to whatever may be happening here? I need to know if my FLIRC is damaged somehow or i'm doing something wrong. I'm on the latest firmware available (3.9.0) and latest GUI for MacOS.
  9. @jason, I would like to ask for the previous firmware so that I can recover that failing FLIRC until you guys figure it out. It's been over a month since this issue was first identified. Having to unplug and replug the FLIRC every time the computer is booted or rebooted is getting tiresome. Thanks, Daniel Born
  10. Earlier
  11. i think it can be done, i dont use flirc to start my pc but i use an app with wake on lan package and it works just fine. also i can turn on my pc with my alexa, so working around a solution for using flirc wont be hard. you can always use a smartplug that uses RF signal and turn on the PC
  12. Only the Flirc SE (SE = Streacom Edition) can do cold booting, because you can only do cold booting by sending a signal to the power button header on your motherboard, the header for which only the Flirc SE has got a connector for. Also your motherboard has to support keeping an internal USB header powered, because the Flirc SE needs to be connected to one, and the Flirc SE needs to remain powered to work as it hasn't got a battery.
  13. Is there any v2 version of the Flirc SE planned? I'm very intrigued about: LONG KEY PRESSES Assign two functions to one button. Press the button for one function, hold down the button for the other function. Now possible with our new powerful arm processor. MACROS Want to run a number of commands on a key press? With the new flirc, you can store over 500 keys, and have more than one keypress per individual remote button. P.S. if there will be one released: please make the PCB black so that it can match the rest of my systems' internals. :)
  14. I just bought the Flirc and am trying to use flirc_util.exe send_ir_raw and it does not seem to be transmitting. Flirc can receive my TV remote key presses and the mapping is working perfectly, but when I try to transmit the codes back nothing happens. My phone camera can see the TV remote flash but not the Flirc. I also have a Pi set up with an IR receiver and transmitter. The Pi can see my TV remote transmit but not the Flirc transmission even if the devices are pointed directly at each other a few inches away. The software I am running is 3.22.4 and the firmware is 4.6.3. I am on Windows 10. I'm not sure if it matters if I have the GUI open or not while I do this so I tried it both ways. I'm getting errors in the debug in the GUI. The command I am running is flirc_util.exe send_ir_raw 0,9012,4424,592,491,588,491,592,1607,588,491,592,486,592,491,587,491,592,487,592,1607,588,1608,591,491,588,1607,592,1607,592,1602,592,1607,592,1607,591,487,591,1608,587,491,592,490,588,491,587,491,592,486,592,490,588,1607,592,491,587,1607,592,1607,592,1603,592,1607,592,1607,592,1602,592 Errors in the GUI: Wed May 8 2019 21:42:21 Flirc GUI Version v3.22.4 Operating System: Windows *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.6.3 SKU: Flirc 2.0 [dori] Git Hash: 0x93a109d3 <3>ir_transmit_push(131): invalid timer value: 0 <3>ir_transmit_push(131): invalid timer value: 0 Errors on the command line (these errors aren't there when the GUI is closed): [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(208): recv timeout [E] lib/libflirc/firmware/fw_4.2.c _fl_transmit_raw(69): error sending data, ceck device log [E] util/flirc_util/src/ir_transmit.c send_ir_raw(85): error sending IR pattern Is there something I am doing wrong? Is there something different I should try? Thank you
  15. I'd love it if the Flirc UI software remembered which controller I used last, or if it would let me choose which controller to see when the app opens. I use Flirc extensively, and I always use the full keyboard controller, so I'd like the Flirc UI app to open with that controller instead of the minimalist one I never use. P.S. I LOVE FLIRC! I've been using the v1 dongle for five years and just bought a v2 in order to upgrade my setup a bit. Flirc is fantastic!
  16. Does anyone read these forums? I've tried posting here, messaging the admins, emailing Flirc, and even calling but I have received zero response.
  17. Has said before In windows 7 it doesnt recognize flirc on gui or computer devices when reboot, we have to replug, downgrading firmware is a no no for me, i need the toogle flirc on/off setting. Its strange that you cant reproduce this problem yourself.
  18. I agree. An option to back-out of the latest and greatest would definitely help both the customer and yourself in these situations. Thanks, Todd
  19. Jason, if there's anything I can do to help (run special firmware version with debugging code, sending you logs from my computer, etc.) please let me know. I'd have several computers to try it on with either linux or Win7 or Win10. Yes, as a last resort, going back to a previous firmware would be a way out but it would mean we couldn't upgrade firmwares ever again? It might be a good idea to have on your side a repository of previous firmware versions with a tool to specifically reflash a FLIRC to any previous version. It would certainly help take the pressure off of you guys when a problem arises due to a new firmware release. :) Cheers, Daniel
  20. Thanks for the extra info. I haven't been able to reproduce this yet with multiple flircs and pc's and usb ports. I must be missing something. Not to worry, I can always give you guys the old firmware, but let me continue looking, I'm sure I'll find it shortly. Today wasn't the best from a time perspective, I was split amongst a few things, but this is considered red hot urgent.
  21. Hi Jason, The SKU is posted below. The problem seems to be the OS does not recognize the USB device on boot up. It sees something but unable to recognize it. As I mentioned above, I have to un-pulg and re-plug it back in for the OS to recognize it. This happened after the latest round of software/firmware updates. Worked fine before then. Thanks, Todd.
  22. In my case, I program the FLIRC from a Win7 laptop so I plug it in while the PC is already up and running so that works fine. Once I plug it in my linux PC, when I power it up while the FLIRC is already plugged in (such as after a reboot), it is not seen at all, as evidenced by the total absence of the device in the dmesg log and even after, when using the lsusb command, it's exactly like the FLIRC was not plugged in. If I pull it out then and plug it back in, then it is recognized normally and works just fine. When I suspend the computer (which I do most of the time), it recovers nicely from that state. I could try powering up the laptop with the FLIRC already plugged in to see what happens, I haven't tried that yet. Thanks, Daniel, **Update: ok, I tried plugging into Win7 laptop first and then powering up and going into GUI. It was recognized. I also tried plugging the FLIRC back into the linux computer while it was in sleep, and it was not recognized after waking up the computer. That test may not be relevant but I still tried it out of curiosity.
  23. In this state, does the GUI detect flirc and no buttons work? Or the GUI doesn't recognize it?
  24. Hi Jason, Mine says SKU: FLIRC 2.0 [dori] Firmware is V4.6.3 Thanks, Daniel
  25. If you go into file->advanced Can you tell me the sku you guys are using?
  26. I was not seeing these posts, I will see if I can figure this out immediately.
  1. Load more activity
×
×
  • Create New...