{"id":1012,"date":"2017-02-10T17:38:50","date_gmt":"2017-02-10T17:38:50","guid":{"rendered":"http:\/\/ofalcao.pt\/blog\/?p=1012"},"modified":"2017-02-10T17:47:15","modified_gmt":"2017-02-10T17:47:15","slug":"using-ftdi-as-ir-5","status":"publish","type":"post","link":"https:\/\/ofalcao.pt\/blog\/2017\/using-ftdi-as-ir-5","title":{"rendered":"Using a FTDI adapter as an IR emitter – 5"},"content":{"rendered":"
This post is part 5 of 5 of \u00a0Using a FTDI adapter as an IR<\/a><\/div>
sudo lircd -dserial=DN01DR29,output=3 -Hftdix<\/pre>\n
We gave lircd 3 parameters:<\/p>\n
    \n
  • “DN01DR29” is the serial number of my FTDI adapter reported by dmesg<\/li>\n
  • “output=3″ is the CTS pin we use to control the LED (in the ‘hello-ftdi.c” test we see LED defined as 0x08, that’s because LIRC ftdix drivers calculates the pin by left-shifting, so 2<<3 = 2\u00b3 = 8)<\/li>\n
  • “ftdix” is the driver to use<\/li>\n<\/ul>\n
    We should check if lircd is running. In Ubuntu it writes several messages at “\/var\/log\/messages” but this log doesn’t exist in ev3dev so<\/p>\n
    pgrep lircd\r\n5411<\/pre>\n
    E also see in dmesg that the ttyUSB device was disconnected by libftdi:<\/p>\n
    [47897.512814] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0\r\n[47897.513393] ftdi_sio 1-1.2:1.0: device disconnected<\/pre>\n
    We now use ‘irsend’ to check for available transmitter:<\/p>\n
    sudo irsend -d\/var\/run\/lirc\/lircd LIST \"\" \"\"\r\n\r\nLEGO_Combo_Direct\r\nLEGO_Combo_PWM\r\nLEGO_Single_Output<\/pre>\n
    We can also list all commands avaible for a particular transmitter:<\/p>\n
    sudo irsend -d\/var\/run\/lirc\/lircd LIST LEGO_Combo_Direct \"\"\r\n\r\n000000000000010e FLOAT_FLOAT\r\n000000000000011f FLOAT_FORWARD\r\n000000000000012c FLOAT_BACKWARD\r\n000000000000013d FLOAT_BRAKE\r\n000000000000014a FORWARD_FLOAT\r\n000000000000015b FORWARD_FORWARD\r\n0000000000000168 FORWARD_BACKWARD\r\n0000000000000179 FORWARD_BRAKE\r\n0000000000000186 BACKWARD_FLOAT\r\n0000000000000197 BACKWARD_FORWARD\r\n00000000000001a4 BACKWARD_BACKWARD\r\n00000000000001b5 BACKWARD_BRAKE\r\n00000000000001c2 BRAKE_FLOAT\r\n00000000000001d3 BRAKE_FORWARD\r\n00000000000001e0 BRAKE_BACKWARD\r\n00000000000001f1 BRAKE_BRAKE<\/pre>\n
    For first test we’ll just use “FORWARD_FORWARD” command (move both motors, “Red” and “Blue”, forward):<\/p>\n
    sudo irsend -d \/var\/run\/lirc\/lircd SEND_ONCE LEGO_Combo_Direct FORWARD_FORWARD<\/pre>\n
    And our motor do spin!<\/p>\n
    So, after such a big post, whats the point?<\/p>\n
    Well, since LIRC can handle several transmitter and for ftdix it uses the serial number of the FTDI adapter to identify each transmitter… we can have as much transmitters as we want as long as our system can handle it. On a laptop or a Raspberry Pi 3 that’s probably 127 (the max number of USB devices we can have). Most probably the Ev3 will gasp will all that USB devices but at least two I know it can handle:<\/p>\n