Building Automation Knowledge Base

Issue This is a detailed explanation of extended logging gaps, performance and load balancing  Product Line Andover Continuum Environment Continuum Windows XP Windows Server 2000 Windows Server 2003 Windows Server 2008 Cause System overloads Slow server and/or server crashes Server CPU Usage running at high percentage rates Low Physical Memory Available Gaps in Extended logging data Resolution This article discusses factors that need to be considered when extended logging is being used to log a large number of points. There are too many variables involved in the Extended logging engine to place specifics on the number of extended logs that can be used. Performance will be contingent on many hardware, software and configuration variables. It is best practice to make one configuration change at a time and wait for the results prior to making an additional change. The SQL server version will affect extended logging performance There are limitations to different versions of SQL server.  For instance, MSDE has a 2 Gig limit and if this is exceeded, it will cause corruption in the database and the database may have to be rebuilt. SQL Standard and Enterprise versions allow a certain number of processors and RAM to be utilized by SQL. This is a link to Microsoft’s web site that compares the versions. http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx PC hardware such as hard drive access times, RAM amount and speed as well and CPU speed and quantity of processors will directly affect extended logging performance. While always at a minimum following the hardware requirements in the Continuum Cyberstation installation manual, there are times when more processing power and memory are needed. Sites that are performing large amounts of extended logging are definite candidates to consider going beyond the recommended hardware requirements. While 64-bit machines are not supported for running Cyberstation software [before v1.94], they can be used to increase performance on SQL server side. One benefit of using a 64-bit OS and SQL2005/2008 64-bit versions is increased memory capabilities and well as the ability to have several processors. Server hard drives with faster read/write capacities can also be improved. Sites that fall under some of the items discussed below should consider the benefits of faster servers to better handle their Lan site communications and data storage needs. How many Cyberstations are being used? As a general rule, we do not recommend using 1 Cyberstation for logging greater than 2000 points. This does not take into consideration the logging interval. 1 Cyberstation as a stand alone could be overwhelmed by 2000 points if the points are configured at small intervals with a large number of entries. In the case of a LAN site with several thousand extended log requests, more than 1 Cyberstation may be needed for load balancing. What is load balancing? Load balancing was implemented to divide extended logging work among Cyberstations based on the overall number of log entries per hour. Each Cyberstation will be logging on average approximately the same number of entries per hour, but the number of points logged by each workstation may be different. The algorithm looks at the timestamp of the log and if it’s not logged for a specific Cyberstation within a certain timeframe + the Global interval then it’s offered up to the rest of the Cyberstations (pool) to load balance equally. How to identify gaps in data: Run a report for extended log data and you notice that the regular interval for points do not show based on the timestamps. Run the following SQL query to verify the data in the database select * from extendedlog order by datetime desc --Selects all logs in descending order Select top 5000000 * from extendedlog --Selects the top 5 million rows (adjustable) When gaps are identified, a number of steps may be examined to eliminate the gaps. Offline controllers will buffer data as long as they can, but if left offline for long enough then data could be lost as it is first in first out. Normally extended log data will be requested from the controller by Cyberstation once it has come back online and the data will be filled in from the most recent to the oldest data. Check the Continuum error logs. If there is a large number of errors being processed, this can contribute to a draw on needed resources on the system. Resolve the issues in the Continuum error log to reduce the resource overhead. Run Acctrace.exe for a period of time. This can often give some additional information about extended logging that is not reported in the Continuum error logs. Determine how many Cyberstations are being used for load balancing for extended logging. This can be done by verifying in the Cyberstation preferences setting. ‘Download Extended Log data from controllers on the LAN is set to True   To verify the number of Cyberstations being utilized in the database Run a query against the database. Select * from ExtendedLogReservation Observe the ReservationWSLo column, points are evenly assigned to a unique id Any new Cyber added to the pool of workstations for extended logging should be assigned within a couple minutes. Examine the Hard drive I/O subsystem According to SQL server performance data, it is recommended to have multiple smaller drives on a hard drive array as opposed to fewer larger drives for better access times. SQL settings Are any governor settings enabled? (MSDE has one by default) Determine the number of processors that are enabled on the SQL server itself. These need to be selected to be used. Is Boost SQL Server priority selected? If not, enable it.   If a database has moved to another PC or an upgrade was done SP_CHANGEDBOWNER 'andover97' must be run or it can cause db problems including extended logging to no work at all or only partially. SQL profiler can be used to examine if there are issues within SQL that could use specific tuning. For example, certain queries or stored procedures could be isolated that have high CPU usage. Help for using SQL Profiler can be found on Microsoft’s web site or from SQL admin literature. Truncating tables Regular maintenance of removing extended logs can increase performance by reducing the number of rows that the need to be read and inserted into the database. Extended Log Automatic Purge Interval (days) This is the number of days to keep extended log data in the database before purging it. Extended log data is stored in a single internal table, so purging the data after a specified number of days prevents this table from becoming too large. A value of 0 ensures that the data is never purged.  If performance is so bad that it is affecting normal operations it may be desirable to directly purge records from the database. (It is best practice to perform a database backup prior to any delete query.) Also, ensure there is a database backup if the data needs to be saved at various points in time.  This query DELETES all records greater than 3/10/08 14:43:00 from extended log table delete from extendedlog where datetime >= ‘2008-03-10 14:43:00.000’  Increase the interval that extended logs are retrieved in points with small interval times. A listview with the ExtLogEnable and ExtLogInterval columns added can be run for numerics, inputs and outputs to indicate which logs have an interval of zero or a small number for the interval. Increase the interval and reduce the amount to reduce the number of requests. Increase the general preference Extended Log Database Check Interval The interval at which Continuum will check the database for points that are enabled for automatic extended logging. It checks the extended logging table, and uploads the point data. The default is 5 minutes. Increase this Database Check Interval if the system is unable to process all extended logs requested in this timeframe.  Extended Log Maximum LAN Buffer Interval (minutes) This is the maximum time interval, in minutes, that CyberStation may check each controller on a LAN network for new extended logging data. This determines how long Cyberstation will allow the controller log to accumulate new data before downloading it. This setting reduces a small amount of overhead when set to a higher value, and allows more up-to-date extended logs when set to a lower value.  Examples: If this is set to 1 minute and a point is logged every 10 seconds then Cyberstation will wait one minute and download 6 entries for that point. If this is set to 1 minutes and a point is logged every hour, Cyberstation will only try to download the data every hour.  Increase the Extended Log Database Check Interval and stagger Continuum startup When it is necessary, enable logging on several Cyberstations for load balancing. If additional Cyberstations have been added and the system is still having trouble keeping up with logging demand, implement the following procedure. Increase the Continuum General Preference Extended Log Database Check Interval to 60 minutes Stagger the start up times of the Cyberstations to 10 minutes apart. Staggering the startups as well as extending the time should allow the load balancing to level off by enabling the load balancing engine to utilize all of the Cyberstation’s resources and disperse the processing. Adding several Cyberstations at the same time could potentially cause the load balancing engine to get into a race condition where it’s trying to reassign all the points at the same time while still logging data.

Issue How to backup and restore Vista databases Product Line TAC Vista Environment Vista Server Cause There are three different ways to backup/restore a Vista database. Each method has its own unique procedures. Resolution Vista database backup methods: Copy the database folder, you can compress the database into a ZIP or RAR file (ZIP preferred method of Product Support) Use the built in database backup feature (this is commonly used for scheduling an automatic database backup) Use the built in export feature (this is commonly used for partial database backup) Vista database restore methods (referring to backup methods accordingly): Restore from a copy of the database folder: Change the database path in Vista Server setup to the copy of the database folder. Restore from the .fvb file Use Vista restore database feature Restore from the exported filed Use Vista import feature

Issue By design, the Continuum system cannot delete personnel objects until all the distributed copies can be first removed from the controller(s). In some cases the distributed copies cannot be removed from the controllers, such as when a controller is permanently offline or has been deleted. Product Line Andover Continuum Environment CyberStation Cause Communication failure between CyberStation and controllers. Resolution Starting in CyberStation version 1.94 a new feature has been added that allows the user to force a delete of personnel objects even if the distributed copies cannot be removed. In CyberStation 'Delay Distribution' dialog, a new button has been added; the button is only enabled when CyberStation is in offline edit mode. Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. Put CyberStation in Offline edit mode to enable the 'Clean up failed personnel delete distribution' button Click on the button, the system will provide the following warning Click OK to force all personnel deletions that are pending or have failed distribution to complete; any distributed copies in the controllers will be left orphaned. If offline controller returns online orphan distributed personnel records in controller can be removed by one of the following methods: Cool start the controller.  (For controllers that support access control and backup to flash such as the CX9680, ACX5720, ACX5740 . Note that personnel objects ARE NOT saved to flash memory, the controller requests a personnel distribution from CyberStation on cool start). See Restart modes of the second generation Infinity controllers for more information on cool start. Reload the controller from the CyberStation, this will perform a cold start and re-send all objects to the controller followed by a personnel distribution.

Issue All inputs on an Continuum Infinet controller read 999.99 when viewing the electrical value "elecvalue" Product Line Andover Continuum Environment Infinet Controller Cause This indicates that the internal voltage reference is "out of range". Resolution Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input.  Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded.  If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables.  If the interference is being caused by the end device such as an auxiliary contact from a high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation.  If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network.  This will eliminate this unit having a duplicate ID on the network and it will also run the power up diagnostics.  Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems.  The easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the powerstrip of the controller and the shield of the Infinet.  This method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Lastly, a board or controller replacement may be necessary

Issue During communication issues with a Continuum BACnet controller, a large amount of the following error messages are seen in the controllers' error log. 0x8000001e 0x00236400 0x08023a50 0x4c000000 0x00000000 BACnet request timeout 0x00001408 0x0023a600 0x080af632 0x000000bc 0x00000284 Not enough memory Product Line Andover Continuum Environment BACnet Controllers Cause Most likely due to incorrect configuration or excessive BACnet traffic..... or both. Resolution Check the following: What is the version of Controller Firmware being used in each controller? This needs to be checked against the Continuum Compatibility Matrix to ensure that it is compliant with the version of Continuum being used on the SQL Server Are BBMDs configured on this site? If so, where are they located and how are they configured? Confirm the "maxinfoframes" value currently set for all controllers. By default, a bCX for example should be set to 8 By default, b3 controller should be set to 2. If these are different from the default then why this has been changed? Confirm the BACtMaxMaster value in each is set to the maximum b3 NodeID + 1. This defaults to 127 but can cause comms delays on a smaller network. Confirm that all controllers on the MSTP are configured for the same Baud Rate. Any talking at a different baud rate would seem like noise on the network and disrupt communications, resulting in many 1408 error messages. Check the COV increment on points. The default of 0 can cause too much traffic on the bus and should never be left at Zero

Issue Cannot get the Site license to run after downloading and installing it. Product Line TAC Vista Environment Vista 5.X LMTOOLS Cause TAC Vista 5 license needs to be recognized by the licensing server (FLEXnet License Server). Sometimes, license needs to be set up manually using the LMTOOLS software. Resolution Please follow the steps below to manually read the site license. Stop and close TAC Vista Server, Workstation, etc.   Generate the License file at schneider-electric.flexnetoperations.com and insert the .lic file into C:/Program Files/Schneider Electric/License Files folder (default path, for TAC Vista 5.1.3 and prior, the default path should be C:/Program Files/TAC/License Files) .   Open the LMTOOLS utility from the Start menu: All Programs/Schneider Electric/TAC Tools 5.x.x/LMTOOLS (for TAC Vista 5.1.3 and prior, use path: All Programs/TAC/TAC Tools 5xx/LMTOOLS).   Under "Service/License File" tab, make sure the "Configuration using Services" choice is selected and "TAC License Server" choice is highlighted.       Under "Config Services Tab", ensure the path to licenses file is correct (C:/Program Files/Schneider Electric/License Files, by default). Browse to the folder if necessary by using the "Browse" function. Make sure "Start Server at Power Up" and "Use Service" choices are checked.   Under "Start/Stop/Reread" tab, check "Force Server Shutdown" box. In order click, "Stop Server" (wait a few seconds, there will be no message when the server stops), "Start Server", "ReRead License File". You should receive a message stating the ReRead License File Completed.   Start any TAC application other than Vista Server (for example: TAC Menta). You will be prompted to "Specify the License Server System" or "Specify the License File". Select "Specify the License Server System" and enter the computer name preceded by an "@" symbol. If the License Server resides on the local machine, type "@localhost". Note: In more recent versions of License Server, the "@" symbol is optional. If in doubt, putting it in will work with all versions. If you are NOT prompted to "Specify a License Server" in Step 7, Please follow the instructions in Switching from the Demo license to the site License in Vista 5.1.7 or older. At this point the License should read correctly and the licensed Vista products should execute. If the license continues to fail, reboot the computer and try to open a Vista product again (for example: TAC Menta). If the license if still failing, please verify the above steps again before contacting Product Support. For additional information about the LMTOOLS software. Please go to What options are NOT supported by Signal XP?.

Issue Delete Lonworks Device Templates Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server LonWorks devices Cause Some templates are preloaded with the software; if the particular device does not have a supplied template, you can upload an XIF file. This is done by selecting File/LonWorks import/Device Template and then importing the XIF from the manufacturer. An unused Device Template causes no harm to the system; however, there may be a desire to remove a Device Template. Resolution EBO 3.x and later Device Templates can be added and deleted in all device types using the Resource Manager - Device Templates tab SBO 1.x and  EBO 2.x Device Templates cannot be directly deleted from Building Operation WorkStation, however, they can manually be deleted from the  Enterprise Server file system. When a device template is imported, you should understand if the template should be located in the Enterprise Server or an Automation Server.   If the device template is located in an Automation Server, it can only be removed by upgrading the Automation Server using the Device Administrator (you can stay with the current release). If the device template is located in an Enterprise Server, it can be removed using the following process. Locate the template path in the Building Operation database (e.g., C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.3\Enterprise Server\db\UDT\public\public\lon\devicetemplates) Note: in newer releases, the path has changed slightly, e.g., For V1.8.1: C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.8\Enterprise Server\db\UDT\pu\public\lon2\devicetemplates   Delete the two template files named Pidxxxxx, where xxxxx are the numbers or letters in parenthesis behind the device template's name visible in WorkStation. After deleting the templates, you may need to restart the Enterprise Server.

Issue Unable to upgrade a JACE 8000 to I/A Series Niagara 4.8 or later due to insufficient memory allocation. Product Line TAC IA Series Environment I/A Series Niagara 4 I/A Series JACE 8000 Cause I/A Series Niagara 4.8 or later running on a JACE 8000 will consume approximately 40 MB more memory than Niagara 4.7 due to new features including a new OS (operating system) and JRE (Java Runtime Engine). Resolution The following information will help identify if there is sufficient system memory to upgrade to Niagara 4.8 or later and if not, how to tune memory parameters to increase required system memory. Use the following analysis to determine if a Niagara 4 platform, operating at release 4.7 or earlier, requires a memory allocation adjustment PRIOR to upgrading to version 4.8 or later. Determine the amount of Free Physical RAM in the embedded platform while running the current release (prior to a 4.8 or later firmware upgrade) Open the embedded platform with the Niagara Platform Administrator tools. Check the amount of Free Physical RAM that is currently available. The image below displays where the information is located. If the amount of Free Physical RAM is greater than 40,000 KB (40 MB), the JACE 8000 platform is ready to perform an upgrade to Niagara version 4.8.  If the amount of Free Physical RAM is less than 40,000 KB (40 MB), the platform will require adjustment to the NRE Memory allocation using the steps below. Determine the amount of memory allocation required Subtract the current amount Free Physical RAM (MB) from the required 40 MB allocation. In the example above, 40 MB – 26.3 MB = 13.7 MB. Round this value up 14 MB. Next, add a buffer value of 10 MB to the previous result for a new total of 24 MB. System memory will be freed by reducing size of RAM disk used for histories. Ensure that /mnt/aram0 contains at least this “allocation adjustment” free space.  Using the above example, there is 326,944 KB (approximately 326 MB) of available memory that can be re-allocated to satisfy the additional 24 MB requirement.  Note: If there is not enough free space available in the /mnt/aram0, please contact Product Support for more options. Adjust the NRE Memory allocation Use the Platform Administrator tool to locate and select the Configure NRE Memory button as shown below. Record the current memory allocations for Heap Space and Meta Space by reviewing the memory sizes shown below. Increase the Meta Space by using the Meta Space slider to provide additional working space. Slide the Meta Space adjustment shown below to add 40 MB to the existing value of 48 MB increasing the Meta Space to 88 MB. Increase the System Reserve by the required 24 MB calculated in the example above. Slide the System Reserve adjustment shown below to set the value to 24 MB. Return (increase) the Heap Space back to the original 384 MB size by adjusting the Heap Space slider shown below. The final adjustment will bring the Meta Space back the original 48 MB size by adjusting the Meta Space slider shown below. Save the changes and reboot the JACE 8000.  Using the information from Step 1, verify that the Free Physical RAM is now above 40 MB.  If confirmed, the JACE 8000 platform is ready to perform an upgrade to I/A Series Niagara version 4.8 or later.

Issue At times the firmware and software on the Roam IO2 requires updating and instructions are needed Product Line Andover Continuum, EcoStruxure Building Operation Environment Roam IO2 Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Windows Mobile Cause Instructions for upgrading the software and firmware are provided in the User's guide, but this article places them in an easy to find location Resolution The full instructions for installing and using the RoamIO2 software and hardware are in the User Guides: BACnet Service Tool User Guide + Software Infinet Service Tool User Guide + Software NOTE: The RoamIO2Appl2.000002.upd firmware firmware can only be updated from the BACnet service tool, the Infinet service tool does not have the update OS option.     Please see instructions for installing firmware and hardware for the RoamIO2 for an overview.  

Issue PageGate allows for network paging or network wide SMS messaging from any combination of the following modules: web, email, commandline/ascii, serial, TAP-in and (GUI) windows workstations. SMS or text messages can be sent to alphanumeric pagers, numeric pagers, cell phones, PIMs, billboards or pcmcia pager cards. For capturing and paging I/NET Seven alarms and messages the “Get Serial” module from PageGate is used. Environment I/NET Seven PageGate Cause Network paging or network wide SMS messaging required. Resolution Click here to download this document as a PDF Configuring I/NET to send a message Open up the IO Server. Choose your configuration profile. Maybe direct connect. Click Modify. Under Peripherals, change Text Output Port to a COM port that is not being used, COM3 for example. I/NET will most probably be using COM1. See screen cap below. Set Baud Rate to 9600. Click OK to close out the Configuration Profile Screen. Restart I/NET and I/O Server for changes to take affect. Open up Alarms, Messages, & Transactions. Go to the Edit drop down menu and select Text Library. Here you will need to know the address for the point that you want to generate a message for when it goes into alarm. Choose add to enter point address and desired text message. As you can see above you can enter any text message you want. I/NET is now configured to send a text message to PageGate. Hardware Connections for PageGate-I/NET interface Three Com Ports are required to send the message from I/NET to PageGate Server. One for the I/NET port, a second for the Text Output Port so AMT can send the message, and the third COM port for PageGate to catch the message. Physically connect the Text Output Port to the PageGate COM port that will be catching the message. See Illustration below. Note:   If you run out of COM ports you can go to Radio Shack and purchase a USB to serial cable. It comes with the software to create another COM port. Be aware that it is not plug in play. The software/PC will refer to that USB port as your new COM port. In other words, if you take the USB plug out and insert it into another USB port you will have to repeat the installation to create another new COM port and it will have a different number then you will have to go back into  I/NET or PageGate to point to the right COM port. I found this out because my customer decide he wanted to move his USB cables around and then PageGate quit working. Configuring PageGate PageGate consists of PageGate server, PageGate Admin, & PageGate Monitor. From now on I will refer to PageGate as PG. PG Server is an e-mail server and will create an e-mail domain such as inet@villadematel.com. PG Server can be ran as a Windows NT application so the customer does not have to worry about starting PG when he boots his machine up. PG Monitor will show I/NET generate the alarm, PG catches that alarm, and PG Server e-mails the message out. It is not necessary to run PG monitor unless you are setting up the software or trouble shooting a problem. Follow these steps to assist you in setting up PG to send your message to a cell phone or pager. Go to http://www.notepage.net/ to download the trial version.  Install the software and then open up PG Admin to begin configuration. The PG software file system is organized in a tree structure. Open up Settings under, Program, and PageGate. From this point on reference tree structure on screen caps to navigate through PG. Under settings choose Run PG as an application and check the box next to scheduler, GetSerial and Dialer 1. Remember to go back and change to NT service once you get customer set up. Set the capture serial port for PG, baud rate, parity, data bits, stop bits, handshaking, & init string as you see below. These are the settings that I/NET uses when it transmits a message out the Text Output Port. Go to the GetSerial drop down to Record and enter the Start Pattern and End Pattern you see below. This tells PG how to determine what the message is. Under Recipient choose static recipient and give whatever name you want. The person or group that will be receiving the message. Now name your Static Sender. The application (In our case I/NET) that is sending the message.  Select Message and choose Dynamic Message since our text alarms from I/NET will be different most of the time. Put START offset at 6 so PG will know when our message starts and –4 so it will know when the message ends. 6 being the length of “START “ plus a space and –4 being a space plus the length of “END”. We have now configured PG Get Serial to capture the I/NET message. Connectors. PG will always require at least 1 dialer running and if you are sending a message on the internet you will need to set up the Global settings as well. Under SMTP create a Local Domain. When your customer receives a message it will be from “static.sender.name@localdomain.com”. For example Villa De Matel receives a text message from inet@villadematel.com. Then enter your customers DNS server addresses. You only need one but enter both if you have them. Obtain from their IT department or internet provider. Dialer set up. Even though we are not dialing with a modem PG uses a dialer to send all messages. Serial Port in this case is for an external dedicated modem. Just make sure you have Dialer 1 running (See step 4). Carrier creation. Here we create the cell phone/pager provider that our customer will be using to receive messages and pages. In my customers case it was T-Mobile. To do this, right click on carrier and select Add. Select the drop down box under protocol and select SMTP or the appropriate protocol you need. TAP, GSM, SNPP, etc. Recipient creation. Here we enter the contact data for the individual’s cell phone, pager, fax number, e-mail address, etc. Fill in name of recipient and check the box for enabled service. It is possible to send messages to multiple devices such as an e-mail and text message at the same time. Just check the service you are using but remember you need a dialer for each service. Refer to cell phone provider for e-mail address format. For T-Mobile it was phone number@tmomail.net. Also check the box for Alpha and Drop non-printable characters. Group creation. You can create a Group and PG will send messages to every recipient in that group for the appropriate enabled service. Right click on group and select add. Check box to enable appropriate service. Select recipients you want to add and move them across into your new group. Select apply and PG will now send messages to all recipients in that group. This write up is intended to be a general guide in setting up PageGate for your customer. Most likely your customer’s setting will differ from the settings in this write up. To download the software here is the link to the website: http://www.notepage.net/ Once you get the trial software working you have about 10 days to pay for it because the trial version will shut the scheduler down every so often until you pay for the software. Good luck!

Issue At times it is helpful to know the default IP address of a new MNB-1000 and it is not in the documentation. Environment All MNB-1000 controllers regardless of firmware version ship from the factory with a default IP address. Cause Connecting to an MNB-1000 for the first time after it is shipped from the factory. Resolution The default IP for all MNB-1000 controllers when they are shipped is 10.1.10.2.

Issue Clarification on dip switch six and station addressing for the SCU1200, SCU1280, or SCU1284 Product Line TAC INET Environment I/NET Seven with Access Control using an SCU SCU1200, SCU1280, or SCU1284 Cause Clarification on SCU and dip switch settings being open, enabled for dual or single station addressing (2 or 4 doors) Resolution If the Device Type is SCU1200, SCU1280, or SCU1284: set the Number of points to either 1 or 2. Choose 1 if the SCU is configured to operate in the “single-address” mode (DIP switch S1-6 = OFF). Choose 2 if the SCU is configured to operate in the “double-address” mode (DIP switch S1-6 = ON). In order to control more than two doors, the SCU1284 must be configured to operate in the double-address mode. Though the TCON312 shows the dip switches for 1-6, there is still a bit of clarity which can be provided on how that looks on an actual SCU. The example from the TCON is shown here: And this is a photo below of an SCU which is setup as 0101 with dual addressing since Dip Switch 6 is in Dual Address mode shown in the picture below. When penetrating down to it using Edit, Host Computer, Network Configuration, SCU 1284 is shown with 2 Points with door addresses: 010108 Door1 010109 Door2 010208 Door3 010209 Door4 After checking MCU Configuration, I added the points in the Network configuration. The main point here is that Dip Switch 6 is up on the Open side of the Switch bar shown in red which is the dual point and 4 door configuration.   Note: Concerning the numbering scheme for addressing the SCU, it is important to number your SCUs with an address then skip the next number so in the event you dual addressing for four doors, the second address is available. Don't use addresses 28, 29,30, and 31 as those are reserved for the Remote Arming Terminal.  Overlooking this can result in future headaches of moving SCUs around in the addressing scheme which is never recommended. Example for a site containing 4 SCU door controllers: SCUa address 2, SCUb Address 4, SCUc Address 6, SCUd Address 8.  Another example configuration: One reader inputs to READER1 and READER2? Here is that wiring example. In order to use more than the first eight inputs on the SCU, you must configure the SCU as a double-address controller. When you enable the double-address mode (DIP switch S1-6 = ON), inputs 1 through 8 are monitored on the selected subLAN address (i.e., the primary address) and inputs 9 through 12 are monitored on the next consecutive subLAN address (i.e., the secondary address). The input points are defined in the I/NET host using two separate SCU controller assignments, the first providing eight input point definitions and the second providing 4 input point definitions. The SCU’s outputs are also divided across two LAN addresses when the SCU is operating in the double-address mode. The first four outputs are assigned to bit offsets 00 through 03 on the SCU’s primary address. The last four outputs are assigned to bit offsets 00 through 03 on the SCU’s secondary address.

Issue During extremely high levels of network traffic Ethernet controllers are going offline. Product Line Andover Continuum Environment The following controller versions and above: bCX1 Firmware V4.500065 bCX1-INF Firmware V1.200021 Netcontroller CX9900 V1.530026 Netcontroller II V2.100027 ACX57xx V1.100027 Cause Although the above firmware versions (and higher) all contain a fix to stop the controllers resetting due to excessive traffic levels in a broadcast storm (LAN Errors), they can still be seen to go offline even though they no longer reset and lose their data. Resolution If a controller detects a broadcast storm and receive excessive data traffic that fills up its buffers, then the controller may turn off their receiver to protect themselves and ensure that they do not reset. By doing this it allows the controller to continue controlling and running PE programs as well as retaining the data in the RAM memory. When the storm stops or data traffic levels reduce enough for normal communication to continue, then the controllers will come back online and communicate again to the Workstations and other Ethernet level controllers. Note: A broadcast storm can be generated by incorrect BBMD configuration, i.e. more than 1 device set as a BBMD in one subnet can cause a storm to occur.

Issue Forgotten or deleted default password. Product Line TAC INET Environment All versions of I/NET Seven Cause Users either delete the default password and then forget what theirs is and is unable to log into the system. Resolution To resolve this, the following steps need to be followed: Close I/NET and I/O Server Open up DBCreate and choose the option to back up the database. Put the backup database on the ftp site so that engineer can get to it. They would then reinsert the default tac/dacs password back into the database. Place it back on the ftp site so that the customer can retrieve and restore it back on the system again.

  Issue Unable to convert DMP file to SmartX servers with EBO 3.x, 4.x and 5.x using Continuum Conversion Tool(CCT) with PCT 2.0 Example: CCT3.2 is unable to connect to an AS-P in v3.2 created in PCT 2.0 It shows the "The user session is lost, no specific reason has been set" error when trying to connect. Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Project Configuration Tool Cause PCT 2.0 is not compatible with earlier versions of CCT Resolution In PCT 2.0, create a version 6.0 ES. In PCT 2.0, create an older version of AS-P. In PCT 2.0, make the older version AS-P a child of version 6.0 ES. In WorkStation 6.0, log on to the ES, navigate to the AS-P, and create the desired MS/TP or Infinet networks. In CCT 6.0, log on to the ES and import and analyze the desired Continuum dump file. In CCT 6.0, click to select the target MS/TP or Infinet networks. When doing so, navigate into the older version of AS-P to select the desired networks. Convert the dump file.

Issue Enterprise Server ES crash Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The ES/EC runs on a Windows platform and there are circumstances that can lead to a single crash or multiple crashes leaving the ES/EC not running Background - The ES service is usually running. The service can be seen below under the Windows services and via "Building Operation Software Administrator"  The ES v4.0 has crashed and will not restart. The "Building Operation x.x Connect Agent" collects any core dumps and packages them, so they can be quickly analyzed. It also checks if an ES is registered and online, then uploads the core dump files for automatic analysis. If the site is not registered or is offline, then these files are stored locally at %ProgramData%\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise [Server|Central]\db\Crash information (default for v4.0 "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\db\Crash information") The "Building Operation x.x Connect Agent" is a Windows Service and installed with the ES, the service should be left to run continually. If it is not running during an ES crash, the core dump may still get created, but does not get packaged up in a way that can be easily analyzed. Each packed crash dump file may look like "ES_ES_MYCOMPUTER_20221104T121314Z.zip" and likely be between 40MB and 200MB in size. The individual core dump will look like "server_20230314_132853__r4.0.3.176.dmp", but is very time consuming to analyze, without the other associated files Resolution Following a crash,the EC/ES will usually restart and operate correctly, however in some cases the EBO database or install file structure may be damaged and the EC/ES may fail to restart correctly EC/ES has crashed and is now running correctly Send the following information to Support - All core dumps from the "\db\Crash information" folder - All data from the "\db\logs" folder - Ideally a full backup of the ES (with history), always zip before sending to Support If the "Crash information" folder is empty, then check the "Building Operation x.x Connect Agent" is running. It is possible the core dumps have already been uploaded and analyzed automatically EC/ES has crashed, tried to restart but just stops again. (as seen in the first screen shot, "The server has made too many unsuccessful attempts to start..." is seen It is important to gather all the data as stated above, but also collected the EC/ES and AS backups from "\db_backup" It can be useful to get full copy of the files in "/db" Ideally the EC/ES is not critical to the operation of a site, but it can still cause a big problem. Checking the Trace and System logs may give a clue to the problem, e.g. a lack of disk space, but often there are only a few options   Collect the files above, then wait for a reply from support. Please state if the EC/ES is stopped and a resolution is being sort. Reinstall the EC/ES at the same version and choose repair current version, or upgrade to a newer CP Fix version or maintenance version. Uninstall the EC/ES, then re-install the same version with an empty database, then restore the last good backup to the ES. If option 2 or 3 is used, it is still important to log a case with support, so the crash can be investigated. The backup can be checked for errors using the XBK Analyzer.

Issue The License server cannot be seen by either the Workstation or Enterprise Server Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation Workstation Building Operation Enterprise Server Cause When attempting to log onto a system using Workstation, or start an Enterprise Server, the license is not seen on a remote License Server. Resolution Make sure your firewall setting is not blocking the license system. For more information read SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96) The system consisted of a PC running the Building Operation License Server. The license on the PC had been generated from an entitlement for an Enterprise Server, Workstation and program editing tools. A second PC was running the Workstation and Enterprise Server programs. Confirming that the correct licenses are available on the License server. On the License Server, select Internet Explorer and enter http://localhost:8888 in the address bar. Select the "Concurrent View" Below shows the page displayed, confirm that the expected licenses are shown. Check that the License administrator has the correct address of the license server. Open the license administrator and select the "License Server Address" tab. NOTE: the @ symbol before the IP Address must be used.

Issue These LED light sequences are not found in the documentation Solid White Flashing White Alternating Blue and Amber Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Cause Not yet added to current documentation Resolution Solid white forever is either no firmware in the controller or the controller is running UBoot and not launching the firmware. Solid white, transient, and followed by yellow/amber, is UBoot running. Perform a factory reset and attempt to upgrade the firmware to the latest revision allowed based on the version of EBO used on site Flashing white would indicate a defective board requiring RMA or a power supply problem (It was seen on one site the 24Vdc power supply had been damaged and was only supplying 12 to 14Vdc. Thus replacing the power supply solved the problem) Alternating Red/Blue happens during an up rev of the firmware. It specifically happens when the EFR32 (the Bluetooth chip) is being upgraded. Generally, power supply problems can cause various issues with RPx and MPx controllers, including partial corruption of the firmware/application. A recent case had transformer secondary circuits linked that cause Red/Blue flashing and 'untranslated BACnet errors’ following a site wide power cycle. Always ensure the RPx power supplies are within tolerance and fully compliant to Grounding and Power for Systems WebHelp has been updated to include more information see RP Controller Status LED

Issue Will J-Bus operate with Modbus RTU devices on the same bus? Product Line EcoStruxure Building Operation  Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Compatibility of J Bus required. Resolution The J Bus protocol is supported by the Autimation Server, it runs on an RS485 network and uses a subset of the Modbus RTU protocol function codes. The J Bus devices addressing usually has an offset of 1 compared to the Modbus RTU standard, to apply this offset select "J-Bus Mode" = Yes in the Modbus Master Network Properties.   Verify that the devices to be used have a standard RS485 electrical connection and do not require any special electrical biasing, also ensure that all units connected on the bus have a unique ID/ address number. If this is the case then you should be able to connect both Modbus RTU and J Bus devices on the same Automation Server port connection but in the Modbus Master Network select the J Bus Mode setting to No. In J-Bus mode, the Automation Server will automatically reduce the polled register addresses by one, so if the AS is set to Modbus mode, you may need to manually set the register addresses of any J-Bus devices by minus one. With J Bus as with Modbus sometimes the point addressing needs to be offset by +1 or -1, but check with the 3rd party device supplier/ documentation to determine its specific point addressing requirements.  

Issue How to Mass Create Trend Logs and Extended Trend Logs Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause If you did not create Trend Logs at the same time as you created the points or values, it is possible to create several trend logs or extended trend logs at the same time. Resolution For this example, we assume all of the values are in the same folder. You can hold down SHIFT to select multiple adjacent objects, or CTRL+click to select non-adjacent values Mass Creation of Interval Trend Logs Select all of the Values you wish to add the same type of Log to Right Click and select New connected object>Trend Select the Log type and the settings you wish to use.  Note that the log name will be the values name with either a prefix or suffix defined by the user Be sure to Select a useful folder location, either same folder as each selected object, a different folder, relative to the selected object or a single folder for all created objects. Click Edit in wizard. Set the Interval Settings, if iterval log type is selected. Click Next, configure initial meter settings if required, click next tehn click create Mass Creation of Extended Trend Logs if required Select the group of Logs you wish to create Extended Trend Logs for Right Click and select New connected object>Extended Trend Log Enter the desired settings. Just as above, the Extended log will use the Log' name plus either a prefix or suffix Be sure to Enter an appropriate Location. Use a folder on the ES if you wish these logs to show up on the Reports Server (Report server is not supported in EBO 2022 and higher). Click Edit in Wizard, Configure the Extended Log as desired, then click create. Fore more information, refer to: Mass Creating Trend Logs and Mass Creating Extended Trend Logs