1
USB Infrared Toy / Re: Panasonic Remote not being interpreted.
I ran into the same issue. With irrecord I had to use --force and after that run irrecord again with --analyse to clean up the new config file.
Let me know if this helps.
Messages
This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.
Messages - Forage
I ran into the same issue. With irrecord I had to use --force and after that run irrecord again with --analyse to clean up the new config file.
Let me know if this helps.
2
USB Infrared Toy / Re: Cant Record Signal From Remote
Nowadays it does yes. Not all platforms have updated to 0.9.2 yet though.
3
USB Infrared Toy / Re: Cant Record Signal From Remote
Recording and simulating an RC6 remote worked for me. With irrecord I had to use --force though and after that run irrecord again with --analyse to clean up the new config file. I never played around with waking up PC's with it.
Both are a different topic though, so please start a new topic (one for recording and one for the waking up) with more details in a new thread if you need any more help.
4
USB Infrared Toy / Re: Linux Lirc (usb_irtoy driver) device stops responding
The command line I used was
./lircd --driver irtoy --nodaemon --listen --device=/dev/ttyACM0 --loglevel=10[/quote]
Playing with the latest lirc sources brings me back to the initial problem. Only a few attempts work, after that the toy is gone.
The lirc debug output gives me the following on the first failing attempt:
Code: [Select]
lircd: Debug registering local clientJudged by the number of issues reported in the forum and the different work-arounds provided (increase process priority, using a USB reset tool, etc.) I personally think it all comes down to either a hardware design flawed or unstable USB firmware. Too bad both don't get any attention any more.
lircd: Notice accepted new client on /run/lirc/lircd
lircd: Debug irtoy_getversion: Got version V222
lircd: Debug irtoy_reset: Got protocol S01
lircd: Debug Version hw 2, sw 22, protocol 1
lircd: Info irtoy_found on /dev/ttyACM1
lircd: Debug received command: "SEND_ONCE ENTONE_URC-4021ABA1-006-R KEY_POWER"
lircd: Debug Sending once, msg: SEND_ONCE ENTONE_URC-4021ABA1-006-R KEY_POWER
, args: ENTONE_URC-4021ABA1-006-R KEY_POWER, once: 1
lircd: Debug clearing transmit buffer
lircd: Debug adding to transmit buffer: 2564
lircd: Debug adding to transmit buffer: 917
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 944
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 944
lircd: Debug adding to transmit buffer: 1158
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 944
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 772
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 944
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 772
lircd: Debug adding to transmit buffer: 944
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 772
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug adding to transmit buffer: 472
lircd: Debug adding to transmit buffer: 386
lircd: Debug transmit buffer ready
lircd: Debug irtoy ready for 0 bytes
lircd: Debug irtoy ready for 2 bytes
lircd: Debug irtoy ready for 0 bytes
lircd: Debug irtoy ready for 58 bytes
lircd: Debug irtoy ready for 0 bytes
lircd: Debug irtoy ready for 6 bytes
lircd: Debug irtoy ready for 0 bytes
lircd: Debug irtoy ready for 57 bytes
lircd: Debug irtoy ready for 0 bytes
lircd: Debug 01 EC
lircd: Error irtoy_send: invalid byte count indicator received: 0F
lircd: Debug Sending error
lircd: Error error processing command: SEND_ONCE ENTONE_URC-4021ABA1-006-R KEY_POWER
lircd: Error transmission failed
lircd: Debug irtoy_raw_rec
lircd: Debug new signal after large space
lircd: Debug readdata 0 1000000
lircd: Debug c1000000
lircd: Debug trying "ENTONE_URC-4021ABA1-006-R" remote
lircd: Debug decode: enter
lircd: Debug <s1000000
lircd: Debug sync
lircd: Debug read_raw 0aff
lircd: Debug read_raw 60053
lircd: Debug readdata 1 60053
lircd: Debug +p60053
lircd: Debug failed on header
lircd: Debug decode: 0
lircd: Debug failed "ENTONE_URC-4021ABA1-006-R" remote
lircd: Debug decoding failed for all remotes
lircd: Info removed client
5
USB Infrared Toy / Re: IRToy Locks Up After a Few Sends on RPi With New Kernel
Ah, then I completely misunderstood, my bad. The bit about the build started after the reference to the latest sources having the patches included.
In that case you might be out of luck. I've been using this combo for a while in the latest kernel (3.17) and the problems still occur. Not having switched to a lower USB speed though.
6
USB Infrared Toy / Re: IRToy Locks Up After a Few Sends on RPi With New Kernel
It always worked in the past with the same device and conf file, be it only for 5-6 times of course.
Did you did anything special when building the latest sources or are doing so when running/using lirc in order to make it work with the toy?
7
USB Infrared Toy / Re: Linux Lirc (usb_irtoy driver) device stops responding
Thanks for the heads-up and good to hear it's working for you.
I tried a build from the latest sources, but despite using the same conf file as before it doesn't work. I don't get errors, the toy lights up as normal when trying to send a command, but nothing happens with the device that I'm trying to control.
It always worked in the past with the same device and conf file, be it only for 5-6 times of course.
Did you did anything special when building the latest sources or are doing so when running/using lirc in order to make it work with the toy?
8
USB Infrared Toy / Re: Linux Lirc (usb_irtoy driver) device stops responding
[quote author="AnalysIR"]We found that these issues were a result of not responding fast enough when sending IR.[/quote]
What is not responding fast enough to what?
[quote author="AnalysIR"]Our solution was 2 part:
1. make sure the sending code on the PC is as fast/efficient as possible
2. Increase the priority of your code or script or process. (this was the most important issue). (===>nice for Linux?)[/quote]
That's not a solution, but a work-around ;-P
Increasing the priority of lircd, as well as irsend doesn't do the trick.
9
USB Infrared Toy / Re: Cant Record Signal From Remote
Incorrect, at least in the way you are saying it. If you have LIRC patched like described above you don't need to use irman any more and other remotes besides RC5, like RC6 remotes, work fine as well.
10
USB Infrared Toy / Re: Cant Record Signal From Remote
pacth file name:
0001-Add-driver-for-USB-Infrared-Toy-in-sample-mode.patch
0002-Add-USB-Infrared-Toy-driver-to-setup-system.patch
Code: [Select]
ble@ble-K43SJ:~$ sudo add-apt-repository ppa:forage/lirc
Result:
Code: [Select]
LIRC with added driver for the Dangerous Prototypes USB Infrared Toy, providing full receive/transmit support compared to using the IRman LIRC driver.[/quote]
NOTE: Requires firmware v20 or higher!
Example usage:
irrecord -n --driver usb_irtoy --device /dev/ttyACM0 RemoteXXX.conf
Driver patch applied: http://sourceforge.net/p/lirc/mailman/message/28032156/
For more information: http://dangerousprototypes.com/docs/USB_Infrared_Toy
More info: https://launchpad.net/~forage/+archive/ubuntu/lirc
Press [ENTER] to continue or ctrl-c to cancel adding it
gpg: keyring `/tmp/tmprud82ld_/secring.gpg' created
gpg: keyring `/tmp/tmprud82ld_/pubring.gpg' created
gpg: requesting key 56D26B9B from hkp server keyserver.ubuntu.com
gpg: /tmp/tmprud82ld_/trustdb.gpg: trustdb created
gpg: key 56D26B9B: public key "Launchpad PPA for Forage" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
After you added the PPA repository, you don't need to apply the patches any more, because they are already included in the updated LIRC package. That's the whole reason you use the package from the PPA so you don't have to apply the patches yourself. Install the updated package and you're done.
After you added the PPA:
Code: [Select]
sudo apt-get update
sudo apt-get install lirc
11
USB Infrared Toy / Re: Toy not available after reboot on RPi
That's two OpenElec distro's failing now. What RPi distro are you on?
12
USB Infrared Toy / Re: Cant Record Signal From Remote
I've created a PPA with a version of LIRC with the driver included. This will safe you the time of having to compile LIRC yourself. https://launchpad.net/~forage/+archive/ubuntu/lirc
Follow this steps provided on that page, on how to add this PPA to Ubuntu and update the LIRC package.
After that replace the driver in the command you are running to usb_irtoy:
Code: [Select]
irrecord -n -H usb_irtoy -d /dev/ttyUSB0 Remote1.conf
13
USB Infrared Toy / Re: Can't get it to work on Xubuntu 14.04
Did you try the Mythbuntu 10.4 way as suggested earlier and did it change anything?
Yes, I already did it but still cant record anything. It still show
Code: [Select]
irrecord: gap not found, can't continue[/quote]
So something has changed, it's a completely different error!
Please understand that you have to be very specific if others are trying to help you. When you say "it's still not working" and don't provide us with that info that there was at least a change we expect that the issue is identical than the one we started off with. When this isn't the case any more we'll just keep going round in circles still trying to solve problem A while we should have moved on to problem B, thus wasting both our times.
Your device is working just fine now, this issue is completely unrelated. Others have ran into this problem before, try searching for a solution first. Start a new forum thread about this new issue if you can't figure it out.
14
USB Infrared Toy / Re: Toy not available after reboot on RPi
15
USB Infrared Toy / M-Stack for USB Ir Toy
Deeming the current USB stack for the USB Ir Toy (v22 and v23) to be unstable/unreliable and due to the fact that firmware updates for the device seem to have stopped, I performed a quick search for open source USB stacks and found M-Stack.
It appears to be maintained, unlike the stack included in the Toy's firmware, and suitable for the PIC 18F2550.
Would there be any advantage using this USB stack over the current one included in the firmware and has anyone attempted to use it already?
I'm no C programmer, I don't have a lot of knowledge about electronics, nor do I know how to build the Toy's firmware.
Are there any intentions to work on the Toy's firmware again and would including this stack be an option?