Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. The SSN is invalid for this installation. Product Line EcoStruxure Security Expert Environment Security Expert Cause Wrong SSN being used. The SSN being used is different to what was used when Security Expert was initially installed. Resolution Uninstall Security Expert and re-install using the correct SSN. Backup the SecurityExpert and SecurityExpertEvents databases and copy the resulting backup files somewhere safe. Manual backups can be initiated from the Global > Global Settings menu. Select the directory location and press backup now. Uninstall Security Expert from Windows Add or Remove Programs. Search for "Security Expert" to filter the results. Install Security Expert from available installation files. When asked for the license make sure to use the correct SSN.

Issue BACnet MSTP Capture Application Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP capture application provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution Download the latest version. Browse to Steve Karg's  BACnet Protocol Stack - Browse /bacnet-tools at SourceForge.net Select the version folder Select bacnet-tools-[n.n.n].zip file to download it From the zip file, extract mstpcap.exe Now you can use it via command prompt as described below or install it in C:\Program Files\Wireshark\extcap if want to use with modern Wireshark version.   To capture data follow these steps: Unzip file Open command prompt with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Bluetooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further information or instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue A Cisco Mediator BACnet/IP controller connected to a Niagara R2 UNC can read exposed BACnet objects but cannot overwrite setpoints or issue commands. Product Line TAC IA Series Environment Niagara R2 all versions Cause The Niagara R2 station requires a specific BACnet user configuration to allow external BACnet devices to write values or send commands. Without this user, write requests are rejected. Resolution Create a special BACnet user in the Niagara R2 station: Open the Niagara R2 station configuration. Navigate to Security → Users. Add a new user with the following properties: User Type: BACnet Assign appropriate permissions for writing to exposed objects. Save and restart the station if required. Refer to Tridium BACnet Integration Guide, pages 4-6 and 4-7, for detailed steps.

Issue LON networks may experience communication issues due to excessive physical length or a high number of connected devices. The Xenta Repeater helps mitigate these issues by restoring and conditioning signals, enabling longer network spans and supporting more devices. Product Line TAC Vista Environment Vista Lon Networks Xenta Repeaters (Part # 007309120) Cause LON communication failures often stem from: Exceeding recommended cable lengths Overloading the network with too many devices Resolution The Xenta Repeater: Uses a standard Xenta 400 base Splits a LON channel into two segments Connects one segment to COM 1 terminals, and the other to COM 2 terminals 🔍 Note: A LON channel is a section of the network separated by a router. A segment is a portion of a channel divided using a repeater. 📏 Cable Length Guidelines Cable Type Max Bus Length (Doubly Terminated) Max Node-to-Node (Singly Terminated) Max Segment Length (Singly Terminated) Belden 85102 2,700 m / 8,858 ft 500 m / 1,640 ft 500 m / 1,640 ft Belden 8471 2,700 m / 8,858 ft 400 m / 1,312 ft 500 m / 1,640 ft UL Level IV 22AWG 1,400 m / 4,593 ft 400 m / 1,312 ft 500 m / 1,640 ft Siemens J-Y(st)Y 900 m / 2,953 ft 320 m / 1,050 ft 500 m / 1,640 ft TIA568A Cat.5 900 m / 2,953 ft 250 m / 820 ft 450 m / 1,476 ft 📌 Design Rules Max 128 devices per LON channel Max 64 devices per segment Up to 2 repeaters per channel (max 3 segments) If no router is used, only 64 devices allowed (single segment) Recommended: ≤ 50 devices per segment for flexibility during installation 🔄 How It Works The Xenta Repeater contains: Two internally connected LON transceivers Transient suppression circuits It: Reads LON packets from one segment Re-broadcasts them to the next segment Filters out noise, ensuring clean signal transmission Unlike simple amplifiers, it does not amplify noise, resulting in strong, noise-free communication across segments.

Issue The following error can occur when logging into Security Expert using a Remote Client:   Could not log on to Server. Please check your remote connection setup. The server has rejected the client credentials. Product Line EcoStruxure Security Expert Environment Security Expert Server / Client Cause The security policy settings are different between the Server and Client.   When installing the Security Expert Server and Clients, the default security policy is used. This requires that the Windows username and password that the operator has used to log in on a client machine is also a valid user on the computer that is running the Security Expert Server. These security requirements are very favourable for corporate networks and setups where the users and policies are easy to manipulate. For that purpose alone, the Security Expert Server and Client are installed with these settings by default.   All installations are not created equal however and sometimes the Security Expert Server is not located within a domain. In another scenario, the server may be in a domain but the operators need to connect to it from a machine that is not in the domain. In these cases, it has been requested that the security policy in place on a domain or the physical machine is disabled and although this is not recommended practice the security of the system can be maintained using a suitable VPN structure.   This solution should be used with full knowledge that the security of the system will rely on the operator user login name and password as well as the security measures put in place for a client to be able to hit the server with a login request. Protection of the infrastructure to the connection is beyond the scope of this document. Resolution The easiest solution would be to put the Client machine(s) in the same Domain as the Server.  However if this is not possible or if no Domain is used then you can still manually update the security policy instead. The following process is a manual edit of the XML configuration files  SecurityExpert.exe.config  SecurityExpertSV.exe.config  Both of these files are located in the .\Program Files\Schneider Electric\Security Expert directory on the Client and Server. It is recommended then to backup these two files prior to performing this task. Close all Security Expert clients and stop the Security Expert Data Service. We are first going to update the Security Expert Client configuration file SecurityExpert.exe.config on the client machine.  If using more than one Client, the change must be done for ALL clients Open Notepad as the administrator, browse to the specified location making sure the 'all files option' is selected.  Then open SecurityExpert.exe.config (Be aware that it may not have the file extension showing and will be called an XML Configuration file by default) Locate the netTcpBinding tag . Nested within this tag is the binding tag Ensure that you insert the below text after the opening binding tag and before the closing \binding tag . If you insert the text outside this tag, the application will fail to run.   "<security mode ="None"></security>" IMPORTANT You must ensure you enter "None" with a capital "N" (not lower case). Ensure you copy input text exactly as shown. Now save the file. If you get a write error then you need to open notepad as the administrator. Repeat the process for the Security Expert Server configuration file SecurityExpertSV.exe.config which is located in the same directory on the server machine.      Again, make sure the line is inserted after the opening tag and before the closing tag or the application will fail to run when you save the changes. Restart the Security Expert Data Service and test the connection settings.

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.

Issue After upgrading the Continuum workstation software, cannot edit workstation programs Environment Continuum Cyberstation Workstation programs Plain English Cause Not able to edit workstation programs. Firing order is edit locked. Resolution To resolve open up the Continuum Commandline program and type in "Firingorder editlock=false" This will unlock the firing order and programs will be able to be edited. In the simple case of editlock where a program may have been editlocked which is different than firing order editlocked. Simply select the program in question and press Ctrl+U or access the properties of the program by right click and select the CurrentStatus tab and press the "Force Object to unlock" button.

Issue Can not see bCX4040 in BACnet view following Find New BACnet Devices from the root. CyberStation and controller are located on the same subnet, no BBMD configuration is required. Environment CyberStation bCX4040 b4920 Cause Subnet mask mismatch between PC and bCX Subnet mask not property configured in controller or the PC Resolution Login to controller's configuration web page and set the subnet mask to the appropriate value for the network. Submit the changes and re-start the controller. If the mismatch is on the PC side, fix it in the network properties in windows control panel.

Issue Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 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 Services for assistance. Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

Issue WorkPlace Tech application was created with constant tags for writing test values to the application.  After uploading a previously downloaded application that contains constant tags with a [NA] value, none of those constant tags are drawn on the regenerated application drawing. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool version 4.x (any release) I/A Series WorkPlace Tech Tool version 5.x.x (any release) Cause The default input value for any unused control object input is a value of [NA].  Since all unused inputs have the implied [NA] constant, they are not drawn on a regenerated WorkPlace Tech application drawing. Resolution This action is by design.  By design, a constant tag can be added to any previously unused control object input and a value written to the controller via that constant tag using the Write to Ram function.  When adding constant tags to inputs, it is not necessary to recompile and download the application unless you desire that the new "Non-NA" value be saved in the application hex file.  With this in mind, remember that constant values are written to an installed application using the "Write to Ram" function will be lost when the controller is rebooted.

Issue Replacement I/NET Controller NICAD Battery info., I/Net Batteries Product Line TAC INET Environment All I/NET controllers Cause Controller battery has failed, because the battery on the controller is over 5 years old   Resolution The 3 pin version Battery is used for the NPR2000 and the DPU48K (MIP Board) -- part number 3/V80H-SLF (Note this battery has to be order from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The 7910, 7920, 7930 7780 & 7940 use the 2 pin version -- part number 3/V80H-LPC (Note this battery has to be ordered from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The battery used on the 7700, 7716, 7718, 7728, 7720, 7928, 7793, 7798B, & 7798C (and like controllers) is the Dallas/INET part number 801288-07. This also can be ordered from the Rockford order entry using 01-2100-545 (Old CSI P/N 801288-07). This battery also has an outside Vendor source from Power-Sonic P/N - PCBM-3.6 Click here to view a PDF on this part. For battery testing process see How to test the NiCAD Battery on a Controller

Issue Is there is an application that will display the duress (panic) button alarm to the operator, when pushed, along with sound. Product Line TAC I/NET Environment I/NET Seven Automatic Page Display, Event Definitions & Sequences, User Defined Button  Cause Sample application / guide to program duress alarms in I/NET. Resolution I/NET provides various functions that allow it to provide a pop-up duress alarm, one feature is to use one (or many) graphic page(s) which automatically appear (pop-up) on activation of an alarm. Along with this, it is also possible to generate a sound either PC based or, the more preferred option, to an externally wired Buzzer / Siren at the same time.  The attached document shows a few steps as a guide to make a start on your own application using the following features: Automatic Page Display AMT Audible Alarm Event Definition / Sequences User-Defined Tools and Buttons If you are not familiar with these items you should refer to the TCON documents mentioned in the attachment.

Issue What does it mean on an MNL-800 if both the top green LED (Transmit) and the Amber LED (Receive) are on continuously? Product Line TAC IA Series Environment MNL-50 MNL-100 MNL-200 MNL-800 MNL-V1R MNL-V2R MNL-V3R Cause LEDs indicate LON traffic on the trunk Resolution For an explanation of the Transmit (Green LED) and Receive (Red LED) see F-26724, MNL-800 Installation Instructions, Table 1 LED Indications: LED Operation Status Green ON Normally ON indicating controller is powered and not actively transmitting data on the LON. Flashes OFF Flashes OFF while actively transmitting data on the LON. Amber OFF Normally OFF unless actively receiving data from the LON. Flashes ON Flashes ON while actively receiving data from the LON. Red OFF  (Neuron - normal communications) indicates the Neuron is operating properly allowing normal communications to and from the HVAC application. OFF  (Neuron - Offline) Neuron responds to network management messages only. In this state, communication to and from the HVAC application is not possible. To correct, place the Neuron online by downloading an application using WP Tech or configure using a third party management tool. Blinking The service LED blinks at 0.5 Hz rate (1 second ON, 1 second OFF) to indicate that the Neuron is unconfigured (i.e. communications parameters not loaded). Corrective action: Configure the Neuron by downloading an application using the Work Place Technician's Tool or configure the neuron using a third party management tool. ON Indicates Neuron is not operating properly. Replace controller.  Heartbeat (Green LED) Blinking (Normal Operation) The heartbeat LED blinks at 0.5 second ON, 0.5 second OFF to indicate controller is operating properly. Wink Mode Wink mode provides a visual means for identifying the controller using WP Tech or third party management tool. During wink, the heartbeat LED blinks as follows: With revision 1.x firmware: 2 seconds ON, 0.5 seconds OFF; cycles five times for a total of 12.5 seconds of wink time. With revision 2.x (or later) firmware: 3 seconds ON, 1 second OFF; cycles three times for a total of 12 seconds wink time. Diagnostic Blink (RAM/ROM Failure) The heartbeat LED repeats a pattern of 2 quick flashes followed by pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink (ROM Failure) The heartbeat LED repeats a pattern of three quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink  (RAM Failure) The heartbeat LED repeats a pattern of four quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. OFF Indicates controller is not operating properly. Check power. Replace controller if necessary.      If the amber LED is blinking fast enough, it appears to be ON continuously, so it is receiving data at a high frequency. The other MNL devices on the same LON should all be behaving the same way, indicating a lot of LON traffic. Confirm with a LON protocol analyzer. If excessive LON communications traffic is suspected, see How can LON communications be throttled in MNL-800 controllers? for a method of throttling LON traffic.

Issue The Niagara 4 JACE's platform daemon fails to start making it impossible to login and configure using Workbench tools such as the Commissioning Wizard or Dist File Installer. The error within the serial shell typically indicates ... /proc/boot/ksh: niagarad: cannot execute - No such file or directory. Product Line TAC IA Series Environment Niagara 4 JACE-603 JACE-645 JACE-600E JACE 8000 Cause This can occur as a result of an Incorrect or failed upgrade or improper downgrade without first installing a clean distribution. Resolution Requirements - You will need the following to complete the recovery steps: A terminal emulator such as PuTTY A SFTP client such as FileZilla Serial-Shell cable for your JACE hardware model (specified in the .PDFs below) The Niagara 4 Clean Dist file for your JACE hardware A zip file utility such as 7-Zip The hardware and startup documentation for your JACE model (provided with Niagara 4 installer) Obtain recovery files from the Niagara 4 Clean Dist File for the matching hardware: The clean dist files can be found in your Niagara4 $system_home directory, or in your Niagara 4 image files under the cleanDist directory or in the overlay\cleanDist directory. Open the .dist file for your JACE's platform using a zip utility like 7-Zip and extract the zip/n4clean.tar.gz file. Also, extract the dev/shmem/n4-xxx.image file, where xxx will be different, depending on the JACE's platform type. JACE 300 ... qnx-jace-n4-npm3xx-etfs2048-clean.dist JACE 600 ... qnx-jace-n4-npm6xx-etfs2048-clean.dist JACE 600E ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 603 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 645 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 700 ... qnx-jace-n4-javelina_booke-etfs2048-clean.dist JACE 8000 ... qnx-jace-n4-titan-am335x-clean.dist Make a Serial Connection to the JACE The .PDFs in the N4 documentation set describe how to make a serial connection to a JACE in the "system shell" section(s) of each document. Once connected, the controller will boot and display the "login:" prompt.  Enter your Platform credentials. After login, either a "#" or "$" shell prompt or configuration menu similar to the following is shown.   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011     dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255         inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------     1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot     L.  Logout     Enter choice:   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011   dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255             inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------   1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot   L.  Logout   Enter choice: Verify correct system time and update as needed The RTC time may not be correct if the unit has been unpowered for longer than the on-board capacitor backup period. Using menu ... the first item in the menu list allows you to Update System Time.  The current date/time is displayed. Enter the new date/time in the form YYYYMMDDhhmm[.SS].  Note that entering the seconds is optional. For example: 201801111420 for 11-Jan-2018 at 8:20am UTC or 8:20am CST. Enable SFPT The Secure FTP service is not enabled by default on a JACE.  Enable the SFPT from the menu above or the shell prompt (if required). Using menu ... the fourth item in the menu list allows you to enable SSH/SFTP.  Enable it now, using port 22. Once enabled, enter another choice, "sh" (without quotes).  This will give you the "#" or "$" prompt that you need. If you could not enable from the menu in the step above, manually start by issuing the command tsudo syssh_sshcfg at the shell prompt.   If the command fails, issue the syssh_sshcfg command.  If the command fails again, enter the following ... $ cd /sys/bin ... then enter $ ./syssh_sshcfg ... then enter Transfer the n4clean.tar.gz and OS Image Files using SFTP Client Using an SFTP client such as FileZilla, transfer the n4clean.tar.gz file previously extracted for the platform from the clean dist file to the JACE's /zip directory. If the transfer fails with a permissions error, issue the command tsudo chmod 777 /zip at the shell prompt and try it again. Next, transfer the .image file you extracted from the clean dist file to the JACE's /dev/shmem directory. Run osupdate From the login menu prompt, type sh.  This will exit the menu system and enter the shell mode.  At the "#" or "$" shell prompt, issue the command osupdate.  After a short delay, the shell prompt will return. Reboot the JACE Finally, reboot the JACE.  This can be done by issuing the command shutdown hf 0 at the shell prompt.  When the JACE restarts, the unit will automatically process the clean dist file.

Issue After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server 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 Services for assistance. Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

Issue Need requirements for email notifications Environment Continuum Cyberstation Email Eventnotification Outlook 2007 (32bit Only) Outlook 2010 (32bit Only) Cause Requirements for sending email notifications with Continuum Resolution Here are some requirements for forwarding Continuum workstation alarm events via email and paging: The Continuum workstations that have been designated primary and backup email and/or page handlers must have a MAPI-compliant email client such as Microsoft Exchange or Outlook. The email client application must communicate with an existing email server application, such as MS Exchange Server. The primary or backup email/paging workstation must be running Continuum at the time an alarm is generated. Each EventNotification object associated with the alarms that you wish to email or page must have its own email distribution list in the personal address book of the client email application using a specified naming convention as outlined in the table below. This email distribution list must be stored in the first address book shown in the list of available address books in the email client application. For example, if you create an EventNotification distribution list in the Personal Address Book in Microsoft Outlook, then the Personal Address Book must be the first one showing in the address list dropdown box when you open the Address Book. How to Create an EventNotification Distribution List Note: The following steps are based on Microsoft Outlook(32bit). Other mail applications may have different menu names and choices but the general procedure is the same. Open the Address Book for the email account on the Continuum workstation that will be providing the email/paging services. Your toolbar may have a button for this. If not, use the Address Book option of the Tools menu. Select New Entry from the Address Book File menu. Select the entry type Personal Distribution List and put this entry in the Personal Address Book. In the Name field enter a name for the distribution list using the following format: For E-mail: ACC.name For Paging: ACC.page.name where name is the name of the EventNotification. Add members (the email addresses or pager and service numbers of those to whom the notification of the alarm will be sent) to your personal distribution lists. Set address book options so that the address book where your personal distribution lists are stored is the first one to be searched when sending emails or pages. ** Ensure that there are not 2 PCs using the same email account for Outlook.

Issue Not possible to download an application(.mta file) to a Xenta 401, Xenta 301/302, Xenta 281/282 The download process looks fine until the file transfer should start. Then it just hangs and nothing happens. Product Line TAC Vista Environment Xenta 401 Xenta 301/302 Xenta 281/282  Cause The problem is that a file transfer is already running for something else (trend logs or alarms) and only one file transfer can run at a time for each LON network. Resolution Shut all graphics pages and try again. Restart the Vista Server and try again. If that doesn't help, restart the Xenta's to stop the ongoing file transfers If that doesn't help, ensure you are running TAC Vista 5.1.9 and  Start the TAC Vista server communication log, let it run for 10 minutes and send that to your local technical support for investigation. To start the communication log: open the Log tab in the TAC Vista server, open "Comm.Log", Set the Physical layer to "Active" The log will be saved in the $Log folder in the Vista database and called PL_"network name"

Issue Troubleshooting steps for the Infinet and MSTP bus. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum SmartStruxure RS-485 Infinet BACnet MSTP Cause Methods are needed to troubleshoot the Infinet and MSTP bus Resolution This is not a comprehensive list of all methods for troubleshooting, but a starting point. The Infinit-mstp troubleshooting document is available here. NOTE If BACnet MSTP devices do not support COV subscriptions, then care must be taken when reading values (eg EBO trends or alarms) as excessive traffic can be created that overwhelms the communication bus. For example, if 30 non-COV BACnet devices have EBO alarms (or EBO change of value trends) bound to 4 objects in each controller, this will create 240 packets (reads/replies) that will be attempted every "Minimum polling Interval". This is likely to fill the MSTP bus bandwidth  

Issue Get server error in '/webClient' Application when attempting to connect with the WebClient Environment WebClient 1.93 Windows 7 Cause Bad installation Resolution 1. Run aspnet_regiis.exe -i (This is done from a DOS prompt, C:\Windows\Microsoft.net\Framework\v2.0.50727)  2. Re-install Continuum WebClient

Issue Previously purchased WorkPlace Tech software is being moved from one computer to another. What proof of purchase is required for the software so that the purchase of a new copy is not required? How can they prove that they purchased the original copy if the original purchase order and invoice or license request form with unlock code cannot be located? Product Line TAC IA Series Environment WorkPlace Tech 5.x.x NOTE: Old installation must be of same major release (release 5) as the new copy being installed. If the old system has release 4 of the WorkPlace Tech software, the new computer will need to be running Windows XP and the release 4 version of the WorkPlace Tech software will have to be installed on the new computer. Cause Software needs to be migrated to a different computer. This could be due to an upgrade in hardware. Resolution The preferred proof of purchase is a copy of the license request form that shows the customer information, license requested, license unlock code, and the original sales order number. Depending on when or how the license for the existing copy of the WorkPlace Tech Tool software was ordered, this document may have been received by fax or email. If this information is available, a copy can be emailed along with the new license request form (requesting the same product license as the original) to IASeries.license@schneider-electric.com. Note that in some cases the new product code may vary slightly from the original. For example, the original license may have been for WP-TECH-52 and the new one for WP-TECH-58 or WP-TECH-50 -- these licenses are all equivalent. The WIB licensing team will verify the submitted information and if complete/correct, generate the new license unlock code. If the old computer is still functional, the License Diagnostic program can be used to generate a proof of purchase for the software installed on the computer. Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file. NOTE: If the old computer has WorkPlace Tech release 4.0.0, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed). If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open". This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. On the new computer run the "Purchase WorkPlace Tech Software" or "Purchase WIBs Software" from the icon on the desktop and fill out the Field Office & Shipping information sections using the information for your office. The "End Customer Information" must match the information from the old system. In the Package List, the same product should be selected as was licensed on the old system. In some cases, the part number may be slightly different, for example, the old system may have been licensed for WP-TECH-53U and on the new system, the product code may be WP-TECH-50U. These license product codes are equivalent. Add the selected package part number to the order list, click the [Accept Order] button and output the order form to a file. Click the [Done] button to exit the purchase screen and click [Done] to exit the Purchase program. Email the saved license diagnostic form and the saved order form to Product Support Services for verification. Product Support Services will verify the information and if correct, forward the information to IASeries.license@schneider-electric.com for processing. They will email the unlock code back to the requesting office. Follow the normal procedures to install the unlock code.