Deltasol bs/4

488 views
Skip to first unread message

Heizraum

unread,
Mar 3, 2011, 2:18:18 PM3/3/11
to Resol Vbus
Hello all

I'm glad that I found this forum.
I already connected my central oven (Fröling FHG 3000) over rs232 into
mysql and internet.
I did it with perl, but this protocol keeps me busy.
Till now, I don't find a particular description how to initial the
vbus.

I connect under linux with perl to /dev/ttyUSB3. However.
All I get are these hex strings continuosly and with some values
changing:

78 42 10 00 01 07 1d 6a 00 68 00 05 28 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

I don'tknow what to send to get some values back. Any help
appreciated.

Best regards

Heizraum

Hardy Griech

unread,
Mar 3, 2011, 4:17:29 PM3/3/11
to resol...@googlegroups.com
On 03.03.2011 20:18, Heizraum wrote:
:

> I connect under linux with perl to /dev/ttyUSB3. However.
> All I get are these hex strings continuosly and with some values
> changing:
>
> 78 42 10 00 01 07 1d 6a 00 68 00 05 28 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
>
> I don'tknow what to send to get some values back. Any help
> appreciated.
:

Heizraum,

why do you think, this has anything to do with VBus?

Hardy

Andrew White

unread,
Mar 3, 2011, 5:24:42 PM3/3/11
to resol...@googlegroups.com
The vbus protocol info for your deltasol are on this groups page along
with some sample scripts.

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

Heizraum

unread,
Mar 3, 2011, 5:55:52 PM3/3/11
to Resol Vbus


Sorry that I didn't pointed out clearly whats my status so far.
I own a deltasol BS/4 which is connected over a VBUS/USB to my rs232.
This is connected into a guruplug server, which already servs
perfectly a 1wire temperature network and also maintaining data from
the Fröling oven s3100 (see http://froeling.foren-city.de for my
documentation)


The Docs found in this group/forum, for me it is not clear how to
initialize ("start talking to deltasol").

Maybe I'm too dumb to understand the scripts here.
But as I recognize, non of them are really talking to a serial
interface to send inital strings or reading from deltasol, nor do I
find a kind of step by step documentation for a basic communication.
As I understood, I have to send a initialization string starting with
"0xaa" to the device, with some other stuff.
Next in the vbus doc, I should send the source and destination adress.
Here I don't find the deltasol bs/4. And so on.
I just need to get the push to jump over the gap off my ignorance of
the basic communication rules.

Thanks for enlightning me :)

Regards

Heizi

Mark Richards

unread,
Mar 3, 2011, 6:02:54 PM3/3/11
to resol...@googlegroups.com
Heizi,

The VBUS data is sent asynchronously on a regular basis from a single control (bus master).  (regular basis = about once per second).

The data stream begins with  0xAA  and follows a format defined in the VBUS communications protocol (available in the documentation).

The data stream consists of a header and a certain number of frames containing data.  You must
1. Detect 0xAA
2. Read the header
3. Evaluate the header to determine what the message is and the number of frames
4. Read each frame and decode the data

This seems simple enough, but there are added issues including CRC checking and adjusting bytes that require it.

There is a transmission from the master that invites other units to take control of the bus.  This permits clients, in your case, to send requests to the master for certain other data that are not in the regular data stream (specifically - certain settings).

Hope this helps,

/m

Heizraum

unread,
Mar 3, 2011, 6:13:11 PM3/3/11
to Resol Vbus
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 ?!?!



Heizraum

unread,
Mar 3, 2011, 6:29:06 PM3/3/11
to Resol Vbus

I just checked it with a serial sniffer jpnevulator with same result

root@guru ~/heizung >jpnevulator --read -t /dev/ttyUSB3
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 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 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

Tim Bennett

unread,
Mar 3, 2011, 6:36:14 PM3/3/11
to resol...@googlegroups.com
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

Tim.


Mark Richards

unread,
Mar 3, 2011, 6:36:07 PM3/3/11
to resol...@googlegroups.com
On 3/3/2011 18:13, Heizraum wrote: 
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 ?!?!
How are you reading these data?  What is your baud rate?

If you ADD 0x32 to 0x78 you get your 0xAA.   Only a quick review but the rest does not make much sense.

The communications protocol is 9600bd 8 data bits 1 stop bit no parity.

A typical header sequence for the RESOL DeltaSol BS Plus looks like this:

    AA 10 00 21 42 10 00 01 07 74

I don't find the BS/4 in Resol's protocol specifications.  Perhaps it is called something else?

/m

Mark Richards

unread,
Mar 3, 2011, 6:39:57 PM3/3/11
to resol...@googlegroups.com
On 3/3/2011 18:36, Tim Bennett wrote:
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

Heh.  I should have asked what sort of adapter you're using.

That thread references a passive adapter that I designed which is NOT polarity insensitive.

If not the ones made by RESOL - in other words a hack of some kind like my own - you might try reversing the polarity of the VBUS lines.  Although these should be polarity insensitive, if you're using a passive method to connect to the vbus, you may have issues.

/m

Heizraum

unread,
Mar 3, 2011, 6:44:57 PM3/3/11
to Resol Vbus
Here my settings on Linux:

root@guru ~/heizung >stty -F /dev/ttyUSB3
speed 9600 baud; line = 0;
min = 1; time = 0;
ignbrk -brkint -icrnl -imaxbel
-opost
-isig -icanon -iexten -echo

and inside the perl script I initate

my $dev = $_[0];
$serial = Device::SerialPort->new($dev);
$serial->debug(1);
# Buffer leeren
$serial ->lookclear();

$| = 1;

$serial->user_msg(ON);
#$serial->baudrate(57600);
#$serial->baudrate(19200);
$serial->baudrate(9600);
$serial->databits(8);
$serial->parity("none");
$serial->stopbits(1);
$serial->handshake("off");


I accidently use aa original Resol vbus/usb device.

I'm just going to twist the polarity ! Interessting point.....

Heizraum

unread,
Mar 3, 2011, 6:53:39 PM3/3/11
to Resol Vbus

Ok changing the polarity didn't solve the problem :(
Now I play around with the speed. Maybe I get diffrent results.

Thanks again

Andrew White

unread,
Mar 3, 2011, 7:02:28 PM3/3/11
to resol...@googlegroups.com
Try

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.
>
>

--

Heizraum

unread,
Mar 3, 2011, 7:07:50 PM3/3/11
to Resol Vbus

root@guru ~/heizung >cat /dev/ttyUSB3|hexdump
0000000 4278 0020 0005 0000 0000 0000 7820 1042
0000010 0100 1d07 005f 006b 3005 2238 2238 4605
0000020 0000 0000 7f00 0009 0000 0000 0000 7f00
0000030 0000 0400 7b00 0048 3601 4278 0020 0005
0000040 0000 0000 0000 7820 1042 0100 1d07 005f
0000050 006b 3005 2238 2238 4605 0000 0000 7f00
0000060 0009 0000 0000 0000 7f00 0000 0400 7b00
0000070 0048 3601 4278 0020 0005 0000 0000 0000
0000080 7820 1042 0100 1d07 005e 006b 3105 2238
0000090 2238 4605 0000 0000 7f00 0009 0000 0000
00000a0 0000 7f00 0000 0400 7b00 0048 3601 4278
00000b0 0020 0005 0000 0000 0000 7820 1042 0100
00000c0 1d07 005f 006b 3005 2238 2238 4605 0000
00000d0 0000 7f00 0009 0000 0000 0000 7f00 0000
00000e0 0400 7b00 0048 3601 4278 0020 0005 0000
00000f0 0000 0000 7820 1042 0100 1d07 005f 006b
0000100 3005 2238 2238 4605 0000 0000 7f00 0009
0000110 0000 0000 0000 7f00 0000 0400 7b00 0048
0000120 3601 4278 0020 0005 0000 0000 0000 7820
0000130 1042 0100 1d07 005f 006b 3005 2238 2238
0000140 4605 0000 0000 7f00 0009 0000 0000 0000
0000150 7f00 0000 0400 7b00 0048 3601 4278 0020
0000160 0005 0000 0000 0000 7820 1042 0100 1d07
0000170 005e 006b 3105 2238 2238 4605 0000 0000
0000180 7f00 0009 0000 0000 0000 7f00 0000 0400
0000190 7b00 0048 3601 4278 0020 0005 0000 0000
00001a0 0000 7820 1042 0100 1d07 005e 006b 3105
00001b0 2238 2238 4605 0000 0000 7f00 0009 0000
00001c0 0000 0000 7f00 0000 0400 7b00 0048 3601
00001d0 4278 0020 0005 0000 0000 0000 7820 1042
00001e0 0100 1d07 005e 006b 3105 2238 2238 4605
00001f0 0000 0000 7f00 0009 0000 0000 0000 7f00
0000200 0000 0400 7b00 0048 3601 4278 0020 0005
0000210 0000 0000 0000 7820 1042 0100 1d07 005e
0000220 006b 3105 2238 2238 4605 0000 0000 7f00
0000230 0009 0000 0000 0000 7f00 0000 0400 7b00
0000240 0048 3601 4278 0020 0005 0000 0000 0000
0000250 7820 1042 0100 1d07 005e 006b 3105 2238
0000260 2238 4605 0000 0000 7f00 0009 0000 0000
0000270 0000 7f00 0000 0400 7b00 0048 3601 4278
0000280 0020 0005 0000 0000 0000 7820 1042 0100
0000290 1d07 005e 006b 3105 2238 2238 4605 0000
00002a0 0000 7f00 0009 0000 0000 0000 7f00 0000
00002b0 0400 7b00 0048 3601 4278 0020 0005 0000
^C
root@guru ~/heizung >

Andrew White

unread,
Mar 3, 2011, 7:25:31 PM3/3/11
to resol...@googlegroups.com
I don't see the magic AA as per the docs

a sample raw output of my system is 


see the AA or aa below.


cat raw.log | hexdump 

0000000 10aa 2100 1042 0100 7407 0149 0076 3a05
0000010 0172 0123 6701 0064 0001 1a00 036c 2e03
0000020 5f00 060a 0432 3900 0344 0261 5401 0002
0000030 0064 1900 00aa 2100 2042 0500 0000 0000
0000040 0000 7700 10aa 2100 1042 0100 7407 0149
0000050 0077 3905 0172 0123 6701 0064 0001 1a00
0000060 036c 2e03 5f00 060a 0432 3900 0344 0261
0000070 5401 0002 0064 1900 00aa 2100 2042 0500
0000080 0000 0000 0000 7700 10aa 2100 1042 0100
0000090 7407 0149 0077 3905 0172 0123 6701 0064
00000a0 0001 1a00 036c 2e03 5f00 060a 0432 3900
00000b0 0344 0261 5401 0002 0064 1900 00aa 2100
00000c0 2042 0500 0000 0000 0000 7700 10aa 2100
00000d0 1042 0100 7407 0149 0077 3905 0171 0122
00000e0 6901 0064 0001 1a00 036c 2e03 5f00 060a
00000f0 0432 3900 0344 0261 5401 0002 0064 1900
0000100 00aa 2100 2042 0500 0000 0000 0000 7700
0000110 10aa 2100 1042 0100 7407 0149 0077 3905
0000120 0171 0122 6901 0064 0001 1a00 036c 2e03
0000130 5f00 060a 0432 3900 0344 0261 5401 0002
0000140 0064 1900 00aa 2100 2042 0500 0000 0000
0000150 0000 7700                              
0000154


--

Heizraum

unread,
Mar 4, 2011, 6:13:47 AM3/4/11
to Resol Vbus
Now I connected the Deltasol to windows. Here it seems to work !
Below, this is a hexdump from windows raw data

I guess I have to do some reverse Engineering :)

BTW it say's

Target: DFA 0x0010
Source: Deltasol BS/Drainback 0x4278
Target: DFA 0x0010

root@guru ~ >cat RawData_20110304.log |hexdump
0000000 0000 4278 0020 0005 0000 0000 0000 aa20
0000010 0010 4278 0010 0701 731d 7200 0500 3815
0000020 3822 0522 0046 0000 0000 097f 0000 0000
0000030 0076 0000 0000 007f 0000 0004 487b 0000
0000040 0100 aa36 0000 4278 0020 0005 0000 0000
0000050 0000 aa20 0010 4278 0010 0701 741d 7200
0000060 0500 3814 3822 0522 0046 0000 0000 097f
0000070 0000 0000 0076 0000 0000 007f 0000 0004
0000080 487b 0000 0100 aa36 0000 4278 0020 0005
0000090 0000 0000 0000 aa20 0010 4278 0010 0701
00000a0 731d 7200 0500 3815 3822 0522 0046 0000
00000b0 0000 097f 0000 0000 0076 0000 0000 007f
00000c0 0000 0004 487b 0000 0100 aa36 0000 4278
00000d0 0020 0005 0000 0000 0000 aa20 0010 4278
00000e0 0010 0701 731d 7200 0500 3815 3822 0522
00000f0 0046 0000 0000 097f 0000 0000 0076 0000
0000100 0000 007f 0000 0004 487b 0000 0100 aa36
0000110 0000 4278 0020 0005 0000 0000 0000 aa20
0000120 0010 4278 0010 0701 741d 7200 0500 3814
0000130 3822 0522 0046 0000 0000 097f 0000 0000
0000140 0076 0000 0000 007f 0000 0004 487b 0000
0000150 0100 aa36 0000 4278 0020 0005 0000 0000
0000160 0000 aa20 0010 4278 0010 0701 741d 7300
0000170 0500 3813 3822 0522 0046 0000 0000 097f
0000180 0000 0000 0076 0000 0000 007f 0000 0004
0000190 487b 0000 0100 aa36 0000 4278 0020 0005
00001a0 0000 0000 0000 aa20 0010 4278 0010 0701
00001b0 741d 7200 0500 3814 3822 0522 0046 0000
00001c0 0000 097f 0000 0000 0076 0000 0000 007f
00001d0 0000 0004 487b 0000 0100 aa36 0000 4278
00001e0 0020 0005 0000 0000 0000 aa20 0010 4278
00001f0 0010 0701 741d 7200 0500 3814 3822 0522
0000200 0046 0000 0000 097f 0000 0000 0076 0000
0000210 0000 007f 0000 0004 487b 0000 0100 aa36
0000220 0000 4278 0020 0005 0000 0000 0000 aa20
0000230 0010 4278 0010 0701 731d 7300 0500 3814
0000240 3822 0522 0046 0000 0000 097f 0000 0000
0000250 0076 0000 0000 007f 0000 0004 487b 0000
0000260 0100 aa36 0000 4278 0020 0005 0000 0000
0000270 0000 aa20 0010 4278 0010 0701 731d 7200
0000280 0500 3815 3822 0522 0046 0000 0000 097f
0000290 0000 0000 0076 0000 0000 007f 0000 0004
00002a0 487b 0000 0100 aa36 0000 4278 0020 0005
00002b0 0000 0000 0000 aa20 0010 4278 0010 0701
00002c0 731d 7200 0500 3815 3822 0522 0046 0000
00002d0 0000 097f 0000 0000 0076 0000 0000 007f
00002e0 0000 0004 487b 0000 0100 aa36 0000 4278
00002f0 0020 0005 0000 0000 0000 aa20 0010 4278
0000300 0010 0701 741d 7200 0500 3814 3822 0522
0000310 0046 0000 0000 097f 0000 0000 0076 0000
0000320 0000 007f 0000 0004 487b 0000 0100 aa36
0000330 0000 4278 0020 0005 0000 0000 0000 aa20
0000340 0010 4278 0010 0701 731d 7200 0500 3815
0000350 3822 0522 0046 0000 0000 097f 0000 0000
0000360 0076 0000 0000 007f 0000 0004 487b 0000
0000370 0100 aa36 0000 4278 0020 0005 0000 0000
0000380 0000 aa20 0010 4278 0010 0701 731d 7200
0000390 0500 3815 3822 0522 0046 0000 0000 097f
00003a0 0000 0000 0076 0000 0000 007f 0000 0004
00003b0 487b 0000 0100 aa36 0000 4278 0020 0005
00003c0 0000 0000 0000 aa20 0010 4278 0010 0701
00003d0 731d 7200 0500 3815 3822 0522 0046 0000
00003e0 0000 097f 0000 0000 0076 0000 0000 007f
00003f0 0000 0004 487b 0000 0100 aa36 0000 4278
0000400 0020 0005 0000 0000 0000 aa20 0010 4278
0000410 0010 0701 731d 7200 0500 3815 3822 0522
0000420 0046 0000 0000 097f 0000 0000 0076 0000
0000430 0000 007f 0000 0004 487b 0000 0100 aa36
0000440 0000 4278 0020 0005 0000 0000 0000 aa20
0000450 0010 4278 0010 0701 731d 7200 0500 3815
0000460 3822 0522 0046 0000 0000 097f 0000 0000
0000470 0076 0000 0000 007f 0000 0004 487b 0000
0000480 0100 aa36 0000 4278 0020 0005 0000 0000
0000490 0000 aa20 0010 4278 0010 0701 731d 7200
00004a0 0500 3815 3822 0522 0046 0000 0000 097f
00004b0 0000 0000 0076 0000 0000 007f 0000 0004

Heizraum

unread,
Mar 4, 2011, 7:26:11 AM3/4/11
to Resol Vbus
I compared now the 2 versions of raw data (Linux <-> Windows)
On windows, data is fine, on Linux data makes almost no sense.
When I compare the to datas I notice


Windows Data: 0000000 0000 4278 0020 0005 0000 0000 0000 aa20
Linux Data: 0000000 4278 0020 0005 0000 0000 0000 7820 1042

(Pitty I cannot switch to courier new font for fixed font size...)

It seems that my device on linux cut or forget some data inbetween.
Somehow I believe it has to do with the tty setting.....



Hardy Griech

unread,
Mar 4, 2011, 8:24:36 AM3/4/11
to resol...@googlegroups.com
On 04.03.2011 13:26, Heizraum wrote:
> I compared now the 2 versions of raw data (Linux<-> Windows)
> On windows, data is fine, on Linux data makes almost no sense.
> When I compare the to datas I notice
>
>
> Windows Data: 0000000 0000 4278 0020 0005 0000 0000 0000 aa20
> Linux Data: 0000000 4278 0020 0005 0000 0000 0000 7820 1042

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

Heizraum

unread,
Mar 4, 2011, 9:21:10 AM3/4/11
to Resol Vbus
Hi Hardy

it seems that I have accidently trouble with my usb driver ftdi_sio.
in the syslog it throws a lot of errors regarding this usb, after I
switched on debugging.
So first I have to fix this, before I can start decoding the data
stream.
@all: Thanks for your almost instant help & support.
As soon I make progress regarding this usb driver I let you know.

Best regards
Tom

Heizraum

unread,
Mar 4, 2011, 1:33:52 PM3/4/11
to Resol Vbus
Ok after further analyses, I crytalize that the ftdi driver is the
origin of the problems.
I uses Debian Lenny on a guruplugserver.
Right now I update the whole distribution on the guru.

If this doesn't help, I will play arround with VCP Drivers from
FTDI...maybe I have more luck.
I really like to know which drivers you guys work with on a similar
setup.
The error messages of the driver, which I stupidly ignore till now,
you find below:


drivers/usb/serial/ftdi_sio.c: ftdi_set_termios Turning off hardware
flow contro l
ftdi_sio ttyUSB3: urb failed to clear flow control
drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 3
ftdi_sio ttyUSB3: ftdi_read_bulk_callback - length = 16, data = aa 00
00 78 42 2 0 00 05 00 00 00 00 00 00 00
20
drivers/usb/serial/ftdi_sio.c: ftdi_process_packet - port 3
drivers/usb/serial/ftdi_sio.c: update_mctrl Error from MODEM_CTRL urb:
DTR HIGH, RTS HIGH
drivers/usb/serial/ftdi_sio.c: ftdi_ioctl cmd 0x5401
drivers/usb/serial/ftdi_sio.c: ftdi_ioctl arg not supported - it was
0x5401 - ch eck /usr/include/asm/
ioctls.h
drivers/usb/serial/ftdi_sio.c: ftdi_chars_in_buffer - port 3
drivers/usb/serial/ftdi_sio.c: ftdi_close
drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 3
drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - nonzero read
bulk statu s received: -2
ftdi_sio ttyUSB3: error from flowcontrol urb
drivers/usb/serial/ftdi_sio.c: update_mctrl Error from MODEM_CTRL urb:
DTR LOW, RTS LOW
drivers/usb/serial/ftdi_sio.c: ftdi_open
drivers/usb/serial/ftdi_sio.c: write_latency_timer: setting latency
timer = 1
ftdi_sio ttyUSB3: Unable to write latency timer: -110
drivers/usb/serial/ftdi_sio.c: ftdi_set_termios
drivers/usb/serial/ftdi_sio.c: Setting CS8
ftdi_sio ttyUSB3: ftdi_set_termios FAILED to set databits/stopbits/
parity
drivers/usb/serial/ftdi_sio.c: get_ftdi_divisor - tty_get_baud_rate
reports spee d 9600
drivers/usb/serial/ftdi_sio.c: get_ftdi_divisor - Baud rate set to
9600 (divisor 0x4138) on chip FT2232C
ftdi_sio ttyUSB3: ftdi_set_termios urb failed to set baudrate
drivers/usb/serial/ftdi_sio.c: ftdi_set_termios Turning off hardware
flow contro l


Regards
Tom

Andrew White

unread,
Mar 4, 2011, 2:46:35 PM3/4/11
to resol...@googlegroups.com
I use a usb pl230x serial adapter.

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.
>
>

--

Heizraum

unread,
Mar 4, 2011, 3:38:25 PM3/4/11
to Resol Vbus
Hi Andy

I have 2 more serial/usb adpter running also with pl2303 driver on the
same guruplug.
I tested it without these 2 usb/serial devices --> Same bad result :(
I now focus on this ftdi_sio driver.
Alas Resol uses this IC's for transfering from vbus to rs232 instead
of a prolific IC which has less problems in Linux envrionemtns.

Thomas

Andrew White

unread,
Mar 4, 2011, 3:45:18 PM3/4/11
to resol...@googlegroups.com
Ah, ok, you are using the resol usb adapter, not the serial one...

On 3/4/11, Heizraum <heiz...@gmail.com> wrote:

Heizraum

unread,
Mar 4, 2011, 3:49:00 PM3/4/11
to Resol Vbus
Is there a seriell one ?!?! Then it was never offered to me ! I would
prefer a VBUS/RS232 than a VBUS/usb.

Hardy Griech

unread,
Mar 4, 2011, 3:57:16 PM3/4/11
to resol...@googlegroups.com
On 04.03.2011 21:38, Heizraum wrote:
:

> I now focus on this ftdi_sio driver.
:

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?

Heizraum

unread,
Mar 4, 2011, 4:11:02 PM3/4/11
to Resol Vbus

I tried to do it set it up with stty. But it hangs. That was
accidently the beginning of my suspicon that something is wrong with
the driver.
When you search the www, you find a lot troubles regarding this driver
under linux.

root@guru ~ >lsusb -t
/: 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 2: Dev 3, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 5, If 0, Class=vend., Driver=pl2303, 12M
|__ Port 2: Dev 6, If 0, Class=vend., Driver=pl2303, 12M
|__ Port 4: Dev 7, If 0, Class=stor., Driver=usb-storage,
480M
|__ Port 3: Dev 4, If 0, Class=comm., Driver=ftdi_sio, 12M
|__ Port 3: Dev 4, If 1, Class=data, Driver=ftdi_sio, 12M
root@guru ~ >



root@guru ~ >lsusb -v

Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303
Serial Port
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port
bcdDevice 2.02
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
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
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

Bus 001 Device 004: ID 1fef:2018
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 32
idVendor 0x1fef
idProduct 0x2018
bcdDevice 10.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 1.10
CDC Call Management:
bmCapabilities 0x03
call management
use DataInterface
bDataInterface 1
CDC ACM:
bmCapabilities 0x06
sends break
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 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 0x0020 1x 32 bytes
bInterval 0
can't get device qualifier: Connection timed out
can't get debug descriptor: Connection timed out
cannot read device status, Connection timed out (110)

Bus 001 Device 003: ID 058f:6254 Alcor Micro Corp. USB Hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x058f Alcor Micro Corp.
idProduct 0x6254 USB Hub
bcdDevice 1.00
iManufacturer 0
iProduct 1 USB2.0Hub
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 4
wHubCharacteristic 0x0080
Ganged power switching
Ganged overcurrent protection
TT think time 8 FS bits
Port indicators
bPwrOn2PwrGood 50 * 2 milli seconds
bHubContrCurrent 100 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0103 power enable connect
Port 2: 0000.0103 power enable connect
Port 3: 0000.0100 power
Port 4: 0000.0503 highspeed power enable connect
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered

Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port
HUB
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x05e3 Genesys Logic, Inc.
idProduct 0x0608 USB-2.0 4-Port HUB
bcdDevice 77.60
iManufacturer 0
iProduct 1 USB2.0 Hub
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 4
wHubCharacteristic 0x00e9
Per-port power switching
Per-port overcurrent protection
TT think time 32 FS bits
Port indicators
bPwrOn2PwrGood 50 * 2 milli seconds
bHubContrCurrent 100 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0503 highspeed power enable connect
Port 3: 0000.0103 power enable connect
Port 4: 0000.0100 power
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 2.06
iManufacturer 3 Linux 2.6.32-00007-g56678ec ehci_hcd
iProduct 2 Marvell Orion EHCI
iSerial 1 orion-ehci.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 1
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0503 highspeed power enable connect
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled

Bus 001 Device 007: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x058f Alcor Micro Corp.
idProduct 0x6366 Multi Flash Reader
bcdDevice 1.00
iManufacturer 1 Generic
iProduct 2 Mass Storage Device
iSerial 3 058F0O1111B1
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 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

Bus 001 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303
Serial Port
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port
bcdDevice 4.00
iManufacturer 1 Prolific Technology Inc.
iProduct 2 USB-Serial Controller D
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
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
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
root@guru ~ >

Andrew White

unread,
Mar 4, 2011, 4:23:09 PM3/4/11
to resol...@googlegroups.com
I don't think they make it anymore, but you might be able to find one somewhere


looking at the docs for the new usb, there is a PCB photo which looks to me like the circuit is 1 part vbus to serail and one part serial to usb, maybe you could connect into the serial part of the circuit.  you'd need to get the chip numbers / ids to check pin outs though ...


On Fri, Mar 4, 2011 at 8:49 PM, Heizraum <heiz...@gmail.com> wrote:
Is there a seriell one ?!?! Then it was never offered to me ! I would
prefer a VBUS/RS232 than a VBUS/usb.

--

Hardy Griech

unread,
Mar 4, 2011, 4:25:12 PM3/4/11
to resol...@googlegroups.com
On 04.03.2011 22:11, Heizraum wrote:
:

> |__ Port 3: Dev 4, If 0, Class=comm., Driver=ftdi_sio, 12M
> |__ Port 3: Dev 4, If 1, Class=data, Driver=ftdi_sio, 12M
:

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

Heizraum

unread,
Mar 4, 2011, 4:27:44 PM3/4/11
to Resol Vbus
> Where is the output of the ftdi_sio?
>
> Hardy

I guess you have to press the "Show more link" after "lsusb -c"

Tom

Hardy Griech

unread,
Mar 4, 2011, 4:33:43 PM3/4/11
to resol...@googlegroups.com
On 04.03.2011 22:27, Heizraum wrote:
:

> I guess you have to press the "Show more link" after "lsusb -c"
:

That did not arrive here.

BTW what is your kernel version (uname -a)?

Hardy

Heizraum

unread,
Mar 4, 2011, 5:54:10 PM3/4/11
to Resol Vbus
guru:/etc/ifplugd# uname -a
Linux guru 2.6.32-00007-g56678ec #1 PREEMPT Mon Feb 8 03:49:55 PST
2010 armv5tel GNU/Linux
guru:/etc/ifplugd#

Heizraum

unread,
Mar 5, 2011, 2:53:51 PM3/5/11
to Resol Vbus

Ok some progress and solved ?

It seems that the idea using the ftdi_sio driver is totally wrong.

So I examined the usb drivers.

As I wrote, I have 3 usb connectors:
- 1Wire
this little electronic, I brazed together by my own, delivers me 6
temperatures arround my oven and send its data over a prolific
usb2rs232 cable to /dev/ttyUSB0
- Fröling 3000 20kw
This was my most difficult project. The protocol delivered by this
device (S3100 Control) just sends data after a quiet funny/complex
initialization which last 25 Minutes.
- Deltasol
You know the status

After I change the order of loading the devices and kick off the
ftdi_sio driver, the data delivered by the Deltasol control looks
much better, even I do not know till now, if it's good enough.
Instead of using the ftdi_sio driver, I didn't know, that I can use
the usbserial driver, when I add as a parameter the vendor and product
id.
Now the task is to rewrite udev rules.
But for now, I do it with this shell script

So basicly I do that:

# unload senseless device driver /dev/ttyACM0 (it is the Resol device
for some reason)
rmmod cdc_acm
# unload the 2 prolific usb/rs232 drivers for devices /dev/ttyUSB0 /
dev/ttyUSB1
rmmod pl2303
# unload the usbserial
rmmod usbserial
# now load usbserial exactly for the Resol device
modprobe usbserial vendor=0x1fef product=0x2018
# load again the 2 prolific usb/rs232 as ttyUSB2 (1wire) ttyUSB1
(Fröling)
modprobe pl2303

And now the deltasol delivered data, looks like that:

aa 10 00 78 42 10 00 01 07 1d 4a 00 72 00 05 3e 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4a 00 72 00 05 3e 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4a 00 72 00 05 3e 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4a 00 72 00 05 3e 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4b 00 72 00 05 3d 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4b 00 72 00 05 3d 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4a 00 73 00 05 3d 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4b 00 73 00 05 3c 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20
aa 10 00 78 42 10 00 01 07 1d 4a 00 72 00 05 3e 38 22 38 22 05 46 00
00 00 00 00 7f 09 00 00 00 00 76 00 00 00 00 00 7f 00 00 00 04 00 7b
48 00 00 00 01 36 aa 00 00 78 42 20 00 05 00 00 00 00 00 00 00 20

What do you think? Is the delivered data in a proper format ?

Tom



Mark Richards

unread,
Mar 5, 2011, 3:45:40 PM3/5/11
to resol...@googlegroups.com
The data looks good.

You're on your way.

/m
Reply all
Reply to author
Forward
0 new messages