We have moved at community.getvera.com

Author Topic: Debugging serial connection  (Read 10816 times)

Offline nlrb

  • Moderator
  • Sr. Member
  • *****
  • Posts: 444
  • Karma: +13/-0
Re: Debugging serial connection
« Reply #15 on: June 20, 2013, 08:52:18 am »
Good that you looked at this! I already was afraid of this. But it clearly identifies the 'PL2303' as the problem. I've previously seen problems with PL2303s, hence I always use FTDI based devices. There are cheap rip-offs around of PL2303s. FTDI based ones are safe.

Offline packhawk

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +1/-1
Re: Debugging serial connection
« Reply #16 on: June 20, 2013, 09:44:24 am »
Good that you looked at this! I already was afraid of this. But it clearly identifies the 'PL2303' as the problem. I've previously seen problems with PL2303s, hence I always use FTDI based devices. There are cheap rip-offs around of PL2303s. FTDI based ones are safe.

I have that already that I was using with the plink2, using a console cable.  but with plink2 not working seems i have to get the visonic rs232 adapter?


Offline packhawk

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +1/-1
Re: Debugging serial connection
« Reply #17 on: June 21, 2013, 11:23:56 am »
Last question as my wife is giving me hell about looking at this soo much and it doesn't work....

Are there any specific settings on the Define Coms on the alarm that maybe i am setting wrong? 

-OEM
-Antenna
-force home networking

BUt stepping away from it until the replacement FTDI usb shows up.

http://www.amazon.com/gp/product/B004LBXO2A/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1

Offline nlrb

  • Moderator
  • Sr. Member
  • *****
  • Posts: 444
  • Karma: +13/-0
Re: Debugging serial connection
« Reply #18 on: June 21, 2013, 03:02:11 pm »
No, nothing special that you need to set. Just wait for the new cable. That one looks good.

Offline packhawk

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +1/-1
Re: Debugging serial connection
« Reply #19 on: June 24, 2013, 09:21:57 pm »
Cable made it....looks like i need to snip and get the appropriate wires connected, not a pnp connection



If all else fails, here is the interesting info off the linked page:


* Pin 1 GND
* Pin 2 CTS
* Pin 3 VCC (+3.3v!)
* Pin 4 TXD   orange
* Pin 5 RXD
  yelllow
* Pin 6 RTS

I'm assuming that the black wire is pin 1.

It's using the FTDI chipset:
* Product ID: 0x6001
* Vendor ID: 0x0403 (Future Technology Devices International Limited)
* Version: 6.00
* Speed: Up to 12 Mb/sec
* Manufacturer: FTDI
* Current Required (mA): 500
« Last Edit: June 24, 2013, 09:42:20 pm by packhawk »

Offline packhawk

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +1/-1
Re: Debugging serial connection
« Reply #20 on: June 24, 2013, 10:18:46 pm »
still not starting due to too many communication errors

50   06/24/13 19:38:41.202   luup_log:11: POWERMAX: loading library L_Powermax... <0x2ba6b680>
50   06/24/13 19:38:41.331   luup_log:11: POWERMAX: library L_Powermax loaded __LEAK__ this:479232 start:479232 to 0xcf4000 <0x2ba6b680>
50   06/24/13 19:38:41.332   luup_log:11: POWERMAX: Not starting due to too many communcation errors. <0x2ba6b680>
01   06/24/13 19:38:41.333   LuaInterface::CallFunction_Startup-2 device 11 function startup failed (null) with return false <0x2ba6b680>
06   06/24/13 19:38:41.333   Device_Variable::m_szValue_set device: 11 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb58fb8/NONE duplicate:1 <0x2ba6b680>
01   06/24/13 19:38:41.334   LuImplementation::StartLua running startup code for 11 I_Powermax.xml failed <0x2ba6b680>
« Last Edit: June 24, 2013, 10:43:28 pm by packhawk »

Offline nlrb

  • Moderator
  • Sr. Member
  • *****
  • Posts: 444
  • Karma: +13/-0
Re: Debugging serial connection
« Reply #21 on: June 25, 2013, 01:23:49 am »
Puzzling ???... Do you have the logs from the moment you connected the new cable?

Offline packhawk

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +1/-1
Re: Debugging serial connection
« Reply #22 on: June 25, 2013, 09:32:25 am »
Clear both variables ('CommExceptions' and 'CommLastException')


just tried it and it filled everything in....  see if it sticks

Offline packhawk

  • Jr. Member
  • **
  • Posts: 55
  • Karma: +1/-1
Re: Debugging serial connection
« Reply #23 on: June 25, 2013, 10:22:28 am »
Looks like that did it!  Thank you again for your help and patience.

It automatically created the zones that I didn't have setup.

@nlrb thank you, thank you again

Offline nlrb

  • Moderator
  • Sr. Member
  • *****
  • Posts: 444
  • Karma: +13/-0
Re: Debugging serial connection
« Reply #24 on: June 25, 2013, 01:38:47 pm »
Glad to see it is working and everything behaves as expected! You had me worried...

Offline itwiz

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: Debugging serial connection
« Reply #25 on: April 24, 2014, 09:55:34 am »
Hi,
I cannot get the plug-in to work with my Vera Lite and PowerMax+, I get "Not starting due to too many communcation errors."
I've cleared both variables ('CommExceptions' and 'CommLastException'), but no go.

I'm using these adapters:
http://www.moxa.com/product/200802011023020685.htm
http://www.deltaco.se/support/infose/UC-232C9.pdf

How do I troubleshoot this?

Any help appreciated.


Offline nlrb

  • Moderator
  • Sr. Member
  • *****
  • Posts: 444
  • Karma: +13/-0
Re: Debugging serial connection
« Reply #26 on: April 24, 2014, 02:53:57 pm »
  • Check that the pinout of the RJ45 -> DB9 is as described in this topic.
  • Check that connection works with the PC programming software
  • Check that the USB to serial converter shows up in Vera (Apps -> Develop Apps -> Serial Port configuration)

Offline itwiz

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: Debugging serial connection
« Reply #27 on: April 28, 2014, 04:10:15 pm »

nlb,
This is what I found out.
I have also removed the cable from the usb port and uninstalled the plug-in.
The connecting the cable to usb and installed the plug-in.

"1. Check that the pinout of the RJ45 -> DB9 is as described in this topic."

->According the datasheet at the Moxa url in my previous post:1 DCD
2 TxD
3 RxD
4 DSR
5 GND
6 DTR
7 CTS
8 RTS


"2. Check that connection works with the PC programming software"
-> I do not know how to do this...

"3.Check that the USB to serial converter shows up in Vera..."
-> Yes, as below:
Name=ftdi_sio
Path=/dev/ttyUSB0
Device number=usb-rt3883-ohci-1
IP address=empty
Port=3481
Baud=9600
Parity=none
Data bits=8
Stop bits=1
Used by device=Powermax Alarm Panel

The Powermax Alarm Panel shows "Mode unknown".
After a while I get "Lua Startup Failure". And after reload I get "Not starting due to too many communcation errors."

I will see if I can find a Cisco cable like this, http://www.ebay.com/itm/New-Cisco-Router-Switch-Console-Cable-DB9-to-RJ45-72-3383-01-/161286560720

Offline nlrb

  • Moderator
  • Sr. Member
  • *****
  • Posts: 444
  • Karma: +13/-0
Re: Debugging serial connection
« Reply #28 on: April 28, 2014, 04:17:58 pm »
If the pinout numbers are the numbers of the RJ45 connector, then it explains why it doesn't work. See this topic how the pinout should be.

For the programmer software, e.g. have a look at the following FAQ: How do I access the Visonic Remote Programming Software?

Offline itwiz

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: Debugging serial connection
« Reply #29 on: May 04, 2014, 05:48:06 am »