Debugging serial connection

[packhawk]

I'm trying to set this up using the powerlink2 and an ethernet to RS232 console cable with a 232->USB connection. 

I've tried a few different ways of installing and just can't seem to get it to mesh with what I am seeing in the WIKI.  Anyone else using the powerlink2?

thx jr

[nlrb]

You should not use the Powerlink2 in conjunction with the Vera plugin. You either use the Powerlink2 or the Vera plugin. Not both.

[packhawk]

So just leave it connected to my network as it is?  And let it find it as a UPnP Device?

[nlrb]

No. Disconnect the Powerlink2 and connect the Visonic dual RS232 via an RS232->USB device to the Vera.

[packhawk]

sorry i don't have the 232 module for the alarm.

I have a Console cable which is RJ45 -> RS232 then RS232 -> USB connected to the vLITE

[nlrb]

Indeed. The Visonic dual RS232 module uses an RJ45 connector. So you do have it .

[packhawk]

Here is the link to the install guide.

PowerLink2, no RS232 connection

http://www.visonic.com/Data/Uploads/PowerLink2_User_Guide_English_D-303208.pdf

[nlrb]

Ok, sorry. Then either you still need to buy and connect the RS232 module or make a connection via a TTL->USB module as discussed in this topic

[packhawk]

So I blew it all up to factory default and it picked up the a few devices and then i only installed the plugin and set it to force standard mode.

Everything was going really well for about 10 minutes...then i got the Startup Error....it would allow me to Arm Home even though it was prompting for 4 digit pin code..  I'm attaching zip with some screenshots & log.

[nlrb]

A factory default won't help. Best thing is to take off the power (mains and battery) to get the panel in the right state again.

Have look at the powermax_pdu.txt file. You'll see that only once an acknowledge message comes back from the panel ('0D 02 FD 0A'). Each message should be acknowledged, so communication is not flowing well.

[packhawk]

10/4

I am just using a USB extension cable from the Vera to the PowerMax.  I can't imagine that it would need to be powered.

[packhawk]

Reset everything last night and got some 'POWERMAX' errors

50   06/18/13 23:03:21.100   luup_log:12: POWERMAX: *** Re-sending PDU (got no response) *** <0x2cb89680>
06   06/18/13 23:03:21.101   Device_Variable::m_szValue_set device: 12 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: CommExceptions was: 3 now: 4 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2cb89680>
06   06/18/13 23:03:21.102   Device_Variable::m_szValue_set device: 12 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: CommLastException was: 1371610896 now: 1371611001 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2cb89680>
50   06/18/13 23:03:21.103   luup_log:12: POWERMAX: *** Houston - we have a communication problem (no response)! Executing a reload. *** <0x2cb89680>
50   06/18/13 23:03:21.104   luup_log:12: POWERMAX: PDU sent to panel: 0D AB 0A 00 01 00 00 00 00 00 00 00 43 06 0A  <0x2cb89680>

[nlrb]

Yes, your serial communication still does not work. Messages that are being sent are not being acknowledged that they have been received by the panel. You will need to describe your setup set-by-step to get any further (type of interfaces, cables, connected devices etc.).

[packhawk]

Powermax Pro PC/IP Port - > Prolific PL-2303HX or HXA USB-to-Serial Bridge connected via (RX -> TX, RX -> TX, Gnd -> Gnd on top row) -> USB Type A Female to Male Cable - > Vera Lite

Running the Visonic Plugin from the Marketplace.

On a fresh restart it works for about 10 minutes in force standard mode, I tick all the sensors and their Zones and it pulls those across from the panel.  It adds the second device for partition 1.

The Control Tab shows version 1.1 and standard mode and that is it.  Nothing else comes across around the panel, version, eprom, etc.

I was able to Arm Home last night but that was it then the Lua Startup Fail...

[packhawk]

from putty

root@MiOS_35010295:~# dmesg | grep "pl2303"
USB Serial support registered for pl2303
pl2303 2-1:1.0: pl2303 converter detected
usb 2-1: pl2303 converter now attached to ttyUSB0
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
usb 2-1: pl2303_read_int_callback - usb_submit_urb failed with result -19
pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
pl2303 2-1:1.0: device disconnected
pl2303 2-1:1.0: pl2303 converter detected
usb 2-1: pl2303 converter now attached to ttyUSB0
root@MiOS_35010295:~#


ttyUSB0 is blank