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

Scanning for Modules
 Moderated by: slychiu
 New Topic   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Friday May 31st, 2013 12:57 pm
   
1st Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3493
Status: 
Offline

  back to top

The modules connected to the Comfort RS485 Bus, ie different types of UCMs, Keypads, Door stations, Slaves, SCS and RIOs can be detected by Scanning.
The IDs of each module Type  must be set to unique IDs before doing the scan
eg
If there are 3 keypads, their IDs must be 1,2,3
If there are 4 UCMs, their IDs must be 1,2,3,4

It is necessary to Scan for the modules and do a Write to Comfort in order for Comfort to be able to Poll the modules

Setting IDs alone will NOT work

Click on the Modules Tab below the menu bar as shown below;


A default template will assume 1 Keypad at ID=1 and 1 UCM at ID=1 as shown above. The Keypad and UCM will be in Gray until a sccan is done

If an existing  file has been opened and before a module scan has been done, the modules which were present are shown in Gray, meaning that scanning has not been done yet. These modules may have been detected on a previous session, however modules may have been removed or added since the last time the file was saved, so it is necessary to do a scan when you connect again.




Scanning for Modules is done by Right-clicking on Modules and selecting Scan for all  Modules (or scanning for a module type only, eg UCMs). This will discover all the modules that are connected to Comfort, which have their IDs set correctly without having duplicate IDs with other modules of the same type



A window will pop up asking for the Security user code for Comfort


Enter the code (default 1234) and press OK

Comfigurator will take a minute to scan, or discover all the modules on the Comfort Bus. When scanning is completed, the Modules Tab shows the type of module (eg UCM, Keypad, Slave, SCS, Door sttaion) and firmware version (eg 7.010), and uses different colours to represent the modules status.

The colours used are:

GREY: Indicates that the module has not been found by Scanning yet, eg when the file has just been opened
BLACK: Indicates that the module has been discovered by scanning
RED: Means that the module is not found on the bus
BLUE: After scanning, a new module has been discovered which is not polled by Comfort because its ID is higher than the Maximum of of this type in Comfort. The module will be polled by Comfort after a write to Comfort.

GREEN: Modules that have their ID changed but before the modules are reset  to activate the ID change. This applies to modules with firmware version 7 and above


Note that Modules discovered by the scanning may not be polled by Comfort. In order for Comfort to recognise and poll for the new module, select "Write Modules and Settings to Comfort" as shown above (by right click)

After the scan, the modules which are found on the bus will be in black


The Module Type and Subtype are shown, eg UCMs may be General, Cbus, KNX, Universal, Zwave etc. Keypads may be KP03, KP04/KP05, KP06, KT03. SCS/RIO may be SCS or RIO
The Firmware Version eg 7.002 and the Latest firmware available are shown for each module. See a later post on upgrading firmware

If a module in the configuration is NOT found by the scan, it will be shown in RED

The Status column in the middle pane also shows information like Scanned (or Polled), Not Found, or Not Polled.
  • Scanned (or Polled) means the module is polled by Comfort. This is the normal condition which means the module is communicating with Comfort
  • Not Found (in red) means the module which was in the cclx file is not on the bus. This could be because the module has been removed.
  • Not Polled (in blue) means a module has been found, but it is currently not polled by Comfort because its ID is higher than the number of modules of this type
Note that if a module has been removed from the network perhaps temporarily, and thus was not found during the scan, it is not deleted but is shown in red with status Not Found. If the module was a KT03 or UCM/KNX where many hours of  programming work has been put in, the absence of the module during scanning will not cause the module with all its properties to disappear. It remains in the file and is not lost.

If you really want to delete the  module, then right click on it and select Delete Module.  However it is not possible to delete a module that is referenced by Responses or other elements.

Modules may have their IDs changed manually due to rearrangement or reconfiguration
If a Scan for modules finds that a module say UCM/KNX, has changed IDs say from ID 2 to ID 5 since the last saved configuration, Comfigurator will assign the module properties to the new ID. Hence the  KNX configuration that has been programmed will not be lost.

If there is an additional module of the same type compared to original configuration, the new module will have a blank configuration eg UCM/Zwave or UCM/Universal.

After scannng for modules, the firmware of the module can be upgraded as shown in the next topic http://www.comfortforums.com/forum92/3400.html

This is a good time to write the configuration to Comfort as shown in http://www.comfortforums.com/forum92/3409.html



 Current time is 10:55 am
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems