Hi Shakti, Thank you for your response. On Tue, 2012-07-31 at 12:04 +0530, Shakthi Kannan wrote: > Hi Ankur: > > --- On Tue, Jul 31, 2012 at 11:09 AM, Ankur Sinha > <sanjay.ankur@xxxxxxxxx> wrote: > | The sensor is detected as /dev/ttyUSB0 > | > | I've tried both moserial and cutecom. > \-- > > Have you tried minicom? > I just did. I'm still reading up from the web on how to use it properly though. moserial is a little easier for dummies :) (minicom mentions stuff like "modem", and I'm not too sure about the relation between that and the sensor at the moment.) > --- > | all. Is there a way of "converting" ttyUSB0 to serial, i.e., ttyS*? (Is > | this an issue?) > \-- > > It is serial data transfer over USB. Okay. > > --- > | [100976.031277] usb 2-1.1: cp210x converter now attached to ttyUSB0 > \-- > > It gets connected as ttyUSB0. Aye. > > --- > | [102143.137564] usb 2-1.1: USB disconnect, device number 8 > | [102143.138220] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 > | [102143.138251] cp210x 2-1.1:1.0: device disconnected > \-- > > But, gets disconnected here. Do you still see /dev/ttyUSB0 in /dev after this? That snippet was when I connected and then I disconnected too. When I connect, it only says (which seems okay): > [108566.390712] usb 2-1.1: new full-speed USB device number 12 using ehci_hcd > [108566.477577] usb 2-1.1: New USB device found, idVendor=10c4, idProduct=ea60 > [108566.477582] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [108566.477586] usb 2-1.1: Product: CP2102 USB to UART Bridge Controller > [108566.477589] usb 2-1.1: Manufacturer: Silicon Labs > [108566.477591] usb 2-1.1: SerialNumber: 0001 > [108566.479479] cp210x 2-1.1:1.0: cp210x converter detected > [108566.553438] usb 2-1.1: reset full-speed USB device number 12 using ehci_hcd > [108566.639599] usb 2-1.1: cp210x converter now attached to ttyUSB0 > [root@ankur ~]# > Check your hardware manual to make sure you have the right hardware > setup to use serial communication. What should I be looking for please? They've provided a tool for windows which "works". Would you have a suggestion on how I could send hex data to the sensor? For instance, "a5005b" is supposed to be the PING command. I've been trying to send this from moserial (selecting hex from the menu), but I don't get a response somehow. The windows tool sends the same and receives a "00" response when I click on "read response" in the UI Some more info from the windows tool: baud rate: 921600 comm port: 4 data rate: 100hz The entire communication appears to be in hex.(Even the responses that the sensor sends are in hex.) -- Thanks, Warm regards, Ankur: "FranciscoD" Please only print if necessary. Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG http://fedoraproject.org/wiki/User:Ankursinha http://dodoincfedora.wordpress.com/
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ electronic-lab mailing list electronic-lab@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/electronic-lab
