Building Automation Knowledge Base

Issue Generating a Xbuilder project results in the error message "The size of the generated project is xxxx KB, which exceeds the maximum size 8192 KB". Environment Xbuilder 5.x.x Cause The generated project size exceeds the maximum limit due to the following reasons: The project contents made up of graphic pages, inserted networks (LON, I/NET, etc), large images (BMP, GIF, etc), or imported files in the UserTargetImage directory cause the project to exceed the limit. The option "Send Project backup file to target device" is checked and this causes pushes the project size over the limit. Resolution Generate the Xbuilder project to see how far above the limit the project currently is. Open the Project\Settings and uncheck the "Send Project backup file to target device" and regenerate the project to see the difference in file size. If the size difference is significant then check for large files in the project directory that should not be sent to the device such as project or device documentation files such as PDFs. Remove these files from the Xbuilder project directory and generate the project again.  Search the Xbuilder project directory for the largest size files such as graphic pages and try to find way to reduce the size by converting background image formats that will result in smaller file sizes. Example convert BMP file to PNG or JPG format.

Issue Xenta 913 will not communicate with the Bacnet device. Wireshark does not show any packets between 913 and Bacnet device Environment Xenta 913 Cause The Xenta 913 has been installed on a TCP/IP network with a switch between the Xenta 913 and Bacnet device. Resolution A basic switch does not pass broadcast messages that a Xenta 913 uses to talk to Bacnet device. The solution to this issue is to replace the switch with a Hub or use a managed switch. If a managed switch is used it will need to be configured to pass broadcast messages from the Xenta 913 to the Bacnet device.

Issue The Values column in the Vista Workstation Object View shows a blank field against a SNVT Switch (or any other structured SNVT) Environment TAC Vista Workstation Cause The TAC Vista Workstation Object View displays a single row for each public variable in a selected folder or device and a single Values column.  For a structured SNVT such as a Switch this means that there is no space to display all the SNVT member values.  Vista solves this problem by not displaying any of the SNVT members. Resolution Open a Status Watch pane in Workstation. Drag the structured SNVT from the Object View on to the Status Watch. In the Property column, select the Property you want to view (in the case of a SNVT Switch either 'Value' or 'State'). N.B.  Vista will not allow you to enter the same SNVT twice in the Status Watch, so you cannot view both members simultaneously.   Alternatively,  display the SNVT on a graphic.  The binding selection dialog allows you to choose which Property of the SNVT to display.  There is no problem with displaying as many properties of the same SNVT as you wish on a graphic.

Issue Password, Passcode for a UNC532 or a UNC632 Keyboard. Environment Sigma, BAS, UNC532 Keyboard, UNC632 Keyboard. Cause What is the password passcode for a UNC532 Keyboard or a UNC632 Keyboard. Resolution The default passcodes are: 2001 1066 1482 0338 8420 Keypads that were used in BAS are now replaced by PDA's. Keyboards can only interrogate the controller they are fitted to and are can only be fitted to UNC532 or UNC632 controllers.      

Issue Can not get xPBA4 / xPBD4 to operate on a b3 controller Environment xPBA4 xPBD4 b3 / i2 controllers xP Modules Cause When connecting a xPB module to an i2 or b3 module the CPU light does not flash Resolution The xPB modules are only supported on the master level controllers. They can be plugged into a ACX57xx,  a bCX1-CR 9640 or 4040 But not the bCX1 4000 router only or any of the field controllers.   The i2 and b3 controllers with expansion ports will only support the Input only or Output only modules. Maximum of  2 xP modules on any controller (plus an xP Display if required).

Issue Changing an object attribute value (i.e. InfinityOutput state) results in error: An error was detected while attempting to set an attribute in a remote Infinity object: Infinity error duplicate item name. Environment All CXs All i2s All B3s Cause An object with the same name as the one being edited exists in the database. Resolution Rename the object in question. From the Continuum Explorer, right click the item Click on 'Rename'. Modify the name and alias to make it unique. For example, change CondensatePump1 to CondensatePump_1 References to the name (PE programs) will automatically pick up the new name as they refer to the object by handle id. Another possible solution is to reload the controller to sync up the controller's DB with the SQL DB.

Issue A particular turnstile requires a one second pulse, thus the door is configured with a one second strike time, turnstile works fine but getting intermittent forced entry alarms when person takes more than a second to go thru. Environment CyberStation ACX5740 ACX5720 CX9680 CX9900 AC1 AC1Plus Cause Continuum generates forced entry if door switch opens after the door strike time has expired. Resolution In the door editor, go to the 'Channels' tab and enter a value for ForcedEntryDelay. For example: Entering a value of 3 suppresses door forced enter for 3 seconds following valid access (or Request to exit) at the door.

Issue How to modify, save, and install Microsmart UDPs in UltiVist Environment UltiVist (any version) Cause n/a Resolution Procedure: Highlight the Microsmart controller. Click on the Functions drop-down menu and select UDP Status. Double-click the UDP number of choice.  Click overtop the UDP descriptor or UDP status portion of the line. Select PROGRAM from the pop-up window. A Watson Works Editor (EPM) appears with a blank screen. Press Enter and begin adding the program code. When complete click the Save button in the toolbar and exit the window.  Alternatively, click on the File drop-down menu and select Save and quit.  NOTE:  Do not do a "Save As" and do not change the name of the file.  The filename at the top will appear as D:\FI\E4000000 or similar.  Do not modify it. Back on the UDP Status screen, double-click the just-programmed UDP.  Select INSTALL from the pop-up window. When the INSTALL completes, double-click it again to ENABLE it.

Issue The need to know what voltages will a Sigma controller operates under. Environment Sigma Power Voltage Input Cause The need to know what voltages will a Sigma controller operates under. Resolution For Sigma controller the specification for the power supply is shown as: Supply voltage. . . . . . . . . . . . . . . . . . . . .230Vac ±10%. Supply frequency. . . . . . . . . . . . . . . . . . .50/60Hz ±10% Power consumption. . . . . . . . . . . . . . . . .25VA maximum

Issue Sigma running on a system using layer three switches? Environment Sigma Layer 3 Switches Routing Cause Site is changing all its layer 2 switches to layer three. Resolution Sigma products support IPv4 Layer 3.  Message routing is done using the routing protocol RIP version 1 only. Sigma devices communicate using 32-bit IP address with various subnet masks.  

Issue I/A Series G3 SMS Driver Part Number Environment I/A Series G3 Cause The SMS (Simple Message Service) driver is used for sending text messages to mobile / cellular phones. The SMS driver allows retransmitting alarm information and sending general text messages. The I/A Series G3 SMS driver is not listed in the datasheets for the Enterprise Network Server or Enterprise Network Controllers. Resolution ENC-DRV-SMS License an ENC-520, JACE 6 or JACE 7 to enable SMS alarms to be sent to any mobile phone via a GSM/GPRS modem connected to the RS-232 serial port * The SMS  Driver is no longer available in the Enterprise Network Server and Soft JACE. There is a technical issue and the driver has been removed from use on Windows based platforms.  If the driver is required for use in the ENC or Soft JACE, contact Schneider Electric Product Management via your local Schneider Electric sales office.  ENC-DRV-SMS License an ENC-520, JACE 6 or JACE 7 to enable SMS alarms to be sent to any mobile phone via a GSM/GPRS modem connected to the RS-232 serial port

Issue Get alarm the "Filename too long for backup" in TAC Vista Workstation. What is wrong? Environment TAC Vista 4.2.5 Cause The too long filename is from one of the debug logs in the $log folder in Vistas database. Resolution Make sure no debug log is started, open the Vista server, Log-Comm. Log, nothing should be active or marked. Delete or copy to another folder the logs in the $log folder.

Issue Fail to install Java 1.5 or greater on the OP1500 Error "low on virtual memory" and "error code 1722" during install Environment OP1500 Cause The OP1500 comes in two versions, with 0.5 GB and 1 GB memory. Java v1.5 or greater requires the 1 GB version. To determine which version you have refer to the Schneider Electric label on the side of the OP1500: SE part number of the 0.5 GB version: MPC ST52 NDJ00T SE part number of the 1 GB version: MPC ST52 NDJ10T If you do have the 1 GB version, it may be an install shield error (described here ) Resolution If you have the older OP 1500 with 0.5 GB I it may still be possible to order a 1 GB memory card upgraded with Java version 1.5 from Schneider Electric Sales/Order. If you have the 1 GB version, you can try download the offline installation package, available here.

Issue Customer desires to use newer release of the G3 software on his existing ENCs and  ENS. Environment I/A Series G3 ENC I/A Series G3 ENS I/A Series G3 NXT I/A Series G3 Soft JACE Cause New upgrade has been released and customer desires to use that version. Resolution To request an upgrade for an existing customer's ENC, complete the ENC-520 series or ENC-410 series I/A Series G3 Hardware License Request Form, checking the box for "Field Upgrade" and the box for the "Software Upgrade for ENC" (IA-LIC-G3-UPG1).  Make sure that the current license information shown on the form matches the existing license and include the device serial number in the appropriate field on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG1 to IASeries.License@schneider-electric.com. To request an upgrade for an existing customer's ENS, complete the Enterprise Network Server / Workbench I/A Series G3 Software License Request Form, checking the box for "Field Upgrade" and the box for the "Upgrade to latest Software Revision" (IA-LIC-G3-UPG2).  Make sure that the current license information shown on the form matches the existing license and include the device serial number in the appropriate field on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG2 to IASeries.License@schneider-electric.com. To request an upgrade for an existing customer's Soft-JACE, complete the Enterprise Network Controller (Soft JACE) Software only License Request Form, checking the box for "Field Upgrade" and the box for the "Software Upgrade for ENC" (IA-LIC-G3-UPG1).  Make sure that the current license information shown on the form matches the existing license and include the Software ENC HostID in the appropriate field on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG1 to IASeries.License@schneider-electric.com. To request an upgrade for an existing customer's JACE-NXT, complete the Soft-JACE I/A Series G3 Hardware License Request Form, checking the box for "Field Upgrade" and the box for the "Software Upgrade for JACE" (IA-LIC-G3-UPG1).  Make sure that the current license information shown on the form matches the existing license and include the ENC Serial Number (NXT Serial Number) and ENC HostID in the appropriate fields on the form. Submit the license request form along with your purchase order for the part number IA-LIC-G3-UPG1 to IASeries.License@schneider-electric.com.

Issue To read "Long" or 32-bit values with an IC3-Modbus. Environment Sigma IC3 - Modbus Modbus Long Data 32-bit Cause Both "Long" and 32-bit data values can be stored in two separate 16 bit registers and this data must be added together to give the correct reading. Resolution To read "Long" or 32-bit data, which is stored in two registers, it is necessary to carry out the following; Configure the Gateway.txt file entry - Object No,controller No,Function code,Reg address,Poll Time,No of registers to call,Min,Max,Hardware. An example could be 50,1,3,4000,1,2,0,0,1 In the controller Sigma AI objects would be created, in the case above, these would be 50 and 51. A programmable object is required to present the final reading, please see the example below. 10 XFlo = POINT 0|50 20 YFlo = ( POINT 0|51 * 65536.0 ) 30 ZFlo = ( XFlo + YFlo ) / 100.000 40 RETURN VIA TEXT 92 VALUE ZFlo The above programme assumes that the value has been multiplied by 100 at the source device. The object numbers match the example given and the correct short text number is required.

Issue A Niagara R2 installation is being upgraded to the current revision.  What's the part number for ordering an upgraded license file? Environment Niagara R2 Cause Installation is being upgraded from 2.301.431 to the current revision Resolution IA-LIC-23G Upgrades the license file to the current revision IA-LIC-CHG Modifies other parameters in the license file like the projectId, orgId, hostId, etc.... Both part numbers apply to an Enterprise Server license and to an UNC license. The list price for both of these part numbers is available on iPortal.

Issue What is the procedure on transferring Continuum from one PC to another PC?   Environment Cyberstation SQL Cause Workstation hardware must be replaced. Resolution Collect information from the existing machine Backup the Continuum Database Collect all IP address, DNS server and WINS server IP information from the existing workstation. Determine if the workstation was a member of a network domain and record the domain name.  Run Continuum Database Initialization on the existing machine. Select Workstation. Record the following information. Workstation Name Folder Name Device Node ID Network ID Data Source Name Database Name User Login ID Server Name. Verify that you have the correct database User Password. Start Continuum and run PinPoint. From the View menu select Options Record the folder path indicated under Graphics (Pin Files):. Record the folder path indicated under Image:. Record the folder path indicated under Background:.  Install CyberStation on the new machine Before removing the existing machine from the network, start the new Workstation without connecting it to the network. Log on to the PC using an the Local Administrator password. Configure the IPaddress, DNS server and WINS server IP address collected from the existing machine. Disable all Virus protection software. Turn off all FireWalls (Windows 7 has three firewalls). On Windows 7 machines disable Windows Defender. On Windows 7 machines shut off SPS Software Protection Services. Install Cyberstation on the new Workstation PC Shut down the PC. Note: Do not run Continuum Database Initialization at this point. Swap the workstations Shutdown the existing workstation and remove it from the network. Connect the new workstation to the network Start the computer. Log on to the computer using an Administrator level user account. If the existing workstation was connected to a network domain, join the network domain. Verify that you have full network connectivity by pinging known ethernet addresses. Update the Continuum Database. Run Continuum Database Initialization. Select Workstation. Enter the information under Workstation using the information collected on the existing machine and apply changes. Launch Continuum CyberStation and verify that Cyberstation is working properly. Run PinPoint From the View Menu select Options Enter the pinpoint file path location collected from the existing workstation. Select the Checkbutton and verify that a failure notice (a red "X") does not appear beside any item. Apply changes. Verify that all Continuum functions are operating as expected.

Issue Andover97 would not create, but the database did create Environment Continuum Windows Server 2008 R2 Windows SQL 2008 R2 Cause Permissions were somehow restricting the Andover97 user from being created Resolution The dbo was set to sa as seen in Enterprise Management Studio under the database > Security > users There may be a number of ways to correct this: Fix the reason why the dbo cannot be created and recreate the db. Run a query to change the dbowner New Query> sp_changedbowner 'Andover97'

Issue Error: "Tenant X individuals for door LLSSPPBB DO exceeds 24,000" when attempting to select additional doors within Tenant Editor Product Line TAC INET Environment I/NET Seven 2.15 and above DPU / SCU Firmware 3.23 and below Cause SCU / DPU firmware revision 3.3 and lower only supports 24,000 individuals per door, even though the I/NET Software (I/NET Seven 2.15 and above) allows you to allocate 32,000 per tenant.  This is why it is important to maintain consistency between I/NET Software Revisions and Hardware firmware. The I/NET Seven 2.xx Compatibility Matrix lists this information. Resolution To allow the controllers to support more than 24,000 individuals per door the firmware in the DPU / SCU must be at revision 3.24 or above. This firmware is included with I/NET Seven Revision 2.15 or above. Although TAC I/NET supports up to 32,000 individuals per tenant, the model type and revision date of a tenant's door controllers will ultimately determine how many individuals will be supported. The following table shows the capacity of various door controllers. For any door controller with revision 2.2x or later firmware, you would have to define multiple tenants in order to reach the door controller’s maximum storage capacity. Firmware Revision Door Controller Maximum Number of Individuals 2.1x and earlier  DPU7910, DPU7920 Up to 24,000 per door 2.2x to 3.23 DPU7910, DPU7920 without DPU48K Up to 48,000 per controller   DPU7910, DPU7920 with DPU48K Up to 48,000 per door 1 3.24 and later DPU7920 with DPU48K, SCU 1284 Up to 64,000 per door 1   1 Typically, the total number of individuals for a selected door cannot exceed 32,000. However, if one of the two doors controlled by a DPU is not being used (that is, no individuals are assigned to the door), you can assign up to 64,000 individuals to the door that is being used. This also requires the use of more than one tenant since no single tenant can have more than 32,000 individuals.  Refer to TCON300-06/11 Chapter 9-62 for further information.

Issue All the alarms in Vista come to alarm receiver which are not wanted. For example, the system alarms are not wanted to be received by Alarm Receiver. Environment Vista Cause The possible cause is that the alarm control is not defined in Menta or Workstation. Resolution For Menta alarm blocks that do not have an alarm control object assigned to them or Menta alarm blocks that references a non-existing alarm control object in TAC Vista, the alarms are sent to the default alarm control object, $Alr_Cntrl. Define the specific alarm control in Menta or Workstation. Then only specific alarms will come to alarm receiver. Refer to the Chapter 18 of the TAC Vista Technical Manual.