On Fri, Aug 27, 2010 at 04:19:27PM -0500, littleideas wrote:
> Okay ... now after i tried to reinstall the Program for the datalogger this ALSO does not work any more.
>
> I give it up... Thanks for your help!
Well, I don't know why you are giving up: it is looking quite promising.
As for re installing, you seem to be back in wine.
As for clicking on the link to the driver, it should just display the
source of the driver, and if you scroll down (or use use ^F or whatever
your browser search sequence is & look for 0x10C4) you will eventually
find the line that I quoted. That merely confirms that the driver
already knows about your data logger, and that it should get loaded
automagically when you plug it in.
So that link was just for information.
You don't seem to have actually found out whether the driver is loaded.
Does that mean that you just don't understand how to read
/var/log/messages, display lsmod or look for /dev/ttyUSB*?
Simple instructions:
1) Plug in your logger.
2) In a terminal, type
less /var/log/messages
{if that doesn't work, do it as root or use sudo};
scroll down towards the end { esc > } will get you there immediately};
Look for messages about the logger being plugged in.
For example, here is what happens when I plug in one of my mobiles
using the same chip:
------------------------------------------------------------------------------------
Aug 28 08:39:40 elf kernel: [ 1628.808139] usb 2-1: new full speed USB device using uhci_hcd and address 2
Aug 28 08:39:40 elf kernel: [ 1628.971181] usb 2-1: New USB device found, idVendor=0489, idProduct=e000
Aug 28 08:39:40 elf kernel: [ 1628.971199] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 28 08:39:40 elf kernel: [ 1628.971211] usb 2-1: Product: TC 300
Aug 28 08:39:40 elf kernel: [ 1628.971221] usb 2-1: Manufacturer: Silicon Labs
Aug 28 08:39:40 elf kernel: [ 1628.971230] usb 2-1: SerialNumber: 0001
Aug 28 08:39:40 elf kernel: [ 1628.971845] usb 2-1: configuration #1 chosen from 1 choic
Aug 28 08:39:40 elf kernel: [ 1629.011334] usbcore: registered new interface driver usbserial
Aug 28 08:39:40 elf kernel: [ 1629.012303] USB Serial support registered for generic
Aug 28 08:39:40 elf kernel: [ 1629.013145] usbcore: registered new interface driver usbserial_generic
Aug 28 08:39:40 elf kernel: [ 1629.013155] usbserial: USB Serial Driver core
Aug 28 08:39:40 elf kernel: [ 1629.019656] USB Serial support registered for cp210x
Aug 28 08:39:40 elf kernel: [ 1629.020672] cp210x 2-1:1.0: cp210x converter detected
Aug 28 08:39:40 elf kernel: [ 1629.132147] usb 2-1: reset full speed USB device using uhci_hcd and address 2
Aug 28 08:39:40 elf kernel: [ 1629.281764] usb 2-1: cp210x converter now attached to ttyUSB0
Aug 28 08:39:40 elf kernel: [ 1629.281843] usbcore: registered new interface driver cp210x
Aug 28 08:39:40 elf kernel: [ 1629.281855] cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
---------------------------------------------------------------------------------------------------------
If you see something similar & particularly the last line mentioning the
cp210x driver, then all is well.
As an additional check, although it is not necessary if the message is
ok, (3) in a terminal type:
lsmod |grep cp210x
{again you might need to do that as root or use sudo}
On my machine, I get:
--------------------------------------------------
# lsmod |grep cp210x
cp210x 9417 0
usbserial 21847 1 cp210x
usbcore 98402 6 cp210x,usbserial,uvcvideo,uhci_hcd,ehci_hcd
---------------------------------------------------------------------------
The first line above shows that the cp210x driver has loaded.
The last step (4) is to check that /dev/ttyUSB(something) has been created.
As usual in a terminal, type
ls -l /dev/ttyUSB*
Example, on my machine this gives:
----------------------------------------------------------
$ ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Aug 28 08:39 /dev/ttyUSB0
----------------------------------------------------------
If you plug and unplug, that might change to ttyUSB1.
If any on these steps fails, then I may be able to suggest how to fix
the problem.
As for the failure to re-install the program under wine, a wine expert
can probably suggest a solution: probably just need to clean out
registry or other wine files. But it is pointless until you have the
cp210x driver working as above. In case you don't realise, the
Windoze driver under wine is completely replaced by cp210x. When
you have the data logger working under wine, wine will use cp210x, so
forget the windoze driver garbage.
ael
