Maybe you can measure the resistance between gnd on the loose cable and gnd on the pi, just make sure power is off when doing it. Could you try posting your hardware. I’m not killing lircd before running it, so lircd mustn’t be connecting to the correct device. I thought it was just to do with the luminosity and angle of half intensity. This configuration allows you to both receive and transmit codes. I love FTDI for making such a flexible chip cheap and abundant. I got the above working with the below config files.
|Date Added:||24 April 2011|
|File Size:||50.57 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I just added a description of a very simple receiver circuit at http: But you say I hook up the ground to the pi’s ground?
Problem with LIRC configuration. But why not use the 5V supply on the P1 header? Notify me of new comments via email. Restarting the lirc service with the new configuration, and issuing another listing of the running processes there are now three instances of lircd. CTLR C to break when done. The debconf configuration options allow for the selection of the FTDI type of receiver device: Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in: At this point I can reliably receive, and transmit worked, but may still have some bugs.
Problem with LIRC configuration – Raspberry Pi Forums
The voltage levels and current appear to be the same. Also, both pick up the transmissions of the other when I send with one and listen with the other: I had to modify some scripts to make it work, so I wanted to post my findings here such that it might help others. The BC has more headroom where the maximum collector current is mA. I thought it was just fftdi do with the luminosity and angle of half intensity.
No output ffdi irw. I get some check sum error notes in my syslog, but I understand that’s unimportant. And also separately provides an option to choose the transmitter.
Using a FTDI adapter as an IR emitter – O Falcão
Cut a couple of old fans cables, soldered up the receiver circuit, and plugged it in; mode2 shows spaces and pulses, used irrecord to generate a lircd. There is currently no option from the list to select an FTDI based transmitter but this can be configured later.
It also failed with 1 repeat. I don’t want to hook something up and find I’ve fried the pi. When I then restarted lirc and used irsend to transmit, I could see a faint light pulsing in the LED. Using the serial number, the following command line can be constructed to start the irrecord program.
I guess if you use power from the same hub as the pi is powered from then the gnd’s are already connected. The subprocess has appeared because the Ubuntu init script has detected that two devices have been configured a receiver and a transmitter and has made use of the lircd networking capabilities which allows two lircd instances to communicate, albeit only one way — from listener to connector, so the receiver lircd instance can send event updates to the connecting lircd instance the transmitter.
I think you can draw somthing like a couple of hundred milliamps before the polyfuse kicks in. You only need one instance of LIRC running it can receive and send at the same time. You are commenting using your Facebook account. The lirc deb package uses debconf to prompt for configuration options during installation lirc can be configured and compiled to work with specific drivers for certain hardware or all supported drivers, this is all handled during the deb installation process.
So from an distance, it would look like; USB black and red wires connecting to the circuit board; then a black wire connecting back to a GND on the pi, and another wire connecting to my GPIO pi? The absolute maximum rating on the collector current is mA I would be vary of getting that close to a maximum rating.
I would be great if they would do that.
Like sunlight or other IR sources that pollutes your commands. Here’s what mine looks like.