Building Automation Knowledge Base

Issue How to load up archived data in a report using Seven Reports Product Line TAC INET Environment I/NET Seven  SevenReports Archiving Cause Reports show nothing or have one blank page and fail to show data that meets the date window specified Resolution When using Seven Reports to view data, archived data can be viewed and put into a report.  From the Archives pull-down menu, Mount/Dismount the archive files. Files, by default, are stored in the c:\INET Seven Data\Arch folder. After mounting the needed reports (look at the date of the files in the archive folder), the report used must have the word ARCHIVE in the file name. This specifies that the reports will be pulled not from the current database but rather from the mounted files and on the dates specified. The reports should now be from the Archived files mounted. Archive Reports are located on the install CD under CD\Program Files\INET Seven\Reports To download, click on the link below and select to save the report to your hard disk in the c:\INET Seven Data\Reports folder:   I/NET Seven Release 2.20 and Prior files: ArchiveOverrideBillingSamples.rpt ArchiveRuntimeSamples.rpt ArchiveTransactionsDoors.rpt ArchiveTransactionsIndividuals.rpt ArchiveAnalogSamples.rpt ArchiveConsumptionSamples.rpt ArchiveDemandSamples.rpt ArchiveDiscreteSamples.rpt   I/NET Release 2.21 to current: ArchiveAnalogSamples_xi.rpt ArchiveConsumptionSamples_xi.rpt ArchiveDemandSamples_xi.rpt ArchiveDiscreteSamples_xi.rpt ArchiveOverrideBillingSamples_xi.rpt ArchiveRuntimeSamples_xi.rpt ArchiveTransactionsDoors_xi.rpt ArchiveTransactionsIndividuals_xi.rpt   Tip: In some instances, while the report is running and the data is being compiled, if you move the mouse or strike a key, the process starts all over. The solution is to start the report and wait for a few minutes if you have input a broad range of data to search and produce.

Issue As part of a site power feed problem investigation where varistors are being blown, how are they connected to the power feed? Environment i2920, b3920, b4920. Cause When a site is experiencing power problems and the mains input varistors blow, it is required to know how the damaged varistor is connected. Resolution The 3 varistors are connected between: Live and Earth, Neutral and Earth, Live and Neutral. The attached sketch shows how  the 3 varistors are connected. The connections are the same for the i2920 and b4920.

Issue When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the LNC. Product Line TAC IA Series Environment I/A Series R2 (Niagara) WorkPlace Pro I/A Series Network 8000 LNC-100 Cause When a third-party network management tool is used to define and commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Click here to see this procedure including screen captures. If the LNC-100 is already communicating to existing controllers on the LON trunk, document the Domain0, Subnet0, and Node0 addressing in either the SYS:SIM or SYS:SIM2 blocks. You don't need to change the existing address in order to add new LON controllers. If you will be using Niagara to commission the new LON controllers, set up the LonWorks Service so that the Local LON device is on the same Domain and Subnet as the LNC-100. Set the Domain length and Domain ID; go to the Properties of the LonWorksService, Netmgmt tab, Engineering tab, domainId, length, domainId. For example, if the SYS:SIM block in the LNC-100 has "DOMAIN0=0D, SUBNET0=01,NODE0=120,..." then in the UNC, it should be domain length = 1 (byte), and domainId = 0D. Apply the changes. Set the Niagara subnetNodeId properties: subnetId = 01, nodeId = 127. The subnet matches SUBNET0 in the SYS:SIM block. Leave the Node ID set to 127 Apply the changes Recommission the Local Lon Device. (Remember to disconnect the LNC-100 from the trunk before commissioning!) With the new controllers connected to the LON trunk, go to the Lonworks service, Lon Device Manager, and run the “find” command; the new controllers should be added to the list of nodes. You can use the Lonworks Utilities, command = identify, SubCommand = service pin to be sure you have the correct node. Then commission the new nodes. Note: Should the LNC-100 be accidentally commissioned, refer to Network 8000 LNC-100 cannot communicate to LON devices under it but can be accessed with WorkPlace Tech or a LON commissioning tool.

Issue Satchwell D?T sensor temperature to resistance Environment Satchwell DOT DRT DDT DWT DST DOS Cause Find the resistance value of a D?T sensor at any temperature in Centigrade. Resolution Referred to Satchwell T type Sensor resistance chart. Click here.

Issue How can I run Windows programs from a workstation plain english program? Environment Cyberstation Plain English Windows programs Cause Launching windows programs from Continuum Resolution Please see this link for information on using the Shell plain english function NOTE A Plain English script can be added to some graphics objects (Plain English Script tab), so for example you could run a batch file (in the continuum directory) from a graphics button using Shell "test.bat"

Issue To assist locating data sheets if you do not have access to The Exchange or other Schneider Electric storage areas Product Line Satchwell MicroNet Environment MicroNet 50 series Controllers Micronet Touchscreens Micronet LCD SLink sensor Cause To assist customers that do not have access to our internet or partner websites. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MN 50 Series MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN350 Controllers MLi and data sheets for Satchwell MicroNet MN450 Controllers MLi and data sheets for Satchwell MicroNet MN550 Controllers MLi and data sheets for Satchwell MicroNet MN650 Controllers Download all of the above (file size 12.0 MB) Data sheets for MicroNet 100 series controllers ETC can be downloaded from MicroNet 100 series controller MLi's and Data sheets.

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue LDAP (Lightweight Directory Access Protocol) Integration of G3 (Niagara) Users with Active Directory Environment I/A Series G3 (Niagara) LDAP Cause None Resolution The Enterprise server or ENC must be part of the site domain before setting up LDAP.  If DNS has been configured proceed to LDAP Configuration Steps.  For further information consult docLdap_3_1.pdf

Issue Will the Multi-Purpose Manager (MPM) act as a BACnet IP BBMD?   Product Line EcoStruxure Building Expert Environment Site using BACnet and one or more  SmartStruxe Lite Multi-Purpose Manager (SSL MPM)  Cause Can the MPM act as a BBMD Resolution The MPM cannot act as a BACnet Broadcast Management Device (BBMD), but it can be a foreign device to another BBMD BACnet protocol includes broadcast traffic which does not pass through on-site routers. For BACnet devices to network across a wide area or across multiple separate sites connected by the Internet, it is necessary to register the BACnet devices with a Schneider BBMD using the Foreign Device Registration function in Building Expert. For a Multi-Purpose Manager (MPM) running Building Expert to function as a BACnet device, when being managed remotely over a standard TCP/IP network, it must be configured as a Foreign Device. It must also be registered on an Automation Server (AS) on the remote network that acts as a BBMD. Once done, BACnet devices can send messages to the BBMD, which are translated by the BBMD so they can pass over a standard on-site router. Then BBMD forwards the messages to the appropriate destination MPM controlling the Devices for which the BACnet messages were originally intended. Then the MPM translates the messages received over the network from the BBMD into standard BACnet messages and passes them on to the intended Devices as if they were direct BACnet messages. This Foreign Device Registration feature allows a single user with a StruxureWare Building Operations (StruxureWare Building Operation) terminal to remotely oversee multiple disparate sites simultaneously using BACnet, without having to install expensive direct connections to each site. You must have Firmware release version 2.9 or higher installed on your Manager to use Foreign Device Registration function. Here is the BACnet-Specifications-PIC-Statement.pdf And the  explanation on how to setup the DR-ForeignDeviceRegistration.pdf

Issue How are the bits allocated in a 26bit Wiegand card format? Environment Access control peripherals data format Cause Although this is an openly published data format, sometimes the actual data bit format is required. Resolution The Wiegand 26 bit format consists of 24 bits of data and 2 Parity bits (Odd and Even) The 24 data bits are split between 8 bits for the Site code and 16 bits for the card number. Giving a card number range of 1 to 65535, and a site code range of 1 to 255. A spreadsheet defining the format can be downloaded here.

Issue Alarms cannot be created in a BACnet b3 controller because the fields are grayed out. Product Line Andover Continuum Environment Continuum Cyberstation b3 BACnet MS/TP controllers Cause Alarms are created differently in a BACnet controller than with an Infinet controller.  These fields are grayed out since they are not used for alarm creation in a BACnet controller. Resolution There are instructions in the BACnet section in the Continuum help for creating an event notification and then mapping the point and the event notification within an alarm enrolment. For an example see AlarmCreatingAndConfiguring BACnet.doc

Issue Information on the MicroSmart Laptop Interface Module (MSC-LIM) Environment DMS MicroSmart Cause Information Resolution Installation / Connection sheet

Issue How to convert earlier versions of Microzone II PSI files to 3.3 revision or later Environment Network 8000 Microzone II, PSI/XPSI Revision(S) 3.13 and 4.1 Cause Error Not a valid application file!  File is not compatible with existing XPSI revision.  It must be upgraded with Zconvert.exe Resolution Procedure on how to convert Microzone II files to revision 3.3 or later and read me file.

Issue How to open an external document (e.g. Word, Excel, PDF) from a G3 graphics page Environment I/A Series G3 (Niagara AX), revisions 3.3 and later Cause N/A Resolution The attached document provides detailed instructions on how to launch an external documents from a G3 graphic.  Click Here to open the document.

Issue What OPC options does sigma support? Environment Sigma OPC DA AE ModBMS IC-GEN-OPC IC GEN OPC Cause Requested details Resolution There are two options available; 1. OPC Server:  ModBMS software available from Product Support London. This supports up to 5000 OPC DA tags and OPC AE events.  See release note for details 2. OPC Client:  IC GEN OPC software mimics a Sigma controller and is loaded onto the same PC as the OPC Server. This supports up to 1000 OPC DA tags only.  See datasheet for details.

Issue Satchwell "AM" series Rotary Actuator requires replacement Environment Satchwell “AM” series Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.   N.B. Where a Satchwell “AM” series Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. In addition to replacing the AMS Actuator it will also be necessary to replace the VV Butterfly Valve Body. The replacement Actuator is S-E type MF type. Please check the latest catalog for current equipment. The Satchwell VV Butterfly Valve Body should be replaced by a S-E Butterfly Valve Body selected from the VF208W series of Butterfly Valve Bodies. It should be noted however that significant pipe work modifications will also be necessary in order to accommodate any selected VF208W series Butterfly Valve Body due to the differing construction of the VF208W Butterfly Valve Body. Please check the latest catalog for current equipment. Cause Obsolescence of Satchwell AM series Rotary Actuator. Resolution Replace Satchwell AM series Rotary Actuator with MV15B-230 Linear Actuator and Linkage Kit :- AM = MV15B-230 + L7SV (880-0126-000) Linkage Kit. N.B. Should the Satchwell AM series Actuator include a wired Auxiliary Switch then the following Auxiliary Switch Pack S2 (880-0469-000) - two independent 250 volt 10 amp (inductive) 3 amp (resistive) rated SPDT Auxiliary End Point Switches - may be purchased separately permitting local installation.   Please check the latest catalog for current equipment.

Issue OPC Server with third party and alternatives Product Line Andover Continuum, TAC INET Environment System requiring third party connectivity Cause OPC Server to communicate between hardware and the iBMS (intelligent Building Management System). Resolution The OPC server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. OPC Client Servers are used to communicate between BACnet IP interfaces and iBMS (intelligent Building Management System) programs such as TAC I/NET or Andover Continuum. There is also no Continuum OPC Client software to use for a direct OPC link. The best way to integrate from 3rd party EIB or OPC protocols is using BACnet IP on Continuum; there are third party interfaces and gateways that will convert to BACnet/IP and others that go from OPC Client/ Server to BACnet/IP. I/NET OPC For I/NET a great solution is to install a Xenta 913 controller which gives the capability to go with Modbus or BACnet/IP to third party solutions. The I/NET to Xenta 913 allows communication with Continuum BCX, StruxureWare AS-B, and other 3rd Party solutions. Continuum OPC Standard 3rd party gateways are established to communicate between the protocols such as BACnet and Modbus. Andover Continuum has an OPC Server available here. The hardware requirements are Windows NT 4.0 or Win2K. If wanting to run on XP or newer operating systems, please be aware that no testing has not been done with these OS. For more info on the OPC and XDriver, please see OPC Server Integration. Only one instance of the OPC server on a computer. Each system would need a separate PC with license key to connect to the individual systems and host controllers. The Andover Controls OPC server must be running a separate 3rd Party OPC client computer and cannot be on the same computer as CyberStation. From there it is configured to retrieve point values from a the suggested dedicated Infinity (CX) Controller. It is suggested to install a OPC gateway Infinity Controller since this controller will constantly be busy with OPC traffic. Therefore it is the separate third party vendor computer which requires the ACC OPC Server security key, not Cyberstation security key. Both USB and parallel port keys are available. If no choice is available for OS, one alternative is to check on 3rd party OPC servers like Kepware and Matrikon. Note: For Continuum, determine which one of your controllers will become the “Primary Controller” The Server requires that you designate one external Andover Controls Infinity or Continuum controller located on the same network as its “Primary Controller.” This controller must have had the network taught to it prior to selection. (This is done through the “Teach” function in the workstation.) The Server gets its information about the network through this controller. This suggested single controller is designated as the interface through which all point access is obtained. Controller Type Select the type of network where the controller is located. For a NetController, b4920, CX9702 or upgraded Infinity controllers that can be connected to a Continuum network you would select “Continuum”. For older Infinity controllers, select Infinity. Works with any IP level controller. There is no limit on the quantity, but rather it depends on how you tune.

Issue Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E until 1.532  Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, until 1.532. Cause Common IP (Internet Protocol) ports echo (7), daytime (13) and time (37) are open. Having any of these IP ports open may be a cause of concern for customers that are sensitive to network security issues; these customers include defense installations, financial institutions, and government buildings. Resolution The services using the echo, daytime, and time protocols have been disabled which prevents IP ports 7, 13, and 37 from being open. These services and protocols have no purpose during the normal operation of the MNB-1000. Disabling the echo protocol and closing of port (7) has the side effect that the MNB-1000 cannot be “pinged”. Using the command line program Ping will not detect an MNB-1000 that has firmware v1.50E installed. Use WPCT instead of Ping to verify communications with the MNB-1000. Click here to see the Release Notes for firmware Revision 1.50E. Update; In firmware 1.532, the ping function was re-initiated as the default.  Please see the TPA-IA-19-0004.00 Firmware 1.532 Release Notes.  It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue BAS2800+ does not  see the dongle when it is started. Environment Windows XP, BAS2800+ V2.9 Cause The PC is too fast for the dongle to be detected. When BAS2800+ is installed on a PC and BAS2800+ is run for the first time, a warning message is displayed - "No Dongle Driver Detected".  Resolution Download here the fast dongle driver, unzip and install in c:\bas\bin and run dk2wn32.exe Follow the on screen instructions and finally restart the PC. The dongle should now be detected and BAS2800+ is allowed to run.

Issue Attempting to commission and bind to a Trane lon controller (object name:  Lcir & programID 80:00:CF:07:00:0A:04:05, 80:00:2A:55:00:03:04:0C, and Lcir-DAC 80:00:2A:56:0A:03:04:04. Both processes fail.  An xif file was created directly from the controller using Nodeutil. Click here to view the xif file. Environment Niagara G3 version 3.5.25 Cause The commissioning process concludes with a change of state to the controller ('config/online' to 'offline' to 'online'). The issue is that this particular Trane controller responds to the first requests ('config/online' to 'offline') but fails to respond to the 'online' request (original message plus three retries as defined by the LonWorks protocol) or approximately 400 mSec. In addition, the binding process also utilizes an 'online' to 'offline' to 'online' change of state and has some similar delays within the controller response. Resolution Modifying the Retry Count within the Lon Comm Config settings (from 3 to 6) allows up to 6 retries in the event of a no response for this type of  message. The actual Trane node appears to take a long period of time (over 500 mSec) to respond to the change of state message. This change to the retry count will not affect the bus unless there are bus issues that generate multiple retries. Basically, the change will be not be noticeable on a solid operating bus.