Omnimaga

Calculator Community => TI Calculators => General Calculator Help => Topic started by: dinosteven on September 08, 2012, 12:42:58 pm

Title: Tilp isn't working!
Post by: dinosteven on September 08, 2012, 12:42:58 pm

I can't get Tilp to work!
The GUI looks fine, but upon searching for a calc, it says "Can't set cable". And since it can't connect to a calculator, it's entirely useless...
I can't upload or download any files unless I strart up my corrupted-beyond-repair Windows OS partition to use TI Connect...

Information:

Computer:

Spoiler For Computer:

Dell Inspiron 1545
Sometimes the touchpad mouse doesn't work...
Originally shipped with Windows Vista, then got dropped - causing a broken hard drive. Then a new hard drive was installed (idk what brand) with a pirated Windows 7. (Not my intention, those computer guys put it on the hard drive pirated w/out telling me it was pirated.)
Used Wubi to install Ubuntu 12.04, then Windoze thought it was corrupt and "repaired" the system, corrupting it.
Used USB stick to install Ubuntu 10.10
Later, uninstalled Ubuntu 12.04 and installed it again with Wubi
Since the "corruption repair", Windoze has wanted to keep repairing every time I start up - It'll probably mess up Ubuntu 12.04 again...
So it's hard to use Windoze...

Tilp info:

Spoiler For Tilp installation info:

Installed with command "sudo apt-get install tilp", launched with command "tilp" or by clicking button.
It's never worked since I installed it.

Calculator info:

Spoiler For Calculator:

TI 84+SE, bought around March
Linking with a black Male->Female USB cable...

Please help!

Title: Re: Tilp isn't working!
Post by: dinosteven on September 08, 2012, 12:47:30 pm

Also, I'm not sure if this is the right place for this topic. Please move it if it's not.

Title: Re: Tilp isn't working!
Post by: Lionel Debroux on September 08, 2012, 02:31:24 pm

From the moderators' POV, it's probably not the appropriate section - but the fact that you posted in this section notified me (it's one of the few sections I'm subscribed to), so from my POV, you did it right ^^

Your problem report is quite detailed, which is a good thing :)

The Ubuntu packages are very outdated, especially if you're trying to communicate with a Nspire - but it has fixes and improvements all over the board.
You'll have to compile TILP yourself using http://lpg.ticalc.org/prj_tilp/download/install_tilp.sh . Be sure to either look inside the script to know which packages you need to install, or search the forum for other topics where the ready-made `sudo apt-get install ...` command is written ;)

BTW, unlike the severely outdated Ubuntu packages version, the latest version will attempt to auto-detect the calculator and cable model, so that you don't have to perform the configuration yourself. No, or improper, configuration is one of the leading causes of "TILP doesn't work".

And should you experience any problems, the somewhat verbose (at times) terminal output is the most useful debugging tool for the maintainer.

Title: Re: Tilp isn't working!
Post by: dinosteven on September 08, 2012, 05:48:31 pm

What does this mean?
Msg: attempting to use a cable which has not been open before.
Cause: Internal error.
System: Operation not permitted (errno = 1)

Title: Re: Tilp isn't working!
Post by: Jim Bauwens on September 08, 2012, 06:15:07 pm

Try running TiLP as root, should do the trick. (sudo tilp)

Title: Re: Tilp isn't working!
Post by: dinosteven on September 08, 2012, 07:43:01 pm

It sends files now!
Unfortunately, it still can't detect my calc and therefore I can't upload to my computer.
Which cable is it? Direct link, right? And which port do I need to use? (yes, I have "USB scan at startup" checked)

Here's the error then attempting to connect:

Spoiler For Spoiler:

Msg: failed to open the USB device.
Cause: Check that the USB cable is plugged in and that the calculator is turned ON! Also, check libusb and usbfs for valid permissions.
System: Inappropriate ioctl for device (errno = 25)

Also, when checking for calcs, terminal spat out:

Spoiler For Spoiler:

(tilp:4553): ticables-WARNING **: no devices found!

1: 0 0 0 0
2: 0 0 0 0
3: 0 0 0 0
4: 0 0 0 0
5: 1 0 0 0
1: 00 00 00 00
2: 00 00 00 00
3: 00 00 00 00
4: 00 00 00 00
5: 13 00 00 00

Title: Re: Tilp isn't working!
Post by: Lionel Debroux on September 09, 2012, 03:05:42 am

DirectLink, port #1 should do the job.

Does your previous message mean that you can send files to the calculator, but not receive from the calculator ? Taken literally, "It sends files now!" and "it still can't detect my calc" are contradictory.

Have you now compiled libti*/gfm/tilp yourself ?

Title: Re: Tilp isn't working!
Post by: dinosteven on September 09, 2012, 09:19:47 am

I'm using DirectLink, port #1.
The problem is, it doesn't detect anything on the calc. When clicking the "refresh" button or attempting to backup the calc, Tilp crashes and the terminal spits out:

** (tilp:24205): ERROR **: Invalid byte sequence in conversion input

However, after sending a program, the program appeared on my calc's prgm list! Weird, I don't know why.

I have no idea what "libti*/gfm/tilp" is... Sorry, I'm a noob at this.

Title: Re: Tilp isn't working!
Post by: Lionel Debroux on September 09, 2012, 09:32:07 am

I meant, have you used install_tilp.sh to build TILP ? :)
On Ubuntu 12.04, the TILP II version is 1.13 (it should tell you so in the terminal), which is more than three years old. As I mentioned above, there have been many improvements in the code base since then (including recent changes that should reduce the chance of character-encoding-related trouble). Please get a recent version of TILP through install_tilp.sh, TILP II 1.13 has been unsupported for a long time ;)

Title: Re: Tilp isn't working!
Post by: Jim Bauwens on September 09, 2012, 09:51:50 am

http://ourl.ca/12289 contains some details on how to use that script.
Shouldn't be too hard to follow :)

Title: Re: Tilp isn't working!
Post by: dinosteven on September 09, 2012, 10:18:41 pm

Wait so I can't use the standard ">./configure >sudo make >sudo make install"?

Title: Re: Tilp isn't working!
Post by: Lionel Debroux on September 10, 2012, 01:15:50 am

That's indeed what the core of install_tilp.sh does, as libticonv, libtifiles, libticables, libticalcs (collectively known as "libti*"), gfm and tilp are based on autotools.

However, install_tilp.sh does much more than this: some sanity checking, friendly reminders at the beginning and at the end, downloading the latest development sources for each of the six pieces (either as a whole, or just updating them if a working copy is found), building the six pieces in the appropriate order, and stopping upon the first error (if any - this script has been used successfully by dozens of persons on a variety of Linux distros, especially Debian and its derivatives, so by now, errors are almost always due to the user) :)

TILP and gfm aren't the only users of libti*, there are also TIEmu (TI-68k emulator) and TilEm (TI-Z80 emulator). Having a single common code base for multiple clients is the reason why libti* exist in the first place. 4 libraries may seem a lot, but in fact, that's too low, the code base is not modular enough.

Title: Re: Tilp isn't working!
Post by: Darl181 on September 10, 2012, 01:33:11 am

Using that post, just installed it on Ubuntu 12.04 on a flash drive, it's working with the CX \o/

Title: Re: Tilp isn't working!
Post by: shmibs on September 14, 2012, 06:25:17 pm

i can't get it to build under 64 bit arch. it fails to compile libticables:

Code: [Select]

make[2]: Entering directory `/root/lpg/tilp/libticables/tests'
/bin/sh ../libtool --tag=CC   --mode=link gcc  -g -O2 -D__LINUX__ -fvisibility=hidden   -o test_ticables_2 test_ticables_2.o ../src/libticables2.la
libtool: link: gcc -g -O2 -D__LINUX__ -fvisibility=hidden -o .libs/test_ticables_2 test_ticables_2.o  ../src/.libs/libticables2.so
../src/.libs/libticables2.so: undefined reference to `usb_error_type'
../src/.libs/libticables2.so: undefined reference to `usb_debug'
../src/.libs/libticables2.so: undefined reference to `usb_error_str'
collect2: error: ld returned 1 exit status
make[2]: *** [test_ticables_2] Error 1
make[2]: Leaving directory `/root/lpg/tilp/libticables/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/lpg/tilp/libticables'
make: *** [all] Error 2

i thought this may have something to do with the warning in the script that not using libusb 1.0 may cause things to fail, but it appears that i have libusb-1.0.so.0.1.0 installed. what else could be the problem here?

Title: Re: Tilp isn't working!
Post by: Lionel Debroux on September 15, 2012, 01:41:11 am

You need to modify install_tilp.sh so as to use libusb 1.0 proper for compiling libticables, instead of 0.1 / the silly 0.1 compatibility layer for 1.0 used for most Linux distros, the latter which does not work for the purposes of libticables :)
Search for "--enable-libusb10" in install_tilp.sh.

Debian and derivatives keep a proper libusb 0.1 version, so I don't have the problem; but at some point, I guess I'll have to switch the default to libusb 1.0.

Title: Re: Tilp isn't working!
Post by: shmibs on September 15, 2012, 02:21:50 pm

thanks! it works =D
oh, and is there any reason why this shouldn't work over usb 3.0 ports? detecting the device and listing files both function, but receiving returns an error unless i plug it in a 2.0 port.

Title: Re: Tilp isn't working!
Post by: Lionel Debroux on September 15, 2012, 02:41:54 pm

Hmm... I used an USB 3.0 port, precisely, for sending and receiving multiple files today :D
That was with the libusb 0.1 backend, though.
What OS version is your calculator running ? I used 3.1.0.392.

Title: Re: Tilp isn't working!
Post by: shmibs on September 15, 2012, 03:08:46 pm

this is an 84+se on 2.43
and this is odd. it always works over the 2.0 port, but sometimes it does and sometimes it doesn't over 3.0. when it fails, it's timing out.
i'm using a longer than normal (about 2 metres) usb-mini usb cable to connect, if that makes a difference.

Title: Re: Tilp isn't working!
Post by: Jim Bauwens on September 15, 2012, 05:17:08 pm

Maybe it's the kernel driver that has problems. Or libusb, but I don't think libusb should have any problem as the kernel provides the USB support.
Maybe you can find something interesting in dmesg ?

Title: Re: Tilp isn't working!
Post by: shmibs on September 15, 2012, 06:42:11 pm

gui:

Code: [Select]

Msg: timeout occured while reading from the device.
Cause: check that link cable is plugged and/or the calculator is ready.
System: File exists (errno = 17)
terminal:

Code: [Select]

tilp-INFO: Opening cable DirectLink on port #1 to communicate with calculator TI84+ USB
ticables-INFO: Check for lib-usb support:
ticables-INFO:     usb support: available.
ticables-INFO: Check for lib-usb usability:
ticables-INFO:     usb filesystem (/dev/bus/usb/): mounted
ticables-INFO:  found TI-84 Plus Silver Edition on #1, version <1.10>

ticables-INFO: found bulk in endpoint 0x81

ticables-INFO: found bulk out endpoint 0x02

ticalcs-INFO: Checking hand-held status:
ticalcs-INFO:   PC->TI: Buffer Size Request (1024 bytes)

(tilp:2787): ticables-WARNING **: slv_bulk_read (Operation timed out).

ticalcs-INFO: Checking hand-held status:
ticalcs-INFO:   PC->TI: Buffer Size Request (1024 bytes)

(tilp:2787): ticables-WARNING **: slv_bulk_read (Operation timed out).

ticables-INFO:  found TI-84 Plus Silver Edition on #1, version <1.10>

ticables-INFO: found bulk in endpoint 0x81

ticables-INFO: found bulk out endpoint 0x02
dmesg:

Code: [Select]

[ 9279.488658] usb 1-2: new full-speed USB device number 4 using xhci_hcd
[ 9294.331481] usb 1-2: reset full-speed USB device number 4 using xhci_hcd
[ 9294.345761] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802026a0700
[ 9294.345769] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802026a0740


Title: Re: Tilp isn't working!
Post by: Jim Bauwens on September 17, 2012, 03:25:07 am

Looks like several more people have issues with USB 3.0 ports, and are getting the same errors in dmesg.
So this looks like a kernel module problem to me. You could try upgrading your kernel, but of course that depends what distro you are running.