Re: [irda-users] Sitecom infrared device

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Giuseppe,
I have had the same problem but have not been able to get the solution
to my problem on this list.

Below is the information sitecom sent me.  It did not help me but may
help you.

---------------------------------------------------------------------------=
---------------------------------
Linux HOWTO
CN-100 IrDA USB adapter

1. Requirements

For using the CN-100 IrDA adapter, your system must be able to meet the
following requirements :

One free USB port
Linux kernel 2.4.x or higher
Linux installation CD=92s (unless you have already installed irda-tools)

2. Installation

The CN-100 can be plugged into any free USB port. After you have plugged
in the CN-100 turn on the computer and log in as root. First you must
make sure the device has been detected in the system. To do this type
the following at the command prompt:

[linuxprompt]# dmesg

You will have to watch for messages resembling something like this:

hub.c: USB new device connect on bus1/2, assigned device number 2
usb.c: USB device 2 (vend/prod 0x50f/0x180) is not claimed by any active
driver.
usb.c: registered new driver serial
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial Driver core v1.4
usbserial.c: USB Serial support registered for IR Dongle
usbserial.c: IR Dongle converter detected
usbserial.c: IR Dongle converter now attached to ttyUSB0 (or usb/tts/0
for devfs)
ir-usb.c: USB IR Dongle driver v0.4
usb.c: registered new driver irda-usb
USB IrDA support registered

This means the device has been successfully detected. The problem is
that due to a bug in the linux kernel the device is linked to the wrong
port (ttyUSB0). Therefore you must edit the file /etc/hotplug/blacklist
and add the bold printed line as stated below.

#
# Listing a module here prevents the hotplug scripts from loading it.
# Usually that'd be so that some other driver will bind it instead,
# no matter which driver happens to get probed first.  Sometimes user
# mode tools can also control driver binding.
#
# Syntax:  driver name alone (without any spaces) on a line. Other
# lines are ignored.
#

# uhci ... usb-uhci handles the same pci class
usb-uhci
ir-usb

# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
de4x5
# At least 2.4.3 and later xircom_tulip doesn't have that conflict
# xircom_tulip_cb
dmfe

After you have done this please make sure to install the IrDA tool
package (commonly known as irda-tools), this should be located on the
first installation CD of your Linux OS (packages can be installed by
using i.e. kpackage).

Once the package is installed restart the computer.

After the computer has restarted check again wether or not the device is
recognized using the dmesg command. If everything has gone well, you
should be able to see something like this.

hub.c: USB new device connect on bus1/2, assigned device number 2
usb.c: USB device 2 (vend/prod 0x50f/0x180) is not claimed by any active
driver.
usb.c: registered new driver irda-usb
IRDA-USB found at address 2, Vendor: 50f, Product: 180
usb.c: ignoring set_interface for dev 2, iface 0, alt 0
IrDA: Registered device irda0
USB IrDA support registered

This means the IrDA device has been detected and this time it has been
linked with the idra0 port.

Now to get Linux to communicate with the IrDA device we will need to run
the following command.

[linuxprompt]# irattach irda0 =96s 1

To check wether there is communication between Linux and the CN-100 use
the next command.

[linuxprompt]# irdadump

If all has gone well, you should be able to something like this.

11:55:54.475191 xid:cmd 52ef4a59 > ffffffff S=3D6 s=3D0 (14)
11:55:54.565175 xid:cmd 52ef4a59 > ffffffff S=3D6 s=3D1 (14)
11:55:54.655175 xid:cmd 52ef4a59 > ffffffff S=3D6 s=3D2 (14)
11:55:54.745177 xid:cmd 52ef4a59 > ffffffff S=3D6 s=3D3 (14)
11:55:54.835175 xid:cmd 52ef4a59 > ffffffff S=3D6 s=3D4 (14)
11:55:54.925175 xid:cmd 52ef4a59 > ffffffff S=3D6 s=3D5 (14)
11:55:55.015177 xid:cmd 52ef4a59 > ffffffff S=3D6 s=3D* localhost hint=3D04=
00
[ Computer ] (25)
If you see this communication between the CN-100 and Linux is going
well.

We have noticed that on some occasions communication will not be present
after running irattach the first time. To solve this, type =93killall
irattach=94 and then run irattach in the same way as stated above.
3. Examples of use

ATTENTION: This chapter only gives an example of one of the uses for the
CN-100. Sitecom can not be held responsible for wether or not this will
work in individual cases. If you are experiencing any problems with the
example shown below we advise you consult the many HOWTO=92s that are
freely available on the internet.

3.1 J-Pilot

In our tests with the CN-100 we succesfully managed to HotSync a Palm
m105 with the third party program J-Pilot 0.99.2 under RedHat Linux 7.3.

3.2 Problems with J-Pilot (and may be the cause of other malfunctions)

J-Pilot  will not connect to the Palm

It has come to our attention that a HotSync with J-Pilot will only work
when the HotSync is enabled on the Palm before the sync button is
pressed in J-Pilot. This may also be valid for other sync-programs.

J-Pilot reports that the Palm has been reset (no userid)

This problem can be solved by using the install-user command, which is
also a part of the irda-tools package. It is used as follows:
install-user irda0 <username> <id>.

So for example you might want to try something like:

[linuxprompt]# install-user irda0 =93Sitecom=94 12345

This will set the Palm username to Sitecom and the Palm userid to 12345.
Then try J-Pilot again.
---------------------------------------------------------------------------=
--------------------------------

Kiggundu

On Thu, 2002-10-24 at 13:13, Giuseppe Furlan wrote:

    Hi
    i'm Joseph from Italy and i can't speak english very well! sorry!
   =20
    To communicate with Motorola Timeport IrDA port I have to link the Site=
com
    infrared device to a usb device (like ttyUSB0).
    I have istalled irda-tools on my laptop ( Debian distribution ) and my
    configuration is:
   =20
    cat /etc/irda.conf
    #irda.conf Version: 1.0
    IRDADEV=3D/dev/ttyUSB0
    DONGLE=3Dgirbil
    DISCOVERY=3D-s
    ENABLE=3Dyes # if you do not need to start irattach, set "no"
   =20
    Then I have to "attach" the infrared port to the device with "irattach:
    irattach /dev/ttyUSB0
   =20
    After put the Sitecom infrared device in the USB port of the notebook a=
nd=20
    check the log file by typing "tail /var/log/messages"; the result is li=
ke
    this:
   =20
    Oct 24 09:57:48 furlinux kernel: IrCOMM protocol (Dag Brattli)
    Oct 24 11:15:37 furlinux kernel: hub.c: USB new device connect on bus1/=
1,
    assigned device number 2
    Oct 24 11:15:37 furlinux kernel: usb.c: USB device 2 (vend/prod
    0x50f/0x180) is not claimed by any active driver.
    Oct 24 11:15:38 furlinux kernel: usb.c: registered new driver irda-usb
    Oct 24 11:15:38 furlinux kernel: IRDA-USB found at address 2, Vendor: 5=
0f,
    Product: 180
    Oct 24 11:15:38 furlinux kernel: usb.c: ignoring set_interface for dev =
2,
    iface 0, alt 0
    Oct 24 11:15:39 furlinux kernel: IrDA: Registered device irda0
    Oct 24 11:15:39 furlinux kernel: USB IrDA support registered
    Oct 24 11:15:39 furlinux kernel: usb.c: registered new driver serial
    Oct 24 11:15:39 furlinux kernel: usbserial.c: USB Serial support
    registered for Generic
    Oct 24 11:15:39 furlinux kernel: usbserial.c: USB Serial Driver core v1=
.4
    Oct 24 11:15:39 furlinux kernel: usbserial.c: USB Serial support
    registered for IR Dongle
    Oct 24 11:15:39 furlinux kernel: ir-usb.c: USB IR Dongle driver v0.4
   =20
   =20
    Using minicom to "communicate" with my modem...let's type:
   =20
    minicom -s
   =20
    ...select "Serial port setup" and be sure to set up the parameters like=
:
   =20
         A - Serial Device         : /dev/ircomm0
         B - Lockfile Location     : /var/lock
         C - Callin Program        :
         D - Callout Program       :
         E - Bps/Par/Bits          : 38400 8N1
         F - Hardware Flow Control : No
         G - Software Flow Control : No
   =20
    Then put the cellphone in front of Sitecom infrared device and ...NOTHI=
NG
    ...doesn't work
   =20
    please let me know as soon as possible
    Thanks in advanced
   =20
    Bye
    Joseph
   =20
   =20
   =20
    -------------------------------------------------------
    This sf.net email is sponsored by: Influence the future=20
    of Java(TM) technology. Join the Java Community=20
    Process(SM) (JCP(SM)) program now.=20
    http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/java=
vote
    _______________________________________________
    irda-users mailing list
    ird...@li...
    http://lists.sourceforge.net/lists/listinfo/irda-users
   =20

--=20
****************                          *****************************
Kiggundu Mukasa                          # Computer Network
Consultancy###
KYM-NET LTD.                             # Intranets & Internet
Solutions#
House 73              	                 # Data Communication Service
####
Plot 7, Kent Lane, off Kiira Raod
P.O. Box 173 Kampala, Uganda            =20
Tel:     +256 71 221141
         +256 77 221141
Fax:     +1-401-696-9767
*************************************************************************