Agent Loop Problem on Raspberrypi

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
albersag
Posts: 4
Joined: 02 Dec 2012 11:44

Agent Loop Problem on Raspberrypi

Post by albersag » 02 Dec 2012 11:59

Hi

I have compiled and seems to work fine, but i get a loop problem an disconected from server.

He it is a portion of log


root@raspberrypi:/home/pi/Z-Connector/Unix# cat debug
Opening device...
[D] Configuring device...
[D] Creating a socket...
[D] Enabling keep-alives on the socket...
Connecting to server...
[D] Initialising OpenSSL environment...
[D] Allocating SSL context...
[D] Loading personal certificate...
[D] Loading personal certificate key...
[D] Loading CA certificate...
[D] Setting verification mode...
Establishing SSL connection...
[D] Allocating SSL session...
[D] Assigning socket...
Performing SSL handshake...
[D] Initialising SSL state...
[D] Sending handshake...
[D] Server has closed the SSL connection
[D] Shutting down SSL session...
[D] Freeing SSL session...
Establishing SSL connection...
[D] Allocating SSL session...
[D] Assigning socket...
Performing SSL handshake...
[D] Initialising SSL state...
[D] Sending handshake...
Loop started
[D] socket has data
[D] 5 bytes:
[D] 01 03 00 07 FB
[D] socket has data
[D] 5 bytes:
[D] 01 03 00 07 FB
[D] socket has data
[D] 5 bytes:
[D] 01 03 00 07 FB
[D] Server has closed the connection
[E] Socket has gone
Loop ended


What coult be wrong? Any idea what to check?

I could open /dev/ttyUSB0 and seems to be recognised without problems

dmesg output:


[ 3269.930924] usb 1-1.2.2: new full-speed USB device number 9 using dwc_otg
[ 3270.032499] usb 1-1.2.2: New USB device found, idVendor=067b, idProduct=2303
[ 3270.032528] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3270.032545] usb 1-1.2.2: Product: USB-Serial Controller D
[ 3270.032559] usb 1-1.2.2: Manufacturer: Prolific Technology Inc.
[ 3270.033657] pl2303 1-1.2.2:1.0: pl2303 converter detected
[ 3270.037573] usb 1-1.2.2: pl2303 converter now attached to ttyUSB0


lsusb -v

Bus 001 Device 009: 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)


im using a zwave me USB connector

User avatar
PoltoS
Posts: 4334
Joined: 26 Jan 2011 19:36

According to the log the

Post by PoltoS » 02 Dec 2012 11:59

According to the log the stick does not repy to init commands.

Make sure the port is not used by some other program.
Also try the stick on another port.
Are you sure the stck works on another Linux machine?

Also try to unload pl2303 module and load it back - sometimes it helps:
modprobe -r pl2303
modprobe pl2303

Check this: https://bugs.launchpad.net/ubuntu/+sour ... bug/661321

albersag
Posts: 4
Joined: 02 Dec 2012 11:44

I have tried same device on

Post by albersag » 02 Dec 2012 11:59

I have tried same device on Windows and get same trouble. So as you mention it seems a problem connecting to stick? Is there any way to check if its working properly sending som commands?

User avatar
PoltoS
Posts: 4334
Joined: 26 Jan 2011 19:36

Did it worked once? May be it

Post by PoltoS » 02 Dec 2012 11:59

Did it worked once? May be it is boken/damaged? Exchange it in your shop.

albersag
Posts: 4
Joined: 02 Dec 2012 11:44

It never worked. No under

Post by albersag » 02 Dec 2012 11:59

It never worked. No under windows no under linux

It seems to be damaged.

Post Reply