Show status for counters and sensors, zones, outputs are updated when there is any change to the item monitored. You do not need to refresh because changes are automatically reflected
It is different with flags because Flags changes are not known by the UCM until it queries them, which is why Comfigurator chevcks every few seconds. It is due to the lack of a flag update message in the UCM
X10 status does not have a Show status box because there is no command for the UCm to interrogate this in Comfort. It is also less useful becase most X10 devices do not provide status. Often they are operated by a local button on the x10 module
The UCM 5.178 firmware which fixed the s? bug is available for download from the Upgrades page
https://www.cytech.biz/upgrades.html
Remember that you need another UCM to do the upgrade
I\'m a little confused by the release note for UCM 5.178 firmware.
Most of it seems to refer to the same description as point (1) on firmware 5.174. No explicit mention of S? fix.
Only difference seems to be the \"Hex 0800\" fix for Zwave?
Obviously you say the S? fix is in there but what other fixes?
Sorry, silly mistake in the entry which is corrected now to show the s? fix
Hi,
Upgraded to 5.178 and the SCS sensors now report correctly. Here\'s an example (provided for others as I didn\'t know what response to expect when I first tried) for SCS1 (sensor 8):
> s?08
< s?082A
I first upgraded the UCM into which the SCS was plugged but this didn\'t make any difference; didnt report back. Next upgraded my UCM05/Eth to 5.178 too and it then did work. Did both UCMs NEED to be upgraded and if not what\'s the logic? I had assumed the ONLY the one connected to the SCS, but is it the UCM/Eth one only, or BOTH? Confused!
Anyway it works.
J
The SCS is never connected to any specific UCM even though you physically connect the wires to it
The SCS and UCMs share the KA/KB connections which is an RS485 bus. They are all connected to Comfort itself which is the controller.
The commands from your PC are issued to the UCM which it is connected to, if a serial UCM05, to the RS232 port, if a Ethernet UCM, to the network with the correct IP address and port. It is that UCM which is receiving the s? command and replying with the s?
I\'ve noticed an interesting feature with 2.9.12.
When reading the event log it prompts you for a user code. If you use the Engineer code here then every time you read the event log it adds a \"....Sign-in - User # Engineer\" entry to the event log. Clear the event log and press the \"Read Event log\" button to see this in action.
Now this might be correct functionality but you dont get the same outcome if you log in with a User code; here no entry logged in this case.
So inconsistent?
J
Signing in as Engineer is always logged in the Event Log, regardless of where it is done. It is a more exceptional event than a user login which is not captured
The \"Modules\" tab in 2.9.12 is confusing me on a couple of fronts and i couldn\'t find any info in the online help.
(1) For the \"UCM\'s\" node I\'ve setup my 3 UCM\'s and named them etc. This is I assume direct replacement of UCM section under Names in 2.2.3 and works OK. BUT if I do a SCAN I get the following error attached and the cursor shows busy until I exit.
(2) What is the \"Keypads\" node for as can see no way to enter data in here. I have 2 keypads defined in \"Modules & Settings\" but nothing shows up. There\'s no right-click SCAN or ADD buttons so what\'s this tree node for?
[Update: actually I\'ll revise (2), if you right-click the UCM section first to get the pop-up menu, then close it and do the same for the KEYPADS section a thin 2-3mm line apperas which i\'d assume should be the pop-up menu? If you right-click KEYPADS without clicking the UCM node first then this \"line\" does not appear!]
J
The Scan function will require a later firmware version which is to be released soon. This will support the new types of UCms for external interfaces that will be released in future eg UCM/Zwave which is being redesigned, using configuration software which is part of Comfigurator.
The keypads in the modules tab is also for the future to support new kinds of keypads
Any later betas of Configurator after 2.9.12 that we can play with yet?