Comfort  Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

Slave Panel Communication Failure
 Moderated by: admin
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Tuesday Nov 21st, 2006 10:43 am
   PM  Quote  Reply 
1st Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

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.



 Posted: Tuesday Nov 21st, 2006 11:59 pm
   PM  Quote  Reply 
2nd Post
adlim
Member


Joined: Wednesday May 3rd, 2006
Location: Singapore
Posts: 210
Status: 
Offline

  back to top

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



 Posted: Wednesday Nov 22nd, 2006 09:00 am
   PM  Quote  Reply 
3rd Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

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.



 Posted: Thursday Nov 23rd, 2006 01:38 am
   PM  Quote  Reply 
4th Post
adlim
Member


Joined: Wednesday May 3rd, 2006
Location: Singapore
Posts: 210
Status: 
Offline

  back to top

Hi Clinton,

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

Last edited on Thursday Nov 23rd, 2006 05:49 am by



 Posted: Thursday Nov 23rd, 2006 01:39 am
   PM  Quote  Reply 
5th Post
adlim
Member


Joined: Wednesday May 3rd, 2006
Location: Singapore
Posts: 210
Status: 
Offline

  back to top

After modification.

Attachment: soldered.JPG (Downloaded 101 times)



 Posted: Thursday Nov 23rd, 2006 01:43 am
   PM  Quote  Reply 
6th Post
adlim
Member


Joined: Wednesday May 3rd, 2006
Location: Singapore
Posts: 210
Status: 
Offline

  back to top

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.

Last edited on Friday Aug 3rd, 2007 04:54 am by



 Posted: Thursday Nov 23rd, 2006 07:52 am
   PM  Quote  Reply 
7th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

Hi,

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

Thanks.

Clinton.



 Posted: Thursday Nov 23rd, 2006 08:07 am
   PM  Quote  Reply 
8th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

Please upgrade to the new version to avoid any problems. Then uou can upload event log again
regards



 Posted: Thursday Nov 23rd, 2006 01:55 pm
   PM  Quote  Reply 
9th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

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/comfort-technical/message/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.



 Posted: Friday Nov 24th, 2006 03:24 am
   PM  Quote  Reply 
10th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

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



 Posted: Friday Nov 24th, 2006 07:44 am
   PM  Quote  Reply 
11th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

Hi,

Just to check - I have Comfort I - so will the upgrading to 2.1.0 still apply?

Thanks.



 Posted: Friday Nov 24th, 2006 07:52 am
   PM  Quote  Reply 
12th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

Ultra 4.230 and above will support branch actions but if you dont have that version, you should still use the latest comfigurator

A new version will be released soon

regards



 Posted: Friday Nov 24th, 2006 10:44 am
   PM  Quote  Reply 
13th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

Hi,

Thanks for the help so far.  I will upgrade Comfigurator and try disconnecting the modules this weekend.

In the meantime the problem is getting worse.  I include the event log below to illustrate this.

Further, this morning the panic alarm went off, without the panic button being pressed.

This is becoming an issue for us.

Regards,Clinton.

Event log:

Nov 24, 06:57, RS485 Comms Restore, 81
Nov 24, 06:57, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 06:57, RS485 Comms Restore, 81
Nov 24, 06:57, RS485 Comms Fail, REM 1
Nov 24, 06:57, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 06:57, RS485 Comms Fail, 81
Nov 24, 06:57, RS485 Comms Fail, 18
Nov 24, 06:58, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 06:58, RS485 Comms Restore, 81
Nov 24, 06:58, RS485 Comms Fail, REM 1
Nov 24, 06:58, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 06:58, RS485 Comms Fail, 81
Nov 24, 06:58, RS485 Comms Fail, 18
Nov 24, 06:59, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 06:59, RS485 Comms Restore, 81
Nov 24, 06:59, RS485 Comms Fail, REM 1
Nov 24, 06:59, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 06:59, RS485 Comms Fail, 81
Nov 24, 06:59, RS485 Comms Fail, 18
Nov 24, 07:00, RS485 Comms Restore, 12
Nov 24, 07:00, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:00, RS485 Comms Restore, 81
Nov 24, 07:00, RS485 Comms Fail, REM 1
Nov 24, 07:00, RS485 Comms Restore, REM 1
Nov 24, 07:00, RS485 Comms Fail, REM 1
Nov 24, 07:01, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 07:01, RS485 Comms Fail, 81
Nov 24, 07:01, RS485 Comms Fail, 18
Nov 24, 07:02, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:02, RS485 Comms Restore, 81
Nov 24, 07:02, RS485 Comms Fail, REM 1
Nov 24, 07:02, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 07:02, RS485 Comms Fail, 18
Nov 24, 07:02, RS485 Comms Fail, 81
Nov 24, 07:03, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:03, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:03, RS485 Comms Restore, 81
Nov 24, 07:03, RS485 Comms Fail, REM 1
Nov 24, 07:03, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 07:03, RS485 Comms Fail, 81
Nov 24, 07:04, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:04, RS485 Comms Restore, 81
Nov 24, 07:04, RS485 Comms Fail, REM 1
Nov 24, 07:04, RS485 Comms Fail, 18
Nov 24, 07:04, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 07:04, RS485 Comms Fail, 81
Nov 24, 07:05, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:05, RS485 Comms Fail, REM 1
Nov 24, 07:05, RS485 Comms Fail, 18
Nov 24, 07:05, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 07:06, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:06, RS485 Comms Restore, 81
Nov 24, 07:06, RS485 Comms Fail, REM 1
Nov 24, 07:06, RS485 Comms Fail, 18
Nov 24, 07:06, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 07:06, RS485 Comms Fail, 81
Nov 24, 07:07, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 07:07, RS485 Comms Restore, 81
Nov 24, 08:24, RS485 Comms Fail, REM 1
Nov 24, 08:24, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:25, RS485 Comms Fail, 81
Nov 24, 08:25, RS485 Comms Fail, 18
Nov 24, 08:25, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:25, RS485 Comms Restore, 81
Nov 24, 08:25, RS485 Comms Fail, REM 1
Nov 24, 08:25, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:25, RS485 Comms Fail, 81
Nov 24, 08:25, RS485 Comms Fail, 18
Nov 24, 08:26, RS485 Comms Restore, 12
Nov 24, 08:26, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:26, RS485 Comms Restore, 81
Nov 24, 08:26, RS485 Comms Fail, REM 1
Nov 24, 08:26, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:26, RS485 Comms Fail, 81
Nov 24, 08:26, RS485 Comms Fail, 18
Nov 24, 08:26, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:26, RS485 Comms Restore, 81
Nov 24, 08:26, RS485 Comms Fail, REM 1
Nov 24, 08:26, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:26, RS485 Comms Fail, 81
Nov 24, 08:26, RS485 Comms Fail, 18
Nov 24, 08:27, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:27, RS485 Comms Restore, 81
Nov 24, 08:27, RS485 Comms Fail, REM 1
Nov 24, 08:27, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:27, RS485 Comms Fail, 81
Nov 24, 08:27, RS485 Comms Fail, 18
Nov 24, 08:27, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:27, RS485 Comms Restore, 81
Nov 24, 08:28, RS485 Comms Fail, REM 1
Nov 24, 08:28, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:28, RS485 Comms Fail, 81
Nov 24, 08:28, RS485 Comms Fail, 18
Nov 24, 08:29, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:29, RS485 Comms Restore, 81
Nov 24, 08:29, RS485 Comms Fail, REM 1
Nov 24, 08:29, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:29, RS485 Comms Fail, 81
Nov 24, 08:29, RS485 Comms Fail, 18
Nov 24, 08:30, RS485 Comms Restore, 12
Nov 24, 08:30, RS485 Comms Fail, REM 1
Nov 24, 08:30, RS485 Comms Fail, 18
Nov 24, 08:30, RS485 Comms Restore, 12
Nov 24, 08:30, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:30, RS485 Comms Restore, 81
Nov 24, 08:30, Alarm, Tamper
Nov 24, 08:30, Zone Trouble, Zone 30 - RemotePanic
Nov 24, 08:30, Zone Restore, Zone 30 - RemotePanic
Nov 24, 08:30, Dial Out Index, Phone Number 3
Nov 24, 08:31, RS485 Comms Fail, REM 1
Nov 24, 08:31, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:31, RS485 Comms Fail, 81
Nov 24, 08:31, RS485 Comms Fail, 18
Nov 24, 08:31, Alarm, Alarm Abort
Nov 24, 08:31, Sign In, User 1
Nov 24, 08:31, Mode Change, Disarmed
Nov 24, 08:31, Sign In, User 1
Nov 24, 08:31, Dial Out Index, Phone Number 3
Nov 24, 08:32, RS485 Comms Restore, 12
Nov 24, 08:32, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:32, RS485 Comms Restore, 81
Nov 24, 08:32, RS485 Comms Fail, REM 1
Nov 24, 08:32, RS485 Comms Fail, 18
Nov 24, 08:32, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:32, RS485 Comms Fail, 81
Nov 24, 08:32, Sign In, User 1
Nov 24, 08:32, RS485 Comms Restore, 12
Nov 24, 08:32, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:32, RS485 Comms Fail, REM 1
Nov 24, 08:32, RS485 Comms Fail, 18
Nov 24, 08:32, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:32, Dial Out Index,
Nov 24, 08:33, Sign In, User 1
Nov 24, 08:33, Dial Out Index,
Nov 24, 08:33, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:33, RS485 Comms Restore, 81
Nov 24, 08:33, RS485 Comms Fail, REM 1
Nov 24, 08:33, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:33, RS485 Comms Fail, 81
Nov 24, 08:33, RS485 Comms Fail, 18
Nov 24, 08:34, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:34, RS485 Comms Restore, 81
Nov 24, 08:34, RS485 Comms Fail, REM 1
Nov 24, 08:34, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:34, RS485 Comms Fail, 81
Nov 24, 08:34, RS485 Comms Fail, 18
Nov 24, 08:35, Dial Out Index,
Nov 24, 08:35, Remote Sign-in, User 1
Nov 24, 08:35, Sign In, User 1
Nov 24, 08:35, RS485 Comms Restore, 12
Nov 24, 08:35, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:35, RS485 Comms Restore, 81
Nov 24, 08:36, RS485 Comms Fail, REM 1
Nov 24, 08:36, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:36, RS485 Comms Fail, 81
Nov 24, 08:36, RS485 Comms Fail, 18
Nov 24, 08:36, RS485 Comms Restore, 12
Nov 24, 08:36, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:36, RS485 Comms Restore, 81
Nov 24, 08:37, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:37, RS485 Comms Fail, 81
Nov 24, 08:37, RS485 Comms Fail, 18
Nov 24, 08:37, RS485 Comms Restore, 12
Nov 24, 08:37, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:37, RS485 Comms Restore, 81
Nov 24, 08:37, RS485 Comms Fail, REM 1
Nov 24, 08:37, RS485 Comms Restore, 12
Nov 24, 08:37, RS485 Comms Fail, REM 1
Nov 24, 08:37, RS485 Comms Fail, REM 1
Nov 24, 08:38, RS485 Comms Restore, 12
Nov 24, 08:38, RS485 Comms Fail, REM 1
Nov 24, 08:38, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:38, RS485 Comms Fail, 81
Nov 24, 08:38, RS485 Comms Fail, 18
Nov 24, 08:39, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:39, RS485 Comms Restore, 81
Nov 24, 08:39, RS485 Comms Fail, REM 1
Nov 24, 08:39, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:39, RS485 Comms Fail, 81
Nov 24, 08:39, RS485 Comms Fail, 18
Nov 24, 08:40, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:40, RS485 Comms Restore, 81
Nov 24, 08:40, RS485 Comms Fail, REM 1
Nov 24, 08:40, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:40, RS485 Comms Fail, 81
Nov 24, 08:40, RS485 Comms Fail, 18
Nov 24, 08:40, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:40, RS485 Comms Restore, 81
Nov 24, 08:41, RS485 Comms Fail, REM 1
Nov 24, 08:41, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:41, RS485 Comms Fail, 81
Nov 24, 08:41, RS485 Comms Fail, 18
Nov 24, 08:41, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:41, RS485 Comms Restore, 81
Nov 24, 08:41, RS485 Comms Fail, REM 1
Nov 24, 08:42, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:42, RS485 Comms Fail, 81
Nov 24, 08:42, RS485 Comms Fail, 18
Nov 24, 08:42, RS485 Comms Restore, 12
Nov 24, 08:42, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:42, RS485 Comms Restore, 81
Nov 24, 08:42, RS485 Comms Fail, REM 1
Nov 24, 08:42, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:42, RS485 Comms Fail, 81
Nov 24, 08:42, RS485 Comms Fail, 18
Nov 24, 08:42, RS485 Comms Restore, 12
Nov 24, 08:42, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:42, RS485 Comms Restore, 81
Nov 24, 08:43, RS485 Comms Fail, REM 1
Nov 24, 08:43, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:43, RS485 Comms Fail, 81
Nov 24, 08:43, RS485 Comms Fail, 18
Nov 24, 08:43, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:43, RS485 Comms Restore, 81
Nov 24, 08:43, RS485 Comms Fail, REM 1
Nov 24, 08:44, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:44, RS485 Comms Fail, 81
Nov 24, 08:44, RS485 Comms Fail, 18
Nov 24, 08:44, RS485 Comms Restore, 12
Nov 24, 08:44, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:44, RS485 Comms Restore, 81
Nov 24, 08:45, RS485 Comms Fail, REM 1
Nov 24, 08:45, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:45, RS485 Comms Fail, 81
Nov 24, 08:45, RS485 Comms Fail, 18
Nov 24, 08:45, RS485 Comms Restore, 12
Nov 24, 08:45, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:45, RS485 Comms Restore, 81
Nov 24, 08:46, RS485 Comms Fail, REM 1
Nov 24, 08:46, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:46, RS485 Comms Fail, 81
Nov 24, 08:46, RS485 Comms Fail, 18
Nov 24, 08:47, RS485 Comms Restore, 12
Nov 24, 08:47, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:47, RS485 Comms Restore, 81
Nov 24, 08:47, RS485 Comms Fail, REM 1
Nov 24, 08:48, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:48, RS485 Comms Fail, 81
Nov 24, 08:48, RS485 Comms Fail, 18
Nov 24, 08:48, RS485 Comms Restore, 12
Nov 24, 08:48, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:48, RS485 Comms Restore, 81
Nov 24, 08:48, RS485 Comms Fail, REM 1
Nov 24, 08:48, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:48, RS485 Comms Fail, 81
Nov 24, 08:48, RS485 Comms Fail, 18
Nov 24, 08:48, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:48, RS485 Comms Restore, 81
Nov 24, 08:49, RS485 Comms Fail, REM 1
Nov 24, 08:49, RS485 Comms Fail, Doorstation 1 - Door station 1
Nov 24, 08:49, RS485 Comms Fail, 81
Nov 24, 08:49, RS485 Comms Fail, 18
Nov 24, 08:51, RS485 Comms Restore, Doorstation 1 - Door station 1
Nov 24, 08:51, RS485 Comms Restore, 81
Nov 24, 09:18, Sign In, User 1



 Posted: Friday Nov 24th, 2006 12:17 pm
   PM  Quote  Reply 
14th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

I suspect that the Slave is causing an intermittent communication failure which is affecting the communications
is it possible to temporarily disable the slave, ie remove it and change the Number of slaves to 0
Ask if komfort has a spare slave they can send you to replace this one and see if the problem goes away

Unless you are able to try the solution proposed by Adrian

Last edited on Friday Nov 24th, 2006 12:21 pm by slychiu



 Posted: Monday Dec 11th, 2006 08:53 am
   PM  Quote  Reply 
15th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

Hi,

Just a bit of an update:

Over that last few weeks I have been disconnecting modules and testing to see if I could isolate the problem better.  It takes a bit of time because the problem is random and doesn't occur immediately after a change has been made. 

Nothing seemed to make much difference.  I had status LEDs which I also disconnected (and unprogrammed) - this made the problem go away for about five days - but it still came back.

I soldered a resistor onto the board as per your instructions this weekend - so far so good - I will just have to wait to see if the problem is gone permanently.

Many thanks,

Clinton.



 Posted: Tuesday Dec 12th, 2006 08:14 am
   PM  Quote  Reply 
16th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

Hi,

This morning the alarm went off.  The system was armed in night mode and a communication failure occurred again.  Hence, it appears that the resistor has not solved the problem.

Any ideas?

Regards,

Clinton.



 Posted: Tuesday Dec 12th, 2006 12:19 pm
   PM  Quote  Reply 
17th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

Can you get a replace SEM from Komfort. I suspect that the Slave has an intermittent problem
\



 Posted: Wednesday Dec 13th, 2006 09:51 am
   PM  Quote  Reply 
18th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

Hi,

I believe Komfort are not operating any more.  How should I go about getting the board replaced?

Thanks,

Clinton.



 Posted: Thursday Dec 14th, 2006 09:43 am
   PM  Quote  Reply 
19th Post
cgiltrow
Member
 

Joined: Monday Jun 12th, 2006
Location: Johannesburg, South Africa
Posts: 107
Status: 
Offline

  back to top

Hi,

I have managed to get hold of Komfort.  I believe they are getting some new slave boards soon.  Apparently they are G2 slaves though.  Would these slaves work with my G1 main board, and will my G1 LEM01 work with a G2 slave?

Regards,

Clinton.



 Posted: Thursday Dec 14th, 2006 10:32 am
   PM  Quote  Reply 
20th Post
adlim
Member


Joined: Wednesday May 3rd, 2006
Location: Singapore
Posts: 210
Status: 
Offline

  back to top

Your SEM-M2 would work with Comfort II. However, due to differences in voltage, it is not recommended that you use a LEM from Comfort I with a SEM-M2.



 Current time is 08:01 am
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems