Issue Receive "Error 1606. Could not access network location\." when installing I/NET Seven Software with StruxureWare Building Operation Environment I/NET Seven SmartStruxure Solution 1.3 Cause When uninstalling / Installing I/NET with Building Operation software already installed the Enterprise Server and InetIoSrv service must be stopped.  In some situations when not installing the for site it may be best to set both the Enterprise Server and InetIoSrv services to manual avoiding this situation. Resolution To resolve this problem.  Stop the Building Operation Enterprise Server service, either from the Software Administrator application or from the Windows Services. It is also recommended to stop or remove the InetIoSrv service prior to any update of the I/NET Seven software.

Issue When attempting to build connection to a Filemaster the error "invalid I/NET seven operator" is given Environment I/NET Filemaster Equalized client Cause When building a connection to a remote database, you must use the credentials for the remote PC not the local PC. In this example, when creating the connection to a Filemaster from a Equalized client, you must use the I/NET log in credentials for the Filemaster. Resolution Change the I/NET user name and password to one that has full permissions on the Filemaster PC.  You may need to attempt to log into the filemaster PC to verify the username and password.

Issue In Chinese OS, values under Xenta server on graphics in Webstation show offline. But in Workstation, it is fine. Environment Xenta 5/7/9 Vista Graphics Webstation Cause In Chinese OS, the characters contain space will show odd symbols. If the path of the value contains space, it will be fine in Workstation, but offline in Webstation. Resolution The solution of this issue is to avoid space in the path of the value. Use underline instead of space to separate characters. For these path that can’t avoid space(for example, the Public signal and Time schedule under Xenta server), create dummy variables to connect to them, and use these variables in graphics.

Issue What is an acceptable induced voltage on to I/Net signal terminals Environment I/net SCU Cause If you have 10V which is induced on to an input cable. And The installer ran 24Vac alongside signal wires in a multicore cable with a common screen. And  have a plan to eliminate the induced voltage by reducing the number of pairs carrying voltage and using other cables Resolution Of the input signal types, the Thermistor type is considered the most vulnerable to the pickup of stray voltage from sources in the local area. This is because the AI input is a high input impedance (as it is with all voltage measurement modes of operation), AND the signal source is also very high impedance (the 10K thermistor itself). With one side of the circuit grounded, this presents the 10K ohm impedance of the signal wire as a prime candidate for inducing AC voltage noise from and local adjacent AC voltage sources AND especially any such run in the same cable. There is no “acceptable limit” definition on such AC pickup. Acceptability is directly related to the system application and/or customer tolerance for fluctuations of temperature readings. In the room temperature range, a thermistor signal changes by only ~ 54mv for each degree C. Without filtering, this 54mv/C sensitivity would produce constant variation form small induced noise levels. We provide both hardware and software filtering on the analog signals that allows rejection of AC noise seen on the input terminal, BUT you still want to minimize the level of the noise pickup as seen on the analog inputs. In the I/NET controllers the hardware filter provides a 94/95 % reduction of the 50/60 hz AC noise level presented to the controller. The controller firmware follows with implementation of  deglitching and averaging filters that further reduce the effect of noise on the AI point value.  We also have a input filter technique specifically targeted at reducing the impact from AC line induced noise. That filter works on the principle of making the AI readings at a scan rate of 1.5 times the AC line frequency. This is the purpose of making the AC line frequency a configuration item (50 or 60 hz) in the CLAN controllers. On the SubLAN, this is scan rate is fixed at 25ms (1.5 times 60hz) which make the line frequency filter not as effective for 50hz, but still very helpful.   As the analog inputs are scanned, we capture a reading on the negative or positive cycle of the induced noise and then we average that with a reading taken from the opposing cycle of the induced AC noise as seen 25ms (or 20ms) away from the previous sample. The average of the positive and negative cycle of the induced noise creates a near complete cancelation of the induced error – for a sinusoidal wave noise signal. This technique does a great job of producing a notch filter centered on the AC line frequency and reducing/filtering the impact from such line frequency noise.   This combination of several filters allows you to see AC line induced noise on the analog input terminal, and still maintain a stable temperature reading in many cases.  Note -- If the AC noise is non-sinusoidal, due to anomalies in the noise transfer or originating from an AC source other than the sine wave AC power line, then the affectivity of the noise reduction will be reduced and signal reading impact will be larger. The 10V of induced voltage you describe is very large (huge) and far beyond anything I have seen, but then I have never seen 24VAC wired in the same cable with thermistor signals.  Separation of the 24VAC as you describe below is needed. Your described past tolerance for  5V is also above what I would expect to accept.   However, it is possible that the AC line frequency filter has been making such high noise level appear acceptable on the temperature reading display.   For possible work-around use, the high impedance of the thermistor source makes the addition of a capacitor on the AI terminal to ground very effective in reducing the applied voltage from AC noise pickup. Here a capacitor value in the range from 2 to possibly 100 micro-farads can sometimes be useful to reduce or work-around an installation wiring problem. The capacitor should be of the “Low Leakage” type.  Leakage in the capacitor would be exhibited as a small reduction in the DC voltage and associated increase in the temperature reading.  The higher the micro-farad capacitance value, the more reduction in noise you will achieve, but it is easier to obtain low leakage capacitors in the smaller capacitance values.  If polarized electrolytic capacitors are used, be sure to position the negative terminal toward ground.

Issue MR-VAV-AX output 3 set to an AO instead of a DO Environment MR-VAV-AX Cause This is correct. The output will always be labeled as an AO even thought the function of the output will be a DO Resolution If a DO is required for additional programming needs, create an internal DO point and use either a calculation or event sequence to control the new internal point.

Issue The UNC and Enterprise server, as well as many other Schneider-Electric Buildings products, use a TIME protocol server to provide clock synchronization. The address of that Time Protocol Server no longer works. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Schneider Electric Buildings products that rely on the use of TCP TIME protocol servers for time synchronization. This includes the I/A Series R2 UNC & ES and the I/A Series G3 ENC & ENS as well as other IP ethernet based products. Cause Many server sites are discontinuing support for the TCP TIME protocol because it is so bandwidth intensive. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. The site http://tf.nist.gov/tf-cgi/servers.cgi lists most of the currently available TIME protocol servers as well as the status of the entire TIME protocol system. Resolution If the product supports the use of the NTP time sync protocol, switch to the use of that protocol. If the device only supports the TIME protocol, consult the web site http://tf.nist.gov/tf-cgi/servers.cgi for currently available sites.

Issue Used the script to make an automatic backup and after the first one, it doubled on the next one. Is this what is expected from the backup? Product Line TAC INET Environment All versions of I/Net Cause What does an automatic backup really do to a database? Resolution The Automatic backup is a script that will backup the database whenever it is executed. It creates a generic database the first time but does not append it. Each time after that a backup is created and time stamped that it was executed. If it changed in size, then it would have been due to events occurring during the time that has elapsed.

Issue Unable to install the SQL Server with I/NET. Error shows: The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine "machinename" error:2147942405(0x80070005). Environment I/NET Seven Cause Some security settings have been changed under DCOM. If local launch and local activation properties are set to 'Not Defined,' the installation will fail. Resolution Open Administrative Tools > Local Security Policies Find Local Policies > Security Options > 'DCOM: Machine Launch Restriction in Security Descriptor Definition Language(SDDL)' Set the System user 'Local Launch' and 'Local Activation' to ALLOW.

Issue Cannot get changed I/NET point or controller name to update in StruxureWare Building Operation Environment SmartStruxure I/NET integration Cause There is a designed feature for integrated I/NET objects within Building Operation.  Once an object is imported into SmartStruxure, it can be re-named and given description with more options than on the I/NET controller.  For this reason, when changing a point or controller name through the I/NET interface, it will not be updated in SmartStruxure.  All name changes should be done through the Building Operation Workstation interface. Resolution If you wish the StruxureWare Building Operation names to match the changed I/NET name, you have 2 options. Change the name manually in Building Operation Delete the point and re-upload the controller, or delete the controller and re-discover it NOTE: Do not change point names in SmartStruxure until after all converted graphics have been imported.  The import process requires the SmartStruxure name and I/NET name to match.

Issue I/NET alarms not coming into StruxureWare Building Operation as Alarms, but are showing up in Event Window Environment SmartStruxure StruxureWare Building Operation Cause In order for an event to register as an Alarm in SmartStruxure, there must be a SmartStruxure object in the Enterprise Server Resolution Ensure all Controllers generating desired alarms are visible in the I/NET interface. If they are not, use the device discovery feature to import them. Ensure all Controllers are up to date.  Right click upload any that are not. For alarms that originate from a Host or NPR, you will need to add these to the I/NET interface System Folder.  Right click on the I/NET Interface/System folder and add either a host or link as applicable.  Set the correct host or link number in the properties window.

Issue Is there a way to activate a function which requires a cause note, action note to be added to every I/NET alarm? Environment I/NET SmartStruxure Alarm User Action Cause Need to document user actions in SmartStruxure when an I/NET alarm changes state. Resolution Create a Change of State alarm and bind it to the I/NET alarm object in SmartStruxure. Create a Change of State alarm. On the User Action page of the alarm configuration attach a Cause Note Group, Action Note Group or Checklist. Bind the alarm object to the Alarm attribute of the I/NET Value.

Issue After logging on to I/NET, an error comes up saying "Verifying Database. The database file "RptASample" has changed. Proceeding to fix up the report." Environment I/NET upgraded version 2.4X Cause The table structure that was saved with the report is different than the current database table structure. Resolution There is no resolution as there is nothing wrong with the report. Click on the OK button and the report will be generated. The original report's structure is different and Crystal Reports recognizes it then alters or realigns them to work in the new format.

Issue Text in I/NET is showing up as gibberish, but the text in the SQL database looks OK Environment I/NET Cause If you upgrade I/NET and the SQL database but do not use DBcreate, the text in I/NET can become gibberish. Resolution Restore/upgrade the database with the help of DBcreate (follows I/NET )

Issue Changing an I/NET DI to a DA does not show up in StruxureWare Building Operation Workstation Environment I/NET SmartStruxure Integration Cause After integrating I/NET to SmartStruxure the designed intent is to allow all point name changes and alarming to be done in SmartStruxure workstation.  If you delete a point and re-create it using the same point address, point name but a different point type, the change will not show up in SmartStruxure. Resolution To successfully change an I/NET point from DI to DA: Delete the Point using the I/NET Resident I/O Editor Re-create the Point using the I/NET Resident I/O Editor using the new point extension DA. YOU MUST change the point name in some way. Perform a Station Save Open Building Operation Workstation Right Click on the Controller and select Update.

Issue When using User Defined PIN in the individual, it can’t take effect. Environment I/NET Cause Large card number should be used if User defined PIN is needed. Resolution User-defined PINs are supported when all of the following requirements are met: The door controller’s firmware is version 2.30 or later. DIP switch 7 at the door controller is ON or the Card Translation option is enabled in the Door Extension editor The individual is directly assigned a large key/card number (i.e., a key/card translation table is not being used to translate the user’s key/card number).

Issue Unable to update an ASC when adding a new MR to an existing system. Product Line TAC INET Environment All versions of I/Net utilizing HVAC applications. Cause On a system that has multiple sublan devices and adding a new or several devices to the controller, when updating the UPD files it appears to get downloaded but when the MCI update is done, only one point is written to the database. If the points are added manually, a Memory Error would come up indicating that there is not enough memory in the controller to do this. However, this is not seen when doing the UPD file update nor MCI Update. Resolution To resolve this issue, the following steps needs to be done: Connect to the controller Go to Edit/Controller/Configuration Verify that the controller does in fact have memory left If not, look at the trends that are on the resident I/O Points If possible, delete unwanted trends that are using up memory to free it up to allow these devices to be added Once done, go back to ASC Parameters and then update the ASC and MCI again.

Issue Filtering The AnalogSamples_xi.rpt SevenReport using the cell definition Environment I/NET Seven Reports Cause In some cases, the cell number can be used on a 7 trend to allow only trends of a certain type to show up in reports. If this rule is applied, you will need to change the stock reports to allow for this function. Resolution Open the AnalogSamples_xi.rpt file in Seven Reports Cancel the Date Time range selector In the Design View, click on the second icon from the left, directly underneath the word "Design" the tool tip labels it as "Select records to be used in report  Select Expert" Click on the " " tab browse to the bottom and expand "RptTrendDefinitions" Click on "CellNumber" Click OK In the left hand drop down select "is equal to" In the Right hand drop down, enter the cell number you wish to filter for. Click OK Preview the Report Save it using a different file name. 

Issue User has a backup of my files that they have restored onto a new workstation PC but now they are unable to edit the files.  For example: A Continuum graphic needs to be edited and cannot save changes but can save as a new graphic. Environment Window OS Windows XP Windows 7 8 8.1 10 Windows Vista Cause This is caused by Microsoft Windows OS. Windows will automatically make a file "Read only" if it has been moved from another PC  Resolution The solution is to change the files back to read / write. Example: Open Windows Explorer and find the folder you want to change, for this example it is "Continuum graphics." Right click on the folder and select properties, which shows a tab that will be ticked next to "read only" deselect this tab and then select apply. Once windows has finished changing the folder and its contents to read/write the user will be able to go into continuum and edit graphics.

Issue When using Conversion Coefficient slope m = 1.0, the return to normal (RTN) Alarm Limit on an AI point appears to have a built-in offset. Environment I/NET Seven - Analog Inputs (AI), all revisions. Cause There is a built-in hysteresis of 3 counts on the return-to-normal settings for both the low and high limit setting of an analog input (AI) point.  When using a conversion coefficient slope (M) of 1, this provides a 1:1 scale between counts and engineering units which could provide undesired results.  So this built-in hysteresis needs to be considered when using a slope (M) of one or higher on analog input alarm points.    Resolution Consider using a conversion coefficient slope (M) of 0.1.  Alternatively if this is not possible, creating an internal AI point (using a m = 0.1) or a DA and applying a calculation to reflect the points value or alarm state as required as a workaround.

Issue Receive data from Trend log (Seven Trends) with incorrect base time hh:12 even though it is set to 00:00.   Environment I/NET Seven  Seven Trends Xenta Server 527 / 527-NPR / 731 Cause When using a Xenta Server as an I/NET NetPlus Router (NPR) and have configured a Trend (Seven Trends) with a sample count of 24 and sample interval of 60 minutes it appears that the time is incorrectly reported to the I/NET Host.  This issue will be rectified in a future release of the Xenta Server firmware.  Resolution As workaround to this issue, the Sample Count value below 24 should be used.   This is issue is not seen when using a Direct Connect configuration