Jump to content
Flirc Forums

PeterC

Members
 View Profile  See their activity

  • Posts

    12

  • Joined

  • Last visited

 Content Type 

Posts posted by PeterC

  2. Need to press every button twice

    in General Questions

    Posted

    Hello!

    I use Flirc v2 together with a Logitech Harmony One+ on Debian Buster (10.4) and MythTV.

    On the Flirc I have selected a full keyboard layout.

    The problem is that I need to press every remote button twice for the command to work.

    Before I bought a Flirc I used ir-keytable and did not experience this problem.

    Any help or suggestion would be appreciated.

    Best regards,
    Peter

  3. Bought a Flirc Gen 2 and it behaves very strange

    in Firmware Bugs

    Posted

    The remote control is a Logitech Harmony One+.

    The problem is that the setup is very unreliable and I don't know if it is the Flirc, the remote control, Debian Buster or a combination.

    The remote control has worked without problem for several years together with Debian. But when Debian was upgraded from Stretch to Buster the drivers for my IR receiver stopped working. I then bought a Flirc.

    The problems are several:

    1. It sometimes output errors when using flirc_util as I have posted above.
    2. It sometimes deletes the recorded keys and I have to do the configuration again.
    3. It almost always don't respond to the first press on the remote control. It needs a second press on the same button. I noticed that last time the recorded keys were deleted I have managed to record multiple entries for the enter key. But even before that I had to press twice for the remote command to be recognized by the computer.

  5. Bought a Flirc Gen 2 and it behaves very strange

    in Firmware Bugs

    Posted

    Today when the PC started I got no response whatsoever from any commands from the remote control and when I tried with flirc_util I got:

    flirc_util unit_test
    Flirc Okay
    htpc:~# flirc_util settings
    3.25.3
    FW Version: v4.9.3
       SKU:     Flirc 2.0 [dori]
       Branch:  master
       Config:  release
       Hash:    0xCB185BDE

    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
    -----  --------   ---  --  ------------

    Now the list of recorded keys was empty again.

  6. Bought a Flirc Gen 2 and it behaves very strange

    in Firmware Bugs

    Posted · Edited by PeterC

    I was trying to start logging to file by following the example of creating a configuration file (/usr/bin/flirc.ini) and start the GUI but I can not find the log file. Is it supposed to be stored in /usr/bin/ if I don't enter any path in the ini-file?

    Using for example 'flirc_util unit_test' it still spit out  errors but it kind of work although it still need two key presses for every command. And thats why I wanted the log file.

    [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
    [E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(132): error recording test0
    Flirc Not Okay
    [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'

    I also noticed that just after I executed the 'flirc_util unit_test' command the computer stopped responding to any commands from the remote control.

    Best regards,
    Peter Carlsson

  8. Bought a Flirc Gen 2 and it behaves very strange

    in Firmware Bugs

    Posted

    Thanks for your quick response!

    It is directly on the PC and I have tried different ports. Both USB 2.0 and 3.0. I need to have a 0.5m cable since the ports are at the back of the PC. The Flirc and the remote has clear sight and the distance is approximately 3m.

    The double record was no issue before I bought the Flirc when I used ir-keytable but it had other issues.

  9. Bought a Flirc Gen 2 and it behaves very strange

    in Firmware Bugs

    Posted

    Hello again!

    Just after I posted the last reply, Debian released an update to Buster (10.3) so here is the output again:

    uname -a
    Linux htpc 4.19.0-8-686-pae #1 SMP Debian 4.19.98-1 (2020-01-26) i686 GNU/Linux

    flirc_util settings
    3.25.3
    FW Version: v4.9.3
    [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state'
    [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
       SKU:     Flirc 2.0 [dori]
    [E] lib/libtransport/hid.c hid_recv_packet(161): Wrong response length = 33
    [E] lib/libtransport/hid.c hid_recv_packet(162): hidapi: (null)
    [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: (null)
    [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
       Hash:    0xCB185BDE

    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  CB4837F1   130  01  d
        1  CF32DFB0   130  01  i
        2  42E4A325   116  01  escape
        3  67EC17FD   130  01  m
        4  B64D7ABD   116  01  return
        5  BE6018B0   130  01  up
        6  361F4CE4   130  01  left
        7  BE6017C9   130  01  down
        8  3B263EB1   130  01  right
        9  E79BD7A4   130  01  u
       10  4B7A5A31   130  01  j
       11  411EB1E4   130  01  p

    I recorded my remote once again after the first disappeared. However, I notice that almost every button I press I need  to press twice for the computer to react. So I would definitely say that something is wrong, either with the Flirc, the computer or a combination. I would be happy to provide more information if that helps to solve my problem.

    By the way, I read in the documentation that there should be some predefined settings for Logitech remotes. The one I have is a Harmony One+ but I could not find it in the menu. So that is why I use the full size keyboard layout for recording.

    Best regards,
    Peter Carlsson

  10. Bought a Flirc Gen 2 and it behaves very strange

    in Firmware Bugs

    Posted

    This time when booting the computer I got this:

    flirc_util unit_test
    Flirc Okay

    flirc_util settings
    3.25.3
    FW Version: v4.9.3
       SKU:     Flirc 2.0 [dori]
       Branch:  master
       Config:  release
       Hash:    0xCB185BDE

    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
    -----  --------   ---  --  ------------

    But the recorded keys are missing.

  12. Bought a Flirc Gen 2 and it behaves very strange

    in Firmware Bugs

    Posted

    Hello!

    I just recently bought a Flirc Gen 2 and it behaves very strange.

    Almost every time I boot my computer (Debian Buster) the Flirc device is not recognized and I see this in journalctl:

    kernel: usb 3-2: device descriptor read/64, error -110
    kernel: usb 3-2: device descriptor read/64, error -110
    kernel: usb usb3-port2: attempt power cycle
    kernel: usb 3-2: new full-speed USB device number 4 using uhci_hcd
    kernel: usb 3-2: device not accepting address 4, error -110
    kernel: usb 3-2: new full-speed USB device number 5 using uhci_hcd
    systemd-udevd[307]: usb3: Worker [311] processing SEQNUM=1761 is taking a long time
    kernel: usb 3-2: device not accepting address 5, error -110
    kernel: usb usb3-port2: unable to enumerate USB device

    If I unplug and then plug the Flirc back again it will be recognized.

    And when I run 'flirc_util settings' I get:
    3.25.3
    FW Version: v4.9.3
    [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state'
    [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
       SKU:     Flirc 2.0 [dori]
    [E] lib/libtransport/hid.c hid_recv_packet(161): Wrong response length = 33
    [E] lib/libtransport/hid.c hid_recv_packet(162): hidapi: (null)
    [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: (null)
    [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
       Hash:    0xCB185BDE

    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  880AE241   130  01  0
     

    And for 'flirc_util unit_test' I get:
    [E] lib/libtransport/hid.c hid_recv_packet(161): Wrong response length = 33
    [E] lib/libtransport/hid.c hid_recv_packet(162): hidapi: (null)
    [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/libflirc/firmware/fw_4.7.c _fl_transmit_raw(83): error sending data, ceck device log
    [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: (null)
    [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/libflirc/firmware/fw_4.2.c _fl_unit_test(132): error recording test0
    Flirc Not Okay

    Any help would be extremely appreciated!

    Best regards,
    Peter Carlsson

×
×
  • Create New...