Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Slave Panel Communication Failure
#1
Hi,

I have a Comfort I Ultra Action 4.233.

I went away for the past weekend and something strange triggered the system.

The message I received when the system called was \"Tamper Alarm ID 33\" (Not exact words).

When I got back I downloaded the log and checked out the system.

The log file read as follows:

Nov 19, 17:42, RS485 Comms Fail, REM 1
Nov 19, 17:42, Tamper, REM 1
Nov 19, 17:43, RS485 Comms Fail,Doorstation 1 - Door station 1
Nov 19, 17:43, RS485 Comms Fail,81
Nov 19, 17:43, RS485 Comms Fail,18
Nov 19, 17:43, RS485 Comms Restore,Doorstation 1 - Door station 1
Nov 19, 17:43, RS485 Comms Restore,81
Nov 19, 17:43, Tamper,REM 1
Nov 19, 17:44, RS485 Comms Fail,Doorstation 1 - Door station 1
Nov 19, 17:44, RS485 Comms Fail,81
Nov 19, 17:44, RS485 Comms Fail,18
Nov 19, 17:44, RS485 Comms Restore,Doorstation 1 - Door station 1
Nov 19, 17:44, RS485 Comms Restore,81

Nov 19, 20:52, RS485 Comms Fail, REM 1
Nov 19, 20:52, Tamper,REM 1
Nov 19, 20:52, RS485 Comms Restore,REM 1

What is REM 1?  I assumed it was the slave panel because the message mentioned ID 33.  UCM 2 (ID 18) and RIO (ID 81) are connected to the slave panel.

I checked the system, and especially the wiring, but everything seemed fine.

Then this morning the communications failure happened again.  The system was not armed, so the alarm was not triggered.  The event log from this morning said the following:

Nov 21, 07:16, RS485 Comms Fail, REM 1
Nov 21, 07:16, RS485 Comms Restore, REM 1
Nov 21, 07:17, Sign-in, User 1
Nov 21, 07:17, RS485 Comms Fail, REM 1
Nov 21, 07:16, RS485 Comms Restore, REM 1
Nov 21, 07:18, Sign-in, User 1
Nov 21, 07:33, RS485 Comms Fail, REM 1
Nov 21, 07:33, RS485 Comms Restore, REM 1
Nov 21, 08:51, Sign-in, User 1

I tried to establish if there was anything else that occurred at these times that could be related to the comms failure, but I could not find anything.

Please help.

Regards,

Clinton.
Reply
#2
Hi Clinton,

I would suggest that you some of the modules and see if the same problem occurs.

Perhaps you could tell us more of your configuration? Such as number of modules, relays connected, etc. Is your slave panel powered up separately or tapping from the main panel?

Probably why you are seeing a REM1 is because of a wrong eventlog.cfg file, which is where Comfigurator gets the name of the various devices based on the ID.


Regards
Reply
#3
Hi,

My system consists of the following:
  • 1 x Mainboard (Action 4.233)
  • 1 x SEM01 Slave Expansion Board with its own power supply and battery (The 0V of the mainboard and the slave are commoned)
  • 1 x Ringer Module connected to the mainboard
  • 1 x LEM01 Local Expansion Module connected to the mainboard
  • 1 x LEM01 Local Expansion Module connected to the slave board
  • 1 x RIO connected to the slave board
  • 1 x Ethernet UCM connected to the mainboard and local network
  • 1 X Serial/IR/Audio UCM connected to the slave board and not connected to anything at the moment
  • 1 x KP04 Keypad connected to mainboard
  • 1 x Door Station
Inputs are connected to PIR and magnetic contact sensors and a light sensor.

Outputs are connected to relays to switch lights, open gate and call security company (via RF).

It is going to be difficult to disconnect modules as the system provides our security but I will see what I can do.

The problem occurred again this morning, but earlier, and as a result triggered the alarm and called the security company which is now charging me fines for false alarms.

How do I fix the eventlog.cfg file?

Many thanks.

Clinton.
Reply
#4
Hi Clinton,

Please contact adlim or adrian@cytech.biz for instructions about some changes you may be able to make

Reply
#5
After modification.


Attached Files Thumbnail(s)
   
Reply
#6
As for the Event Log, there is a new Eventlog.cfg file which is available from http://www.cytech-technology.com/software.html . Use this file and you should see the module name correctly.
Reply
#7
Hi,

I am still using Comfigurator 1.6.0.  Will the Comfigurator 2.1.0 eventlog file work with my older version?

Thanks.

Clinton.
Reply
#8
Please upgrade to the new version to avoid any problems. Then uou can upload event log again
regards
Reply
#9
Hi,

I upgraded once, but experienced too many issues.  One of the issues I had was the same as this one http://finance.groups.yahoo.com/group/co...ssage/8482 (I have the exact same RF Arm Disarm configuration).  I then reverted back to 1.6.0.

I would be a bit concerned about adding all of that into the scenario now.  What is your view - should I upgrade?

Thanks.
Reply
#10
One of the things which 2.1 addressed was precisely the coding of the If/Then statements for Comfort II
If you still continue to use 1.6 it will be difficult to support as there will be other issues which will confuse things

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)