Text only | Text with Images

Dangerous Prototypes

Dangerous Prototypes => USB Infrared Toy => Topic started by: protorob on May 14, 2014, 03:36:00 pm

Title: Can't get it to work on Xubuntu 14.04
Post by: protorob on May 14, 2014, 03:36:00 pm
Hi, today i  received a couple of ir-toys and while i'm configuring it i'm begining to see some dificulties i would like to know if they are overcomeable

I'm stucked on the "Configure LIRC" manual, i can actually see the device when i imput # dmesg


When i go to stop lircd service i get this:

rosita@1005ha-XUBUNTU:~$ service lircd stop
lircd: unrecognized service
rosita@1005ha-XUBUNTU:~$

 when i enter to this part:

$ irrecord -n -H irman -d /dev/ttyACM0 RemoteXXX.conf

i get this error:

irrecord: could not open /dev/ttyACM0
irrecord: irman_init(): Permission denied
irrecord: could not init hardware (lircd running ? --> close it...)


Can you help me understand how should i proceed on the installation

Thanks in advance
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: teknetik on May 15, 2014, 11:11:35 pm
You're running this as root or another user?
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: AndThen on May 16, 2014, 02:51:22 am
^^ Agreed, you can tell a root prompt from a normal user by the "$" instead of a "#" on the prompt. You need to start/stop services as root. The second command indicates you user doesn't have the "serial" group, so i doesn't have access to the serial port device file.

"sudo service lircd start" <-- proper cmd to start the service, assumes it was properly installed with the prefix set to "/"
"sudo adduser rosita serial" <-- Enables read & write to serial port, which sould solve the irrecord "Permission" error.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: protorob on July 22, 2014, 08:25:08 pm
I Don't know what to honestly, while adding rosita user to serial group (that later happened to be <<dialout>> group instead in xubuntu) user manager UI blocked and i had to restart the system. Now i can't see ttyACM0 nor ttyUSB0 in /dev/ so i can not continue with the installation...
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: protorob on July 22, 2014, 08:55:01 pm
Ok, i managed to activate the root account.
now i can stop lirc service as you pointed out
but when i try to run irrecord command now i get:

irrecord: could not open /dev/ttyUSB0
irrecord: irman_init(): Connection timed out
irrecord: could not init hardware (lircd running? --> close it, check permissions)
root@1005ha-XUBUNTU:~#

at least something changed...
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on July 27, 2014, 03:04:55 pm
[quote author="protorob"]Ok, i managed to activate the root account.[/quote]
You really shouldn't need to be root to use it. Just make sure you are in the 'dialout' group (as non-root):
Code: [Select]
sudo adduser $USER dialout
Next make sure you have the latest firmware installed on your Toy.
In order to do this you'll have to manually compile the firmware tool. To summarize from the wiki (http://http://dangerousprototypes.com/docs/USB_IR_Toy_firmware_update):
Code: [Select]
sudo apt-get install libusb-dev
wget https://github.com/dpavlin/fw_update/archive/master.tar.gz
tar xf master.tar.gz
cd fw_update-master/
LIBS=-lusb ./configure --with-usb-includes=/usr/include
make
sudo ./fw_update -e -w -v -m all -vid 0x04D8 -pid 0xFD0B -ix ../USBIRToy.v22.hex
Make ABSOLUTELY SURE you got no spaces in the path of the firmware tool source code, i.e. the location of the fw_update folder, before you run configure. Otherwise you'll be spending a lot of time figuring out what's going wrong using completely unrelated error messages, just like me.
I also recommend you to use the jumper method for flashing the firmware. Activating the bootloader with a terminal command did not function for me.
Replace the last part of the sudo ./fw_update command with the actual location of the firmware file.

Now on to LIRC (http://http://dangerousprototypes.com/docs/USB_IR_Toy:_Configure_LIRC).
There's no need to do the Mythbuntu 10.04 trickery as explained in the wiki. If you did, revert the changes and reboot.
Next disconnect your Toy, check what /dev/ttyACM* entries your have (where * is a single number), reconnect the Toy, and check again.
You should have a new /dev/ttyACM* entry listed in the /dev/ folder. This is your Toy.

To take full advantage of your Toy you would want to use LIRC with the usb_irtoy driver for the Toy instead of the general irman LIRC driver.
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 (https://launchpad.net/~forage/+archive/ubuntu/lirc)

Continue with the LIRC instructions in the wiki and other LIRC documentation to do whatever you intended to do with your Toy. Just make sure you replace irman with usb_irtoy wherever the driver is specified and use the correct /dev/ entry to specify your device.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on July 30, 2014, 06:49:21 am
HI, I'm having a same issue as well and I'm new to ubuntu. Please teach/guide how to solve this issue.

i already keep trying but still cant stop the licd service. I really dont have any idea what to do right now.

Thank you so much.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on July 30, 2014, 08:51:18 am
[quote author="birdlayegg"]HI, I'm having a same issue as well and I'm new to ubuntu. Please teach/guide how to solve this issue.

i already keep trying but still cant stop the licd service. I really dont have any idea what to do right now.[/quote]
You're really not giving us much to go on (what are you trying how where and what is the result), but if it's just stopping LIRC you are after:
Code: [Select]
sudo service lircd stop
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on July 30, 2014, 09:31:34 am
it keep show me "    lircd: unrecognized service" . May i know what is the problem?
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on July 30, 2014, 01:01:58 pm
Did you install LIRC? If yes, how? If no, it doesn't come installed on Ubuntu by default, so make sure you do.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on July 30, 2014, 02:14:12 pm
I already install it using this code
Code: [Select]
$ sudo apt-get install lirc

and it show:
lirc is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 330 not upgraded.

Or i need to start the service first?
i try to   

ble@ble-K43SJ:~$ sudo service lirc start
 * Loading LIRC modules                                                  [ OK ]
find: `/sys/class/rc/*/': No such file or directory
 * Starting remote control daemon(s) :  lircd: there seems to already be a lircd process with pid 993
lircd: otherwise delete stale lockfile /var/run/lirc/lircd.pid                                                                    [fail]
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on July 30, 2014, 02:41:51 pm
If you didn't restart or manually started LIRC after the installation than there wouldn't have been a reason to stop it first.
Try stopping it first, just to make sure it's not running with:
Code: [Select]
sudo killall -9 lircd
And start trying to record or whatever you want to do.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on July 30, 2014, 05:38:03 pm
Okay, I already do it but i still cant record it. Here is the msg.

ble@ble-K43SJ:~$    sudo killall -9 lircd
[sudo] password for ble:
ble@ble-K43SJ:~$ sudo service lirc stop
find: `/sys/class/rc/*/': No such file or directory
 * Stopping remote control daemon(s): LIRC                              [ OK ]
ble@ble-K43SJ:~$ irrecord -n -H irman -d /dev/ttyACM0 RemoteXXX.conf

irrecord -  application for recording IR-codes for usage with lirc

Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de)

irrecord: could not open /dev/ttyACM0
irrecord: irman_init(): Connection timed out
irrecord: could not init hardware (lircd running ? --> close it, check permissions)

May i know what is the problem?
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on July 30, 2014, 06:54:05 pm
Please post the output of the following, just to be sure:
Code: [Select]
groups
Also disconnect and reconnect you USB IR Toy and post the last 20 lines of the output of:
Code: [Select]
dmesg
And, why not, the output of the following two commands while you are at it, having the Toy connected:
Code: [Select]
lsusb
ls -lah /dev/tty*
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on July 31, 2014, 05:56:28 pm
1)
ble@ble-K43SJ:~$    groups
ble adm dialout cdrom sudo dip plugdev lpadmin sambashare
2)
[41897.442455] type=1400 audit(1406763447.381:65): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=4340 comm="apparmor_parser"
[41897.442467] type=1400 audit(1406763447.381:66): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=4340 comm="apparmor_parser"
[41897.443242] type=1400 audit(1406763447.381:67): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=4340 comm="apparmor_parser"
[51916.418436] perf samples too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[99660.489321] usb 2-1.3: USB disconnect, device number 6
[99662.481341] usb 2-1.3: new full-speed USB device number 7 using ehci-pci
[99662.577640] usb 2-1.3: New USB device found, idVendor=04d8, idProduct=fd08
[99662.577653] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[99662.577659] usb 2-1.3: Product: USBIRtoy (CDC-232)
[99662.577664] usb 2-1.3: Manufacturer: DangerousPrototypes.com
[99662.578302] cdc_acm 2-1.3:1.0: This device cannot do calls on its own. It is not a modem.
[99662.578346] cdc_acm 2-1.3:1.0: ttyACM0: USB ACM device

3)
ble@ble-K43SJ:~$ lsusb
Bus 002 Device 007: ID 04d8:fd08 Microchip Technology, Inc.
Bus 002 Device 003: ID 045e:075c Microsoft Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp. Asus Integrated Webcam
Bus 001 Device 006: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ble@ble-K43SJ:~$ ls -lah /dev/tty*
crw-rw-rw- 1 root tty      5,  0 Jul  30 23:36 /dev/tty
crw--w---- 1 root tty      4,  0 Jul  30 19:59 /dev/tty0
crw-rw---- 1 root tty      4,  1 Jul  30 19:59 /dev/tty1
crw--w---- 1 root tty      4, 10 Jul  30 19:59 /dev/tty10
crw--w---- 1 root tty      4, 11 Jul  30 19:59 /dev/tty11
crw--w---- 1 root tty      4, 12 Jul  30 19:59 /dev/tty12
crw--w---- 1 root tty      4, 13 Jul  30 19:59 /dev/tty13
crw--w---- 1 root tty      4, 14 Jul  30 19:59 /dev/tty14
crw--w---- 1 root tty      4, 15 Jul  30 19:59 /dev/tty15
crw--w---- 1 root tty      4, 16 Jul  30 19:59 /dev/tty16
crw--w---- 1 root tty      4, 17 Jul  30 19:59 /dev/tty17
crw--w---- 1 root tty      4, 18 Jul  30 19:59 /dev/tty18
crw--w---- 1 root tty      4, 19 Jul  30 19:59 /dev/tty19
crw-rw---- 1 root tty      4,  2 Jul  30 19:59 /dev/tty2
crw--w---- 1 root tty      4, 20 Jul  30 19:59 /dev/tty20
crw--w---- 1 root tty      4, 21 Jul  30 19:59 /dev/tty21
crw--w---- 1 root tty      4, 22 Jul  30 19:59 /dev/tty22
crw--w---- 1 root tty      4, 23 Jul  30 19:59 /dev/tty23
crw--w---- 1 root tty      4, 24 Jul  30 19:59 /dev/tty24
crw--w---- 1 root tty      4, 25 Jul  30 19:59 /dev/tty25
crw--w---- 1 root tty      4, 26 Jul  30 19:59 /dev/tty26
crw--w---- 1 root tty      4, 27 Jul  30 19:59 /dev/tty27
crw--w---- 1 root tty      4, 28 Jul  30 19:59 /dev/tty28
crw--w---- 1 root tty      4, 29 Jul  30 19:59 /dev/tty29
crw-rw---- 1 root tty      4,  3 Jul  30 19:59 /dev/tty3
crw--w---- 1 root tty      4, 30 Jul  30 19:59 /dev/tty30
crw--w---- 1 root tty      4, 31 Jul  30 19:59 /dev/tty31
crw--w---- 1 root tty      4, 32 Jul  30 19:59 /dev/tty32
crw--w---- 1 root tty      4, 33 Jul  30 19:59 /dev/tty33
crw--w---- 1 root tty      4, 34 Jul  30 19:59 /dev/tty34
crw--w---- 1 root tty      4, 35 Jul  30 19:59 /dev/tty35
crw--w---- 1 root tty      4, 36 Jul  30 19:59 /dev/tty36
crw--w---- 1 root tty      4, 37 Jul  30 19:59 /dev/tty37
crw--w---- 1 root tty      4, 38 Jul  30 19:59 /dev/tty38
crw--w---- 1 root tty      4, 39 Jul  30 19:59 /dev/tty39
crw-rw---- 1 root tty      4,  4 Jul  30 19:59 /dev/tty4
crw--w---- 1 root tty      4, 40 Jul  30 19:59 /dev/tty40
crw--w---- 1 root tty      4, 41 Jul  30 19:59 /dev/tty41
crw--w---- 1 root tty      4, 42 Jul  30 19:59 /dev/tty42
crw--w---- 1 root tty      4, 43 Jul  30 19:59 /dev/tty43
crw--w---- 1 root tty      4, 44 Jul  30 19:59 /dev/tty44
crw--w---- 1 root tty      4, 45 Jul  30 19:59 /dev/tty45
crw--w---- 1 root tty      4, 46 Jul  30 19:59 /dev/tty46
crw--w---- 1 root tty      4, 47 Jul  30 19:59 /dev/tty47
crw--w---- 1 root tty      4, 48 Jul  30 19:59 /dev/tty48
crw--w---- 1 root tty      4, 49 Jul  30 19:59 /dev/tty49
crw-rw---- 1 root tty      4,  5 Jul  30 19:59 /dev/tty5
crw--w---- 1 root tty      4, 50 Jul  30 19:59 /dev/tty50
crw--w---- 1 root tty      4, 51 Jul  30 19:59 /dev/tty51
crw--w---- 1 root tty      4, 52 Jul  30 19:59 /dev/tty52
crw--w---- 1 root tty      4, 53 Jul  30 19:59 /dev/tty53
crw--w---- 1 root tty      4, 54 Jul  30 19:59 /dev/tty54
crw--w---- 1 root tty      4, 55 Jul  30 19:59 /dev/tty55
crw--w---- 1 root tty      4, 56 Jul  30 19:59 /dev/tty56
crw--w---- 1 root tty      4, 57 Jul  30 19:59 /dev/tty57
crw--w---- 1 root tty      4, 58 Jul  30 19:59 /dev/tty58
crw--w---- 1 root tty      4, 59 Jul  30 19:59 /dev/tty59
crw-rw---- 1 root tty      4,  6 Jul  30 19:59 /dev/tty6
crw--w---- 1 root tty      4, 60 Jul  30 19:59 /dev/tty60
crw--w---- 1 root tty      4, 61 Jul  30 19:59 /dev/tty61
crw--w---- 1 root tty      4, 62 Jul  30 19:59 /dev/tty62
crw--w---- 1 root tty      4, 63 Jul  30 19:59 /dev/tty63
crw--w---- 1 root tty      4,  7 Jul  30 19:59 /dev/tty7
crw--w---- 1 root tty      4,  8 Jul  30 19:59 /dev/tty8
crw--w---- 1 root tty      4,  9 Jul  30 19:59 /dev/tty9
crw-rw---- 1 root dialout 166,  0 Jul  31 23:39 /dev/ttyACM0
crw------- 1 root root      5,  3 Jul  30 19:59 /dev/ttyprintk
crw-rw---- 1 root dialout  4, 64 Jul  30 19:59 /dev/ttyS0
crw-rw---- 1 root dialout  4, 65 Jul  30 19:59 /dev/ttyS1
crw-rw---- 1 root dialout  4, 74 Jul  30 19:59 /dev/ttyS10
crw-rw---- 1 root dialout  4, 75 Jul  30 19:59 /dev/ttyS11
crw-rw---- 1 root dialout  4, 76 Jul  30 19:59 /dev/ttyS12
crw-rw---- 1 root dialout  4, 77 Jul  30 19:59 /dev/ttyS13
crw-rw---- 1 root dialout  4, 78 Jul  30 19:59 /dev/ttyS14
crw-rw---- 1 root dialout  4, 79 Jul  30 19:59 /dev/ttyS15
crw-rw---- 1 root dialout  4, 80 Jul  30 19:59 /dev/ttyS16
crw-rw---- 1 root dialout  4, 81 Jul  30 19:59 /dev/ttyS17
crw-rw---- 1 root dialout  4, 82 Jul  30 19:59 /dev/ttyS18
crw-rw---- 1 root dialout  4, 83 Jul  30 19:59 /dev/ttyS19
crw-rw---- 1 root dialout  4, 66 Jul  30 19:59 /dev/ttyS2
crw-rw---- 1 root dialout  4, 84 Jul  30 19:59 /dev/ttyS20
crw-rw---- 1 root dialout  4, 85 Jul  30 19:59 /dev/ttyS21
crw-rw---- 1 root dialout  4, 86 Jul  30 19:59 /dev/ttyS22
crw-rw---- 1 root dialout  4, 87 Jul  30 19:59 /dev/ttyS23
crw-rw---- 1 root dialout  4, 88 Jul  30 19:59 /dev/ttyS24
crw-rw---- 1 root dialout  4, 89 Jul  30 19:59 /dev/ttyS25
crw-rw---- 1 root dialout  4, 90 Jul  30 19:59 /dev/ttyS26
crw-rw---- 1 root dialout  4, 91 Jul  30 19:59 /dev/ttyS27
crw-rw---- 1 root dialout  4, 92 Jul  30 19:59 /dev/ttyS28
crw-rw---- 1 root dialout  4, 93 Jul  30 19:59 /dev/ttyS29
crw-rw---- 1 root dialout  4, 67 Jul  30 19:59 /dev/ttyS3
crw-rw---- 1 root dialout  4, 94 Jul  30 19:59 /dev/ttyS30
crw-rw---- 1 root dialout  4, 95 Jul  30 19:59 /dev/ttyS31
crw-rw---- 1 root dialout  4, 68 Jul  30 19:59 /dev/ttyS4
crw-rw---- 1 root dialout  4, 69 Jul  30 19:59 /dev/ttyS5
crw-rw---- 1 root dialout  4, 70 Jul  30 19:59 /dev/ttyS6
crw-rw---- 1 root dialout  4, 71 Jul  30 19:59 /dev/ttyS7
crw-rw---- 1 root dialout  4, 72 Jul  30 19:59 /dev/ttyS8
crw-rw---- 1 root dialout  4, 73 Jul  30 19:59 /dev/ttyS9

Here is the output of the commands.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on August 01, 2014, 03:19:31 pm
All looks fine and it should just work.
Are you sure you flashed the Toy with the latest v22 firmware?
If no, than do that first, as already explained in my earlier post (http://http://dangerousprototypes.com/forum/viewtopic.php?f=29&t=6563#p58840).
If yes, than I'm afraid I can't help you much more. You might have better luck with the Mythbuntu 10.04 way (http://http://dangerousprototypes.com/docs/USB_IR_Toy:_Configure_LIRC#Mythbuntu_10.04), though this did not work for me on Ubuntu 14.04.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: AndThen on August 02, 2014, 08:58:17 am
check it with a terminal program, "screen /dev/ttyACM0" or "minicom /dev/ttyACM0" once you are connected with one of those typing V gives a version string.

note that is ACM0, (zero) not the letter O.. I mention it because it is a common mistake and hard to tell depending on your fonts and if you wear glasses ;-)
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on August 02, 2014, 03:36:46 pm
I try to update but it cant work may i know what is the problem? Here is the code:
ble@ble-K43SJ:~$ wget http://jesshaas.com/software/IRToy-fw_update.tar.gz (http://jesshaas.com/software/IRToy-fw_update.tar.gz)
--2014-08-02 21:34:39--  http://jesshaas.com/software/IRToy-fw_update.tar.gz (http://jesshaas.com/software/IRToy-fw_update.tar.gz)
Resolving jesshaas.com (jesshaas.com)... 72.167.232.77
Connecting to jesshaas.com (jesshaas.com)|72.167.232.77|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 376632 (368K) [application/x-tar]
Saving to: ‘IRToy-fw_update.tar.gz.3’

100%[======================================>] 376,632      115KB/s  in 3.2s 

2014-08-02 21:34:54 (115 KB/s) - ‘IRToy-fw_update.tar.gz.3’ saved [376632/376632]

ble@ble-K43SJ:~$ tar xf IRToy-fw_update.tar.gz
ble@ble-K43SJ:~$ cd IRToy-fw_update
ble@ble-K43SJ:~/IRToy-fw_update$ LIBS=-lusb ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether the C++ compiler works... no
configure: error: in `/home/ble/IRToy-fw_update':
configure: error: C++ compiler cannot create executables
See `config.log' for more details
ble@ble-K43SJ:~/IRToy-fw_update$ make
make: *** No targets specified and no makefile found.  Stop.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: aon on August 02, 2014, 04:23:34 pm
You need to install the build-essential package to be able to compile stuff.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on August 03, 2014, 08:43:07 am
May i know how to install the the build-essential package to be able to compile stuff??
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on August 03, 2014, 11:54:18 am
[quote author="birdlayegg"]May i know how to install the the build-essential package to be able to compile stuff??[/quote]
It would have saved you the time of typing and waiting, as well as ours, if you just did a quick look on your favourite search engine first:
Code: [Select]
sudo apt-get install build-essential
Also, there's a reason you should download the update tool from a different location, as I'm doing in my earlier post and as explained in the wiki.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on August 03, 2014, 02:57:52 pm
ble@ble-K43SJ:~/IRToy-fw_update$ sudo ./fw_update -e -w -v -m all -vid 0x04D8 -pid 0xFD0B -ix ../USBIRToy.v22.hex
U2IO flash erasing: DONE.
U2IO id programming: DONE.
U2IO eeprom programming: DONE.
Failed to open file "../USBIRToy.v22.hex"  for reading.
Operation aborted.

May i know this consider Done upgrade??
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on August 03, 2014, 05:05:02 pm
[quote author="birdlayegg"]ble@ble-K43SJ:~/IRToy-fw_update$ sudo ./fw_update -e -w -v -m all -vid 0x04D8 -pid 0xFD0B -ix ../USBIRToy.v22.hex
U2IO flash erasing: DONE.
U2IO id programming: DONE.
U2IO eeprom programming: DONE.
Failed to open file "../USBIRToy.v22.hex"  for reading.
Operation aborted.

May i know this consider Done upgrade??[/quote]
Seriously, you are in way over your head.
Read the instructions given more carefully and try to understand what is happening before doing them.

You didn't supply the correct path of the firmware file it has to flash. Check the wiki for the download location of the firmware and try the update again with the correct path to the firmware file.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on August 04, 2014, 02:06:44 pm
Thank you so much finally it is done but now may i know why IRToy cant receive any signal from my remote control and i cant record it as well? Is there anyway to check it?
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on August 09, 2014, 01:14:47 pm
We can't do much if you aren't more accurate.

Note to put output of commands and files contents between code tags in your post. This makes it easier to read.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on August 26, 2014, 05:13:57 pm
Did anything change after you updated the firmware?
Yes, Here is the result

Code: [Select]
U2IO flash erasing: DONE.
U2IO id programming: DONE.
U2IO eeprom programming: DONE.
U2IO flash programming: DONE.
U2IO id programming: DONE.
U2IO eeprom programming: DONE.
U2IO flash verifying: DONE.
U2IO id verifying: DONE.
U2IO eeprom verifying: DONE.
RESET Device
Operation successfully completed.
    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

    Please supply to output of the commands you are executing and don't work
Code: [Select]
irrecord -n -H irman -d /dev/ttyUSB0 Remote001.conf

    Please supply the contents of /var/log/syslog after you tried the commands
Code: [Select]
Aug 26 20:29:50 ble-K43SJ anacron[886]: Job `cron.daily' terminated
Aug 26 20:29:50 ble-K43SJ anacron[886]: Normal exit (1 job run)
Aug 26 21:11:09 ble-K43SJ wpa_supplicant[786]: message repeated 29 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Aug 26 21:12:38 ble-K43SJ wpa_supplicant[786]: wlan0: WPA: Group rekeying completed with 34:08:04:c8:32:64 [GTK=TKIP]
Aug 26 21:13:09 ble-K43SJ wpa_supplicant[786]: wlan0: CTRL-EVENT-SCAN-STARTED 
Aug 26 21:17:01 ble-K43SJ CRON[2728]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Aug 26 21:56:15 ble-K43SJ kernel: [ 6647.055288] usb 2-1.3: new full-speed USB device number 4 using ehci-pci
Aug 26 21:56:15 ble-K43SJ kernel: [ 6647.150606] usb 2-1.3: New USB device found, idVendor=04d8, idProduct=fd0b
Aug 26 21:56:15 ble-K43SJ kernel: [ 6647.150618] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 26 21:56:15 ble-K43SJ kernel: [ 6647.150625] usb 2-1.3: Product: Diolan
Aug 26 21:56:15 ble-K43SJ kernel: [ 6647.150630] usb 2-1.3: Manufacturer: Diolan
Aug 26 21:56:15 ble-K43SJ kernel: [ 6647.152649] hid-generic 0003:04D8:FD0B.0002: hidraw1: USB HID v1.01 Device [Diolan Diolan] on usb-0000:00:1d.0-1.3/input0
Aug 26 21:56:15 ble-K43SJ mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Aug 26 21:56:15 ble-K43SJ mtp-probe: bus: 2, device: 4 was not an MTP device
Aug 26 21:56:24 ble-K43SJ dbus[641]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
Aug 26 21:56:24 ble-K43SJ dbus[641]: [system] Successfully activated service 'org.freedesktop.hostname1'
Aug 26 22:00:24 ble-K43SJ kernel: [ 6896.082819] usb 2-1.3: USB disconnect, device number 4
Aug 26 22:00:24 ble-K43SJ kernel: [ 6896.282990] usb 2-1.3: new full-speed USB device number 5 using ehci-pci
Aug 26 22:00:24 ble-K43SJ kernel: [ 6896.377742] usb 2-1.3: New USB device found, idVendor=04d8, idProduct=fd0b
Aug 26 22:00:24 ble-K43SJ kernel: [ 6896.377754] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 26 22:00:24 ble-K43SJ kernel: [ 6896.377761] usb 2-1.3: Product: Diolan
Aug 26 22:00:24 ble-K43SJ kernel: [ 6896.377766] usb 2-1.3: Manufacturer: Diolan
Aug 26 22:00:24 ble-K43SJ kernel: [ 6896.379454] hid-generic 0003:04D8:FD0B.0003: hidraw1: USB HID v1.01 Device [Diolan Diolan] on usb-0000:00:1d.0-1.3/input0
Aug 26 22:00:24 ble-K43SJ mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Aug 26 22:00:24 ble-K43SJ mtp-probe: bus: 2, device: 5 was not an MTP device
Aug 26 22:01:54 ble-K43SJ lircd-0.9.0[1025]: caught signal
Aug 26 22:03:04 ble-K43SJ kernel: [ 7056.427345] usb 2-1.3: USB disconnect, device number 5
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.519807] usb 2-1.3: new full-speed USB device number 6 using ehci-pci
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615248] usb 2-1.3: New USB device found, idVendor=04d8, idProduct=fd08
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615260] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615266] usb 2-1.3: Product: CDC Test
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615272] usb 2-1.3: Manufacturer: Dangerous Prototypes
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615277] usb 2-1.3: SerialNumber: 00000001
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615776] usbserial_generic 2-1.3:1.0: Generic device with no bulk out, not allowed.
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615797] usbserial_generic: probe of 2-1.3:1.0 failed with error -5
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615947] usbserial_generic 2-1.3:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615956] usbserial_generic 2-1.3:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.615963] usbserial_generic 2-1.3:1.1: generic converter detected
Aug 26 22:03:31 ble-K43SJ kernel: [ 7083.617923] usb 2-1.3: generic converter now attached to ttyUSB0
Aug 26 22:03:31 ble-K43SJ mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Aug 26 22:03:31 ble-K43SJ mtp-probe: bus: 2, device: 6 was not an MTP device
Aug 26 22:03:31 ble-K43SJ ModemManager[654]: <warn>  (ttyUSB0): port attributes not fully set
Aug 26 22:03:47 ble-K43SJ ModemManager[654]: <info>  Creating modem with plugin 'Generic' and '1' ports
Aug 26 22:03:47 ble-K43SJ ModemManager[654]: <warn>  Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type'
Aug 26 22:03:47 ble-K43SJ ModemManager[654]: <warn>  Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3': Failed to find primary AT port
Aug 26 22:05:01 ble-K43SJ kernel: [ 7173.227765] usb 2-1.3: USB disconnect, device number 6
Aug 26 22:05:01 ble-K43SJ kernel: [ 7173.228164] generic ttyUSB0: generic converter now disconnected from ttyUSB0
Aug 26 22:05:01 ble-K43SJ kernel: [ 7173.228183] usbserial_generic 2-1.3:1.1: device disconnected
Aug 26 22:05:01 ble-K43SJ ModemManager[654]: <info>  (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.805101] usb 2-1.3: new full-speed USB device number 7 using ehci-pci
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.899991] usb 2-1.3: New USB device found, idVendor=04d8, idProduct=fd08
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900002] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900009] usb 2-1.3: Product: CDC Test
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900014] usb 2-1.3: Manufacturer: Dangerous Prototypes
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900019] usb 2-1.3: SerialNumber: 00000001
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900555] usbserial_generic 2-1.3:1.0: Generic device with no bulk out, not allowed.
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900572] usbserial_generic: probe of 2-1.3:1.0 failed with error -5
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900668] usbserial_generic 2-1.3:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900674] usbserial_generic 2-1.3:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900679] usbserial_generic 2-1.3:1.1: generic converter detected
Aug 26 22:05:06 ble-K43SJ kernel: [ 7178.900856] usb 2-1.3: generic converter now attached to ttyUSB0
Aug 26 22:05:06 ble-K43SJ mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Aug 26 22:05:06 ble-K43SJ mtp-probe: bus: 2, device: 7 was not an MTP device
Aug 26 22:05:06 ble-K43SJ ModemManager[654]: <warn>  (ttyUSB0): port attributes not fully set
Aug 26 22:05:22 ble-K43SJ ModemManager[654]: <info>  Creating modem with plugin 'Generic' and '1' ports
Aug 26 22:05:22 ble-K43SJ ModemManager[654]: <warn>  Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type'
Aug 26 22:05:22 ble-K43SJ ModemManager[654]: <warn>  Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3': Failed to find primary AT port
Aug 26 22:05:29 ble-K43SJ kernel: [ 7201.659495] usb 2-1.3: USB disconnect, device number 7
Aug 26 22:05:29 ble-K43SJ kernel: [ 7201.659937] generic ttyUSB0: generic converter now disconnected from ttyUSB0
Aug 26 22:05:29 ble-K43SJ kernel: [ 7201.659968] usbserial_generic 2-1.3:1.1: device disconnected
Aug 26 22:05:29 ble-K43SJ ModemManager[654]: <info>  (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3
Aug 26 22:05:47 ble-K43SJ kernel: [ 7220.044269] usb 2-1.3: new full-speed USB device number 8 using ehci-pci
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.139562] usb 2-1.3: New USB device found, idVendor=04d8, idProduct=fd08
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.139574] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.139580] usb 2-1.3: Product: CDC Test
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.139586] usb 2-1.3: Manufacturer: Dangerous Prototypes
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.139590] usb 2-1.3: SerialNumber: 00000001
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.140129] usbserial_generic 2-1.3:1.0: Generic device with no bulk out, not allowed.
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.140151] usbserial_generic: probe of 2-1.3:1.0 failed with error -5
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.140292] usbserial_generic 2-1.3:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.140300] usbserial_generic 2-1.3:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.140314] usbserial_generic 2-1.3:1.1: generic converter detected
Aug 26 22:05:48 ble-K43SJ kernel: [ 7220.140996] usb 2-1.3: generic converter now attached to ttyUSB0
Aug 26 22:05:48 ble-K43SJ mtp-probe: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Aug 26 22:05:48 ble-K43SJ mtp-probe: bus: 2, device: 8 was not an MTP device
Aug 26 22:05:48 ble-K43SJ ModemManager[654]: <warn>  (ttyUSB0): port attributes not fully set
Aug 26 22:06:03 ble-K43SJ ModemManager[654]: <info>  Creating modem with plugin 'Generic' and '1' ports
Aug 26 22:06:03 ble-K43SJ ModemManager[654]: <warn>  Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type'
Aug 26 22:06:03 ble-K43SJ ModemManager[654]: <warn>  Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3': Failed to find primary AT port
Aug 26 22:12:00 ble-K43SJ kernel: [ 7592.787290] usb 2-1.3: USB disconnect, device number 8
Aug 26 22:12:00 ble-K43SJ kernel: [ 7592.787693] generic ttyUSB0: generic converter now disconnected from ttyUSB0
Aug 26 22:12:00 ble-K43SJ kernel: [ 7592.787746] usbserial_generic 2-1.3:1.1: device disconnected
Aug 26 22:12:00 ble-K43SJ ModemManager[654]: <info>  (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.571183] usb 2-1.3: new full-speed USB device number 9 using ehci-pci
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666233] usb 2-1.3: New USB device found, idVendor=04d8, idProduct=fd08
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666245] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666251] usb 2-1.3: Product: CDC Test
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666257] usb 2-1.3: Manufacturer: Dangerous Prototypes
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666262] usb 2-1.3: SerialNumber: 00000001
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666710] usbserial_generic 2-1.3:1.0: Generic device with no bulk out, not allowed.
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666727] usbserial_generic: probe of 2-1.3:1.0 failed with error -5
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666821] usbserial_generic 2-1.3:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666827] usbserial_generic 2-1.3:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.666832] usbserial_generic 2-1.3:1.1: generic converter detected
Aug 26 22:12:04 ble-K43SJ kernel: [ 7596.667085] usb 2-1.3: generic converter now attached to ttyUSB0
Aug 26 22:12:04 ble-K43SJ mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Aug 26 22:12:04 ble-K43SJ mtp-probe: bus: 2, device: 9 was not an MTP device
Aug 26 22:12:04 ble-K43SJ ModemManager[654]: <warn>  (ttyUSB0): port attributes not fully set
Aug 26 22:12:19 ble-K43SJ ModemManager[654]: <info>  Creating modem with plugin 'Generic' and '1' ports
Aug 26 22:12:19 ble-K43SJ ModemManager[654]: <warn>  Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type'
Aug 26 22:12:19 ble-K43SJ ModemManager[654]: <warn>  Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3': Failed to find primary AT port
Aug 26 22:11:09 ble-K43SJ wpa_supplicant[786]: message repeated 29 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Aug 26 22:12:38 ble-K43SJ wpa_supplicant[786]: wlan0: WPA: Group rekeying completed with 34:08:04:c8:32:64 [GTK=TKIP]
Aug 26 22:13:09 ble-K43SJ wpa_supplicant[786]: wlan0: CTRL-EVENT-SCAN-STARTED 
Aug 26 22:17:01 ble-K43SJ CRON[3168]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Aug 26 22:19:30 ble-K43SJ dbus[641]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
Aug 26 22:19:30 ble-K43SJ dbus[641]: [system] Successfully activated service 'org.freedesktop.hostname1'
Aug 26 22:23:43 ble-K43SJ lircd-0.9.0[3282]: lircd(irman) ready, using /run/lirc/lircd
Aug 26 22:23:52 ble-K43SJ lircd-0.9.0[3282]: accepted new client on /run/lirc/lircd
Aug 26 22:24:25 ble-K43SJ lircd-0.9.0[3282]: removed client
Aug 26 22:24:27 ble-K43SJ lircd-0.9.0[3282]: accepted new client on /run/lirc/lircd
Aug 26 22:24:38 ble-K43SJ lircd-0.9.0[3282]: removed client
Aug 26 22:24:54 ble-K43SJ lircd-0.9.0[3282]: accepted new client on /run/lirc/lircd
Aug 26 22:25:04 ble-K43SJ lircd-0.9.0[3282]: removed client
Aug 26 23:11:09 ble-K43SJ wpa_supplicant[786]: message repeated 29 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Aug 26 23:12:38 ble-K43SJ wpa_supplicant[786]: wlan0: WPA: Group rekeying completed with 34:08:04:c8:32:64 [GTK=TKIP]
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: Forage on September 05, 2014, 04:10:30 pm
[quote author="birdlayegg"]
    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.
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: birdlayegg on September 06, 2014, 06:22:11 pm
Okay, really sorry about that. I'm newbie in this ubuntu and others. Hope you understand. I had post a new threat hope you may help me to solve it as well. I already try my best to search online but still cant figure it.

Thanks in advance
Title: Re: Can't get it to work on Xubuntu 14.04
Post by: cncook001 on January 03, 2016, 03:55:51 am
In case anyone else has issues installing the v22 firmware the wiki was not clear for me.

I would add another step before "Step 2" can call it "Download firmware".  This step would show the commands to download the correct zip file, extract it and put it in the correct directory ready for the following step that references "../USBIRToy.v22.hex".  It was not obvious where that file came from.  I expected it to be produced by the IRToy-fw_update.tar.gz step.  That step only creates the bootloader though.
Text only | Text with Images

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01602236080session_write_close ( )...(null):0
20.01632367672ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01632368448Database_MySQL->query( ).../DatabaseHandler.php:119
40.06022507184Database_MySQL->error( ).../Db-mysql.class.php:273