Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Sunrise/Sunset does function correctly in I/NET Seven rev 2.16 Sunrise/Sunset workaround in I/NET Seven 2.16 Product Line TAC INET Environment I/NET Seven rev 2.16 Cause Currently there are some issues with Sunrise and Sunset working correctly in I/NET Seven rev 2.16. The follow steps are given as a work around to solve these issues. Resolution There are two different ways to make this work correctly: Add some starts between the Sunrise and Sunset. It is important that these starts do not have any days of the week defined. Use a Cycle between the Sunrise and Sunset. It is important that this Cycle does not have any days of the week defined.

Issue Using the %D and %N on the FeedBack tab of an AlarmEnrollment and it is not filling in the Name or Description of a point. Product Line Andover Continuum Environment Continuum Cyberstation Alarm View Cause Enhanced Alarm Logging has not been enabled. Resolution Make sure that you have selected Enhanced Alarm Logging on the Database Initialization screen. This is a requirement to use %D and %N in AlarmEnrollments.

Issue LDF file of a database is growing rapidly. SQL Database Recovery Modes Explained Product Line Andover Continuum Environment Continuum SQL Server Cause Recovery Mode setting could allow all transactions to be logged. Resolution The Full Recovery Mode basically logs all transactions successfully, failed, table creations, columns created etc... When the Continuum database is created, there are no additional tables added or columns added unless there is an update to the database to a different version. Some sites will require Full Recovery Mode but for most sites, we only need to know when an error occurs when updating or altering rows occurs and Simple Recovery Mode will log those. The Continuum Databases are created with Simple Recovery Mode. It is up to the individual site whether they need Full Recovery Mode. Most sites run with the default Simple Recovery Mode since there is no need to log every successful transaction but only want to catch the transactions that have an error. The Recovery Mode is especially important if your site is a single-user setup. Single user databases are limited in size and if you fill-up the .LDF log file, you can exceed Microsoft's database limitations in a short period of time. As for Enterprise versions of SQL for Continuum Lan systems, you'll need to watch your available disk space. Check what the Recovery Mode is set to by using SQL Server Management Studio Express, right-click your ContinuumDB and select properties, go to the Options tab, and check the Recovery model. See the image below for details. Furthermore, if you have selected Full Recovery Mode in the past and now have a large unwanted .Ldf file that is causing you issues, then selecting Simple Recovery Mode at this point will also truncate your original Log file down to a more usable size retrospectively. (Although it may take a few hours before you see any changes).

Issue When creating a trend log in TAC XBuilder it is possible to choose automatic activation. If the automatic option is chosen you can browse in a start time for the trend log using a calendar. It is not possible to open this calendar. Product Line TAC Vista Environment XBuilder Trend Logs Cause TAC XBuilder is using Microsoft's ActiveX Calendar Control file (mscal.ocx) this is normally installed when you install Microsoft Office Professional (i.e. a version including Access) or when you install Microsoft Access. If mscal.ocx is not installed on the computer it is not possible to open the calendar. Resolution The file mscal.ocx should be in the folder \\windows\system or \\windows\system32. If not, please follow the steps below to install the mscal.ocx file. Click here to download the file. Store the file at \\windows\system or \\windows\system32 go to Start->Run and type cmd to open the command window type "regsvr32.exe mscal.ocx" Now the calendar should be able to edit in Xbuilder.

Issue Determine the current year in a Menta file. Product Line TAC Vista Environment Menta Cause Menta has built in Simple Blocks for weekday, date, month, minute and second, but does not have a "YEAR" block to tell the program the current year. Resolution Please use the attached Menta macro block. This code will take the current year and transition to the next year at midnight on December 31st. ***Please note*** The SHR block named "Year" has to have the current year put in it before downloading this code. YEAR_CALC.MTA

Issue How can a WorkPlace Tech application be identified as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x? Product Line TAC IA Series Environment WorkPlace Tech Cause Jobsite with an installed base of MNL or MNB controllers but the version of WorkPlace Tech used is not known. Resolution NOTE: Do not allow the application to be converted, if so prompted. Open the application file in an appropriate version of Visio. (WorkPlace Tech not needed). While holding down the left-shift key, right click on the background of the application and select "Show ShapeSheet", holding the left-shift key down until the ShapeSheet window is displayed. Verify that the text table window that is opened shows the file name followed by "". If not, close the shapesheet window and repeat step 2. The left-shift key must be held down until the ShapeSheet table is displayed. Look for the "User-defined Cells" table in the displayed information and verify that an entry named "User.wptVersion" is shown. This field will show the version of WorkPlace Tech that created the application. If either the "User-defined Cells" section or the "User.wptVersion" field are not displayed in the shape sheet, the application was created / edited with a version of Workplace Tech prior to version 3.2sp1. Close Visio. Respond by clicking NO if Visio prompts to save the document. In Visio 2010, the ShapeSheet is located on the Developer tab, which is not displayed by default. To show the Developer tab, do the following: Click the File tab. Under Help, click Options. Click Customize Ribbon. Under Customize the Ribbon, select the Developer check box. To open the ShapeSheet, do the following: On the Developer tab, in the Shape Design group, click the arrow below Show ShapeSheet and then do one of the following: To open the ShapeSheet for a selected shape, click Shape. To open the ShapeSheet for the active page, click Page. To open the ShapeSheet for the entire drawing, click Document.

Issue Is there an easier way to get log information out of a Niagara R2 Enterprise Server station other than by using a web browser, saving the data, and importing it to Excel? Product Line TAC IA Series Environment I/A Series R2 (Niagara) station with logs. Cause Tech tip. Resolution There is no easier way to get log information than to use a web browser, save the data, and import to Excel. However, by default, a query to the archived log limits the number of records to 2500. This limit can be changed by adding $limit=xxxx. Note: Attempting to query a large number of records (> 7500) may cause the process to fail due to timeouts. A review of the cloudscape2excel document provides some details.

Issue Monitor the online status of a base unit's associated I/O modules Product Line TAC Vista Environment Menta Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta I/O Modules Cause Alert the end user to communication failures between a Xenta programmable base unit and its associated I/O modules. Resolution Add a DI block to the Menta program. Name the DI point Click the bind button and choose online device. Within the device address box, enter the I/O module number. For module 1, type 1. For module 2, type 2, etc. Also, attached is a Menta macro that contains code for 10 modules. If there are less than 10 modules, remove the unnecessary points / alarms. Note: Any I/O module defined in the Device Specification that has no hardware inputs or outputs assigned to it in the Menta application will always report an offline status.

Issue Replacement for Drayton A703 Immersion Temperature Sensor by S-E STP600D Product Line Field Devices Environment Drayton A703 Immersion Temperature Sensor installation. Cause Obsolescence of Drayton A703 Immersion Temperature Sensor Resolution 1. Replace Drayton A703 Immersion Temperature Sensor with S-E STP600D The S-E STP600D provides the same functionality as the Drayton A703, differing only in its appearance and dimensions. The S-E STP600D Terminals are not polarised. N.B. It should be noted that the S-E STP600D is not supplied with a compatible Pocket. If it is not possible to utilise the existing Drayton Pocket, then a 100mm S-E Pocket (9121041000-Brass or 9121051000-Stainless Steel) should be selected as appropriate and in order to comply with the system requirements. There is a intentional gap between the top of the pocket, and the sensor housing, to ensure the probe tip touches the end of the pocket.

Issue Configuring LON tunneling in Niagara G3 Product Line TAC IA Series Environment Niagara G3 Cause See below to watch a video document (vdoc) explaining the process to configure Lon tunneling in Niagara G3. Resolution The purpose of this video is to show you how to configure Lon Tunneling in G3. It's already assumed that there is a LON network that has been installed, commissioned, and discovered in the G3 ENC.

Issue SNVT_press_p will not display correctly in Imperial units on a TGML graphic on a Xenta Server Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 711, 731 Cause There is a bug with the TGML graphic editor that causes a SNVT_press_p to only display in the SI units of pascals. Resolution Until this issue is corrected you can manually convert the value on the graphic page using a JavaScript. This Pascal to H2O Snippet can be used to modify a numeric or text presentation object.

Issue After upgrade of Xbuilder or opening a project built on another computer generating the project causes a "File not found:" error message. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder Cause Find the alarm or event page that is causing this problem and view the reference field to identify the cause of the problem. XBuilder was upgraded and the xmle files from the previous version are no longer present. XBuilder installation directory was on a different drive on the computer the project was last used on. Resolution In Xbuilder, right click on all the Alarm and Event pages, select Change reference, and browse in the new path to the referenced file.

Issue Getting "invalid status error 503" when trying to access a Niagara R2 UNC station remotely Product Line TAC IA Series Environment Remote I/A Series R2 station Cause Issue is due to large number of UNCs on site, and / or high browser traffic. Resolution This is an issue seen from time to time on sites that either have many UNCs present or see lots of browser traffic. Check the system.properties file. There is a line that reads: webServer.threadPoolSize=15 . This is the number of web server threads that can be opened to the UNC station. Each station to station connection takes up one thread, as does a web browser connection. I believe the JDE takes up three threads when it connects to the UNC station. If the UNC station runs out of available threads you will see the "503" error. Change that number to 25 or 30 and reboot the UNC. If the problem persists, then change this line to false: ie.activex.activation=true

Issue Echelon now has an easier way to check the status of your LonMaker License. Determine the status of your credits in seconds. Product Line TAC Vista Environment LonMaker 3.1 LonMaker 3.2 (Turbo) LNS Cause Determine corrupted credits/licensing issues without the old method of using the command prompt. This will do the same thing with a click of a button. Resolution The tool will diagnose the license status and give you the solution you need to follow to fix the problem. Download here: Echelon License Diagnostic Utility Save or run Choose LonMaker credits Copy to clipboard and email to Echelon if corrupted credits are shown. Screen shot of invalid LonMaker license: This error occurs if the license file you specified is not located in the application directory. To resolve this, you will need to reboot your PC and log in as a user with Administrative privilege. Next, make sure the files listed below are located in the C:\Windows\LNS Licenses folder. Note that the "LNS Licenses" folder is a hidden one; therefore, in Windows Explorer, go to Tools - Folder Options..., and in the View tab, select "Show hidden files and folders." Now uncheck the "Hide protected operating system files (Recommended)" option.

Issue 3 State Event Sequence to control certain Access Control Doors Product Line TAC INET Environment I/NET site Cause Three State control requirement Resolution When using the Door Points ("08" & "09") with event sequences, the following actions will occur: A “Start” command is equal to the “Secure Mode” of the door A “Stop” command is equal to the “Unlock Mode” of the door A “Lock Door” command is equal to the “Lock Mode” of the door

Issue How do I properly acknowledge and purge a "Force Door" alarm in AMT. Product Line TAC INET Environment I/NET Access Control Cause The return to normal condition (Door Normal) "Message Type" must have the same "Message Type" as the alarm cause (Forced Door). This is the same condition as for DOTL (Door Open Too Long) alarms. For I/NET to clear both these alarms. the Message Types must match within the Door editor. Resolution You have to properly configure the Door editor before you can properly remove this from AMT. In order to acknowledge and purge a "Force Door" alarm you must have the "Force Door" entry set to "Alarm." The "Door Normal" should also be set to "Alarm."

Issue Can I use the Xenta 527 on an old I/NET 2000 system? Product Line TAC INET Environment I/NET 2000 Cause Adding a Xenta 527 to an I/NET 2000 network. Resolution Yes you can, provided you set the Xenta 527 up to be compatible with I/NET 2000. With the Xenta programming cable (P/N 3-781-0128-0) inserted in port "B" of the Xenta 527, go into Windows Hyper-Terminal and make the following changes for the Xenta 527 to operate in an Inet 2000 program. Please be aware that I/NET 2000 is no longer a supported product and this mode should be used at your own risk.

Issue USB Prox enrollment reader for I/NET Seven Environment I/NET Seven Cause I/NET supports the use on an Enrollment reader via the Hosts PC Serial port, most PC's no longer have serial ports. One solution is to use a USB supported reader which can be sourced by the supplier listed in the resolution Resolution The USB enrollment reader is made by RF Ideas. It is very easy to program for use in the I/NET Seven System. After you program certain steps it becomes a "Plug and Play" device at the job site. To set up this USB reader please consult this whitepaper.

Issue The "Transactions Individual" report in Seven Reports does not sort the transactions by Date and Time. Product Line TAC INET Environment I/NET Seven Seven Reports Cause The "Transactions Individual" report is not sorted by Date and Time Resolution The "Transactions Individual" report is not sorted by Date and Time for a reason. I was determined by TAC, that the customer needs to design the method by which they want this report to be presented. This White Paper will define how to go about setting the Sort process by the Date and Time Option. Start Seven Reports and open the “Transactions Individuals” report Once the report is fully developed on the screen. Choose the “Design” tab In any of the blank white area do a “Right Mouse” Click In the “Popup” window selects the “Report” Option In the next “Popup” window selects the “Sort Records…” Option In the next “Popup” window you need scroll the left window unit you find the “RptEvents.DateTime” Option. Then Select the “Add” button the place the “RptEvent.DateTime” Option in the right window. After you do Step 6 this is what you will see in the right window You need to highlight the “RptEvent.DateTime” function. Then select either “Ascending” or “Descending” sort order. In the “Ascending Mode” the “Oldest Date” is on the top of the list and the most “Recent Date” is at the bottom of the list. In the “Descending Mode” the most “Recent Date” is on the top of the list and the “Oldest Date” is at the bottom of the list. I selected the “Descending” Mode as the way I wanted to sort the Date and Times. You also need to select the “OK” button to finish the setup process. You need to close out of this report. Select “Yes” button to save the changes you made in the “Canned” report. Remember to rename you newly created report to something other than the Original “Canned” report name.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Sunrise/Sunset does not function correctly in I/NET Seven rev 2.16

%D and %N on the FeedBack tab of an AlarmEnrollment is not filling in Name or Description of point

Database size is growing rapidly, SQL Database Recovery Modes Explained

Unable to open Trend Log automatic activation start time calendar

"Error HRESULT E_FAIL has been returned from a call to a COM component" when saving a TGML graphic

Determine the current year in a Menta file

How to identify a WorkPlace Tech application as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x

Get log information out of a Niagara R2 Enterprise Server station and into Excel

Monitor the online status of a base unit's associated I/O modules

Replacement for Drayton A703 Immersion Temperature Sensor by S-E STP600D

Configuring LON tunneling in Niagara G3

SNVT_press_p will not display correctly in Imperial units on a TGML graphic on a Xenta Server

After upgrading the XBuilder program, you may get "File not found" error message when generating the project.

Getting "invalid status error 503" when trying to access a Niagara R2 UNC station remotely

Use Echelon License Diagnostic Utility to check the status of LonMaker credits

3 State Event Sequence to control certain Access Control Doors

Acknowledge and purge a "Force Door" alarm in AMT

Use a Xenta 527 on an old I/NET 2000 system

USB Prox enrollment reader for I/NET Seven

The "Transactions Individual" report in Seven Reports does not sort the transactions by Date and Time.

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!