Resol VBUS/USB adapter on Raspberry Pi receiving garbage

[Niko Raes]

I am trying to connect the official Resol Vbus USB adapter to a Raspberry PI (B+ with Raspbian Wheezy) but without success.

When I connect the adapter the wrong driver is used so I use the following script.

#! /bin/bash
rmmod cdc_acm
rmmod ftdi_sio
rmmod usbserial
modprobe usbserial vendor=0x1fef product=0x2018
modprobe ftdi_sio
exit 0

I then get the following dmesg output, which looks ok I think, except for the error -5

[ 1399.161523] usbcore: registered new interface driver usbserial
[ 1399.161648] usbcore: registered new interface driver usbserial_generic
[ 1399.163270] usbserial: USB Serial support registered for generic
[ 1399.163385] usbserial_generic 1-1.4:1.0: Generic device with no bulk out, not allowed.
[ 1399.163432] usbserial_generic: probe of 1-1.4:1.0 failed with error -5
[ 1399.163481] usbserial_generic 1-1.4:1.1: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 1399.163501] usbserial_generic 1-1.4:1.1: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
[ 1399.163517] usbserial_generic 1-1.4:1.1: generic converter detected
[ 1399.165688] usb 1-1.4: generic converter now attached to ttyUSB0
[ 1399.212258] usbcore: registered new interface driver ftdi_sio
[ 1399.212406] usbserial: USB Serial support registered for FTDI USB Serial Device

Then I get a device /dev/ttyUSB0 but I only receive garbage from it.

cat /dev/ttyUSB0

^@xB ^@^E^@^@^@^@^@^@^@ ^C^^@ ^C^^@ ^C^^@ ^C^^@ ^C^^@ ^C^^@ ^C^^@ ^C^^@ ^C^^@ ^$
yy^Ay^Aye�
yyye�
yye�
ye�
ye��^@^@@(^A^@^@ �^@^@ �^@^@ �^@^@ �^@^@ �^@^@ �^@^@ �^@^@ �^@E+8"@^@^@@ �^@^@ �^$

I use the vbus and usb cables I received in the Resol package so I don't really see how there could be a problem with those.

Does anybody have a clue what's wrong?

Tomorrow I'll try to connect a windows pc with RSC to make sure there isn't anything wrong with the adapter.

Thank you,

Niko

[Niko Raes]

Everything works fine with RSC on Windows, so it's not a hardware problem.

Could it be a problem with my stty settings?

pi@raspberrypi ~ $ 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

[Andrew White]

Resol vbus is a protocol. It is not plain text.  What happens when you decode it ?

--
You received this message because you are subscribed to the Google Groups "Resol Vbus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resol-vbus+...@googlegroups.com.
To post to this group, send email to resol...@googlegroups.com.
Visit this group at http://groups.google.com/group/resol-vbus.
For more options, visit https://groups.google.com/d/optout.

[Niko Raes]

It doesn't work. I use vbusdecode, but it expects something like this:

ª !B tI v :r # gd l ._
2 9D a T d ª!B wª !B tI w 9r # gd l ._
2 9D a T d ª!B wª !B tI w 9r # gd l ._
2 9D a T d ª!B wª !B tI w 9q " id l ._
2 9D a T d ª!B wª !B tI w 9q " id l ._
2 9D a T d ª!B w

It works with this sample but not with my data.

[Niko Raes]

It works!

It was the stty setting.

After this command everything works.

stty -F /dev/ttyUSB0 1:0:bd:0:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0

[Niko Raes]

Would somebody be able to point me in the good direction to make this work automatically?

I now have the following udev rule

/etc/udev/rules.d/95-usb-serial.rules

# Rule for vbus-usb adapter
SUBSYSTEM=="tty", ATTRS{idVendor}=="1fef", ATTRS{idProduct}=="2018", RUN="sh /etc/vbusinit"

With the following /etc/vbusinit

#! /bin/bash
rmmod cdc_acm
rmmod ftdi_sio
rmmod usbserial
modprobe usbserial vendor=0x1fef product=0x2018

modprobe ftdi_sio
stty -F /dev/ttyUSB0 1:0:bd:0:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0

exit 0

But this doesn't do anything automatically. I always have to manually start the script (and then it works).

Thank you

Op zaterdag 11 oktober 2014 13:17:33 UTC+2 schreef Niko Raes:

[Niko Raes]

I installed Raspbian Jessie on a new raspberry pi and the solution below no longer works.

Has anybody managed to use the Resol Vbus USB adapter on a raspberry pi with Jessie?

Thank you,

Niko

Op maandag 13 oktober 2014 20:16:39 UTC+2 schreef Niko Raes:

[Andrew White]

Nope. What bit doesn't work ?

--

You received this message because you are subscribed to the Google Groups "Resol Vbus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resol-vbus+...@googlegroups.com.
To post to this group, send email to resol...@googlegroups.com.

Visit this group at https://groups.google.com/group/resol-vbus.

[Niko Raes]

The driver wasn't loaded anymore and specifying a vendor and product for modprobe no longer works.
Eventually I found a solution.

Add blacklist cdc_acm to /etc/modprobe.d/vbus-blacklist.conf

Udev rule /etc/udev/rules.d/95-usbserial.rules

ACTION=="add", ATTRS{idVendor}=="1fef", ATTRS{idProduct}=="2018", SYMLINK+="ttyVbus", RUN+="/etc/vbusinit"

edit /etc/vbusinit

#! /bin/bash
echo 1fef 2018 > /sys/bus/usb-serial/drivers/generic/new_id
/etc/vbusinit1 & exit

Edit /etc/vbusinit1

#! /bin/bash
sleep 5
stty -F /dev/ttyVbus 1:0:bd:0:0:0:0:0:0:0:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0
exit 0

Somehow it doesn't work with a single script.

[Marco Bender]

Hello,

i have two Resol USB Devices with the same idVendor and so on.
Can i fix it in the raspberry on restart with a symlink?

Thanks a lot.