Building Automation Knowledge Base

Issue Door goes to Secure mode even when there is no ATS on it. Environment All versions of I/net Software. Cause The software puts the door in the secure mode by default. Resolution The access control functions within TAC I/NET Seven depend partly on schedules to determine when access will be granted to individuals or groups. The following door related schedules are used for access control: 1. Mode Schedules — You can assign a mode schedule to each door in order to control what mode the door will operate in during specific times of the day. When a door is in the Locked mode, access will not be permitted regardless of any other schedules. 2. Personnel Schedules — You can define up to 31 personnel schedules for each door. Personnel schedules are only used to control access when a door is operating in the Secure or PIN Enable mode. Mode Schedule A door Mode Schedule controls the operating mode of the door at specific times of the day. The following door Mode Schedule actions are available:  APB Reset — Use this action to reset anti-passback memory for this door.  Lock — This mode inhibits entry and exit through the door. All readers and release buttons for the door are disabled while this door mode is in affect.  Unlock — This mode allows open access through the door.  Secure — This mode allows access only after a valid key/card has been read. All key/cards will be validated based on personnel schedules, tenant, key/card issue number, anti-passback, and access level.  When a door equipped with a PIN pad is operating in the "Secure" mode, the PIN pad will not be enabled (that is, entry of a personal identification number will not be required in order for an individual to gain access).  PIN Enable (firmware version 3.20 or earlier)  OR Sec/PIN (firmware version 3.21 or later) — When this mode is active, the PIN reader on the DPU will be enabled. This mode is the same as the "Secure" mode except that it also requires the individual to enter a valid PIN after a valid key/card read. If an individual enters an invalid PIN, the setting of the PIN Retry Count parameter in the Door Extension Editor will determine how many retries (if any) the individual can use to enter a valid PIN.  You can schedule a door's PIN pad to become disabled without unlocking the door by following this mode with a "Secure" mode. When the "Secure" mode becomes active, individuals will no longer be required to enter a PIN in order to gain access through the door.  Sec/Code (firmware version 3.22 or later) — This mode is similar to the "Secure" mode; however, rather than using a key/card to gain access, the user simply uses the PIN pad to enter the door's assigned code. If the individual enters the correct door code, the door will open.  When the door is operating in the Sec/Code mode, user-definable door attributes or PIN pad functions are not available. Note: If the door needs to be unlocked then they can manually be unlocked for that period then return to the secure mode when needed.

Issue At times there is a need to display Pinpoint graphics on multiple displays from one Cyberstation Environment Continuum Windows XP Windows Vista Windows 7 Windows 2003 Windows 2008 Cause There is a need to display multiple graphics, but opening multiple graphic panels opens them in the same Pinpoint window Resolution Open up one pinpoint graphic normally through Cyberstation Start>Programs>Continuum>Pinpoint  then File>Open and select the graphic (launches another session of pinpoint.exe) Drag and drop the second pinpoint session to your second display Repeat Caution: Pinpoint.exe can be resource intensive, so opening multiple sessions will increase the number of resources consumed at least by the number of sessions that are open. This method does not get tested in QA.

Issue The reports installation completes without error but Reporting Agent service never gets installed. Without the Reporting Agent service, reports will not collect data and the WebReports login page will not load in a browser. Environment StruxureWare Building Operation WebReports, version 1.1 Cause Error in installation files Resolution The workaround for this issue is as follows: Ensure that in Windows, the Folder Options are configured to show hidden files, file extensions, and protected operating system files. Open Windows Explorer, navigate to the C:\Program Files\Schneider Electric\StruxureWareReports\StruxureWare Reporting Agent directory, and edit StruxureWareReportingAgentInstall.bat. Remove the "%1\" from the first two lines so that it simply reads: installutil.exe SE.WebReports.StruxureWareReportingAgent.exe regedit /s StruxureWareReportingAgent.reg pause   Save the file and exit. Edit the config file, SE.WebReports.StruxureWareReportingAgent.exe.config. Find the section with the following line: Note: They will appear without the "." after the "<" <.add key="uid" value="appuser"> Copy & paste the above line just below it , then edit the copied line so that it reads: <.add key="ServiceName" value="StruxureWare Reporting Agent"> When finished, the two lines should read: <.add key="uid" value="appuser"> <.add key="ServiceName" value="StruxureWare Reporting Agent">   Save the config file and exit. Run the batch file StruxureWareReportingAgentInstall.bat.

Issue Customer has an older ENC-520-2 and has run out of memory for his station programming.  His ENC has only 128mb of memory, not the 256mb of memory in the current ENC-520-2 controllers. Environment ENC-520-2 or ENC-520-2-N manufactured in Rockford (SN xxxxxB) prior to BootFlash upgrade. Cause Manufacturing change. Resolution The base memory (128mb) version of the ENC-520-2 cannot be field upgraded to extended memory (256mb) due to other component changes on the controller circuit board.

Issue How to use the Piecewise command in Sigma Graphics when displaying a multiple value status from a programmable object. Environment Sigma Graphics Ver 4.0 onwards Cause When using a prog point that returns multiple states for certain conditions if this is required to be displayed on a graphic then problems can arise with updates when the state changes and the graphic is open. Unless the prog object actually changes value from 0 to 100 the graphic will not update. Resolution There is an engineering workaround to this problem. Example of prog object. 10 IF POINT 0|123 = 1.00000 THEN RETURN TRUE "Off" 20 IF POINT 0|123 = 2.00000 THEN RETURN TRUE "Text No1" 30 IF POINT 0|123 = 3.00000 THEN RETURN TRUE "Text No2" 40 IF POINT 0|123 < 1.0 OR POINT 0|143 > 3.0 THEN RETURN "Invalid" In the graphic create 3 text objects. 1 - Off 2 - Text No1 3 - Text No2 Next position them one above the other in the order shown with 1 at the bottom, and align them over the top of each other creating a stack of the texts. Next select them all and combine them. Select the combined object and assign a piecewise command to it. Assign object 123 and select min = 1 max = 3. The graphic will then display the text according to the object value. If the value is 0 or > 3 then the text will be blank. There are many variations on this but in general all you need is an analogue value from the prog object then the piecewise command can be used.

Issue Changing the LON device's subnet and node address. Environment I/A Series G3 LonWorks Integration Cause When a LON device is added to the station database, its subnet and node addresses are automatically assigned. For the correct communication to be established there may be a need to change the subnet / node address of the LON device. Resolution To change the device subnet / node address: Right click on the LonNetwork and go to the Lon Device Manager. Select the LON device for which subnet / node address needs to be changed Edit the device by double clicking on the LON device or using the 'Edit' button at the bottom of the Lon Device Manager view. Enter the correct subnet address and a unique node address for the device. Commission the LON device regardless of whether it has been commissioned before. 

Issue Which power supply options are specified on the MD10SR-TS actuator? Environment MD10SR-TS Cause The data sheet may be a bit unclear at some points regarding the requirements on which power supply that can be used on this Universal actuator. Resolution AC 50/60Hz: 19,2-264 V DC: 21,6 -137,5 V

Issue Pin Code or general code not working from access control keypad Environment Continuum access control Keywords: Pin Code, general code, #, 8 bit burst Cause Pin Code or general code not working from access control keypad. Resolution The 4 numbers in the PIN code or General Code need to be followed by the # key When personnel are created with no PIN number they are allocated "0" but this does not work at a PIN code. The PIN number must be changed from non "0" before it will work. The PIN number does not need to be 4 digits long (ACX57 only fully tested) The keypad/ reader used must provide an 8 bit burst wiegand output.

Issue Linux source code is public source Environment StruxureWare Building Operation AS Cause Provide source code for AS Linux operating system. Resolution Software License Notices This product contains code that is covered by the GNU General Public License (GPL). In accordance with the GPL, you may request the relevant code for up to three years from the date of original purchase of this product. The code will be supplied on CD free of charge, though there will be a small fee to cover the cost of the CD, plus shipping and handling. For further information on the GNU GPL licenses, please visit http://www.gnu.org/licenses and, for the complete GPL texts, http://www.gnu.org/licenses/gpl-2.0.txt and http://www.gnu.org/licenses/gpl-3.0.html To request a CD copy, please e-mail us at info@buildings.schneider-electric.com

Issue The Veris H8920-3 will not update its Lon SNVTs unless a fetch is performed. The H8920-3 shadow object in the Niagara R2 UNC-410 will not update automatically. Environment Niagara R2, UNC-410, UNC-510, UNC-520 Veris H8920-1, H8920-3, H8920-4, H8920-5   Cause The Veris H8920-3 Auto Propagate Feature is not configured to automatically update all network variables. The Auto Propagate Feature of the H8920-3 must be set accordingly for its network variables to be automatically updated to the UNC. Resolution The following steps configure the H8920-3 Integrator to automatically update it variables to the UNC. Open the UNC-xxx station in WorkPlace Pro. Expand the folder containing the H8920-3 shadow object Right-click and open the H8920-3 properties Click on the OpenLoopSensor tab and then Config tab Set the nciMaxSendTg to and value above its default of “0”. (suggested value is 100) The Veris H8920-3 Integrator will now periodically update its network variables to the UNC. NOTE: The following is an excerpt from the Veris H8920-x Installation Guide: The H8920-x automatically propagates all network variables. If nciMaxSendTg is set above zero (default is zero), all variables are propagated periodically. Units are in tenths of a second. For example, if nciMaxSendTg is set to 100, the H8920-1 will automatically propagate all variables every 10 seconds.

Issue Launching Continuum results in error "This workstation is currently unable to connect to the database. Click OK to exit." Also, running Continuum DB initialization results in error: SQL Server [server name] does not exist or access denied. Workstation Setup Failed! Please try again or click Cancel to exit. Environment CyberStation LAN system Cause Fire wall on the server machine is blocking TCP port 1433 Another cause for this happening is a Windows firewall or McAfee firewall being enabled and blocking the IP of the 2nd Cyberstation that is trying to connect. Resolution Disable fire wall at the server or add an exception for TCP port 1433 (or the port used by the client to get access to the server if different).

Issue The MNB-Vx (MNB-V1, MNB-V2) controllers are shown as replaced by the MNB-Vx-2 (MNB-V1-2, MNB-V2-2) on iPortal.  What is the difference? Environment MNB-V1 (-2) MNB-V2 (-2) Cause Production change Resolution There are no functional differences between the MNB-V2 and the MNB-V2-2 controllers. The part number was changed to allow tracking of an internal manufacturing change in the actuator part of the assembly.

Issue A hard drive failure on the LAN SQL server or on a Stand Alone workstation is preventing Cyberstation from starting. Environment LAN Server and StandAlone workstations Cause A hard drive failure on the LAN SQL server or on a Stand Alone workstation is preventing Cyberstation from starting. The site does not have a verified SQL backup of the database. The raw data files, typically named ContinuumDev.mdf and ContinuumLog.ldf, can be recovered. Resolution For a standalone, use the Microsoft SQL Server 2005 Management Studio Express. The freeware SQL front end is much easier to use than the command line. The Microsoft SQL Server 2005 Management Studio Express will also allow you to administer SQL 2000 MSDE databases. The Management Studio Express can be downloaded for free from Microsoft using the link below. http://www.microsoft.com/downloads/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796&DisplayLang=en  This procedure assumes that the Continuum database no longer exists on the SQL Server. It is also critical that SQL is up and running.  If the SQL Server or StandAlone workstation hard drive has crashed, SQL must be reinstalled on a functioning workstation before attempting to attach the raw data files. See the link below for the steps to attach the db using the SQL Management Studio Express http://msdn.microsoft.com/en-us/library/ms190209.aspx  This links to an article that describes how to attach the data files and of the log files for a database running Microsoft SQL Server 2005, SQL Server 2000, or SQL Server 7.0 database. http://support.microsoft.com/kb/224071

Issue Regarding the purchase of NL220 credits for devices that have previously been commissioned in LonMaker: Do the devices need to be recommissioned in NL220 once the conversion is complete? Environment NL220 LonMaker Vista Cause Conversion of LonMaker database to NL220 Resolution It is NOT necessary to purchase NL220 credits for the purpose of converting from an existing Lonmaker database to NL220 if the devices are already commissioned in LonMaker.  All of the nodes will show up in NL220 as commissioned as long as the devices are still commissioned in LonMaker when you begin the conversion.   *Note: When an original LonMaker Credit is replaced with an NL Credit, the LM credit will be lost.

Issue Changing the default port numbers for the Fox, Platform Daemon and HTTP ports in I/A Series G3 Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server / Enterprise Network Controller Cause There is a need to change the default port numbers of the Fox, Platform and HTTP ports used in I/A Series G3. Below are the descriptions of the ports usage and their default port numbers: TCP port 1911 (Fox port) Default port for a station's Fox Service used for Workbench to station and station to station communications TCP port 80 (HTTP port) Default port for a station's Web Service used in browser access (Hx, Wb) TCP port 80, 3011 (HTTP and Platform Daemon ports) Default ports for Workbench Platform connection Resolution The default ports for the Fox and HTTP ports can be changed during the process of creating a new station. Follow the following procedures if the ports need to be changed after the station has been created. To change the Fox port: In Workbench, open the station. Expand 'Config' > 'Drivers'. Open the Property Sheet of the NiagaraNetwork. Expand the 'Fox Service' and you can change the port number from the default of 1911. To change the HTTP: In Workbench, open the station. Expand 'Config' > 'Services'. Open the Property Sheet of the WebService and you can change the Http Port number from the default of 80. To change the Platform Daemon port: In Workbench, open the host's Platform. In the Platform view, go to the Platform Administration. In the Platform Administration view, click on the 'Change HTTP Port' button to change the default port.

Issue Where to find information on how to set up SSL for webstation Environment TAC Vista Webstation Cause Can not find the documentation on how to set up SSL in Webstation Resolution This is documented in chapter 4.3 of the TAC Vista Software Installation Manual.

Issue Roam IA communications error when disconnecting from one standalone controller and plugging into another Environment I/A Series Workplace Tech WorkPlace Commissioning tool Cause The Roam IA is designed to join a trunk and then access various devices.  As such the Roam IA must be connected to a communicating trunk or device before it's turned on so it can be detected when switched on and it can sync to the established baud rate, see the TAC I/A Series RoamIA Quick Start Guide for details.  Resolution When working with standalone controllers turn off the Roam IA after completing work with one controller, connect to the next standalone controller and turn on the RoamIA.  It will establish communications with the new unit and allow communications.

Issue WebPinpoint is not successfully installing on client machine during initial graphic launch. Environment WebClient WebPinpoint Cause Client PC has been locked down by customers IT department. Resolution Ask the customers IT department to open up security on the client machine until the WebPinpoint installation is completed.  Once WebPinpoint has installed the security setting on the client machine can be restored. On Windows 7 machines, set User Account Settings to minimum until WebPinpoint has completed its initial installation. 

Issue Alarms are not clearing from the Active Alarm View when they Return To Normal and are Acknowledged. Environment Continuum Cyberstation Cause The "To Normal" Transition is not being sent to the recipient Workstation. Resolution Confirm that the "To Normal" transition events are configured to be sent to the recipient Workstation. In your EventNotification objects: Go to the Recipients tab. For each recipient Workstation, check the "To Normal" transition entry.

Issue If user exits I/NET (Using System > Exit) and then re-starts I/NET again with logging off, the previously logged on user is automatically logged back in. When starting I/NET, user is not required to enter a password.   Environment I/NET Seven Cause The I/O Server with no clients has three settings which can be configured for its active profile as defined below: Maintain – Enable this option to allow the I/NET I/O Server to continue running in the background, even when no I/NET client is currently active. In this case, you will remain logged into the I/NET system. Logoff – Enable this option to be automatically logged off of I/NET when you shutdown the host software application. The I/NET I/O Server will continue running in the background, even when no I/NET client is currently active. Shutdown – Enable this option to shutdown the I/O Server after all I/NET clients have been shutdown. Resolution Change the active profile I/O Server setting to either logoff or shutdown.  Both Logoff and Shutdown will deactivate the last user logged into I/NET so if this is the functionality required, then either of these two settings should be used.