Menu

#8 Support homemade grey cable on USB

open
nobody
None
5
2014-08-17
2008-03-16
No

Please support homemade grey cable on USB port.
not /dev/ttyS0...3

with:
- USB Serial converter: /dev/ttyUSB0...3
with
- Homemade Grey cable with PIC18F2550: /dev/ttyACM0

USB Grey cable construction:
http://www.microtronic.es/index.php?option=com_content&task=view&id=14&Itemid=29

On any notebook (& desktop PC), not have serial port and paralell port, only USB ports.

IgiBoy

Discussion

  • Nobody/Anonymous

    I concur. Serial/paralell ports are also rare on new motherboards these days ;)

    I connect my TI-89 with a genuine Gray TI-Graph Link and an USB-serial converter (TRENDnet TU-S9, Prolific PL2303 chipset).
    I made a quick trick (should make a udev rule...) to make it work under TiLP-I 6.80 : # rm /dev/ttyS0 && ln -b /dev/ttyUSB0 /dev/ttyS0
    It also works under TI-Graph Link 89 with Wine. But TiLP-II 1.12 doesn't find my calculator, even with root privileges.

    Could TiLP-II scan serial cable throught /dev/ttyUSB[0-n] and not only /dev/ttyS[0-4]?

    Thanks.

    PS: /dev/ttyUSB0 and /dev/ttyS0 group is dialout and i'm member of it.

    TiLP2 - Version 1.12, (C) 1999-2008 Romain Lievin
    THIS PROGRAM COMES WITH ABSOLUTELY NO WARRANTY
    PLEASE READ THE DOCUMENTATION FOR DETAILS
    built on Sep 6 2008 10:55:59
    tilp-INFO: setlocale: en_US.UTF-8
    tilp-INFO: bindtextdomain: /usr/share/locale/
    tilp-INFO: textdomain: tilp2
    ticables-INFO: ticables library version 1.2.0
    ticables-INFO: setlocale: en_US.UTF-8
    ticables-INFO: bindtextdomain: /usr/share/locale
    ticables-INFO: textdomain: libticables2
    ticables-INFO: kernel: 2.6.24-19-generic
    tifiles-INFO: tifiles library version 1.1.1
    tifiles-INFO: setlocale: en_US.UTF-8
    tifiles-INFO: bindtextdomain: /usr/share/locale
    tifiles-INFO: textdomain: libtifiles2
    ticalcs-INFO: ticalcs library version 1.1.2
    ticalcs-INFO: setlocale: en_US.UTF-8
    ticalcs-INFO: bindtextdomain: /usr/share/locale
    ticalcs-INFO: textdomain: libticalcs2
    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: Check for tty support:
    ticables-INFO: tty support: available.
    ticables-INFO: Check for tty usability:
    ticables-INFO: node /dev/ttyS0: exists
    ticables-INFO: node /dev/ttyS0: accessible
    tilp-INFO: Msg: unable to use serial (/dev/ttySx) device.
    Cause: the /dev/ttySx node doesn't exist or you don't have required permissions. How to grant permission to devices to the user depends on the distribution, it may involve adding the user to a group such as 'dialout' or 'uucp'. This can be done by editing /etc/group and add the username after the ':'. Example: dialout❌20:romain
    System: Invalid argument (errno = 22)

    tilp-INFO: Msg: attempting to use a cable which has not been open before.
    Cause: Internal error.
    System: Invalid argument (errno = 22)

    kbuildsycoca running...

     
  • Nobody/Anonymous

    I concur. Serial/paralell ports are also rare on new motherboards these days ;)

    I connect my TI-89 with a genuine Gray TI-Graph Link and an USB-serial converter (TRENDnet TU-S9, Prolific PL2303 chipset).
    I made a quick trick (should make a udev rule...) to make it work under TiLP-I 6.80 : # rm /dev/ttyS0 && ln -b /dev/ttyUSB0 /dev/ttyS0
    It also works under TI-Graph Link 89 with Wine. But TiLP-II 1.12 doesn't find my calculator, even with root privileges.

    Could TiLP-II scan serial cable throught /dev/ttyUSB[0-n] and not only /dev/ttyS[0-4]?

    Thanks.

    PS: /dev/ttyUSB0 and /dev/ttyS0 group is dialout and i'm member of it.

    TiLP2 - Version 1.12, (C) 1999-2008 Romain Lievin
    THIS PROGRAM COMES WITH ABSOLUTELY NO WARRANTY
    PLEASE READ THE DOCUMENTATION FOR DETAILS
    built on Sep 6 2008 10:55:59
    tilp-INFO: setlocale: en_US.UTF-8
    tilp-INFO: bindtextdomain: /usr/share/locale/
    tilp-INFO: textdomain: tilp2
    ticables-INFO: ticables library version 1.2.0
    ticables-INFO: setlocale: en_US.UTF-8
    ticables-INFO: bindtextdomain: /usr/share/locale
    ticables-INFO: textdomain: libticables2
    ticables-INFO: kernel: 2.6.24-19-generic
    tifiles-INFO: tifiles library version 1.1.1
    tifiles-INFO: setlocale: en_US.UTF-8
    tifiles-INFO: bindtextdomain: /usr/share/locale
    tifiles-INFO: textdomain: libtifiles2
    ticalcs-INFO: ticalcs library version 1.1.2
    ticalcs-INFO: setlocale: en_US.UTF-8
    ticalcs-INFO: bindtextdomain: /usr/share/locale
    ticalcs-INFO: textdomain: libticalcs2
    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: Check for tty support:
    ticables-INFO: tty support: available.
    ticables-INFO: Check for tty usability:
    ticables-INFO: node /dev/ttyS0: exists
    ticables-INFO: node /dev/ttyS0: accessible
    tilp-INFO: Msg: unable to use serial (/dev/ttySx) device.
    Cause: the /dev/ttySx node doesn't exist or you don't have required permissions. How to grant permission to devices to the user depends on the distribution, it may involve adding the user to a group such as 'dialout' or 'uucp'. This can be done by editing /etc/group and add the username after the ':'. Example: dialout❌20:romain
    System: Invalid argument (errno = 22)

    tilp-INFO: Msg: attempting to use a cable which has not been open before.
    Cause: Internal error.
    System: Invalid argument (errno = 22)

    kbuildsycoca running...

     
  • Romain Liévin

    Romain Liévin - 2008-10-31

    Using a USB adapter could work but ticables2 library use hard-coded paths for serial devices (/dev/ttySx).

    If needed, I can tell you which file you can patch (just 1 line!).

     
  • Nobody/Anonymous

    > If needed, I can tell you which file you can patch (just 1 line!).

    Please do so :-)

    Let me guess...
    file:linux/link_gry.c,
    line:case PORT_1: h->address = 0x3f8; h->device = strdup("/dev/ttyS0"); break;

    Thank you for your concern!