Issue On a new JACE-8000, or on one in which the clean-dist or factory restore procedure has been applied, the JACE can be pinged but, you cannot connect to the platform, and the system time's year shows as 2020 or greater.   The following symptomatic messages can be observed in the serial shell via the debug port:  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  sysmon: niagarad is no longer running  The following symptomatic messages appear in the system logs:  Jan 01 01:26:53 2 11111 0 niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  Jan 01 01:26:53 2 11111 0 niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  Jan 01 01:26:53 2 11111 4 sysmon: niagarad no longer running Product Line TAC IA Series. Environment I/A Series Jace-8000 Cause This issue is encountered when the RTC clock's date is Wednesday, December 30, 2020, or later.  Resolution Use the debug port to connect to the system shell with PuTTY. See the System Shell section of the JACE-8000 Install and Startup Guide Set the system clock to a date before the year 2020, and then commission the JACE with 4.2 or newer.  The issue is corrected within the fix for the following issue, addressed in Niagara 4.2.36.10:   NCCB-19628: Code signing timestamps checked improperly, verification will fail Jan 1, 2021    We will continue to see the issue on new JACE-8000 as they ship with a 4.1 daemon. This may also occur on a JACE-8000 on which the clean-dist or factory restore procedure has been applied.

Issue What should be considered when prepairing for upgrading to Niagara 4.10? What known issues should I be aware of when upgrading to Niagara 4.10 and how can I prepair for them? Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 Cause Define potential issues with an N4.10 upgrade Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.10. Please review prior to upgrading to Niagara 4.10. Niagara 4.10 and Default NRE Memory Changes: The increased size of some core libraries in Niagara 4.10 required changes to the default NRE Memory Pool settings for use on a JACE-8000. MetaSpace memory needed to be increased to allow applications to run without issue.   Note: any previous custom memory configuration applied to the JACE-8000 will be reset upon upgrade to 4.10. Prior to upgrading your JACE-8000, please review Default NRE Memory Pool Configuration Changes In 4.10.     Niagara 4.10 System DB Upgrade: In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10.   Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index is complete accordingly. Prior to upgrading your Supervisor, please review System DB Must Be Re-indexed for Upgrades to Niagara 4.10+ from Earlier Niagara.     Niagara 4.10 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.10, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised or derived from untrustworthy sources.   Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules.   Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.10, unsigned modules will not execute.   For more information, please review the Niagara documentation on Third Party Module Signing   Niagara 4.10 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide.   Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.10.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10)   As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward.   Using Web Launcher with Niagara 4.10 Web Launcher 20.4.2 was recently revamped for Niagara 4.10 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 275 and certificate management has been updated to work with Niagara 4.10 along with any legacy or prospective release.   Prior to using Web Launcher with Niagara 4.10, the customer should update Web Launcher accordingly (see steps below). Updating WebLauncher Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page.   Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version.

Issue The following error occurs on startup following upgrading of Niagara Station to  4.10.   SEVERE [20:42:01 23-Oct-20 UTC][nreconfig] invalid nre memory configuration values, 832 > 816   Product Line TAC IA Series Environment I/A Jace 8000 N4.10 Cause The default NRE memory pool settings are incorrect after an N4.10 upgrade and need configuration to function correctly. Resolution Niagara 4.10 and Default NRE Memory Pool Changes The increased size of some core libraries in Niagara 4.10 required changes to the default NRE Memory Pool settings for use on a JACE-8000. MetaSpace memory needed to be increased to allow applications to run without issue.   Note: Any previous custom memory configuration applied to the JACE-8000 will be reset upon upgrade to 4.10. The overall size of the pool of memory available to the NRE installation has decreased.  T As the overall size of the pool has decreased, customizations based on the old total pool size are invalid and cannot be maintained.   If a custom memory configuration is required, the user will need to manually adjust the platform administration menu after a device is upgraded. A longer-term approach to address this issue is in development and should be available with the Niagara 4.11 release.   NRE Memory pool default settings for Niagara 4.9: Changes to the default configuration: Heap Space size 4.9 value: 384 MB 4.10 value: 360 MB Meta Space size 4.9 value: 48 MB 4.10 value: 56 MB System reserve 4.10: allocated additional 16MB NRE Memory pool default settings for Niagara 4.10:

Issue There is a problem after upgrading the SystemDB to N4.10. Product Line TAC IA Series Environment I/A Jace 8000 N4.10 I/A Enterprise Server N4.10 Cause In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10. Resolution In Niagara 4.10, the SystemDB has been upgraded from Orient v2 to v3.  Because of this change, customers that are utilizing SystemDB on their Supervisor stations will need to re-index upon upgrade to 4.10.  Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index upgrade is complete.   After upgrading to 4.10, invoke the actions that force system indexing.  Be aware that re-indexing can take some time, and that the DB won’t have accurate information when queried until the index is complete.   The following image shows how to invoke execute on the Local System Indexer:                                     If the Station has a DB configured to contain information about points on other stations, the Niagara Network System Indexer should be used, rather than the Local System Indexer.  Additional details regarding indexer actions can be found in the Niagara System Database and System Indexing Guide.

Issue Upon presenting valid credentials at the door and physically entering thru it, the event reported for the transaction is "Valid Access No Entry" instead of the normal Valid Access event. The door is properly configured with a door switch but the controller does not see the door switch open. Product Line Andover Continuum Environment Continuum CX Gen 1 Continuum Net Controller II Cause For unknown reasons the door's entry and exit IOU are set to the same value, typically the GUI will not allow such invalid configuration. Resolution Edit the door and set the Exit IOU to zero (for a single-sided door) or to the appropriate IOU number associated with the AC1/AC1Plus on the exit side of the door. 

Issue How to create a proper XLSX/Excel template under Alarm Triggered Notification of EcoStruxure Building Workstation, in order to receive the Multi trend logs report in the XLSX/Excel format. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation Cause Additional information is needed to create a template for presenting multi-trend log information in Excel XLSX format.    Resolution Below screenshot shows where users can select the Report format and XLSX template.   The multi trend log containing four Interval Trend Logs 1 to 4 with their time stamp is shown as below as an example   In order to get the XLSX multi trend log report in XLSX/Excel format upon receiving a trigger, the following XLSX template needs to be used containing two rows: The first header row contains the column headers from the trend log. The second row include the <Multi Log List> command   Here is final report  in Excel/XLSX format:  

Issue Notification Report Template creates blank data if External Log Storage is enabled Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Notification Report Template External Log Storage PostgreSLQ TimeScale Cause The default timeout for a Notification Report Template is 5s. If External Log Storage is enabled and logs are being added to the report, the timeout may need to be increased. Resolution The screenshot below shows a Notification Report Template where the default timeout of 5s caused an empty Report to be created (both an email and csv file were seen to be empty). Increasing the timeout to 20s resolves the issue.    

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 Security Expert Data Sync Service is randomly crashing and there is an error 'Failed to GetTableSchema' in the DSS Log Product Line Security Expert   Environment   Security Expert Application Server Security Expert Data Sync Service Microsoft Windows IIS Cause Memory may be consumed by IIS over time and crashes data sync service once the total memory approaches Microsoft's 4 GB limitation for 32-bit applications. Resolution There are a few items that can be configured in Data Sync Service (DSS) and in IIS to manage memory consumption which will prevent application crashes and DSS from not importing .csv contents   1. Remove additional table references in the Settings.xml configuration file in the C:\Program Files (x86)\Schneider  Electric\Data Sync Service. Making this change will stop Security Expert application event view errors from posting. Here is what is seen in the SX application event view. Each event will represent a different table.  Ex. Salto Calendars    a. Make a backup copy of the settings.xml file  b. Copy the settings.xml to a temp folder  c. Edit the settings.xml in the temp folder using Notepad++ Admin mode and remove all unnecessary rows just below the <DataMapping> section. <RecordType238... <RecordType225...   The example below removes all entries except *Users  Before:    After:    d. Save the file  e. Copy the settings.xml from the temp folder into the C:\Program Files (x86)\Schneider Electric\Data Sync Service  folder and select the Replace option (This ensures the older settings.xml file is overwritten)  f. Close the DSS application and restart it.   When the new settings.xml file is being used only *Users will have an asterisk in DSS.   Also, as a result of this change, the errors in the SX application log will stop posting and no longer consume "extra" resources.   2. Increase the IIS Worker Processes from 1 to 4  a. Open IIS Manager   b. Select Application Pools  c. Select DefaultAppPool  d. Select Advanced Settings  e. Change the Worker Process from 1(default) to 2, 3 or 4 (In at least one case, R&D recommended setting this to 4 in order to spread the processes and memory out) f. Select Recycle in the right-hand pane   3. Recycling Condition Workers IIS by default sets application pool(s) to recycle after an interval of 29 hours (1740 minutes). This can cause issues when using in-memory sessions.   Example: DSS application crashing about every 28 hours. Memory was being accumulated over such a long period without being recycled. Recycling every 8 hours reduces the time the memory accumulates. This setting is like a  Windows reboot, but specific to an application pool.    a. Open IIS  b. Go to Application Pools, select DefaultAppPool. In the right-hand pane select Recycling.  c. Change Regular time intervals (in minutes) from 1740(29 hours) to 480 (8 hours)  d. Click Next, Finish  e. Select Recycle   Summary: Making these changes will reduce the memory consumption that increases over time for the Data Sync Service application and prevent crashing of the application.

Issue PCT error hardware virtualization is not enabled. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool Windows 10 Cause Windows Hyper-V is enabled Resolution Firstly, in BIOS check and confirm the computer’s Hardware Virtualization is enabled.   Next, within Windows, open Control Panel\All Control Panel Items\Programs and Features, in the left pane select “Turn Windows features on or off” Check to see if Hyper-V is enabled: If it is, uncheck the checkbox next to Hyper-V. This change will require the computer to be restarted for the change to take effect.   If the issue persists, the following article may provide the answer Knowledge Base article - PCT Intel Processor Virtualization.

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 PCT client can't start properly with "Hardware virtualization is not enabled" error. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) (All Versions) Cause Hardware Virtualization is Disabled or not available for PCT Resolution  Install "Intel® Processor Identification Utility" then verify the status of "Intel® Virtualization Technology" from the Utility. Using the table below, you can see if your processor supports Intel® Virtualization(provided by Intel ).   The above information can also be found at Intel® Virtualization Technology web page If Virtualization is disabled in BIOS then enable it from BIOS else identify other software utilizing the Virtualization and stop the application.    If the issue persists, the following article may provide the answer Knowledge Base article - PCT error Hardware-virtualization is not enabled-Please-enable.

Issue In the Security Expert v4.3.285.42 (current release), there is an issue assigning an OSDP Reader to an Elevator. With the reader expander port Network Type set to RS485, when configuring the Smart Reader record to use the OSDP reader, the option to assign it to an elevator is not available.   Product Line Security Expert Environment Elevator OSDP Security Expert Smartcard Reader Security Expert Server Cause The configuration steps are not obvious and a temporary workaround is required until the issue is fixed. Resolution This is a temporary workaround as the issue is fixed in a future version. Change the reader expander port network type to Third Party Generic and click save Navigate to the Smart Reader record and change the reader mode to the elevator and assign the elevator, click save Then change the reader expander port back to RS485.   *Note* The saved elevator settings on the Smart Reader’s Reader tab will not be visible but the settings you saved will be properly downloaded to the controller.

Issue Cannot find documentation on how to use the new Graphic components release with EBO 2.0 Getting the following errors when previewing my graphic page: "Script error in function "onLoad" .... ReferenceError: "_firstRun" is not defined "Script error in function "onChange" ... ReferenceError: "_setVisuals" is not defined Product Line EcoStruxure Building Operation. Environment Building Operation Graphic Editor 2.0 and above GlobalScripts V2.0.0262 and above Cause With the release of EBO 2.0, a set of new components/snippets have been released which are different to those issued in earlier releases, although visually there is very little change. The scripting, in most cases but not all, has been removed from the components themselves and put into single scripts, this means we can take advantage of the global scripts functionality. This requires the user to set the UseGlobalScripts attribute to True within the TGML graphic editor, this can be on a per graphic basis and ensures that existing graphics will still function. Once turned to True, all components that have scripts, and have requirements for other global scripts to function correctly, can function as designed. For example, the setpoint box requires global scripts to ensure units and decimal places are displayed as designed/required due to the scripts. There are also two binds available on the box, one for reading, one for write. Both need to be bound to enable the component to function correctly.  The components are designed in this way to allow use in BACnet where it may require to read the resultant Value but Write at a specific Priority. Without the scripts added to the graphic, the component cannot function. For further details/questions refer to the following Community Posts which also includes the current PDF documentation: Help-with-an-EBO-2-0-component EcoStruxure-Building-Operation/Graphic-Component-Library-Rev-AB1-002-pdf This article provides the necessary steps required to enable and get these new components working and does not provide in-depth functionality. With the release of EBO 2.0, a set of new components/snippets have been released in the latest build which are different to those previously issued although visually there should be very little change for your customer. In summary, the scripting, in most cases but not all, has been removed from the components themselves and put into single scripts which then means we can take advantage of the global scripts functionality. This requires the user to set the UseGlobalScripts attribute to True within the TGML graphic editor, this can be a per graphic basis and ensures existing graphics still function. Once turned to True, all components that have scripts, and have requirements for other global scripts to function correctly, can indeed function as designed. For example, the setpoint box requires global scripts to ensure units and decimal places displayed as designed/required due to the scripts. There are also 2 binds available on the box, one for reading, one for write. Both need to be bound to enable the component to function correctly. The components are designed in this way to ensure use in BACnet where we may require to read the resultant Value but Write at a specific Priority. Without the scripts added to the graphic, the component cannot function. For further details/questions refer to the following Community Posts which also includes the current PDF documentation: • https://exchangecommunity.schneider-electric.com/t5/EcoStruxure-Building-Operation/Help-with-an-EBO-2-0-component/m-p/107342 • https://exchangecommunity.schneider-electric.com/t5/EcoStruxure-Building-Operation/Graphic-Component-Library-Rev-AB1-002-pdf/td-p/149876 This article provides the necessary steps required to enable and get these new components working and does not provide in-depth functionality. Resolution Within Graphics Editor enable UseGlobalScripts. To do this: Select the -Tgml object shown in the Objects pane In the Properties pane Change the UseGlobalScripts from False to True In the Global Graphic Snippets: Drag the GlobalScripts V2.0.xxxx onto the -Tgml object.  GlobalScripts then appends as shown below. Note: This must be done before doing adding any components and ONLY once on each Graphic page. Add Component by dragging it into the Design window Example showing the Component: Analogue Single Line Text, 100W Add Snippets to allow the relevant Bindings to be added to this component.  To do this: Select Snippets tab, Select Select Global Bind Snippets Drag the appropriate snippet onto the Component. EcoStruxure Analog Value bind snippet is added to the Analogue Value component Save the graphic Preview - no errors should appear.  If there are errors: Ensure that the scripts/components have been added in the correct order Ensure the correct Snippet has been added to the correct Component.  Refer to the Graphic-Component-Library-Rev-AB1-002-pdf documentation for the tested snippets/component combinations. Open WorkStation and Edit Bindings on the saved graphic page Note: The default binding name displayed View the graphic page   Example: Showing forced value      

Issue How to control an output with one or more inputs. Product Line EcoStruxure Security Expert Environment Security Expert Cause Unsure how to program one or more inputs to directly control an output. Input Control Output Resolution The below guide details how to use an Input to activate an Output on Security Expert and SP-C-WEB systems. An output can be assigned to the Input Type and to the Input allowing many to one and one to many configurations.   In order for an Input to activate an Output it needs two things: To be inside an always armed area - This can be an Automation/Dummy area with its only purpose being to activate the output. To have an Input Type that tells it to activate an Output   Single/Multiple Input Activating the same Output If one or more inputs are required to activate the same output, this output can be defined by the input type. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Set the Control Output to the required output Under Options 2 enable the required control options for your scenario e.g. to have the output follow the input exactly enable "Activate Control Output on Alarm" and "Deactivate Control Output on Restore". To have the output activate for a time simply enable "Activate Control Output on Alarm" and set the "Activation Time" under the General tab of the Input Type Menu (Control Output Time) Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following: Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Check for any related health status messages that need to be resolved Arm both portions of the Area Activate the Input to confirm Output Activates   Multiple Inputs Activating Different Outputs When multiple inputs are required to activate different outputs, one input type can be used and the outputs can be defined at each input. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Under 'Options 3' enable the required control options for your scenario. e.g. to have the output follow the input exactly enable Activate Input Control Output on Alarm and Deactivate Input Control Output on Restore. To have the output activate for a time simply enable Activate Input Control Output on Alarm and set the Activation Time at the Output itself Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following Set the Control Output to the appropriate Output Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Arm both portions of the Area Activate the Input to confirm Output Activates

Issue What is "Verbose" within Vista Server Setup? Documentation refers to "certain dialogs and messages." What are these certain dialogs? Product Line TAC Vista Environment TAC Vista Server Setup TAC Vista Workstation Cause The documentation states that this setting: "Enables or disables the display of certain dialogs and messages for operator communication."  Resolution Verbose turns on questions that ask if you really want to do something. An example, "Do you really want to quit?" when closing Vista 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 for assistance. Issue Both the STAT LED and the BEAT LED is off on the Jace controller and cannot successfully ping the JACE 8000 IP address Product Line TAC IA Series Environment I/A Series JACE 8000 Cause The STAT and BEAT LED remaining in an off state is an indication that no SD card is installed in the JACE card carrier.  When the Micro SD card is installed the STAT LED is solid Green, and BEAT LED is blinking Amber. Resolution Make sure to insert the SD card prior to startup commissioning of the JACE 8000. See JACE-8000 Install and Startup Guide

Issue Display options now the DCX250 is no longer available Product Line Andover Continuum Environment Continuum DCX250 Touch Screen Display part number 01-0008-300 Cause The DCX250 is not available from January 2012: Discontinuation of Infinity 01-0008-300 (DCX 250) - PA-00184 Resolution There is no direct replacement for the DCX250 and there is no other display that works directly on Infinet.   The Continuum display options are- Netcontroller IO Bus - Infistat or LD-1 Direct connection to some controllers - Smart sensor or xP-Display A Continuum Cyberstation could be used if more information and input is required. Another option would be a Bacnet or Lon display. Or, the L-VIS from Loytec using bacnet MSTP may be such an option (LonWorks and BACnet Touch Panels Release - PA-00106). http://www.loytec.com/products/lvis (LON via NC2-F- port16 would also be an option, see Can LONMark Devices be used with Continuum?) NOTE - All support for this product is via Loytec. The EMX170 was a small display and keyboard available for some older Infinity Controllers (i1) This unit is obsolete, although it may be possible to repair one. There is no replacement for this unit. If the i1 controller is being replaced with an i2 unit then either a smart sensor or an xP Display plus room sensor could be used

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.

Issue What are VOCs and which ones are detected by our SLA/SLP sensor? Product Line Field devices Environment SpaceLogic SLA series and SpaceLogic SLP Series VOC Sensors Cause Unsure what substances are detected by the Space Logic SLA/SLP VOC sensors Resolution What are VOCs? Volatile organic compounds (VOCs*) are a wide range of carbon based (organic) chemicals (compounds) found in various man-made and naturally occurring solids and liquids. They evaporate easily at ordinary room temperature** which is why they are termed volatile. VOCs are numerous, varied, and ubiquitous. They include both human-made and naturally occurring chemical compounds. Most scents or odors are of VOCs. Some VOCs are dangerous to human health or cause harm to the environment. Respiratory, allergic, or immune effects in infants or children are associated with man-made VOCs and other indoor or outdoor air pollutants. Government regulations have prompted several companies in the paint and adhesive industries to adapt with VOC level reductions in their products. * VOCs play an important role in communication between plants, and messages from plants to animals. ** For example, formaldehyde, which evaporates from paint and releases from materials like resin, has a boiling point of only –19 °C (–2 °F). Typical Indoor VOC Sources There are over 600 VOCs that can be found in the air. The following are commonly encountered in buildings: Anthropogenic*** VOCs are regulated by law, especially indoors, where concentrations are the highest. Harmful VOCs typically are not acutely toxic (result in throat irritation and headaches) but can have serious compounding long-term health effects(damage to internal organs). Because the concentrations are usually low and the symptoms slow to develop, research into VOCs and their effects is difficult. *** Relating or resulting from the influence of human beings on nature   How Are VOCs Measured? VOC sensors normally present their measurement in Total Volatile Organic Compounds (TVOC) which corresponds to the sum of volatile organic compounds. VOC contamination is an established concept in regulatory and scientific literature. It is a practical method (time and cost-effective) of surveying indoor environments for contamination. The specific TVOC composition varies between different ambient indoor environments and indoor air is always composed of different volatile organic substances. Therefore, it is helpful to consider TVOC concentrations as statistical reference values which help to indicate indoor air quality.   The World Health Organization (WHO) guidelines for TVOC are shown below and these are in line with the AQI table published in our specification sheets. Indoor Air Quality Level Guidelines for Europe by the World Health Organization (WHO)   The sensing principle of the VOC sensor is based on a heated film of metal-oxide nano-particles. In clean air, donor electrons in tin dioxide are attracted toward oxygen which is adsorbed on the surface of the sensing material, preventing electric current flow. In the presence of reducing gases, the surface density of adsorbed oxygen decreases as it reacts with the reducing gases. Electrons are then released into the tin dioxide, allowing current to flow freely through the sensor. VOC sensors are normally calibrated while using only one VOC (Ethanol).   Summary There are over 600 identified VOCs that may be present in indoor air and the sensing element used by VOC sensors reacts to any of these compounds. Therefore it's not possible to state what VOC is responsible for a raised reading.

Issue Need to delay an Input from going into alarm before sending that alarm to an email recipient. Product Line Security Expert Environment Security Expert Cause Have a requirement to email alarms for Door inputs that are not actually tied to Door records. Resolution One method of configuring this is to use an Area: Add the Input to the Area to trigger an alarm Configure that alarm event into an Email using an Action.  See the following detailed steps:  Under Programming: Inputs Configure the Alarm Input Speed option for the Input. This will be the delay time before the input triggers an alarm event. Set this to how long the door needs to be open before the alarm is generated. Under Events Create an Event Filter and add Area <Area_Name> Alarm Activated Create an Alarm and add the Event Filter to it. Create an Action. Configure the Type as Send E-mail Configure the Event Filter to that created previously. Set the Email Settings as required. Under Programming Create an Area On the Configuration tab set all timings to 0. Within the Input On the Areas and Input Types tab add this new Area to Area 1 field Set the Input Type 1 to Instant. In the Options enable Log to Event Buffer so the activations are reported. This setting can be reverted after testing.

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.