Jump to content
C4 Forums | Control4

Ademco 4232CBM Connected Building Module


Bullseye

Recommended Posts

Hey Grant, I have the exact same issue with my older ICM module. I think it's more of a driver problem and how often it polls the system. Sometimes it takes several minutes for an event to occur, others it's almost instantaneous... Try watching on the GUI to see when it shows a door actually open or close again. You'll be amazed at the lag!! I actually have mine connected to an HC800 which I thought would be faster but it's no different. I'm considering using the Houselogix piece that acts like a control panel instead: http://c4central.com/2012/05/24/houselogic-honeywell-integration-module/

Link to comment
Share on other sites


  • Replies 102
  • Created
  • Last Reply
Ok, So I have finally figured out what was going wrong with the 4232CBM talking to my system. The RS232 wiring has to be wired null modem and NOT straight through. Did this and everything is talking. However I have some serious lag between a door opening (wired contact sensor breaking contact) and a event going off (i.e. turn on light). Does anyone else have lag issues or found a way to fix these? I would like it if a sensor going off would cause an event with in 15 seconds.

Thanks!

Grant, I have zero lag. In fact, I have an event tied to motion sensors after 11pm to turn on the overhead lights in that hallway to 5%. Even with the slight lag of the motion detector itself, the lights are on within 2 seconds.

How long is your cable:

* between panel and 4232cbm

* between 4232cbm and C4 controller

In my case, I picked up a cheap 200B controller off eBay and mounted it next to the panel and have it dedicated to just handling alarm functions (although it's nice having it as a secondary to act as an embernet upgrader too).

Link to comment
Share on other sites

  • 3 weeks later...

Well after a lot of calling and searching, I finally got the 4232CBM working with my Vista 20P. A few things everyone should know:

The instructions that come with the 4232CBM are wrong! The TX and RX wires on the board are transposed.

The following settings are necessary in the driver:

ECP Address for 4232CBM 25

ECP Address for first Keypad 1

Number of Zones Depends on your system

Polling Off

AUI Support Yes

Debug Off

Now all works ok.

Link to comment
Share on other sites

I have a Vista 128BPT with the 4232CBM Module and am having a hell of a time getting any output from the unit.

Configuration is:

Device 25: Type 12 (RIS)

Device 26: Type 01, AUI Enabled

I connect a 10 foot null-modem cable with (1200-8-N-1 and no flow control) to the unit, and the data LED does flash when I send data to it. The power light is blinking continuously, and the HUB light will stay solid for a while and then will blink as well. Additionally, I configured zone 825 as a type 05 (fault) to create a fault if the panel can't communicate with the device, and when the board is unplugged, the fault does occur.

All that said, I don't get any output, and yet I would expect to get some data back on my PC when a zone is tripped.

Any help would be most appreciated!

Link to comment
Share on other sites

Well after a lot of calling and searching, I finally got the 4232CBM working with my Vista 20P. A few things everyone should know:

The instructions that come with the 4232CBM are wrong! The TX and RX wires on the board are transposed.

The following settings are necessary in the driver:

ECP Address for 4232CBM 25

ECP Address for first Keypad 1

Number of Zones Depends on your system

Polling Off

AUI Support Yes

Debug Off

Now all works ok.

"ECP Address for first Keypad" is also dependent on each individual system configuration and is based on how many AUI (touchscreen) alarm keypads you have:

0 AUIs: 1

1 AUIs: 2

2 AUIs: 5

3 AUIs: 6

4 AUIs: <you're maxed out and can't add the control 4 virtual keypad)

Link to comment
Share on other sites

I have a Vista 128BPT with the 4232CBM Module and am having a hell of a time getting any output from the unit.

Configuration is:

Device 25: Type 12 (RIS)

Device 26: Type 01, AUI Enabled

I connect a 10 foot null-modem cable with (1200-8-N-1 and no flow control) to the unit, and the data LED does flash when I send data to it. The power light is blinking continuously, and the HUB light will stay solid for a while and then will blink as well. Additionally, I configured zone 825 as a type 05 (fault) to create a fault if the panel can't communicate with the device, and when the board is unplugged, the fault does occur.

All that said, I don't get any output, and yet I would expect to get some data back on my PC when a zone is tripped.

Any help would be most appreciated!

How fast is the power light blinking? Fast = Proper handshaking not made, so no connection. Slow = Successful handshaking and connection is good.

The 4232CBM requires a proper "handshaking" from the controller (or your laptop in this case) before you'll get much out of it. You can turn debug on in the driver in Director and then tell the virtual touchpad to "reconnect" and see what information is being passed if you'd like to replicate the same from your test bench. The best way I've found (once you've verified that the Control4 controller is definitely sending commands -- I had a problem with this as mentioned earlier) is to just test using Director and the Virtual Keypad -- You know you have the settings "right" when the power light changes to a slow blink (very obvious difference in speed of blink) and you're able to pull the zone descriptors.

Link to comment
Share on other sites

The challenge I'm having is knowing if the 4232CBM module is correctly configured in the first place. I can't troubleshoot Director communicating with it until I know the 4232 is set up properly.

The problem I'm having is this: With a Vista 20P, the compass software only allows you to assign RIS addresses up to 23. The 4232CBM appears to be "hard-coded" to 25.

I've read people have had success with the 20P, so I'm curious how people got around this issue. The power light blinks fast, implying the 4232 is *not configured,* so I know the panel seems to be the issue I need to correct first.

The process we set up so far was:

- Field location 91 was enabled with 82

- AUI was enabled with *189

- Partition was 1, AUI address was 5 (not sure how important using 1 or 5 may be if it's the only AUI keypad)

RIS 23 is set up as a keypad, as that's the highest number available...

The module doesn't seem to leave its rapid flash mode. Any help on this would be majorly appreciated. Thanks.

Link to comment
Share on other sites

Led speed will only change when a virtual key pad in control4 is forced to Reconnect (assuming all other vars are correct. The LED speed will never change by just fiddling with the 4232 and panel by themselves.

Link to comment
Share on other sites

Fantastic, thank you, that helped me figure it out.

For future benefit of people having trouble, here's what I needed to do to get a Vista 20P working:

On the panel (via Compass or locally):

- Enable RIS mode in field *91 with 82.

- The AUI mode was enabled with *189.

- Address the "virtual keypad" as an AUI keypad, it should be 1, 2, 5 or 6.

[We have two older style (non-touchscreen) keypads, addressed 16 and 17, with the virtual AUI keypad set as 5.)

- NOTE: While the Compass software/security contractor will tell you the RIS addresses only go up to 23 on the software, ignore this, you don't need to make any changes in this regard in the panel configuration.)

On the driver:

- ECP address for 4232CBM: 25

- ECP address for 1st keypad: Set to number of first AUI keypad in your system.

(Assuming you have it set up like I did, where I have only one AUI keypad and it's the virtual one set up for address 5, I set this to 5 and it worked properly.)

- Number of zones: Enter number of your zones. In this case, I had 30.

- Polling: Off

- AUI Support: YES

On the 4232CBM module, the Power LED will blink rapidly regardless of how you configure the panel UNTIL the driver makes a successful connection to the card.

I turned Debug Mode to ON, and made sure the debug Lua console was in the background. I then I opened up the virtual keypad (double-clicked on the Security System driver in System Design), select the OTHER tab, and clicked on RECONNECT. I had to do this a couple of times before I started seeing debug information appear. You'll know your wiring is correct if you start seeing hex messages beginning with "Keypad:," "CAL#," "PSD:," or possibly something like "A5 5F," which I assume represents that AUI address. Messages with "Serial:" are output from Director to the 4232CBM, so they won't be useful in knowing if you're connected. Here is some example output:

CAL4 : 0200001BFF12F21620000000006563024543F531FB456CF5EC01020105CA002C

PSD : 0200001B010103020001000000010000000100030A0C04140000000000000056

PSD : 0200001B010103020001000000010000000100030A0E04140000000000000058

CAL4 : 02000017FF12F2122000000000666C02456CF5EC0101010000730028

CAL4 : 0200001BFF12F21620000000006763024543F531FB456CF5EC01020105C8002C

Keypad : 02000033FF12F720008310030000080200004641554C5420303320454E5452592020444F4F52532020202020202020202020710000000044

Once you verify you are connected, leave the virtual keypad and select the ACTIONS tab on the driver, and click the Zone Descriptor button. You should see output in the debugger like this:

Zone descriptors are Retrieving, please wait .....

===============================

Serial : 02 40 00 0D FF 13 F6 05 25 07 00 68 6B 0C 43 61 51 5A

CAL4 : 0200000EFF12F209200000000050FE3364001F

Serial : 02 40 00 12 FF 13 F6 05 25 0C 00 69 62 0C 45 49 F5 31 FB 43 61 A5 5F

CAL4 : 02000010FF12F20B200000000051FEFE3332310021

Serial : 02 40 00 12 FF 13 F6 05 25 0C 00 6A 62 0C 45 49 F5 32 FB 43 61 A3 5F

Now, if it works, you'll see this:

Partition No--> 1 --> Zone No:--> 2 --> Descriptor:--> MOTION DETECTOR

Serial : 02 40 00 17 FF 13 F6 05 25 11 00 6E 62 0C 45 49 F5 31 FB 45 43 F5 33 FB 43 6C E5 64

Keypad : 02000033FF12F720008310DC00000802000055504C4F414420434F4D504C4554454420202020202020202020202020202020EE0000000044

CAL4 : 02000021FF12F21C200000000056FEFEFEEC330031003100454E54525920444F4F5253C80032

Partition No--> 1 --> Zone No:--> 3 --> Descriptor:--> ENTRY DOORS

Serial : 02 40 00 17 FF 13 F6 05 25 11 00 6F 62 0C 45 49 F5 31 FB 45 43 F5 34 FB 43 6C E3 64

CAL4 : 02000021FF12F21C200000000057FEFEFEEC34003300310046414D494C5920524F4F4DDE0032

Partition No--> 1 --> Zone No:--> 4 --> Descriptor:--> FAMILY ROOM

Serial : 02 40 00 17 FF 13 F6 05 25 11 00 68 62 0C 45 49 F5 31 FB 45 43 F5 35 FB 43 6C E9 64

etc., etc. NOTE: I had to go through the RECONNECT sequence, let it do it's thing for a minute, then ZONE DESCRIPTOR button process three times before it synced up and worked. Once that was done, you see this:

Zone descriptors successfully retrieved.....

...and you'll notice the zone descriptors are now in the Connections/binding area on Composer.

Best of luck.

-j

Link to comment
Share on other sites

  • 1 month later...

Hey Everone, sorry to bug you - I'm a complete newbie when it comes to alarm panels & am trying to put one of these in. I'm doing it on our test system first, but haven't been able to get it to connect at all.

I have two flashing lights & one solid light at this point. This is on a VISTA 21ip. There is only one keypad on the alarm panel, and it's not a touchscreen. Can anyone confirm the exact key sequence that I should be putting in the programming menu of the Vista?

What I've been doing is *91 -- 82; *189 -- 1155 & then entering 10 in the address field for Keypad 17. Is that correct, or am I just being a total moron here?

Link to comment
Share on other sites

  • 2 months later...
  • 4 weeks later...

I have a Safewatch Pro 3000 with 9.12 firmware and a newly-installed 4232CBM connected to an HC300 running 1.8.2 using the Control4 Certified on 8/19/2011 driver.

The settings are:

ECP for module: 25

ECP for keypad: 16

Zones: 48

Partitions: 3

Polling: Off

AUI: Yes

I am able to see the data coming from the 4232CBM just fine, such as panel state and status messages.

Attempts to get the zone list suggest that the 4232CBM is not receiving data from the HC300.

Zone descriptors are Retrieving, please wait  .....
===============================

Serial : 02 40 00 0D FF 13 F6 10 30 07 00 68 6B 0C 43 61 46 65
Serial : 02 40 00 0D FF 13 F6 10 30 07 00 68 6B 0C 43 61 46 65
Retrying to get the zone descriptors.......
Serial : 02 40 00 0D FF 13 F6 10 30 07 00 68 6B 0C 43 61 46 65
Retrying to get the zone descriptors.......
Serial : 02 40 00 0D FF 13 F6 10 30 07 00 68 6B 0C 43 61 46 65
Retrying to get the zone descriptors.......
Serial : 02 40 00 0D FF 13 F6 10 30 07 00 68 6B 0C 43 61 46 65
Retrying to get the zone descriptors.......
Keypad : 02000033FF12F70200071008001C0802000020202A2A2A2A20414454202A2A2A2A202020526561647920746F2041726D2020410000000044
Serial : 02 40 00 0D FF 13 F6 10 30 07 00 68 6B 0C 43 61 46 65
Retrying to get the zone descriptors.......

Please try again, Click the zone descriptor button from the Actions tab.....

The possible reasons are:
=========================
** 4232CBM module is not responding.
** Panel is not responding.

Pressing Reconnect yields:

Key Msg: 90->
Serial : 02 00 00 05 FF 11 02 D0 D0 B7
Serial : 02 00 00 07 FF 10 01 00 00 19 00 30
Serial : 02 00 00 05 FF 07 01 00 00 0C
Serial : 02 40 00 0F FF 13 F6 10 30 09 00 68 6B 0E 45 43 F5 31 38 67

Pressing the "*" on the Control4 keypad yields:

Serial	: 02 00 00 08 FF 13 F6 10 10 02 0A E4 20
Key Msg: 10-> 02 00 00 08 FF 13 F6 10 10 02 0A E4 20

I've double-checked the connections. Any idea what the problem could be?

Link to comment
Share on other sites

Right, leave module set at 25 but start by changing the keypad emulation address to 1 then reconnect. Try getting the zone info again. Repeat advancing numerically till it gets it. The panel only supports 5 address usually unless you're using a 128BPT. You transposed the Rx & Tx wires on the female end that connects to your HC-300 per the directions right?

Link to comment
Share on other sites

  • 2 years later...

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.