Could not open IP socket or Error opening COM/USB Por

The meeting point for people using one of the IRTrans OEM Display devices

IMPORTANT: Please note that these devices are neither manufactured nor sold by IRTrans. That means we cannot answer any hardware related questions here. Furthermore there is no direct Email support through IRTrans available for these devices.

Moderator: marcus

Could not open IP socket or Error opening COM/USB Por

Postby samuilinks » Fri 30. May 2008, 06:06

I have an Origenae S16T case with an IR211 IR receiver but cannot get it to work. The Touchscreen works perfectly but the Remote control still doesnt.

When i start irserver /dev/ttyUSB0 it comes with the error "Could not open IP socket" and if i start with sudo it comes with the following error: "Error opening COM/USB Port / LAN Device.

I am using Ubuntu 8.04 final with latest updates, IRTrans 5.9.07, and the receiver manufacturer is Future Device International, Ltd. VendorID: 0x0403 ProductID 0xfc60.

The ORIGENae support doesnt have any help available, so please can any of you help me out here? :(
samuilinks
 
Posts: 3
Joined: Fri 30. May 2008, 05:10

Re: Could not open IP socket or Error opening COM/USB Por

Postby IRTrans » Fri 30. May 2008, 10:59

The irserver SW can only run as the user root or with superuser rights as it is using priviliged TCP/IP sockets.

Are you sure that /dev/ttyUSB0 is the correct port for your device ?

Otherwise it might be a hardware problem - are you sure everything is connected correctly (most important the +5V standby) ?
Please note that we cannot help you with hardware problems as we do not know the hardware design of these OEM devices.

IRTrans
IRTrans
Administrator
 
Posts: 2115
Joined: Mon 21. Apr 2008, 23:32

Re: Could not open IP socket or Error opening COM/USB Por

Postby samuilinks » Sun 1. Jun 2008, 05:37

I think it is /dev/ttyUSB0, can i check this somewhere?

lsusb output gives:
Code: Select all

Bus 004 Device 002: ID 0403:fc60 Future Technology Devices International, Ltd
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0xfc60
  bcdDevice            6.00
  iManufacturer           1 MConsult
  iProduct                2 IRTrans USB
  iSerial                 3 MMUN0000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               50mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 IRTrans USB
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)


dmesg|grep usb gives the following output
Code: Select all
[   41.082123] usbcore: registered new interface driver usbfs
[   41.082143] usbcore: registered new interface driver hub
[   41.082173] usbcore: registered new device driver usb
[   41.084088] usb usb1: configuration #1 chosen from 1 choice
[   41.186901] usb usb2: configuration #1 chosen from 1 choice
[   41.290766] usb usb3: configuration #1 chosen from 1 choice
[   41.394651] usb usb4: configuration #1 chosen from 1 choice
[   41.529309] usb 2-1: new low speed USB device using uhci_hcd and address 2
[   41.542521] usb usb5: configuration #1 chosen from 1 choice
[   42.404422] usb 5-5: new high speed USB device using ehci_hcd and address 3
[   42.540400] usb 5-5: configuration #1 chosen from 1 choice
[   42.784216] usb 5-6: new high speed USB device using ehci_hcd and address 4
[   42.913245] usb 5-6: configuration #1 chosen from 1 choice
[   43.255616] usbcore: registered new interface driver libusual
[   43.495330] usb 2-1: new low speed USB device using uhci_hcd and address 3
[   43.743436] usb 2-1: configuration #1 chosen from 1 choice
[   43.816571] usb-storage: device found at 3
[   43.816572] usb-storage: waiting for device to settle before scanning
[   43.947148] usb 5-6.2: new full speed USB device using ehci_hcd and address 6
[   44.040424] usb 5-6.2: configuration #1 chosen from 1 choice
[   44.041454] usbcore: registered new interface driver usb-storage
[   44.278581] usb 4-2: new full speed USB device using uhci_hcd and address 2
[   44.477763] usb 4-2: configuration #1 chosen from 1 choice
[   48.810362] usb-storage: device scan complete
[   51.819860] usbcore: registered new interface driver usbserial
[   51.819875] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[   51.819908] usbcore: registered new interface driver usbserial_generic
[   51.819909] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   51.844468] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
[   51.844518] /build/buildd/linux-2.6.24/drivers/usb/serial/ftdi_sio.c: Detected FT232RL
[   51.844593] usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB0
[   51.844601] usbcore: registered new interface driver ftdi_sio
[   51.844603] /build/buildd/linux-2.6.24/drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
[   51.861996] usbcore: registered new interface driver hiddev
[   53.377872] hiddev96hidraw0: USB HID v1.10 Device [American Power Conversion Back-UPS CS 500 FW:808.q8.I USB FW:q8] on usb-0000:00:1d.1-1
[   63.367049] /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed
[   63.367059] /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: timeout initializing reports
[   63.367119] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:1d.7/usb5/5-6/5-6.2/5-6.2:1.0/input/input6
[   63.390980] input,hiddev97,hidraw1: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:1d.7-6.2
[   63.391004] usbcore: registered new interface driver usbhid
[   63.391009] /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver


Information about the IR210 (IR Receiver inside the Origenae S16T) can be found here: http://www.origenae.com/en/accessory_ir210.htm

The +5V Standby is plugged in ok. The Case also includes a 7" Touchscreen that is working correctly, and the Remote Control of the LCD screen menu is working over the same IR-Receiver and shows menu and options.

Can i give you more information that can help solve the problem?

thanks in advance.
samuilinks
 
Posts: 3
Joined: Fri 30. May 2008, 05:10

Re: Could not open IP socket or Error opening COM/USB Por

Postby IRTrans » Sun 1. Jun 2008, 11:32

Hi,
the device node is surely correct.

I am quite sure that this is an hardware issue.

As this receiver is non of our products (it is designed and build and sold by OrigenAE) we cannot help you any further here.

Please contact either your dealer or OrigenAE.

IRTrans
IRTrans
Administrator
 
Posts: 2115
Joined: Mon 21. Apr 2008, 23:32

Re: Could not open IP socket or Error opening COM/USB Por

Postby samuilinks » Mon 2. Jun 2008, 03:55

IRTrans wrote:Hi,
the device node is surely correct.

I am quite sure that this is an hardware issue.

As this receiver is non of our products (it is designed and build and sold by OrigenAE) we cannot help you any further here.

Please contact either your dealer or OrigenAE.

IRTrans


It is now working with: sudo irserver /dev/ttyUSB0.

Now i need to autostart it, with the parameter /dev/ttyUSB0 is that possible?
samuilinks
 
Posts: 3
Joined: Fri 30. May 2008, 05:10

Re: Could not open IP socket or Error opening COM/USB Por

Postby IRTrans » Mon 2. Jun 2008, 10:38

You will have to look how your LINUX handles autostart of services (e.g. /etc/init.d)

IRTrans
IRTrans
Administrator
 
Posts: 2115
Joined: Mon 21. Apr 2008, 23:32


Return to OEM Devices

Who is online

Users browsing this forum: No registered users and 7 guests

cron