Building Automation Knowledge Base

Issue The word TEST is displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation preventing it from being commissioned. Environment Satchwell Climatronic CSC5252 CSC5352 CXR5805 CXT5605 CZT5305  Controller Display TEST LCD Screen Cause The cause of the word TEST being displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation and preventing it from being commissioned is normally due to a micro processor programming error occurring during the course of production. Resolution There is no field remedy that can be applied to a Climatronic Controller displaying the word TEST on the Liquid Crystal Display screen that will enable it to be commissioned successfully. The Controller should therefore be returned to the vendor for replacement under the terms and conditions of the warranty applicable at the time of purchase.

Issue Timestamps in Script programs are different by an amount equal to the UTC offset of the workstation's timezone settings. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation WorkStation Script editor Cause Take the following program as an example:   Datetime Output TimeOut, TimeOut2 TimeOut = StrToDate ("1/17/2012 15:00") TimeOut2 = StrToDate ("1/17/2012 3:00 PM") In EcoStruxure Building Operation, the values will read:  "1/17/2012 9:00:00 AM" (in this example, the UTC offset is set for -6). In servers, all time values are stored in UTC, then the offset is applied by the client.  When it receives a value from a Script program, it stores the value as UTC, then the offset for the selected timezone is applied. Resolution Write code in the Script program to adjust the time values to UTC. Check the example code below to help understand operation: Datetime Output dtOut1 Datetime Output dtOut2 String Output str1 dtOut1 = Date 'Local time, displays with added UTCOffset dtOut2 = Date - UTCOffset - DST 'Local time, adjusted by the UTCOffset and DST, displays properly Print Date to str1 'Local time String value displays properly (UTCOffset system variable is available in v2.0 or higher, DST system variable is available in EBO 2022 v4.0 or higher)

Issue Error when trying to add exceptions to a schedule is seen when trying to "apply" the changes. Example: Personnel Manager Error saving data Communication Error Exception has been thrown by the target of an invocation. The personnel object was created Product Line Andover Continuum Environment Continuum Cause Too many old exceptions in the schedule. Sometimes RPC (Remote Procedure Call) errors happen on Cyberstation following the above error. Resolution Delete the old exceptions. This must be done manually for infinet schedules. 1.94 NOTE: If this issue is happening for 1.94, there is Hotfix for TPA CONT 12 0002.00 Schedule Exception Errors.zip that has been released for this issue. The V1.94 issue is also detailed in Technical bulletin: TPA-BOST-12-0002.00  

Issue Instructions on how to configure a Bosch Integration on Version 3. Product Line Access Expert Environment Access Expert Version 3 Microsoft Windows 8.1 and above Access Expert Hosted software with Bosch integration Access Expert Premise with Bosch integration Cause Configuring a Bosch Integration on Version 3 to communicate to Access Expert. There are certain settings that need to be configured from both the Access Expert side and Bosch so that the integration can be seamless and function as designed. Resolution One of the first things when doing this Integration is to have the Bosch Appliance ordered and installed on the Network where the Bosch Panel resides. The device comes pre-configured from Feenics and all that is needed is to make the necessary changes in Access Expert using the following steps: 1. Verify that the connected instance does have the Bosch Services Enabled by going to the Hardware Provisioning and looking at the Bosch Services.  2. Click on the Bosch Services. 3. This entry would come up automatically as it was preconfigured into the Hosted Instance by Feenics. 4. Click on the Panels label and add the Bosch Panel Type from the dropdown. 5. Enter the necessary values on the various fields that correspond to the Bosch Panel, the Password must match what the Bosch Panel is using. 6. Import the Configuration and then save and close. 7. On the Bosch Panel verify that the Port is set for Port 7700, Automation Mode is set to 2 and the Firmware is 2.0 or greater If changes need to be made, you need to first connect to the Panel from RPS > make the changes > sync to the panel > disconnect from the panel Go into the appliance and stop/restart the Feenics Bosch Service within Windows Services 8. Make the necessary changes if needed then save and recycle power 9. Bring up the Hardware Tree and verify that the Panel is Online and communicating 10. All preconfigured Areas, Points, and Outputs will show up in Green, indicating that everything is working properly.

Issue Need an example on how to program a required action where a Door Switch activation triggers alarm sounder to turn on and stay on until a Key Switch is closed. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require a programming example. Resolution There may be a number of ways of doing this, one solution is to have a Door Switch trigger an alarm in the Door's Area which triggers an Alarm Output to turn on. A Key Switch Input is linked to another Automation Area that will disarm the Door's Area which turns off the Alarm Output.   In this example we will use the following objects: Input        Door_Switch_Input Input        Key_Switch_Input Output        v_Alarm_Output        (a virtual output for this test) Area        Door_Opened_Area Area        Area_Automation Input Type        KeySwitch_InputType   Setup 1. Create an Output, in my example this is virtual output v_Alarm_Output. 2. If not already created create the Area your Door is located, in my example I created Door_Opened_Area.   3. On the CONFIGURATION tab set the alarm timings to 0. 4. On the OUTPUTS tab set the Alarm Memory Output to your alarm output. 5. create the Area that will be used as an automation area to reset the door alarm. In my example I created Area_Automation for this purpose.   6. On the CONFIGURATION tab set the alarm timings to 0. 7. Create a new Input Type, in my example this is KeySwitch_InputType. On the GENERAL tab set the Control Area to the area with your door switch in it. (Door_Opened_Area) 8. On the OPTIONS (1) tab, under MISCELLANEOUS OPTIONS, set the Disarm Control Area On Input Restore and Arm Control Area On Input Alarm options. 9. If not already created, create your door switch input. In my example this is Door_Switch_Input.   10. On the AREAS AND INPUT TYPES tab set the Area to your door area and the Input Type to Instant. 11. If not already created, create your key switch input. In my example this is Key_Switch_Input.   12. On the AREAS AND INPUT TYPES tab set the Area to your automation area and the Input Type to the input type you created earlier (KeySwitch_InputType). 13. Go to a Status Page view with these two Areas listed and disarm then arm each of them. This needs to be done after any change to the Area or objects within it (such as inputs) so they will function properly with the new changes.   Notes: KeySwitch = Closed -> Alarm disarmed (Area_Automation) KeySwitch = Open -> Alarm armed (Area_Automation) To disable alarm and reset area, KeySwitch must be Closed and then Opened. DoorSwitch needs to be closed for Alarm to be re-enabled with KeySwitch.   Usage 1. Armed normal state. 2. Door Alarmed. Door_Switch opens triggering alarm in Door_Opened_Area triggering v_Alarm_Output to turn On. 3. Alarm silenced by Key_Switch. Key_Switch is Closed triggering Door_Opened_Area to be disarmed and v_Alarm_Output to turn Off . Key_Switch is Opened triggering Door_Opened_Area to re-arm. 4. Alarm will not re-trigger again until Door_Switch is closed and Area re-armed.

Issue ROAMIO2 fails to connect to i2 controller when the controller is connected to Infinet.  But it succeeds to connect to the i2 controller when Infinet is disconnected from the controller. Environment Netcontroller - CX9900, CX9940, CX9702 Infinet controller - i2 controllers Cause When the netcontroller (CX9900, CX9940, CX9702)  version is old , the ROAMIO2 does not communicate well with the Infinet with the CX connected. Resolution Upgrade the Netcontroller OS (firmware) to the latest version.

Issue In a life safety-related application, such as a fume hood, it is a requirement that the status of the end switch is not shared via peer-to-peer bindings. Instead, the end switch status must be hard-wired to all four controllers. What precautions should be taken to ensure that this will not cause issues. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Cause Connecting multiple RP-C to the same dry contact.    Resolution Make sure to use individual transformers to each controller (i.e. one transformer to one controller power supply) to minimize the risk of short circuit.

Issue Cannot activate embedded license on Automation server, either online or offline, with error: FlexNet Embedded error: The allowed time to process the response has expired.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Automation Server has wrong date and time. Resolution Make sure that Automation Server has correct date, time and time zone. Automation Server can be connected to NTP server to synchronize its clock, refer to Synchronizing the Automation Server Clock.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Creating a report that shows which visitor is being visited Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause The standard visitor report does not record who at the site is being visited Resolution This video demonstrates how to create a visitor report that includes which users have been visited in the Security Expert System.   The advanced Visitor Report is created in 4 main steps: 1. Create an Access level for each user who receives visitors 2. Assign this Access level to the user's visitor tab 3. Create (or use existing) User report with the new "access level" column selected 4. Configure and run the user report   Creating Access levels 1. In Security Expert client, go to Users|Users a-Select a user who receives visitors (ex: John Doe) b-Go to the Visitor tab c-Check the "User supports visitors" box d-Click the ellipsis (3 dots) to open the Access Level window e-Click Add button f-Name it '[User]'s Visitors' (ex: John Doe's Visitors) g-In the configuration section, configure the access level required for the user's visitors h-Save and repeat for each user who normally receives visitors. Close the window and go back to the User table.   Assign Access level 2. Select "John Doe's Visitors" for Visitor access level -Save changes   Create User Report 3. Go to Report|Setup|User -Create (or use existing) report for visitors -Go to the Columns tab -Click Add and choose "Access Level" User Field -Save report setup   Configure User Report 4. Return to the general tab and expand the "Default user report filter" section. Press "edit in report view" and edit your desired layout -Save report view   The next time you run the visitor report it will print who's being visited in the "Access level 1" column

Issue SCD100 is obsolete and needs to be replaced. Product Line Field Devices Environment SCD100: 004630100 004630110 SCD110: 5152300000 5152302000 (SCD110-D) 5152304000 (SCD110-D-H) 5152306000 (SCD110-H) Cause Replacing obsolete sensor SCD100 with new range of sensors SCD110. Resolution The range of SCD110 sensors are replacing the old and obsolete SCD100 sensors. For a complete overview and for more technical details, please see the SCD data sheet.

Issue Newly enrolled users biometrics are not working at Suprema readers while existing users are functioning normally. New user updates appear to be working, the Download Server is online, with changes being made to the controller .dat and suprema reader .dat files in the Security Expert Servers ProgramData folder as users are updated. Controller .dat files Product Line EcoStruxure Security Expert Environment Security Expert Suprema Integration Cause The Suprema BioStar services are running on the Security Expert server which conflicts with the operation of the Security Expert Download service. Both the BioStar software and Security Expert Download service use the same port (51211) to communicate with the biometric readers. Resolution The Suprema BioStar software is only used during commissioning and configuration of the biometric readers and does not need to be permanently running. Due to the port conflict, the Suprema services cannot be run on the Security Expert server with the Security Expert Download service active. Stop all of the BioStar services running on the Security Expert server and set the startup type to manual. Suprema services Restart the Security Expert download service. Download service New user updates will now be downloaded to the Security Expert controllers and Suprema readers.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP server from the virtual machine. Resolution To change the Notification Address in the "Setup for use with remote server" to "localhost". 1. Select "Setup for use with remote server" after PCT start. 2. Update the "Notification address" to localhost  

Issue Capturing packets from Zigbee Standard Security Network shows packets marked Bad FCS or Encrypted Payload Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Room Controller Cause Zigbee Standard Security Networks implement multiple keys to encrypt data for the Zigbee Network and each device Resolution This resolution assumes you have a Zigbee adapter that can capture packets in Wireshark.   Ensure zigbee_pc_keys are available in each profile you are going to use to analyze the Zigbee packets. The file location is generally: %AppData%\Roaming\Wireshark\profiles\<Profile Name>\zigbee_pc_keys   Open Wireshark and configure the Zigbee adapter NOTE: Please substitute your adapter name if not using the TI CC2531 adapter. Open Wireshark Click the gear next to the 'TI CC2531 802.15.4 packet sniffer' Select the known channel (11-26) and click Save Click on 'TI CC2531 802.15.4 packet sniffer' to start capturing Update formatting to resolve Bad FCS packets Go to Edit -> Preferences -> Protocols Select IEEE 802.15.4 Depending on your Wireshark version, check or "TI CC24XX FCS Format" or set FCS format = "TI CC24xx metadata" Add default link key for Zigbee Alliance Go to Edit -> Preferences -> Protocols Select ZigBee Set Security Level = AES-128 Encryption, 32-bit Integrity Protection Click Edit next to Pre-configured Keys Click + and Enter Wireshark Key from below, Byte Order = Normal, and Label Enter the Zigbee Alliance Default Link Key Key = 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39 Key Value = 5A6967426565416C6C69616E63653039 Remove colons (:) for entry into Wireshark ByteOrder = Normal Label = ZigbeeAlliance09 Find and add Standard Network Key Ensure you have configured the default transport key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Find Standard Network Key Look in the Info column for the Transport Key and select it Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Standard Network Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use Descriptive label because you will have Network Key per Zigbee Network, so includes Device, PAN ID, and NetworkKey, ie ASP087_12345_NetworkKey Find and add Trust Center Link Key PER device Ensure the following are configured: formatting, transport key, and Standard Network Key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Since this is per device, one can include the Network Address for the device. Example: If the network address of the device is 0x2074, the display filter would be: zbee.sec.decryption_key and zbee_nwk.addr == 0x2074 Find Trust Center Link Key per device Using the Info field, find the pair of Request Key and Transport Key. The Request Key will have Source = Device Network Address, and the Transport Key will have the Destination = Device Network Address. Click on the Transport Key packet Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Trust Center Link Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use a Descriptive label because you will have a Key per device, so includes Device, Network Address, and Trust Center Link Key, ie TH907-01_0x2074_TCLK

Issue Numbers are rounded. Why two values of nearly equal magnitude are subtracted, significant digits are lost.  This occurs in a variety of places within EcoStruxure Buildings Operation, and explained using a script program in the example below. Product Line Ecostruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause In a string program and the NumToStr function, if a number (example 5.7) is entered and Save is selected, then the Value in the Variables window at the bottom shows 5.6999998. The value is altered from the original. Resolution When looking at a value in the watch window or variables view, there is no rounding so you are going to see the full length of the float number which suffers from a thing called “loss of significance” More information on float numbers can be found at: https://en.wikipedia.org/wiki/Loss_of_significance This phenomenon happens everywhere. An alternative would be to add a formatting feature to do the rounding. Script handles numbers as IEEE754 single precision floats, so the accuracy is limited to (IIRC) seven significant digits. The accuracy loss starts around 1.677E7. On www.binaryconvert.com/convert_float.html?decimal site, a decimal number can be converted to binary and then back to decimal in order to see how the decimal number will be handled in Script. Script handles numbers as IEEE754 single precision floats, so the accuracy is limited to (IIRC) seven significant digits.   The accuracy loss starts around 1.677E7.   On this site you can convert a decimal number to binary and then back to decimal in order to see how the decimal number will be handled in Script. http://www.binaryconvert.com/convert_float.html?decimal

Issue How can I find out whether the EBO 2022 multi-version support applies to AS Classic module?  Does it apply to all the AS, AS-P, and AS-B modules? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The EBO 2022 Release Note describes that the EBO 2022 Device Administrator software is not supported on the original AS classic (part number SXWAUTSVR10001) but there is no description of the software backward compatibility of the EBO on AS classic. Resolution An AS classic can continue to exist in a multi-version system; the maximum version an AS classic can operate at is 3.1.2. It is nowhere implied that it is not supported under a multi-version setup. The statement “EBO 2022 does not support AS classic” in the EBO 2022 Release Note is misunderstood. It simply means that one cannot install EBO 2022 on an AS Classic, the same as the previous EBO 3.2 version. Note that the AS Classic will not inherit any features introduced in later EBO releases when operating in a multi-version system.

Issue Unable to back up the Automation Server Unable to retrieve a working backup from an Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Enterprise Server Building Operation Enterprise Central Cause Corrupt configuration.db Network environment issues Power failure Resolution Database Corruption When the server backup process is initiated, the server tests the integrity of the configuration.db.  If the database does not pass the integrity test, the backup process is terminated, and no resulting backup is produced. In this case, an older backup will need to be used.  The backup should be bench tested for integrity before restoring to the production server.   Network Environment In some cases, the AS may produce a valid backup file, but when the backup is saved off of the server the file size is unusually small.  This can happen when network issues interfere with the backup save to disk process.   In such cases, Automation Server backups taken from the Enterprise server will usually be damaged as well.    You can work around this problem by connecting a Workstation laptop PC directly to the AS with an ethernet cable, thus eliminating the network from the process. Backups can also be retrieved in this way using most versions of Device Administrator.    Power Failure The power fails while the EcoStruxure BMS server is backing up and the system displays a “Failed backup” message in the Event view. The solution is to initiate a new backup when the power resumes and the EcoStruxure BMS server goes back online. Power Failure Occurs During Backup     

Issue Backup and Restore Process for WebReports Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Server 2008 R2 Cause Need detailed backup process Resolution Refer to Online Help Topic for details Backing Up the WebReports Database  On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect.   Note: When using a remote computer to connect to the Report Server SQL database, the Windows Accounts must exist on both machines and have administrative rights for the SQL database otherwise a successful backup will not occur.  In this instance, it is recommended to use the SysAdmin 'sa' login / password details when connecting in remotely.   Expand the Databases folder. Right-click StruxureWareReportsDB, point to Tasks, then click Back Up. Under Destination, click Add. Click OK. In the Destination on disk box, select the backup destination. Click OK. Click OK.   Restoring the WebReports Database Ensure the Enterprise Server is up and running with the correct database.  Stop the SQL Server Reporting Services and WebReports Agent (if installed).  Note: If moving the WebReports Database it is recommended to restore the database then Install WebReports.  Then when Installing WebReports select Upgrade existing (as shown) and NOT New database  Restore the WebReports database to recover reports data from backup.  This will include any Dashboard reports saved. On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect. Expand the Databases folder. Right-click StruxureWareReportsDB and select Tasks, then select Restore, then select Database. In the Restore Database dialog box, select the database set(s) that you want to restore. Click OK. Click OK. If not already installed now complete the installation of WebReports 

Issue Can the DC1100 / DC1400 serve more than 2 boilers Environment DC1100 DC1400 Cause Can the DC1100 / DC1400 serve more than 2 boilers? Resolution The DC1100 or DC1400 is primarily designed for a 1 or 2 boiler installation. However in the case of 3 boilers. Note, 2 additional relays are required: Wire Boiler 1 to Boiler 1 terminals. Wire Boiler 2 to Boiler 2 terminals. Wire the coil of the 1st 230Vac relay to Boiler 1 terminals. Wire the coil of the 2nd 230Vac relay to Boiler 2 terminals. Either wire the relay contacts in parallel or in series, the feed for each contact will be wired from the Boiler 1 and Boiler 2 terminals respectively on the controller, the output of the relay contacts will be wired to Boiler 3. This is a workaround and does have its disadvantages: Boiler 3, when wired in parallel will always be a Lead Boiler and will do more work or when wired in series it will always be a Lag Boiler and will do the least work. In the case of 4 boilers: Wire the boilers in pairs to each boiler output on the controller. Note, the boilers will lead or lag in pairs. In the case of 5 boilers: Adapt both the solutions above.

Issue SE7300 series BACnet controller does not come online in StruxureWare Building Operation if the communications address is greater then 127. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment StruxureWare Building Operation BACnet Cause The communications Address of SE7300 series BACnet controller can be set between 0 to 254. In StruxureWare Building Operation the highest address can be set only up to 127. Resolution Set the communication address less than or equal to 127 for SE7300 series BACnet controllers. Please refer to the Default Device ID / Device Instance of SE7000 series BACnet controllers to know the default Device ID / Device Instance of SE7000 series BACnet controllers.

Issue Unable to connect to the ENC using its IP address. The ENC Ethernet port LED's appear to indicate normal operation. Product Line TAC IA Series Environment I/A Series Enterprise Network Controller Cause The ENC DHCP function was enabled by mistake on a system that does not have a DHCP server. The ENC when booted up will try to get an IP address from a DHCP server which does not exist and the ENC may not have a valid IP address. Resolution Connect to the ENC via its serial shell and perform the following procedure. Refer to Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal for details on connecting to the ENC serial shell. 1. Connect to the ENC serial shell using Windows HyperTerminal. Allow the ENC to boot up completely and you should see output messages similar to the following.   JACE 4/5 IPL Version 6.40 ECC to stop Autobooting on-board nand james startup version 6.41 launching devc waiting for /dev/ser1 creating symlink for /dev/serconsole Welcome to QNX Neutrino 6.4 on the ppc824x(james) starting /ffs0 filesystem ETFS_FS_2048 fs-etfs-jace2048: Truncating fid 0x2f from 337920 to 316718 bytes fs-etfs-jace2048: Truncating fid 0x64 from 5488640 to 13 bytes fs-etfs-jace2048: Truncating fid 0x1ce from 4096 to 0 bytes i2c: Using 100Mhz freq divider Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:20:96:08:ee:06 media: Ethernet none status: no carrier inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- bad battery detected, A/C power test will not function MESSAGE [12:38:25 19-Jun-2013] [tid=1] niagarad: starting, baja_home=/niagara MESSAGE [12:38:25 19-Jun-2013] [tid=1] webserver: web server started [tid = 4] MESSAGE [12:38:25 19-Jun-2013] [tid=1] app registry: station registry starting MESSAGE [12:38:25 19-Jun-2013] [tid=7] engine watchdog: station TEST0817_TIM watchdog thread started [tid = 8] MESSAGE [12:38:25 19-Jun-2013] [tid=7] station: station TEST0817_TIM starting login: tac Password: [2J [H J404 System Shell ------------------------------------------------------------------------- hostid: Qnx-J404-0000-15C8-14F9 serial number: 584966 build version: 2.5.25 build date: built on 2011-04-04 16:47:24 system time: Wed Jun 19 12:38:43 STD 2013 niagara daemon port: 3011 en0: inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- 1. Update System Time 2. Update Network Settings 3. Ping Host 4. Enable/Disable Ftp 5. Enable/Disable Telnet 6. Update Platform Account 7. Reboot L. Logout   2. Select option 2 for update the network settings. 3. Press 'enter' (enter leaves the field at the original setting) for each field until the 'IP address (clear to use DHCP)' field. 4. Type in the required IP address here and press enter. This will disable the ENC DHCP function. 5. Key in the subnet mask at the next line and select 'n' when prompted to use IPv6. 6. Press enter until you are prompted to save the changes.      [2J [HJACE Network Configuration Utility Enter new value, '.' to clear the field or '' to keep existing value Hostname : Domain <> : Primary DNS Server <> : Secondary DNS Server <> : Route <192.168.10.1> : Primary IPv6 DNS Server <> : Secondary IPv6 DNS Server <> : IPv6 Route <> : NET1 Ethernet interface IP address (clear to use DHCP) <> : 192.168.1.141 Subnet mask <> : 255.255.255.0 Enable IPv6 addressing on this adapter? (Y/n) : n Confirm new configuration Hostname : localhost Domain : Default Gateway : 192.168.10.1 Primary DNS : Secondary DNS : Default IPv6 Gateway : Primary IPv6 DNS : Secondary IPv6 DNS : NET1 settings: IP Address : 192.168.1.141 Subnet Mask : 255.255.255.0 IPv6 Addressing disabled Save these settings? (Y/n) : y    7. Reboot the ENC and connect to the ENC using Workbench.