Heizraum,
why do you think, this has anything to do with VBus?
Hardy
Your controller will send a stream of data over and over without any
initialization
> --
> You received this message because you are subscribed to the Google Groups
> "Resol Vbus" group.
> To post to this group, send email to resol...@googlegroups.com.
> To unsubscribe from this group, send email to
> resol-vbus+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/resol-vbus?hl=en.
>
>
--
Sent from my mobile device
How are you reading these data? What is your baud rate?Thanks for the very fast reply. So far I understand what you wrote. Below I show you what I get continously from the Deltasol (without any initialzation before of course :) ) I cannot find a AA ~ 170 dec there. I read from /dev/ttyUSB3 every second. But all I get is this output. 78 42 10 00 01 07 1d 7d 00 7e 00 05 7f 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7e 00 05 7e 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7e 00 05 7e 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7e 00 05 7e 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7d 00 05 7f 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7d 00 05 7f 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7d 00 05 7f 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7e 00 05 7e 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 78 42 10 00 01 07 1d 7e 00 7d 00 05 7f 38 22 38 22 05 46 00 00 00 00 00 7f 09 00 00 00 00 00 00 00 00 7f 00 00 00 04 00 7b 48 00 01 36 78 42 20 00 05 00 00 00 00 00 00 00 20 What do I not understand ?!?!
I believe you're receiving corrupt data (a very common occurrence). You need to read this thread:
http://groups.google.com/group/resol-vbus/browse_thread/thread/9bd08c12b4ccc50
Cat /dev/ttyUSB3 | hexdump
On 3/3/11, Heizraum <heiz...@gmail.com> wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "Resol Vbus" group.
> To post to this group, send email to resol...@googlegroups.com.
> To unsubscribe from this group, send email to
> resol-vbus+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/resol-vbus?hl=en.
>
>
--
--
Try that tty setup:
root@qnap110:~# stty -a -F /dev/ttyUSB0
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S;
susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1;
time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon
-ixoff -iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0
bs0 vt0 ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
-echoprt -echoctl -echoke
Hardy
I ran into a problem when using two usb adapter at the same time with
the same driver (I.e. Two pl2303), however I think this is unique to
that driver, but might be worth trying with only one installed if you
have two
> --
> You received this message because you are subscribed to the Google Groups
> "Resol Vbus" group.
> To post to this group, send email to resol...@googlegroups.com.
> To unsubscribe from this group, send email to
> resol-vbus+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/resol-vbus?hl=en.
>
>
--
On 3/4/11, Heizraum <heiz...@gmail.com> wrote:
Don't worry, the ftdi_sio driver shouldn't be actually a problem. I'm
using just the same VBus adapter like you (Resol) - and it's working for
me without a problem.
My 'server' for Deltasol data acquisition is a small QNAP NAS converted
to Debian. Current kernel is "Linux qnap110 2.6.32-trunk-kirkwood #1
Mon Jan 11 10:57:12 UTC 2010 armv5tel GNU/Linux".
'lsusb -t' shows
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 4: Dev 3, If 0, Class=vend., Driver=ftdi_sio, 12M
'lsusb -v' of the VBus adapter gives the following:
Bus 001 Device 003: ID 0403:6001 Future Technology Devices
International, Ltd FT232 USB-Serial (UART) IC
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 0x6001 FT232 USB-Serial (UART) IC
bcdDevice 6.00
iManufacturer 1 RESOL
iProduct 2 VBus▒ to USB
iSerial 3 RSS3UGWQ
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
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 VBus▒ to 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)
Perhaps that information could be of some help to you.
Hardy
PS: did you try my stty setup?
Is there a seriell one ?!?! Then it was never offered to me ! I would
prefer a VBUS/RS232 than a VBUS/usb.
--
My lsusb tells me
Port 4: Dev 3, If 0, Class=vend., Driver=ftdi_sio, 12M
Note the 'vend'. Don't know if this makes any difference...
> root@guru ~>lsusb -v
Where is the output of the ftdi_sio?
Hardy
That did not arrive here.
BTW what is your kernel version (uname -a)?
Hardy