Electronic Alarms and Home Security Devices - Programming Vista128PADT X-10 or Relay Interface

I have an ADT Security System with a VISTA128PADT board, a relay connection (4204) and an X-10 Interface (with the special transformer). There are two control panels, one of which is ADT's I-Center, and the other is a more convetional panel. At present the system is programmed with one relay device -- which activates the garage door. I only have one X-10 device programmed, and it receives an "ON" command when an alarm is tripped, and an "OFF" command when the system is disarmed. I would like to add a second X-10 device (or use a second relay) to identify for my home control systems (HomeSeer) if the security system is placed in any of the armed states (away, stay, night(instant). I have the installation code, and can enter and exit the data filed or menu programming mode. What are the code sequences to create a second X-10 device, lable it, and have it go "ON" when the system is armed and "OFF" when the system is disarmed? And what are the codes to enter additional X-10 items to my I-Center "Lights" menu?

You have a pretty complex system there. The Vista 128 is a commercial grade panel, with a pretty large number of options and a fairly complicated programming sequence.


You will need the installer manual and the manual for the touchscreen keypad, which has it's own programming and setup info:

http://dougbrander.com/Documents/Vista%20128BP%20Installation.pdf

http://www.myalarm.com/manuals_prog/Ademco_Vista_128.pdf

http://www.knightwatch.net/professional_service/manuals/Ademco%20-%20Honeywell/Automation/HomeAutomation.pdf

http://nassausecurity.com/usermanuals/6270im.pdf

Basically you need to read through the section on output programming that starts on page 3-13 on the V128 installer manual, and the section on device programming mode (*93 programming).

Once you do that I can try to help you interpret it.

There's not really a cookie cutter formula for what you want to do, every installation is custom by definition.

Thank you, I will download and read the manuals. I am on a trip, so it will be time well spent. Fortunately, I have a helper who has worked with security systems before. After I read some more, I will get back.

Success. I read the manuals you provided, and also found that I needed the programming manual, which was most helpful. First, I stepped through all the Data Fields and recorded the present settings. That was a pain. Then I carefully entered and exited the Programming Menu mode (#93) several times to step through the menus and record all the data from the zone programming. That was interesting. Then I entered the Output Programming portion of the Menu Mode and documented the two previous entries -- which were done by the original installer. I then added the entries I wanted. I used two entries, one entry sends an X-10 command upon entry (arming) and exit (disarming) of the STAY security mode, and the other entry sends an X-10 command upon entry (arming) and exit (disarming) of the AWAY security mode. My home control software (HomeSeer) can see these actions and hence now has situational awareness as to the state of the alarm system. I have two tasks yet to perform. One will be rather easy. There are some really dumb zone descriptions, that I need to clean up (for the KeyFobs), but the documentaiton on how to do that is very good. The other problem I need some help with. I have not been able to figure out how I change the descriptions on the panel for the X-10 devices or the 4204 relays. When I added the extra commands, they appeared on the menu but with strange names that were previously used by the installer (M3.P2G.DR and M4.PR.SL.D). Where can I edit these device names? I looked in devices, and I looked in the 600 area for zones and found nothing that appeared to be these devices. Suggestions?

There is a _voice_ descriptor programming for the outputs, but I _think_ that the display descriptors might be only changeable via the Compass software. Even then, I'm not sure. I don't use Compass, and their manual is sketchy at best.

I did try and change the voice descriptors, but they must be different than the device (output) descriptors. I can see the panel "downlaod" to the I-Center (6270) 37 zones decriptors and 5 Output Descriptors. So they must be stored in the panel. I downloaded the Compass Software and will play with it. Kind of a pain, since I have to use the LAN to use it. I very much appreciate your help. Cheers

For $30 I signed up for one month of technical support from ADEMCO. They solved this problem. It turns out that the outputs you program -- which show up on the "Lighting" page -- are correlated with the 6xx zones. That is to say, the alpha descriptor for zone 601 shows up as the descriptor for "output activity" 01. There are a few tricks and interesting nuances to make this work. First the lighting page only displays about 12 characters, so the standard word dictionary will probably not be adequate for your needs. Hence one needs to start with making custom words, and then use these words in the alpha programming section for the zone descriptors. One does not need to make zones 6xx viable, they can be default values and inactive, but their descriptors are used for the outputs. At this point, all of what I hoped to accomplish with this effort has been completed. I did try the Compass software, and -- as you observe -- it does not appear to be very user friendly. I am still working that with ADEMCO. Thanks for your assistance.

Quick Follow-up. ADEMCO Compass program is not compatible with ADT's modified system.

No, it's not. They have their own version. I didn't think about it because I generally recommend DIYs to leave it out of the picture.

Upon giving your prior posts a thorough re-read, I realized that most of the stuff you were chasing was particular to the the AUI touch screen display. Talk about adding more layers or complexity.

Well, you seem to be getting it in hand, so have fun with it.

As I said, this is a _very_ heavy duty system for a residential install. It's got a lot of options that a home system rarely needs.