Vista 20P 4232cbm Honeywell

[abovedeck]

I've read just about every thread on here about integration between this alarm panel and C4.  My programmer has spent about 6 hours trying to get it to work using all of the different combinations posted on this site (although old threads with drivers that are no longer available), and ADT came today and spent another 3.  No luck.  The problem is that the alarm system keeps getting fire triggers or hold up triggers from the C4.  I have another guy from ADT coming on Friday who swears he knows how to do it, but he also states that the correct module is the 4100SM, not the 4232.

 

Is there some more recent history of a successful integration? I've got an EA-5 and a newer Vista 20P panel... Bummed that this has not been an easy install.

[abovedeck]

17 hours ago, Simplyauto1 said:

Ditch the 4232cbm and get the HSIM module from houselogix. Setup takes no time at all. It's the only module we've used for vista panel integration for the last three years.

Sent from my iPhone using Tapatalk

DID JUST THAT.  Received the module this morning.  Will connect later. 

 

In terms of wire from the module to the alarm panel, will cat5 work or is there a difference between that and alarm wire?

[abovedeck]

On 1/21/2017 at 5:58 AM, Joshua Pressnell said:

Doesn't really matter. One or the other but not both. 

From your later post though, I agree... panel programming sounds off. 

 

On 1/21/2017 at 6:25 AM, msgreenf said:

based on the error thrown when you disconnected it has he it programmed wrong 100%.  It should show up as a key pad, not a receiver, like your error says.  and the alarm should NEVER error when disconnected.  It needs to be on the keypad bus...

 

22 hours ago, Simplyauto1 said:

Ditch the 4232cbm and get the HSIM module from houselogix. Setup takes no time at all. It's the only module we've used for vista panel integration for the last three years.

Sent from my iPhone using Tapatalk

Got the HSIM from houselogix and voila!  It works.  Dan Covach was a great help in getting it up and running.  Have a couple ?s about it so I'll post on here, but it's nice to finally have the alarm integrated and start setting up my programming.

[Manlio]

On 16/12/2016 at 5:21 PM, AdamT said:

Did you read this? Also on a side note I know at my work we had to set the virtual keypad to 2 not 5 because if a speedbump we hit and once we went to 2 everything went well.

 

Note below.

 

These are the instructions I wrote down when I did mine.  Maybe it will help. Some of it is from the Honeywell book.

 

Vista 20P simple instructions:

Set these values in the fields:

*91 8,2

*189 1,1,5,5

*190 - *196 1,5 choose a location where there is no physical keypad, and set the keypad address number in the control4 driver. ie. If there is 1 physical keypad it is default address 16, so set address 17 keypad (*191) to 1,5 and enter 17 as the addess under "ECP address for 1st keypad"

 

ECP address for 4232CBM module :

This is the address value equal to 25, to be configured in CBM module to get the panel status updates.

The same 25th address should be configured as RIS module in panel.

Refer the security panel data sheets for more information.

 

ECP address for 1st keypad Emulation :

This is the address to be set to CBM module to get the display messages and virtual keypad functionality in control4.

A keypad should be configured to 1st partition in security panel at the same address.

Refer the security panel data sheets for more information.

 

Number of Zones :

These are the number of zones to be created, monitored and assign the event actions based on the status of the zones.

 

Number of Partitions:

These are the number of Partitions to be created, monitored and assign the event actions based on the status of the Partitions.

 

Polling:

This is the configuration set to the CBM module for whether to send the status update messages from panel to control4 as and when it occurs asynchronously(When polling is OFF) or on status request from control4(when polling is ON).

 

AUI Support:

This is the configuration set to CBM module to get the zone descriptors from security panel. The same AUI option should be enabled in security panel configuration at the same above mentioned ECP address for 1st keypad Emulation.Refer the security panel data sheets for more information.

 

Debug Mode:

This is facility provided to get the RS232 communication logs when the mode is true.

 

Reconnect:

Selecting this button resets and configures the 4232CBM according to the driver settings configured in Composer. If you have made configuration changes and the system is not responding correctly, or if the Control4 system loses communications with the control panel (e.g. if the control panel completely loses both AC and battery power), select this button to re-establish normal operation.

 

Zone Settings:

If you wish to monitor more than 48 zones, you can change the number of zone bindings available with the 'Number of Zones' property on the Properties page.

To use the zone status changes, add Control4 Contact devices (motion sensor contact, door contact, etc. to the Control4 project, and then make Connections in the Connections page to the appropriate security panel zone.

 

Zone Descriptor:

Make sure that AUI option enabled/disabled same as both the panel and driver side.

 

Note:

 

Low end Panel configuration:

 

If both the side AUI option is enabled, ECP address for 1st keypad Emulation address should be one of 1,2,5 and 6 which is enabled AUI option for the Home partition (Partition 1).

 

Wiring configuration:

 

Straight Cable Connection:

 

4232CBM pin Connection

 

5-6->(RX)

7-8->(TX)

3-4->(GND)

 

at DB9 pin Connection

 

2(RX)

3(TX)

5(GND)

 

Limitations:

 

WARNING: If you change/update the Number of Zones, you will lose any connections made to those zone bindings, and need to re-connect them to your project sensors

I use to work for Honeywell, can you please explain why you need to program *190 to *196 thank you!!

[AdamT]

On 1/3/2018 at 1:56 PM, Manlio said:

I use to work for Honeywell, can you please explain why you need to program *190 to *196 thank you!!

Not sure, that was something I quoted from someone else in the group.

[Manlio]

*190-196 these are the fields related to physical keypads like 6160rf so they are not automation related, fiel *189 has to do with the  virtual keypads as far as I know you only need to *189.

[abovedeck]

Trying, but I keep getting errors.

 

The Vista20p and c4 are talking to one another, but i keep the wrong messages on c4.

 

where it should say "ready" it keeps going in to programming and displays "Field?" or sets off the fire code.  my installer from adt is following your instructions and were going to try in a sec, but i feel like this has all already been tried. and im about to pull my head off!!!

[funnyfarm299]

4232CBM is the correct module. They should be using the "security panel" driver, not "security system". What is the zone type sent to the monitoring company?

What is the revision of the panel? I've seen where grounding issues can cause false alarm signals.

[abovedeck]

Oh, I'll bet that's the issue... the driver.  Connection between the Vista and C4 is correct, they are talking to one another, just miscommunicating. 

Not sure about the panel revision, but it's about a year old.

 

Just looked in Composer HE, looks like we have SECURITY PANEL when in programming and SECURITY SYSTEM under monitoring.  Not sure if that says which driver I have.

[funnyfarm299]

It should show like the panel driver, not the system driver.

 

[abovedeck]

16 minutes ago, funnyfarm299 said:

It should show like the panel driver, not the system driver.

 

 

This is what I have:

 

 

[funnyfarm299]

25 minutes ago, abovedeck said:

This is what I have:

That's the current driver.

[msgreenf]

Did they do the correct programming in the panel and wire correctly? Is. Your panel at correct firmware? I use this driver w o issue

Sent from my Nexus 6P using Tapatalk

[abovedeck]

I guess I don't really know the answer to that... or should I say, no.

 

The panel is wired correctly, I'm guessing the ADT guy didn't really know what he was doing. They're sending out another guy on Friday who "knows."  We'll see.  But I'm hesitant and getting annoyed because even the new guy said something about a different part, the 4100.

[msgreenf]

41 minutes ago, abovedeck said:

I guess I don't really know the answer to that... or should I say, no.

 

The panel is wired correctly, I'm guessing the ADT guy didn't really know what he was doing. They're sending out another guy on Friday who "knows."  We'll see.  But I'm hesitant and getting annoyed because even the new guy said something about a different part, the 4100.

the control4 doc on what to program on the panel is very accurate. it also shows how to correctly wire the connector.

[Joshua Pressnell]

I use the 4232CBM and the Vista 20P as well.  Bought the panel about 8 months ago now.  Just to double check, if you mouse-over the driver in the System Design view, you'll get a driver details popup.  You should see the 4232CBM mentioned in that info (mine is attached).  In my security panel driver settings, I have "Emulation Keypad1 Address" set to 5.  I had to have some special programing done on my Vista panel in order to enable that on my security panel.  Don't remember just now exactly what the programming steps were (I self-install/maintain my panel), but it took a bit of tinkering to get the settings in the panel itself correct.  It won't work if your panel configuration is wrong, and that *might* be what's causing the problem.  If things are talking 100%, you should see Panel Name (VISTA-20P) and Panel Firmware Version (10.23) in the driver properties pane, and up top you should see your partitions and zones.  If you see your actual zones listed in the driver properties pane, then C4 is at least talking to the 4232CBM module.  At that point, the issue is most likely grounding or wiring issues (not incorrect wiring, but when I installed mine, I had one wire that was loosely connected and it caused bad comms until I pulled it out, reseated it, and screwed it back in tightly).  But it could also be internal settings on your alarm panel that need to be double-checked.  Frequently alarm techs have about as much training as reading through the manuals and shadowing a guy for a while... so if it requires some "non-standard" details, they may have to go through the panel configuration line by line until they find the incorrect setting and correct it.

This setup should definitely work... so you likely just need a guy with super-solid hardware/software debug skills.

 

[msgreenf]

one other piece of advice, if they hookup a temporary keypad for programming, this integration won't work until they disable that keypad

[abovedeck]

19 minutes ago, msgreenf said:

You can't.

 

Zigbee and INternet are not related.  Internet outage will not cause zigbee devices to go offline

 

15 minutes ago, Joshua Pressnell said:

I use the 4232CBM and the Vista 20P as well.  Bought the panel about 8 months ago now.  Just to double check, if you mouse-over the driver in the System Design view, you'll get a driver details popup.  You should see the 4232CBM mentioned in that info (mine is attached).  In my security panel driver settings, I have "Emulation Keypad1 Address" set to 5.  I had to have some special programing done on my Vista panel in order to enable that on my security panel.  Don't remember just now exactly what the programming steps were (I self-install/maintain my panel), but it took a bit of tinkering to get the settings in the panel itself correct.  It won't work if your panel configuration is wrong, and that *might* be what's causing the problem.  If things are talking 100%, you should see Panel Name (VISTA-20P) and Panel Firmware Version (10.23) in the driver properties pane, and up top you should see your partitions and zones.  If you see your actual zones listed in the driver properties pane, then C4 is at least talking to the 4232CBM module.  At that point, the issue is most likely grounding or wiring issues (not incorrect wiring, but when I installed mine, I had one wire that was loosely connected and it caused bad comms until I pulled it out, reseated it, and screwed it back in tightly).  But it could also be internal settings on your alarm panel that need to be double-checked.  Frequently alarm techs have about as much training as reading through the manuals and shadowing a guy for a while... so if it requires some "non-standard" details, they may have to go through the panel configuration line by line until they find the incorrect setting and correct it.

This setup should definitely work... so you likely just need a guy with super-solid hardware/software debug skills.

 

 

3 minutes ago, msgreenf said:

one other piece of advice, if they hookup a temporary keypad for programming, this integration won't work until they disable that keypad

Thanks guys!

 

They didn't hook up a temp keypad, just the existing ones that I already have.  The instructions seem very clear and I gave both ADT and my C4 programmer printouts from this forum.  Fantastic wrote up a great instruction manual to this configuration a while back but  still no luck.  So I'll have to do the same tomorrow with the guy and maybe have him rewire it just to be safe.  Crossing my fingers!

[msgreenf]

the other thing you have to get right is the keypad bus, the actual bus you need to use could be different based on the number of keypads you have in your house

[abovedeck]

We're starting off with changing out the db9 connector with a new one and setting up pins as:

 

2 (rx)

3 (TX)

5 (GRND)

 

Let's see if that's the magic cure.

[AdamT]

Did you read this? Also on a side note I know at my work we had to set the virtual keypad to 2 not 5 because if a speedbump we hit and once we went to 2 everything went well.

 

Note below.

 

These are the instructions I wrote down when I did mine.  Maybe it will help. Some of it is from the Honeywell book.

 

Vista 20P simple instructions:

Set these values in the fields:

*91 8,2

*189 1,1,5,5

*190 - *196 1,5 choose a location where there is no physical keypad, and set the keypad address number in the control4 driver. ie. If there is 1 physical keypad it is default address 16, so set address 17 keypad (*191) to 1,5 and enter 17 as the addess under "ECP address for 1st keypad"

 

ECP address for 4232CBM module :

This is the address value equal to 25, to be configured in CBM module to get the panel status updates.

The same 25th address should be configured as RIS module in panel.

Refer the security panel data sheets for more information.

 

ECP address for 1st keypad Emulation :

This is the address to be set to CBM module to get the display messages and virtual keypad functionality in control4.

A keypad should be configured to 1st partition in security panel at the same address.

Refer the security panel data sheets for more information.

 

Number of Zones :

These are the number of zones to be created, monitored and assign the event actions based on the status of the zones.

 

Number of Partitions:

These are the number of Partitions to be created, monitored and assign the event actions based on the status of the Partitions.

 

Polling:

This is the configuration set to the CBM module for whether to send the status update messages from panel to control4 as and when it occurs asynchronously(When polling is OFF) or on status request from control4(when polling is ON).

 

AUI Support:

This is the configuration set to CBM module to get the zone descriptors from security panel. The same AUI option should be enabled in security panel configuration at the same above mentioned ECP address for 1st keypad Emulation.Refer the security panel data sheets for more information.

 

Debug Mode:

This is facility provided to get the RS232 communication logs when the mode is true.

 

Reconnect:

Selecting this button resets and configures the 4232CBM according to the driver settings configured in Composer. If you have made configuration changes and the system is not responding correctly, or if the Control4 system loses communications with the control panel (e.g. if the control panel completely loses both AC and battery power), select this button to re-establish normal operation.

 

Zone Settings:

If you wish to monitor more than 48 zones, you can change the number of zone bindings available with the 'Number of Zones' property on the Properties page.

To use the zone status changes, add Control4 Contact devices (motion sensor contact, door contact, etc. to the Control4 project, and then make Connections in the Connections page to the appropriate security panel zone.

 

Zone Descriptor:

Make sure that AUI option enabled/disabled same as both the panel and driver side.

 

Note:

 

Low end Panel configuration:

 

If both the side AUI option is enabled, ECP address for 1st keypad Emulation address should be one of 1,2,5 and 6 which is enabled AUI option for the Home partition (Partition 1).

 

Wiring configuration:

 

Straight Cable Connection:

 

4232CBM pin Connection

 

5-6->(RX)

7-8->(TX)

3-4->(GND)

 

at DB9 pin Connection

 

2(RX)

3(TX)

5(GND)

 

Limitations:

 

WARNING: If you change/update the Number of Zones, you will lose any connections made to those zone bindings, and need to re-connect them to your project sensors

[Joshua Pressnell]

Why are there two wires jammed into each pin and connection?  I wouldn't *think* that would cause any major issues, but I wouldn't be surprised to find out that it was causing some kind of interference or signal bounce that would be causing the problem either.  You might try picking just three wires and only three wires. 

[abovedeck]

and I cannot get it to arm or disarm or actually work as a keypad.

[abovedeck]

Keypad is set to 18 on panel side, should it still be set to 18 on C4 side or 1, 5 etc?  I've seen so many diff conflicting sides.

 

 

[abovedeck]

ISSUE:
 

ECP address for 4232CBM module :

This is the address value equal to 25, to be configured in CBM module to get the panel status updates.

The same 25th address should be configured as RIS module in panel.

Refer the security panel data sheets for more information.

 

The adt guy said that the vista 20p panel will not go to 25, but to 23.  So he cannot do this.  We have chosen 18.  And then input 18 in C4 driver.  Anyone else have a workaround or idea?

[abovedeck]

ALSO-- I'm running Composer HE, not PRO.  Is there an update feature that I do not have in HE that would make sending these new settings impossible?