Building Automation Knowledge Base

Issue How to subscribe to a topic in Azure IoT hub via MQTT protocol. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need to configure EBO MQTT interface and Azure IoT Hub, so EBO can subscribe to MQTT messages from Azure MQTT IOT Hub. Resolution The following video will illustrate how to: Create IoT interface and Azure MQTT client in EBO Configure the MQTT connection Create and configure MQTT data values Create and configure a data group Configure the subscription parameters Test the connection Things you need: EBO 2022 or later with valid MQTT license or demo license (Enterprise Server, AS-P or AS-B) valid Azure Subscription with possibility to use free account during testing. For each Azure subscription one IoT hub in the free tier can be created, refer to IoT Hub | Microsoft Azure Visual studio code to be used to test the connection between EBO and Azure IoT hub, can be download from: Visual Studio Code

Issue How can a BACnet b4920 be reset back to its factory default IP address? Product Line Andover Continuum Environment BACnet b4920 Cause There is no Reset IP switch on the b4920 Resolution There are 2 ways of accomplishing this.   Method One - The first method resets the controller to factory default address settings: IP Address: 169.254.1.1 Subnet Mask: 255.255.0.0 Gateway: 0.0.0.0 Webserver Port: 80 Web User Name: acc Web User pwd: acc EnergyNet ID: 1 BacNetMstpNetId: 2764 BacNetUDPNetId: 2765 During controller startup, there is a 2 minute window in which the controller will be restored to factory defaults based on the following: Seconds since startup is < 120 A Ping packet is received by the controller with a matching Ethernet address but unmatched IP address. Ping payload size of 255 bytes. Prior to running the procedure, the controller must be on the same network as the PC that that is used to issue commands.  The engineer will need to have on hand (1) IP address that is both valid and NOT in use on the network that the PC and Controller are connected to.   Get the Controller's MAC Address Each controller has a 6 byte hardware address, also known as the MAC address or Ethernet address. The address is represented in HEX. The first three bytes of the MAC address are constant and represent Andover Controls vendor ID : 00-40-11 The last 3 bytes of the MAC address are derived from your controller’s serial number. The controller’s serial number is printed on the board and is represented as an Integer value. You must convert this value to HEX in order to obtain the last 3 bytes of your controllers MAC address. Ex. Integer Serial Number: 1033394 Converted to Hex: FC4B2 Controller’s MAC: 00-40-11-0F-C4-B2   Create a batch file Create a batch file named Acc.bat with the following content: arp -s %1 %2 ping -l %3 %1 arp -d %1   Restart the b4920 Controller Within 2 Minutes of restarting, run the batch file with the 3 arguments: Acc.bat IP_Address 00-40-11-XX-XX-XX 255 Where IP_Address = valid IP on the network Where XX-XX-XX = last 3 bytes of controller’s MAC Where 255 = Ping Payload size   After Issuing the command, the controller should restart, and the factory default address settings are restored.    Method Two - Capture the Controllers Currently Configured IP Address This second method is easier to do and is currently recommended because of its ease. Download and install a network sniffing application, such as Wireshark which can be downloaded from their website here. Connect a Cross over Ethernet cable between the b4920 and a PC running the network sniffing application. Start up the network sniffing application and then reset the b4920 by hitting the reset button on the controller. On start up, the controller will send out the IP address (Gratuitous ARP Packet) which it currently has assigned to it.  Once this IP address is captured with Wireshark etc the IP of the Workstation can then be changed to allow connection to the controller's web configuration page to change its IP address as required.  

Issue In Physical Access Control lingo, the term Edge controller typically refers to a device that is installed at the door (or in close proximity to the door) and that has all of the components needed to fully control the door with only and IP connection running back for communications to the front end system. Typically Edge access controllers are PoE so that there is no need to provide a separate power feed to the device, they also provide power to all the components that comprise the door control (door lock, REX etc) Environment CyberStation CX9702 Cause Documentation Resolution Continuum does not have a physical access controller that can be considered an Edge access controller. The Continuum access controller that come closest is the CX9702, although it is NOT a PoE controller. Click HERE to see the specs of the CX9702.

Issue Adding a new Netcontroller II (CX 9680) or a new ACX II(ACX 57xx) to an existing system creates problems if the versions are not compatible Environment Netcontroller II (CX 9680) ACX II (ACX 57xx) Cyberstation Cause Current Production of Netcontroller II and ACX II as of 12/1/08 have versions 2.1 and 1.1 on these products respectively. These versions are only compatible with Cyberstation V1.82 or greater.  Resolution If you have a system that is lower than Cyberstation V1.82 you will need to downgrade these controllers to V2.0 and V1.0 respectively. The flash files are available on the Exchange Extranet as is the complete version compatibility chart.

Issue Error Codes: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Product Line Andover Continuum Environment Continuum Site with BCX Controllers and an Error Log Cause Crash of BCX and log reveals: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1629 E 04/05/2012 10:51:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000 Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1630 E 04/05/2012 10:53:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Resolution It is in the range of “Global System errors” that is usually not good, either faulty controller or need reloading of the O/S. Cold start and update O/S with the latest version supported by the Cyberstation version. Then run it on a test rig with different ID and see if it still crashes, if so will need to be repaired or replaced.

Issue Binding a SmartStruxure Analogue value to a Analogue output in the SE IntesisBox (Panasonic Air Conditioning). Environment IntesisBox Panasonic RPM Read Property Multiple Cause Attempting to bind the analogue value to the IntesisBox analogue output causes the following error; Resolution In this case, the AS database has the wrong unit (no-units) associated with the object, since it does not match to the units in the device "Degrees-Celsius" the failure occurs' This is corrected in StruxureWare Building Operation 1.5, where the unit id is not uploaded if the device does not support read-property-multiple, and it appears from the device documentation, that the IntesisBox does not support RPM. As an immediate workaround, the user can configure the unit id of the analog output object directly - configure the "Value" property to have a unit of Degrees Celsius.  To view the IntesisBox Panasonic manual, please click HERE.

Issue How to program a limit block for use in Niagara G3. Environment Niagara G3 Cause Limit are configure using the Reset object in the kitControl palette in the Math folder. Resolution Use the Reset object found in the kitControl palette in the Math folder.  To use it set the "Input Low Limit" and the "Output Low Limit" to the lowest desired output.  Set the "Input High Limit" and "Output High Limit" to the highest desire value. kitControl-Reset This component performs a linear “reset” on the inA value. Reset is available in the Math folder of the kitControl palette. Reset operation is defined by the following four slots: Input Low Limit — must be less than the Input High Limit Input High Limit — must be greater than the Input Low Limit Output Low Limit — may (or may not) be greater than the Output High Limit Output High Limit — may (or may not) be greater than the Output Low Limit For example, a Reset object is used to establish a hot water control setpoint, based on the outside air temperature at inA. When the outside air temperature is 0°F, the hot water setpoint is 200°F. When the outside air temperature is 75°F, the hot water setpoint is 100°F. The Reset object is configured as: Input Low Limit = 0.0 Input High Limit = 75.0 Output Low Limit = 200.0 Output High Limit = 100.0 Whenever the inA value is beyond the input limits, the output is limited by the corresponding output limit (in this case, 200 at 0°F or below, 100 at 75°F or above). When the input is at an intermediate value, the output scales linearly. For example, when the outside air temperature is at 38.2°F, the Reset output is 149.1°F.

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 Communication issues between the Enterprise Server and Automation Servers result in an offline status of the AS. More information is required on how this status is detected.  Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause An AS behaves as if it is online yet shows up as offline in Workstation.  Resolution As of 1.5.0.10001 there is a new model for detecting online / offline servers. Prior to 1.5.0.10001 When a communication error was detected the Automation Server was marked as offline. As of 1.5.0.10001 and Newer An immediate DetectOnline call is scheduled. Only after three failed DetectOnline with an interval of one second we consider the  server to be offline. When offline an alarm is generated.and set the offline status as normal, and also go back to one minute interval for online detection. In 1.5.0.10001 the number of retries and interval is possible to set in server.properties. From 1.6.0 this is configurable from WorkStation. *** Server Communication folder is hidden in more recent versions of SBO See Also: How BACnet b3 controllers are established as being Online / Offline How the communication status of BACnet devices are verified

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 How to send an event based alarm to one or multiple email addresses using an MPM Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager MPM-VA MPM-UN MPM-GW Cause Emails can only be sent using a Lua script Resolution To send e-mails to alert a list of recipients when a pre-defined condition is met, you need to create a Lua Program object (PG1 for example) on your monitor MPM. Copy and paste the attached Email_Alert_AN015 script in the Loop section of the program object and activate it by pressing the green Play button. Don’t forget to save both the object and the database when you are done. You will need to modify this script to represent your own event, including the server information, the list of recipients and the content of the message sent. The monitored variable and the limit conditions can be modified directly from the Event object in Building Expert. In the above example, room temperature is 23 which means that the "Event State" is 0. An email alert will be sent out when the temperature exceeds the high limit (Event State = 3) or when the temperature goes below the low limit (Event State = 4) defined by the event.   Tip 1 Only a Manager connected via Ethernet has the ability to send emails. For a network composed of a daisy chain (CANbus) or a wireless mesh (ZigBee mesh), the Lua program that manages e-mail alerts for all the nodes on the network must reside on the monitor node. The variables in the Lua program will be obtained from any remote node on the network, and the email sent by the monitor if a condition is met. To get an object from a remote node, refer to Display values/objects from a remote MPM on dashboard of the monitor MPM Tip 2 Should you have issues sending emails with the above script, verify that the User and Password defined in the script are accurate and up to date and that all server information is accurate. Also ensure that the Ethernet configuration (ETH1 object) of your SmartStruxure™ Lite Manager is accurate and represents the current settings of your network. Pay special attention to the DNS and Gateway settings. Your monitor Manager will be able to operate on a local network even if these settings are not accurate, but will not be able to access the Internet, which is required to send emails. Tip 3 When using Google’s server mentioned below, it is important to use the following information Google* Server aspmx.l.google.com Domain google.com Port 25** Sender *** Recipient   Username (Not Required)**** Password (Not Required) *Google can only be used to send emails internally from Gmail to Gmail **When port 25 is used, emails are stored in the spam folder ***Bracket < > are not to be discarded, otherwise syntax error 5.5.2 appears ***Note that the user authentication is not required for the google server and if included, will be rejected. Tip 4 The AOL’s server mentioned below can be used to send emails from an AOL account to any other email and does not send the emails to the spam folder AOL Server Smtp.aol.com Domain Aol.com Port 25 or 587 Sender email@AOL.com Recipient Your_email@AOL.com Username (Required) email@AOL.com     (or any other email) Password (Required) Your password   Tip 5 Email server using Port 25 and not requiring authentication, sendUser and SendPassword lines needed to be deleted from Variables section

Issue All Script programs in the AS have status unloaded. How do I get them working again? Environment Struxureware Building Operation 1.5. Cause A script program had an output binding that was linked to a PVR block in a Function block program. It looks like on the server boot up, the script engine tries to start up before the function block engine does and when an output of a script sees that the binding is null, it throws an exception and shuts down the script engine. This only seems to be a problem when binding a script programs output to any PV type in a function block program. Resolution  Bind to a Numeric output instead of a PVR block in the function block program.

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 The automation server password policy is grayed out making it unavailable to make configuration changes. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium   Cause When an Automation Server is attached to an Enterprise Server, all of the password policy configurations are inherited from the enterprise server. Therefore the AS settings cannot be changed.  Resolution The password policies of the Automation Server must be administered from the ES when it is connected to an Enterprise Server.   In order to make changes to the password policy settings in the Automation Server directly, it must be detached from the Enterprise Server. Note: For EBO V 1.9.X and lower, the password policy settings can be located under Control Panel > Security and Communication > Security settings area. For EBO 2.0.X and higher, the password policy settings can be located under Control Panel > Security and Communication > Password policy.

Issue How to Identify a specific PCT (Project Configuration Tool) project. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause How to identify a specific PCT (Project Configuration Tool) project. Resolution In PCT check the project name for the project to be the backup. For this example, the project named “Test 5 Project” is used.   Go to the project storage folder. (The following is the default locations for PCT v1.2.7.223): C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects   Using a text editor (for example Notepad or Notepad++) open each folder then open the file “project.thrift.pctj”, Open each folder in turn until the correct project has been identified to backup. The stored project folder name can be seen:   Further on in the text editor, the PCT project name can be seen, in this example 'Test 5 Project'.   Alternatively click the “edit” menu item and select find (ctrl + F) from the options and search the text for the PCT project name. Making sure PCT is not running when copies of any of the projects are taken

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 Where to find information for Schneider Electric's SmartStruxure Lite and ExoStruxure Building Expert offer Product Line EcoStruxure Building Expert Environment MPM SE8000 range Cause Information required for the SmartStruxure Lite and ExoStruxure Building Expert offer Resolution SmartStruxure Lite and EcoStruxure Building Expert information. There are several sources of information: Schneider Electric's Building Expert Product Selector website. Schneider Electric's Exchange (filter by SmartStruxure Lite) is a source for the SmartStruxure Lite and Building Expert product. Specification sheets Firmware Product Announcements Guides Videos For support contact your region's Customer Care Center

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 Moving the Enterprise Server database path on an existing system Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Cause The Enterprise Server database can be affected by system changes (system restore, Windows reinstall, reformatting the system drive, etc.) if it is located at the default path on the system drive. In some instances, the default location is not the best for the customers' site. Resolution The default path where the Enterprise Server database is installed depends on the operating system it is installed on as well as the version:  The default database path for Building Operation 1.9 and below: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server For 2.0 and above  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.x\Enterprise Server To move or change the Enterprise Server database path. Log on to the Enterprise Server from Workstation. Perform a backup (all data) of the Enterprise Server (right-click on the server and select 'Backup'). After the backup completes, save the backup set to the local drive (server > System > Backup and Restore > Backup sets > Local).  Exit the Workstation. Stop and uninstall the Enterprise Server. Install the Enterprise Server (same version as the version that was uninstalled). When prompted for the database path, browse to the new directory where the Enterprise Server database is to be located. In the example below, the new Enterprise Server database path is  After the Enterprise Server is installed, run the Software Administrator. The database path should now point to the new database directory. Start the Enterprise Server if it is not already running.  Log on to the Enterprise Server from Workstation and restore the backup set (all data) which was saved.  Log on to the Enterprise Server and verify operation. 

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.