Step by step guide: Visonic Powermax Pro integration

[BornToKill]

Hi,

You need to download the last commit from ayasystems.
It patches this segfault issue when opening zone.

PM me your email if you want latest zip.

[stichx360]

Hi, hoping someone can help me. Thanks for putting this together guys, great work.

I am a newbie with PI and coding so a lot of trial and error for me.

I’ve followed the guide but I’m getting stuck on step 3d when I try to run


root@raspberrypi:~/pmaxd$ ./pmaxd -fvvvvvvvv
(null):0 - file I/O error

I’ve read through the post and not sure how borntokill (who also had the issue) actually resolved this issue. He seemed to imply that it was a location issues and pmaxd.conf should be located in /etc/pmaxd/pmaxd.conf however that’s not how the guide reads and it’s not possible to create the pmaxed folder in /etc.? I have run strace and get the same issue as him….

munmap(0x76f32000, 73990) = 0
brk(0) = 0xa11000
brk(0xa32000) = 0xa32000
open("/etc/pmaxd/pmaxd.conf", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "(null):0 - file I/O error\n", 26(null):0 - file I/O error
) = 26
exit_group(1) = ?
+++ exited with 1 +++

It may however be the cabling I have chosen. Instead of the guide process I had a powermax dual cable rs232, so this may we be the issue, this is connected to the Pi via a rs232/usb adapter using ch340. I did however run through step 2 and test the connection with the visonic interface driver and it seemed to work (I could not however arm/disarm the panel).
I have since ordered the usb ttl auto converter and will try the pc/ipn method as described in the guide.

Just wanted to see if I was doing something wrong other than the possible cabling issue, since I am NEWBIE.

http://www.cts-direct.net/visonic-power ... Ar3q8P8HAQ
Thanks

[BornToKill]

Hi,

open("/etc/pmaxd/pmaxd.conf", O_RDONLY) = -1 ENOENT (No such file or directory)

Mkdir -p /etc/pmaxd/
Then mv pmaxd.conf file in this folder.

Regards.

[stichx360]

Thanks borntokill, that did the trick. stuck on very next stage with starting main loop....................lol...

xpl_hub is running

Code: Select all

NOTICE: [Mon Mar 13 19:30:53 2017 initLog:0058]Logging initialized
 NOTICE: [Mon Mar 13 19:30:53 2017 initLog:0059]Verbose level: 7
 NOTICE: [Mon Mar 13 19:30:53 2017 main:0417]Program started by User 1000
 INFO: [Mon Mar 13 19:30:53 2017 main:0419]setting SID
 NOTICE: [Mon Mar 13 19:30:53 2017 main:0451]Starting......
 INFO: [Mon Mar 13 19:30:53 2017 initSerialPort:0071]there are 2 device in your config file
 INFO: [Mon Mar 13 19:30:53 2017 initSerialPort:0085]opening /dev/ttyUSB0
I have 8 zone:
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 0, name: R.D.C.
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 1, name: Etage
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 2, name: Salon
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 3, name: Salle a manger
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 4, name: cuisine
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 5, name: porte garage
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 6, name: volet garage
 NOTICE: [Mon Mar 13 19:30:53 2017 PmaxInit:0165]zone: 7, name: detecteur incendie
 DEBUG: [Mon Mar 13 19:30:53 2017 sendBuffer:0174]Sending the following buffer to serial TTY
 DEBUG: [Mon Mar 13 19:30:53 2017 logBuffer:0157]BufferSize: 12
 DEBUG: [Mon Mar 13 19:30:53 2017 logBuffer:0158]Buffer: A2 00 00 00 00 00 00 00 00 00 00 43 
 DEBUG: [Mon Mar 13 19:30:53 2017 calculChecksum:0167]checksum: 001A
 DEBUG: [Mon Mar 13 19:30:53 2017 sendBuffer:0183]result of serial write:: 15
 DEBUG: [Mon Mar 13 19:30:53 2017 sendBuffer:0174]Sending the following buffer to serial TTY
 DEBUG: [Mon Mar 13 19:30:53 2017 logBuffer:0157]BufferSize: 12
 DEBUG: [Mon Mar 13 19:30:53 2017 logBuffer:0158]Buffer: AB 06 00 00 00 00 00 00 00 00 00 43 
 DEBUG: [Mon Mar 13 19:30:53 2017 calculChecksum:0167]checksum: 000B
 DEBUG: [Mon Mar 13 19:30:53 2017 sendBuffer:0183]result of serial write:: 15
 DEBUG: [Mon Mar 13 19:30:53 2017 main:0456]Sarting main loop....

[BornToKill]

Come in PM. You seem to be french me too. Easiest to Help.

[andersonherry]

Informative! Your step by step guiding for Visonic Powermax Pro integration will be helpful. Thanks for sharing.

[jelleeelco]

Hi,

You need to download the last commit from ayasystems.
It patches this segfault issue when opening zone.

PM me your email if you want latest zip.

Hi,

Thank you for your reply! I actually got to the same conclusion and completely forgot to check this topic...apologies. All is working now perfectly and have everything nicely integrated into Domoticz. I am now also able to use the sensors to trigger events, something I never dreamed off

[al300kr]

Hi, can you control viconic chime on/off in domoticz?
thanks

[jelleeelco]

Does anyone else is having issues with pmaxd? It just stopped working at some point. I rebuild a new image to test, but also that one doesn't work. Everything is running as it should, but there doesn't seem to be a connection between the PI and the visonic. When I run it manually it just stops at ' Sarting Main loop...'

I tested even with a different PI, no difference. Tested with the serial connector linked to a windows pc, and from there everything worked.

Can it be that xPLL_Hub has changed?

[BornToKill]

Hi,

Same here since rpi-update has been done....
Investigating..

[jelleeelco]

Pfew, so glad you're replying... I think I have done the same thing (rpi-update) and of course with a new build it's the same...

Really can't figure out what's wrong... this is above my knowledge. It looks like the xPL is not communicating, but it's a wild guess.

[BornToKill]

OK,

So kernel 4.9.X broke something.
To downgrade 4.4.50 : rpi-update 52241088c1da59a359110d39c1875cda56496764
Reboot !
Enjoy

PS : I'm on Jessie (Raspbian)

[jelleeelco]

Ok mate... after helping me like that you're my mate, so....forgive me my familiarity

So how do I downgrade? I go to ssh, sudo rpi-update and then I enter that whole string of code?

Apologies if this is a stupid question....!!

[BornToKill]

PM your email.
Will be easier.

[jelleeelco]

Send!

[jelleeelco]

Ok. Thanks to BornToKill it's sorted. As he said, the kernel update must have broken something. I don't know how I performed the kernel update, as the instruction rpi-update was not available.
So, this is what I did (well, what BortToKill asked me to do....and it worked). SSH into the pi and then:

Code: Select all

cat /etc/issue

(outcome should be Raspbian GNU/Linux 8 \n \l which means running Jessie)

Code: Select all

uname -a

This gives the kernel currently running, mine was: Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:4

I didn't have rpi-update installed, so first I installed that:

Code: Select all

apt-get update
apt-get install rpi-update

and then downgrade the kernel by being root user:

Code: Select all

sudo su
rpi-update 52241088c1da59a359110d39c1875cda56496764

Then reboot and it worked!

All credits to BornToKill, I just followed his instructions via the email.

[BornToKill]

happy to help the community!
Thanks for your reply.

[jelleeelco]

You are right though that the lua script is breaking pmaxd... I get the same thing now.

What script are you running and how does domoticz then get the status?

[Holland]

Thanks guys

After an uptime of 6 months, I thought, maybe a good idea to update the pi to the latest version. Not....

Kernel 4.9 kills the pmaxd!!

So did; rpi-update 52241088c1da59a359110d39c1875cda56496764

And it's up and running again. Cool

[BornToKill]

Glad to help you !