Jump to content
Flirc Forums

Steve H


Steve H
 Share

Recommended Posts

Hi
I just bought a Flirc v2
I have successfully mapped an IR remote button to keyboard functions using the GUI app

This is the device log:
    Wed Aug 18 2021 16:34:58
    Flirc GUI Version v3.25.3-15-gc366d26+
    Operating System: Windows
    *** Device Disconnected *** 
    *** Device Connected *** 
    Firmware Version: v4.9.3
    SKU: Flirc 2.0 [dori]
    Git Hash: 0xcb185bde


I want to record some macros, but I'm getting errors with the flirc_util.exe

I did these steps:
Format the Flirc (to clear all settings)
Attempt to record a key "h", but I get an error before I had time to press any IR remote buttons
I then ran the "settings" command and got  what appears to be multiple errors

I need to know if my unit is faulty (so should be exchanged), or if  there is another problem (and solution).

My system is windows7
I have posted the CMD prompt info below - note the commands were issued one after the other

Cheers
Steve

C:\Program Files (x86)\Flirc>flirc_util.exe format
Formatting Device, please wait...  Done!

C:\Program Files (x86)\Flirc>flirc_util.exe record h
 Press any button on the remote to link it with 'h'

[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
Error, button exists

C:\Program Files (x86)\Flirc>
C:\Program Files (x86)\Flirc>flirc_util.exe settings
3.25.3-16-g28e8a01+
FW Version: v4.9.3
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
[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.0.c fl_ver4_header_peek(50): invalid address you idiot
   SKU:     Flirc 2.0 [dori]
[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/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'h_peek'
[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:    0x00000001

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
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
[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
not a valid image
  product sku:      NA
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'h_peek'
[E] lib/libflirc/firmware/fw_4.0.c get_config(101): command error
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_display_config(960): couldn't get config
  Records:          NA

Link to comment
Share on other sites

Hi Jason

I've tried it in a different USB port.  The list of errors from the settings command is shorter and the record command still did not work

I will attempt to try it on different computer tomorrow

Cheers

Steve

 

C:\Program Files (x86)\Flirc>flirc_util.exe format
Formatting Device, please wait...  Done!

C:\Program Files (x86)\Flirc>flirc_util.exe settings
3.25.3-16-g28e8a01+
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(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/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
-----  --------   ---  --  ------------

C:\Program Files (x86)\Flirc>flirc_util.exe record h
 Press any button on the remote to link it with 'h'

[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
Error, button exists

C:\Program Files (x86)\Flirc>

 

Link to comment
Share on other sites

  • 2 weeks later...
  • 6 months later...
  • 4 weeks later...

I'm having an identical problem. Interesting this is it "WAS" working fine. I'm at a lose to determine what has changed.  I've unistalled and reinstalled a couple of times and reloaded the flirc firmware. WIndows 10. The device disconnects and reconnects after every yril cmd.

:\Program Files (x86)\Flirc>flirc_util.exe settings
3.26.0
FW Version: v4.9.3
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion'
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
[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/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot
[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]
   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]

 

 

C:\Program Files (x86)\Flirc>flirc_util.exe unit_test
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state'
[E] lib/libflirc/firmware/fw_4.9.c fl_ver4_set_record_api(108): command error
[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
[E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(141): error recording
Flirc Not Okay
[E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state'

 

*** Device Connected ***

Firmware Version: v4.9.3

SKU: Flirc 2.0 [dori]

Git Hash: 0xcb185bde

*** Device Disconnected ***

*** Device Connected ***

Firmware Version: v4.9.3

SKU: Flirc 2.0 [dori]

Git Hash: 0xcb185bde

*** Device Disconnected ***

*** Device Connected ***

Firmware Version: v4.9.3

SKU: Flirc 2.0 [dori]

Git Hash: 0xcb185bde

<3>report_callback(227): pkt recv err

<3>report_callback(227): pkt recv err

 

Link to comment
Share on other sites

It was on both. I've connected it directly to a USB port on the PC. Still no joy. Very flakey . My application is a web accessible remote remote. I've got a little web page with a pile o' buttons that wrappers flirc_util in shell mode to "sendir" commands to control my cable box.

Here's an interesting observation, manually running the send_ir commands it turns out it works much better if the GUI isn't running, See below.

########## GUI not running #####################

<5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518
Transmitting IR Pattern...Done!
<5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518
Transmitting IR Pattern...Done!
<5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518
Transmitting IR Pattern...Done!

############ Turned on GUI #################


<5,521,2160,516,2165,520,2160,516,2165,520,4408,525,2155,520,4408,524,2157,518
Transmitting IR Pattern...[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] util/flirc_util/src/cmds/ir_transmit.c sendir(112): Error: could not transmit data
Done!
flirc_sudo.exe $

I'll try to do some more debugging. In the meantime can you tell me how to find the Flirc device in Device Manager so I can verify the proper driver is being used?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...