Announcement

**mnsandler** · May 7, 2011, 04:01 PM

Originally posted by chrisgo View Post

I have a AD2USB version 2.0. I have been experiencing issues with disconnects (1 every 10 days or so) so I purchased a serial adapter from Nutech.

I am having problems with the AD2USB and Nutech suggested switching down from 115200 baud to 19200. Is there any way to do this with the plugin?

Sean from Nutech has told me he has firmware that will work with 19200 if the plugin can accomodate this.

Well it does now. give this build a try.

Add a BaudRate=19200 line to the [General] section of your vistaalarm.ini

this will override the default of 115200

shutdown hs and backup and replace the current hspi_vistaalarm.dll file with the attached.

Attached Files

HSPI_VistaAlarm_1.2.5.1.zip (56.2 KB, 7 views)

**chrisgo** · May 7, 2011, 07:18 PM

Hi Mark, many thanks for compiling a new version of the plugin so that we can try this out.

I will let you know how the testing goes once Sean sends me the firmware.

**mnsandler** · May 7, 2011, 09:57 PM

Originally posted by chrisgo View Post

Hi Mark, many thanks for compiling a new version of the plugin so that we can try this out.

I will let you know how the testing goes once Sean sends me the firmware.

you're welcome. it surprises me that you are still having problems with a serial based ad2usb.

good luck

**chrisgo** · May 7, 2011, 10:18 PM

Me too. Do you know if many people are using the serial adapter?

I have automated events to arm and disarm the system in the evening and the morning. This morning the disarm action triggered a fire alert which almost resulting the fire services being called out.

It doesn't seem to matter which event is run as this morning the disarm triggered the problem yet later when I was testing it was the arm-stay action that triggered things.

It seems to work fine most of the time but then malfunctions at other times. I did a test today of repeatedly arming and disarming the system and it worked fine every time except once. The arm-stay action initiated a burglar and fire alarm as show in the log below.

Sean believes it may be noise coming from the alarm panel and that reducing the baud rate will resolve this.

Sean is also wondered if the plugin is configured correctly. I don't think that's the problem as everything was working fine on the USB interface. The reason I switched is because the USB interface disconnects after a couple of weeks and I wanted a solid connection.

If however you can think of anything in the plugin I could check that would cause this sort of problem, I'd welcome the advice.

Here's a snapshot of the log while I was testing earlier today. I have all logging enabled.

07/05/2011 11:17:25 AM ~!~Vista Alarm~!~Opened COM port 10
07/05/2011 11:17:25 AM ~!~Vista Alarm~!~Sent cmd: V
07/05/2011 11:17:25 AM ~!~Vista Alarm~!~Found the AD2USB on COM port 10 running firmware version V2.1f.10
07/05/2011 11:17:25 AM ~!~Vista Alarm~!~Error starting monitor
07/05/2011 11:17:31 AM ~!~Vista Alarm~!~Processing msg on Partition 1
07/05/2011 11:17:31 AM ~!~Vista Alarm~!~[100000011000--------],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
07/05/2011 11:17:41 AM ~!~Vista Alarm~!~Processing msg on Partition 1
07/05/2011 11:17:41 AM ~!~Vista Alarm~!~[100000011000--------],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
07/05/2011 11:17:51 AM ~!~Vista Alarm~!~Processing msg on Partition 1
07/05/2011 11:17:51 AM ~!~Vista Alarm~!~[100000011000--------],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
07/05/2011 11:18:01 AM ~!~Vista Alarm~!~Processing msg on Partition 1
07/05/2011 11:18:01 AM ~!~Vista Alarm~!~[100000011000--------],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
07/05/2011 11:18:10 AM ~!~Vista Alarm~!~Processing msg on Partition 1
07/05/2011 11:18:10 AM ~!~Vista Alarm~!~[100000011000--------],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
07/05/2011 11:18:20 AM ~!~Vista Alarm~!~Processing msg on Partition 1
07/05/2011 11:18:20 AM ~!~Vista Alarm~!~[100000011000--------],008,[f700000f1008001c28020000000000]," DISARMED CHIME Ready to Arm "
07/05/2011 11:18:26 AM ~!~Event~!~Event Trigger "Arm alarm (stay)"
07/05/2011 11:18:26 AM ~!~Vista Alarm~!~Sending [code]+3
07/05/2011 11:18:26 AM ~!~Vista Alarm~!~Setting Partition 1 to Burglar Alarm
07/05/2011 11:18:26 AM ~!~Vista Alarm~!~Setting System to Burglar Alarm
07/05/2011 11:18:26 AM ~!~Event~!~Event Trigger "Burglar alarm activated"
07/05/2011 11:18:26 AM ~!~Vista Alarm~!~Setting Partition 1 to Fire Alarm
07/05/2011 11:18:26 AM ~!~Vista Alarm~!~Setting System to Fire Alarm
07/05/2011 11:18:26 AM ~!~Vista Alarm~!~Processing msg on Partition 1
07/05/2011 11:18:26 AM ~!~Vista Alarm~!~[100100011100--------],095,[f700000f109500312a020000000000],"FIRE 95 "

**DSteiNeuro** · May 8, 2011, 12:10 PM

I am setting up a new 20P panel with AD2USB serial and have had the same problem with a false Fire alarm. The ademco displayed Fire 95.

I am not sure what I did to cause the false alarm, but it may have happened during an Arm, disarm or zone bypass from HS Touch.

I didn't think to grab the HS Log entry but have turned debug mode on and will do so if it occurs again.

One thought is that I had Device Code (DC) #1 set to the Partition 1 status. By default on the 20P zone 1 is fire. I have switched the Partition 1 status to a different DC and haven't had a reoccurrence, but it is an intermittent problem.

My panel is still on local, but obviously can't risk false fire alarming.

The other issue that I am having is the Last Panel Message displays ****Disarmed**** Ready to Arm, even when the system is armed and in other modes. I have Suppress duplicate alarm messages ticked with a message timeout setting of 10 secs.

Plugin version 1.2.00
AD2USB (Serial version Firmware V2.2a.1) I have the serial cable attached to a Quatech.

/8/2011 8:23:21 AM Vista Alarm Opened COM port 5
5/8/2011 8:23:21 AM Vista Alarm Sent cmd: V
5/8/2011 8:23:21 AM Vista Alarm Found the AD2USB on COM port 5 running firmware version V2.2a.1
5/8/2011 8:23:21 AM Vista Alarm Monitor started...
5/8/2011 8:23:21 AM Plug-In Finished initializing plug-in Vista Alarm
....
5/8/2011 8:23:26 AM Vista Alarm Ignoring Message
5/8/2011 8:23:26 AM Vista Alarm [100000010000--------],008,[f70000800008001c08020000000000],"****DISARMED**** Ready to Arm "
...
5/8/2011 10:01:34 AM Vista Alarm Sending [code]+6#
5/8/2011 10:01:35 AM Vista Alarm Sending *
5/8/2011 10:01:35 AM Vista Alarm Processing msg on Partition 1
5/8/2011 10:01:35 AM Vista Alarm [000100010000--------],008,[f700004f1008000c08020000000000],"BYPAS "
5/8/2011 10:01:35 AM Vista Alarm Zone changed. Set device #7 to Value=Bypass
5/8/2011 10:01:35 AM Vista Alarm Processing msg on Partition 1
5/8/2011 10:01:35 AM Vista Alarm [100101110000--------],007,[f700004f1007011018020000000000],"BYPAS 07 LIVING SLIDING "
5/8/2011 10:01:36 AM Vista Alarm Zone changed. Set device #12 to Value=Bypass
5/8/2011 10:01:36 AM Vista Alarm Processing msg on Partition 1
5/8/2011 10:01:36 AM Vista Alarm [100101110000--------],012,[f700004f1012011018020000000000],"BYPAS 12 MASTER SLIDING "
5/8/2011 10:01:38 AM Vista Alarm Setting Partition 1 to Bypass-Ready
5/8/2011 10:01:38 AM Vista Alarm Clearing all zones for Ready-Bypass mode.
5/8/2011 10:01:38 AM Vista Alarm Setting System to Bypass-Ready
5/8/2011 10:01:38 AM Vista Alarm Processing msg on Partition 1
5/8/2011 10:01:38 AM Vista Alarm [100100110000--------],008,[f700004f1008001c18020000000000],"DISARMED BYPASS Ready to Arm "
5/8/2011 10:01:38 AM Vista Alarm Sending [code]+3
5/8/2011 10:01:39 AM Vista Alarm Ignoring Message
5/8/2011 10:01:39 AM Vista Alarm [001103110000--------],008,[f70000011008038c18020000000000],"ARMED ***STAY***You may exit now"
5/8/2011 10:01:39 AM Vista Alarm Setting Partition 1 to Armed Stay
5/8/2011 10:01:39 AM Vista Alarm Setting System to Armed Stay
5/8/2011 10:01:39 AM Vista Alarm Processing msg on Partition 1
5/8/2011 10:01:39 AM Vista Alarm [001100110000--------],008,[f700004e0008008c18020000000000],"ARMED ***STAY***You may exit now"
5/8/2011 10:02:03 AM Vista Alarm Sending [code]+7
5/8/2011 10:02:38 AM Vista Alarm Processing msg on Partition 1
5/8/2011 10:02:38 AM Vista Alarm [001100110000--------],008,[f700004f1008008c18020000000000],"ARMED ***STAY*** ZONE BYPASSED

**mathewss** · May 8, 2011, 01:12 PM

Firmware updates to investigate this issue.

I am working on a modification to the firmware for V2.0 and V2.2 hardware today and will be posting them in the next few hours. This will do two things.

1. make it harder to trigger a fire or panic by removing the chr(1) - chr(4) as keys to trigger these events. It is way to easy to have a bad character sent to the serial port cause a F1-F4 to happen. I had planned on a complex series of keys but for now I am going to keep it simple. to trigger a F1 you would send chr(1) 3 times. This is much more difficult to happen by accident.

2. Echo added to the "Sending." message to include what is being sent. This is a temporary patch to see if we can get to the bottom of where these accidental characters are coming from and how often. as long as the homeseer logs records these messages we will be able to do better diagnostics.

I will keep you posted.

Re
Sean M

**chrisgo** · May 8, 2011, 01:33 PM

Hi Sean, many thanks for working on this over the weekend. This was not expected but is greatly appreciated as we are now somewhat paranoid that the alarm system will malfunction again.

Reference the code used to trigger the alarms, I'd rather have something that it is closer to impossible to accidentally trigger rather than much more difficult.

This is just my 2 cents but I'd much rather have to program a complicated series of keys than ever have this issue again. I have a young child in the house and the false alarm yesterday caused quite an upset.

Thanks again for giving this your attention.

Chris

**DSteiNeuro** · May 9, 2011, 11:48 PM

Hi Sean,

Thanks for working on this. Had another false alarm.
Here is the HS Log, in case it will help.

5/9/2011 9:38:16 PM Vista Alarm Sending [code]+608
5/9/2011 9:38:17 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:38:17 PM Vista Alarm [100100111000--------],008,[f700004f1008001c38020000000000],"BYPAS "
5/9/2011 9:38:24 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:38:24 PM Vista Alarm [100101111000--------],008,[f700004f1008011038020000000000],"BYPAS 08 KITCHENDOOR "
5/9/2011 9:38:26 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:38:26 PM Vista Alarm [100101111000--------],012,[f700004f1012011038020000000000],"BYPAS 12 MASTER SLIDING "
5/9/2011 9:38:34 PM Vista Alarm Sending [code]+1
5/9/2011 9:38:35 PM Vista Alarm Ignoring Message
5/9/2011 9:38:35 PM Vista Alarm [000101011000--------],008,[f70000011008010c28020000000000]," DISARMED CHIME Hit * for faults"
5/9/2011 9:38:35 PM Vista Alarm Setting Partition 1 to Faulted
5/9/2011 9:38:35 PM Vista Alarm Setting System to Faulted
5/9/2011 9:38:35 PM Vista Alarm Sending *
5/9/2011 9:38:35 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:38:35 PM Vista Alarm [000100011000--------],008,[f700004e0008000c28020000000000]," DISARMED CHIME Hit * for faults"
5/9/2011 9:38:35 PM Vista Alarm Zone changed. Set device #8 to Value=Normal
5/9/2011 9:38:35 PM Vista Alarm Zone changed. Set device #12 to Value=Normal
5/9/2011 9:38:35 PM Vista Alarm Zone changed. Set device #4 to Value=Normal
5/9/2011 9:38:35 PM Vista Alarm Updated Cleared Zones, System is Faulted
5/9/2011 9:38:36 PM Vista Alarm Zone changed. Set device #12 to Value=Fault
5/9/2011 9:38:36 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:38:36 PM Vista Alarm [000100011000--------],012,[f700004f1012000028020000000000],"FAULT 12 MASTER SLIDING "
5/9/2011 9:38:50 PM Vista Alarm Sending [code]+604
5/9/2011 9:38:51 PM Vista Alarm Sending *
5/9/2011 9:38:51 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:38:51 PM Vista Alarm [000100011000--------],008,[f700004f1008000c28020000000000],"BYPAS "
5/9/2011 9:38:52 PM Vista Alarm Zone changed. Set device #4 to Value=Bypass
5/9/2011 9:38:52 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:38:52 PM Vista Alarm [000101111000--------],004,[f700004f1004010038020000000000],"BYPAS 04 GARAGE DOOR "
5/9/2011 9:39:03 PM Vista Alarm Sending [code]+612
5/9/2011 9:39:04 PM Vista Alarm Sending *
5/9/2011 9:39:05 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:39:05 PM Vista Alarm [000100111000--------],012,[f700004f1012000138020000000000],"FAULT 12 MASTER SLIDING "
5/9/2011 9:39:08 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:08 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:08 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:08 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:08 PM Vista Alarm Processing msg on Partition 1
5/9/2011 9:39:08 PM Vista Alarm [000100111100--------],095,[f700004f109500213a020000000000],"FIRE 95 "
5/9/2011 9:39:12 PM Vista Alarm Setting Partition 1 to Faulted
5/9/2011 9:39:12 PM Vista Alarm Setting System to Faulted
5/9/2011 9:39:13 PM Vista Alarm Ignoring Message
5/9/2011 9:39:13 PM Vista Alarm [000101011100--------],095,[f7000001109501202a020000000000],"FIRE 95 "
5/9/2011 9:39:13 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:13 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:13 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:13 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:13 PM Vista Alarm Zone changed. Set device #4 to Value=Normal
5/9/2011 9:39:13 PM Vista Alarm Updated Cleared Zones, System is Fire Alarm
5/9/2011 9:39:17 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:17 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:17 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:17 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:17 PM Device Update Device: Thermostat Z-Wave Interface Thermostat Temperature value set to 70.5 (7050/F)
5/9/2011 9:39:21 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:21 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:21 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:21 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:25 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:25 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:25 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:25 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:29 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:29 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:29 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:29 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:33 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:33 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:33 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:33 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:37 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:37 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:37 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:37 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:41 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:41 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:41 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:41 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:45 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:45 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:45 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:45 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:48 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:48 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:48 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:49 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:52 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:52 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:52 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:52 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:39:56 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:39:56 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:39:56 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:39:56 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:40:00 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:40:00 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:40:00 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:40:00 PM Vista Alarm Setting System to Fire Alarm
5/9/2011 9:40:04 PM Vista Alarm Setting Partition 1 to Burglar Alarm
5/9/2011 9:40:04 PM Vista Alarm Setting System to Burglar Alarm
5/9/2011 9:40:04 PM Vista Alarm Setting Partition 1 to Fire Alarm
5/9/2011 9:40:04 PM Vista Alarm Setting System to Fire Alarm

**mnsandler** · May 10, 2011, 09:51 AM

I see that i need to make a change to keep the plugin from bouncing from Fire to Burglar state and back.

i wonder if its worth disabling the plugin monitor (dev 99) for a few days and see if you get any false alarms. Maybe logging the msgs via putty or hyperterminal would be helpful.

thanks

**chrisgo** · May 11, 2011, 11:34 PM

I have had monitoring disabled for the last few days. The AD2USB is still hooked up the serial port.

I have not had a false alarm with the monitoring disabled. I believe the false alarms are only triggered when the AD2USB is instructed to send a command to the alarm panel. Every time my alarm has triggered falsely coincides with the plugin sending a command as shown by the logs.

Sean has sent me a new version of firmware. I plan to upgrade the firmware and test extensively Friday morning when the family is out.

I've created an event that repeatedly arms and disarms the system every 10 seconds. I'll leave this running for an hour or so and let you know is the alarm triggers accidentally.

I believe Sean has increased the logging output from the AD2USB so I'll make sure I capture this in full.

Chris

**mnsandler** · May 12, 2011, 12:41 PM

Originally posted by chrisgo View Post

I have had monitoring disabled for the last few days. The AD2USB is still hooked up the serial port.

I have not had a false alarm with the monitoring disabled. I believe the false alarms are only triggered when the AD2USB is instructed to send a command to the alarm panel. Every time my alarm has triggered falsely coincides with the plugin sending a command as shown by the logs.

Sean has sent me a new version of firmware. I plan to upgrade the firmware and test extensively Friday morning when the family is out.

I've created an event that repeatedly arms and disarms the system every 10 seconds. I'll leave this running for an hour or so and let you know is the alarm triggers accidentally.

I believe Sean has increased the logging output from the AD2USB so I'll make sure I capture this in full.

Chris

let me know if you don't see the extra ad2usb msgs in the hs log. I can't remember if i log everything.

**kfriedenberger** · May 12, 2011, 07:21 PM

Fire 95

sean - this definitely occurs when simply sending instructions to the device. i have a vista 10se and the latest 2.2 firmware (which fixed the 10se connect issue!). i'm using python pyserial to send "[Master_code]1" multiple times to the device a few seconds apart and I get the 95 FIRE alarm; seemingly randomly but always within 3 or 4 attempts.

pyserial code:

Code:

import serial
ser = serial.Serial('/dev/ttyUSB0',timeout=12,baudrate=115200)
ser.write("33331")
ser.close()

**chrisgo** · May 13, 2011, 10:21 AM

New firmware testing

I tested the new firmware this morning. So far so good.

The test:

1. Send [master code]+3
2. Wait 5 seconds
3. Send [master code]+1
4. Wait 5 seconds
5. Repeat from step 1

This ran for about an hour and the system armed and disarmed without any issues.

**mnsandler** · May 13, 2011, 01:00 PM

Originally posted by chrisgo View Post

I tested the new firmware this morning. So far so good.

The test:

1. Send [master code]+3
2. Wait 5 seconds
3. Send [master code]+1
4. Wait 5 seconds
5. Repeat from step 1

This ran for about an hour and the system armed and disarmed without any issues.

good deal. btw, what vista model do you have? didn't see it in the thread

Announcement

Setting baud rate

Setting baud rate

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment