Building Automation Knowledge Base

Issue When you open LonMaker 3.13 the LonMaker Menu list is not shown in Visio. Environment Lonmaker Cause The Visio macro security settings sometimes become corrupted Resolution  To restore the link to the LonMaker software, follow these steps: Open the Windows Start menu, point to Program Folders, and then click Microsoft Visio. Visio starts Open the Tools menu, point to Options, and then click Security. If any of the check boxes under Macro Security are not selected, select them, click OK, and then exit and restart the LonMaker tool. If you restart the LonMaker tool and you see the LonMaker menu, skip the rest of this procedure. In LonMaker  open the Tools menu, point to Options and then click File Paths tab. Write down the LonMaker path shown in the Add-ons box, and then delete it. By default, the LonMaker path is C:\LonWorks\LonMaker\Visio. *This should be C:\LonWorks\LonMaker. The path may be followed by a semicolon if there are any additional paths in the list. Exit and restart Visio. Open the Tools menu, point to Options, point to Advanced, and then click File Paths. Enter the LonMaker path you wrote down in step 5 in the Add-ons box. Include the semicolon if there are additional paths after the LonMaker path. Exit Visio and then start the LonMaker tool.

Issue Is the use of Windows Server 2008 R2 64 bit Service Pack 1 supported when using release 1.3? Environment Release 1.3 Documentation Release notes Operating system Cause The release note for StruxureWare Building Operation 1.3 states that only Windows 2008 R2 64 bit is supported, but it also says that .Net 4.0 is required. When downloading .Net 4.0 from the following site,  http://www.microsoft.com/en-us/download/details.aspx?id=3556 you are advised in system requirements that Windows Server 2008 R2 64 bit SP1 is required. Is Windows Server 2008 R2 64 bit SP1 supported? Resolution When our software quality assurance teams tested and qualified 1.3.0  they all used SP1, so yes SP1 is officially supported.  

Issue Sigma Server crashes and the hard drive has filled with archived Alarm Logs all of which are of the same time. Environment Sigma Cause Sigma Server has crashed. The hard drive has filled with alarm logs with approximately the same file date. When Sigma is re-started, the Alarm Fail Safe window is filled with "Logging Database is 100% full" "Unable to archive"  Resolution What happens: When the Logging Database becomes full, it is normally automatically archived. If the c:\sigma\data\archivedlogs folder is not present then the Logging Database cannot be archived, Sigma will continuously retry to archive the database and fails continuously, each time a System Message is raised, the Alarm Log Database is filled, the Alarm Log is then archived, and the process is repeated. To resolve: The 3 folders are created when Sigma is installed. The folders may have been removed or deleted. Re-create the following folders under c:\sigma\data ArchivedAlarms ArchivedLogs ArchivedTransactions To test: Create an Action and Schedule to archive the log. Let the time pass, and check the ArchivedLogs folder and the file Sigma0nnnn.dbs is present. If successful, either remove the daily schedule or it can remain.

Issue Some engineers are being issued with new HP Probook 6570b laptops, running Windows 7.  The Loytec NIC_USB100 network interface does not work with these machines, even when the latest Loytec drivers (version 4.1.4) are installed.  Environment Lonworks Windows 7 Cause Plug'n'Play does not recognise the NIC_USB100 when it is plugged in and fails to install the drivers. Resolution As a workaround, install a virtual machine running Windows XP on the HP Probook 6570b.  Install the Loytec software on the virtual machine.  The NIC_USB100 is then recognised and the drivers install correctly.

Issue Shutting Down I/O Server while running as a Client Environment I/NET Seven rev 2.X and above I/O Server Cause Running I/NET I/O Server as a service and need to shut it down in order to do a backup or to run DBCreate. Resolution Close I/NET, since I/O Server will still be running, it can’t be closed. Open I/O Configuration Editor, if you right click on I/O Server, the Exit button will be grayed out. Close I/O Configuration Editor, right click on I/O Server again and this time the Exit button will become available and it can be selected. Select Exit and I/O Server will now be closed. To restart I/O Server again, either restart the PC or launch it through Administrative Tools > Services > MSQL Agent  

Issue Procedure for changing the name of a FLO2 block in a Network 8000 GCM, and in the MicroFlo II controller Environment Unknown Environment Cause Unknown Cause Resolution The name comes from the FLO2 block in the GCM. Once the block is created and named, there is no direct way to edit the name, either in the GCM or from PSI. The name is saved in the backed-up PSI application file, and when the application is downloaded, the name in the controller changes to the name from the file. Download a different file, and the MFII gets a different name. To keep the programming intact, but change the block name in the GCM and in the controller: 1. Set the physical address of the existing FLO2 block (with the wrong name) = 0. 2. Copy the block, give the new FLO2 block the name you want. 3. Edit the new FLO2 block, set the physical address = the DIP switch setting on the MFII. 4. Reset the new block, created in step 3. This writes the new name to the MF2 controller. 5. Delete the original FLO2 block, that had the wrong name.

Issue Creation and testing of a Scheduled Action to retime the Sigma controllers. Environment Sigma Scheduled Actions Retiming controllers. Cause The Scheduled Action to retime Sigma controllers does not appear work. Resolution Create the Action to Retime the Sigma controllers. 1 - In Sigma Setup, select "General - Scheduled Actions - Actions". 2 - Highlight "Actions" and select "New". 3 - Give the Action a title, "Retime Controllers" for instance. 4 - Highlight the new action, and in the "Select Required Actions" window select, "Retime Devices". Save the changes. Create the type of schedule you require. 1 - Highlight "Daily" and select "New". 2 - Give the Schedule a title, "Retime Controllers" for instance. 3 - Highlight the new schedule, and in the "Actions" window select, "Retime Controllers". 4 - Select the Days / Times you require, and save the changes. Testing the operation of the new "Retime Controllers" schedule. 1 - Allow the system to operate normally and then confirm that the controller retime has taken place, by using the "Transaction Logging", or by checking the controller times, to confirm this. OR 2 - Manually change the PC Time / Date to confirm that the schedule operates correctly. If using this method then make sure that the PC clock is allowed to pass through midnight automatically. An example of this, would be to set the controllers retiming to take place at 00:05 and then set the PC clock to 23.55. This ensures that the PC time passes through midnight, before the "Scheduled Action" is run at 00:05.

Issue Alarm archiving at release 4.5 SEB. Environment Sigma Alarms Archiving AlarmLog.rec Cause The alarm archiving mechanism is unclear. Resolution Sigma 4.05 SEB includes a mechanism for archiving alarms on basis of a number of conditions. User Settings. The user is able to set the following "Alarm File Sizes".  Current (Max). this is the maximum number of alarm records * 1000. Archive (20 - 50) %. this is the percentage of the "Current (Max)" record setting that will be archived.  These setting are located in the "System Setup" / "General" / "Archive Sizes" as shown below. Automatic Alarm Archiving. The Sigma alarm archiving process is an automatic function that will operate to the requirements of the settings above. When an archive takes place a low level alarm message is produced to advise the user, it does not require acknowledgement as it is only for information. Archive alarm files are stored in the C:\Sigma\Data\ArchivedAlarms folder using a sequence reference number. Timed Alarm Archiving. These Schedules are located in the "System Setup" / "General" / "Scheduled Actions", and the first step is to create an "Action", as shown below.  Next create either a "Daily" or a "Once Only" schedule. The alarms will now be archived on a regular basis as dictated by the above schedule. Please note that the archive will still follow the configuration setup up in "Archive Sizes".

Issue The STS safety feature for Forta actuators is obsolete since a few years. Environment Forta STS M700 MG900 Cause With the Forta STS battery safety feature no longer available, a replacement actuator with similar safety function is requested. Resolution Depending on torque requirements, the Forta M700 and Forta MG900 spring return actuators are available. Just make sure the correct closing direction (stem up/stem down) is defined when ordering these actuators.

Issue Require the Automation license option to be able to configure C-BUS integration but the option is not enabled. Product Line EcoStruxure Security Expert Environment SP-C-WEB Cause Older SP-C-WEB controllers were shipped without the Automation license enabled. Resolution SP-C-WEB controllers purchased after 4-Oct-2021 are shipped with the Automation option included with the license.   For controllers ordered before this date the option can be enabled by contacting Product Support and providing the controllers serial number.

Issue PinPoint graphics crashes when creating or editing "Active Animation" or "Combo Box" Environment Windows 7 1.93 1.94 Cause If logged on to the PC as a Power User or other non Administrator account you may not have the correct permissions to run some items within Continuum Resolution If the user is required to modify or create PinPoint graphics or various other activities, full access to the Continuum Folder may be required ( or Graphics Folder if this is an a remote server) 1. Log on to the PC as an Administrator 2. Locate the Continuum directory (usually C:/Program Files/Continuum) or Graphics directory 3. Open Properties (Right Click) 4. Select Security 5. Add the required Group or user name, give the write permission

Issue Where are the CE certificates available for the products in the Xenta family portfolio? Environment Xenta family Cause In some applications, CE certificates are required by the end customer or consultant as Declaration of Conformity .  Resolution In general, the CE certificates are available for download on The Exchange Download Center. Download Xenta CE Declarations certificates

Issue Using reference shapes to clean up a LonMaker drawing Environment LonMaker Visio Cause A Xenta 401 controller can have as many as 125 SNVT inputs and 125 SNVT outputs visible on a LonMaker drawing. If every one of these signals is connected with a SNVT binding with graphical lines connecting the source and destination signals it can be rather difficult to differentiate between the connections. Resolution One way to clean up your drawing is to select the "Use References" option when you are in the process of creating your SNVT bindings. This will graphically display a line to a numbered balloon at the source and a numbered balloon with a line drawn to the destination. Since the balloons will contain the same number you can easily identify these as bound together. If for some reason you need to revert a referenced binding to a graphical line, right click on the reference object and select the "Don't Use Reference" option and a normal graphical line will be added. If you have a large network, the destination of the binding is on another page, or the destination is not easily visible, right click on the reference object and select "Go To Reference" to have LonMaker take you directly to the destination.

Issue Which Xenta 101 stencil should be use in LonMaker? Environment Xenta 101-1VF, 101-1VFC, 101-2VF, 101-2VFC, 101-VF Cause Adding a Xenta 101 to a LonMaker drawing. Resolution Please use the following chart when deciding which Xenta 101 stencil to use in LonMaker:   Xenta Unit Stencil 101-1VF 101 101-1VFC 101 101-2VF 101 101-2VFC 101 101-VF 101-VF

Issue When running Sigma 4.05 on an laptop that is also running VMware to minimize or close the application can take up to 5 seconds. Environment Sigma 4.05 VMware Cause Require to run the SetSigmaForVMware.exe Resolution The utility SetSigmaForVMware.exe has been developed to prevent the delay, but must be used on Schneider-Electric engineering laptops only. This applies to normal Windows and the VMware version where Sigma 4.05 is loaded. Download SetSigmaForVMware utility.

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. Issue Want to be able to import a list of individuals quickly without having to retype all the details from a spreadsheet or text file again into I/NET Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft Access 2003 Microsoft Access 2007 Cause Customers usually have a spreadsheet or database of employees and / or users which they want to quickly import into their I/NET Seven Access control database.  The process below describes how to do this along with its limitations. Resolution Process to import Individuals via the IDWorksView table using Microsoft Access 2003 / 2007 The import process will NOT update any existing data; it will only add new entries and leave existing entries as they were.  So this is typically a process used for a new installation.  If you are attempting to import into an existing Access control database with individuals then it is strongly recommended to backup your I/NET SQL database. It is also strongly recommended you test this in an ‘offline’ state, that is, it is not connected to any physical controllers until you are comfortable that the process provides the desired results. The same limitations that apply with ID Works (Refer to TCON 301 Chapter 5) apply to this import process. TAC I/NET Seven (not just I/O Server) must be running on the server specified in TAC I/NET Seven’s ODBC data source in order for records created or modified from ID Works to be downloaded to affected DPUs. ID Works does not allow you to add or modify multiple cards for a single individual. ID Works does not allow you to remove a card from an individual without deleting the individual record. You cannot disable an individual’s card without disabling the individual. You cannot create a new group or a new tenant.  All Tenant and Group information must already exist in I/NET You cannot make an individual’s record be DPU resident. You cannot assign a decimal card number to an individual. You cannot set an individual’s APB scheme (that is, hard, soft, or graced anti-pass back). You cannot assign a PIN to an individual. The steps to import are as follows: Download ZIP file containing necessary files here. If you are using Microsoft Access 2007 use the following files Format customer data into the Excel template (dbo_IdWorksView.xlt in the ZIP file) or provide this to the customer to complete the Employee details.  Pay attention to required data shown in the comments for each title cell. Open db1.mdb file in the ZIP file using Microsoft Access 2003 /  idworks.accdb if using Microsoft Access 2007. Double click (open) the table dbo_IdWorksView to establish the connection to I/NET on the respective machine.  You may be prompted for login details – you must use the ‘sa’ login and password installed on the PC. If successful you should see any individuals that already exist in the database (unless blank).  Close the table. If you are using Microsoft Access 2007 Click Here to view the changes for steps 6 though to 8. Right–click in any of the white space and select Import (or go to File>Get External Data>Import) Browse to the location of the Excel Spreadsheet, saved in step 2, containing the data to be imported.  Be sure to change the File Type to *.xls otherwise you will not find the file.  Select the file. Import wizard should appear, now select the following options within the import wizard: Select the Check box “First row contains column headings..” Select Next Select “In an Existing Table” and select the table from the drop down list – there should only be one there. dbo_IdWorksView. Select Next. Select Finish. Be patient – the process can take a few minutes based on the number of entries that you are trying to import.  Once imported you should receive a message indicating that the import was completed.  Select OK. If you have images referenced in your import file, be sure that the Images are in place before modifying ANY individual in I/NET.  Otherwise the image path will be deleted.  The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality. There is also a way to realize this function using Microsoft SQL Server Management Studio Express instead of Microsoft Access. See How to Import a Large Number of Individuals from Excel to I/NET SQL Database at One Time for more information. 

Issue Access Environment CMC 1803 Access Password Pin Number Cause Access required Resolution

Issue Does TAC plug-ins work with NLStart? Environment TAC Plug-ins NLStart Cause NLStart is a non LNS based binding tool for small networks from Newron systems. Since the tool is not LNS based out plug ins will not work Resolution You can not use NLStart and TAC plug ins

Issue Manual override lever / handle is missing or broke. What is the part no for replacement? Environment VTRE Cause Broken / missing handle Resolution Unfortunately, the manual override handle is not available as a spare part. It only comes delivered together with the valve.

Issue When trying to access the NPR configuration editor, why does an error message stating "bad subcommand" display? Environment NPR configuration editor Cause There is no BIN file within the NPR. Resolution Perform a Software Restore.