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?