Building Automation Knowledge Base

Issue Values sent from a Xenta 121 FC/HP controller via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the Xenta 121 shows a value, but the inbound SNVT on the receiving controller is invalid or a default value. Product Line TAC Vista Environment  Vista NL220 LonMaker ZBuilder Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All Xenta 121 controllers come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution In order to adjust the send or receive heartbeat of a Xenta 121 controller, follow these steps: Right click on the controller and go to PlugIns > TAC ZBuilder Plug-In. In ZBuilder, click on the Configuration tab and go to LON > Node. Here the Send heartbeat and Receive heartbeat can be changed. The following nvo values will require the Send heartbeat be set to a value greater than zero in order to communicate with another controller using a SNVT binding. nvoSpaceTemp nvoUnitStatus nvoHeatPrimary nvoHeatSecondary nvoCoolPrimary nvoEffectOccup nvoTerminalLoad nvoEffectSetpt nvoFanSpeed nvoEnergyHoldOff nvoOccSensor nvoRawDOStatus   The following nvi values will default to invalid if they do not receive an update within a specified period of time. For most applications this should be left at zero. If the application must actively poll a SNVT then the receive heartbeat can be set to a value greater than zero. nviApplicMode nviSetPtOffset nviEnergyHoldOff nviFanProof nviOccSensor nviSpaceRH nviOutdoorRH nviSpaceIAQ nviOutdoorTemp nviSourceTemp nviAuxHeatEnable nviSourceFlow nviComprEnable

Issue Unable to connect Continuum I/O's to Access Expert Product Line Access Expert Environment Win 8.1 and above on Version 3 Cause The Continuum Integration has only been configured to bring in the AC-1 and AC-1 Plus door controllers as sub-devices. Resolution There is no resolution, but the Continuum I/O's are simply not compatible with Access Expert. Use Mercury 16 In/Out boards for applications that require these types of devices.

Issue What does "AT&F" do to a modem? Environment I/NET site Cause What does "AT&F" do to a modem? Resolution It resets the modem to its factory default. (TCON209, 2-17,18)

Issue If there is a routing problem with a MNB-1000, how can the routing table be cleared? Environment MNB-1000 Cause The MNB-1000 controller need to relearn the network information. Resolution Anytime there is a routing loop or a network mis-configuration on a BACnet internetwork containing MNB-1000 controllers, it is possible to get a network mismatch displayed in the status column of the WorkPlace Commissioning tool. Because the MNB-1000 controller has learned the mis-configured network information, its routing tables will have incorrect information. Currently, the only way to remove this information and fix the problem is to correct the network mis-configuration and reboot the MNB-1000. Upon restarting the MNB-1000 controller, if the problem still exists the network mismatch will still appear in the status column, indicating that the problem is not resolved. If the problem is resolved this message will not display.

Issue When presenting a card to a card reader I see a message in the Active Event view that says "Custom Card" instead of "Valid Access" Environment AC1 ACX78x ACX57xx Netcontroller 1 Netcontroller 2 Active Event View Access Event Cause This is being caused by the controller not having an "AccessFormat" numeric set up.  The AccessFormat numeric is used to define the fields when using a Custom Card. Resolution   Use the below procedure to set up a Custom Card.  This procedure uses a Corporate 1000 35 bit card as an example. Custom Card Format for:  HID Corporate 1000, 35 bit Here is the information on creating a custom format in the Andover System. A custom format must be used when the card format is not one of the standard pre-defined formats. Only one custom format can be used in an ACX controller or NetController. Setting Up a Custom Wiegand Format In each ACX700 and ACX780/781 and NetController, create an InfinityNumeric point called AccessFormat (use this spelling exactly!). During the creation process, attach a manual array (log) with 19 entries to the point. Create he following Infinity Program, once created, can be copied to all other access controllers that need it. Program Name: SetArray FlowType: FallThru AutoStart: True Code: Set AccessFormat[1] to 35      'overall number of bits Set AccessFormat[2] to 0        'control mask Set AccessFormat[3] to 0        ' manufacturer’s code Set AccessFormat[4] to 0       ' start bit of man. Code (first bit is 0, not 1) Set AccessFormat[5] to 0       ' end bit of man. code Set AccessFormat[6] to 2       ' start bit of site code Set AccessFormat[7] to 13      ' end bit of site code Set AccessFormat[8] to 14      ' start bit of card number Set AccessFormat[9] to 33      ' end bit of card number Set AccessFormat[10] to 0      ' odd parity mask, first 16 bits Set AccessFormat[11] to 0      ' odd parity, next 16 Set AccessFormat[12] to 0      ' odd parity, next 16 Set AccessFormat[13] to 0      ' odd parity, next 16 Set AccessFormat[14] to 0      ' even parity, first 16 Set AccessFormat[15] to 0      ' even parity, next 16 Set AccessFormat[16] to 0      ' even parity, next 16 Set AccessFormat[17] to 0      ' even parity, next 16 Set AccessFormat[18] to 0      ' card number multiplier Set AccessFormat[19] to 0      ' card number divisor In each Door Configuration, select the Custom Wiegand card type. Other card types may also be selected. For each Personnel, select the Custom Wiegand card type, and enter the correct card number and site code.   If the card is not working, check the Event Log and determine the cause. For Invalid Card Parity errors, set all the parity masks to 0 and try again. For proximity cards, the parity check may be eliminated with little consequence.

Issue Duplicated SFE Short Form Edit graphics Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Sigma Cause A duplicated set of Short Form Edit graphics are created but are in a different language appear along side the original SFE graphics when using Data Import with a Sigma transition into EBO The example below shows the original DataImport was completed in English, the second DataImport was completed in Danish. Resolution Before a Sigma DataImport is undertaken, ensure that the correct language is set in EBO. Delete the Sigma Interface, set the correct language and start the transition again. Note: By deleting the Sigma Interface, this will delete all the SFE graphic links on the objects and a clean set of SFE graphics will be created on all the objects.

Issue Repeater for large distances between card reader and controller Environment Site with iBMS using Access Control Cause Site has large distances between card reader and access controller Example: maximum permissible cable length for a HID reader to the ACX controller - the length depends on the gauge of cable used: Wiring Distance Card Reader to ACX: 200 ft. (60.96 m) max using 22 AWG 500 ft. (152.4 m) max. using 18 AWG Resolution The communication between access controllers and card readers is using RS-422. Access controllers supply power as well as data to the card readers. To increase beyond the recommended guidelines a repeater can be used which extends the data length. A separate power supply would have to be installed to power the card reader.  Solutions for RS-422 data repeaters are: Westermo Cypress Computer Schneider Electric PSS in no way is endorsing nor including support of Cypress Computer & Westermo products in the following example: An example of a site using Continuum: the project used the Cypress SPX-1300 and was able to run the cables up to 3000 meters as long as the reader was powered from within the lift car, he utilised the Continuum elevator add on module with the Net11 and AC-1 Module per car.

Issue When importing an I/NET network into a Vista Workstation, the point names are available, but only after you drill down to the link, station, point, bit offset, and view the point type.  This can be cumbersome when trying to bind graphics or navigate the network. Product Line TAC Vista Environment Vista Workstation 5.1.1 and above I/NET Shortcut wizard Cause This is how the I/NET network is structured in I/NET. Resolution Right-click on the I/NET network Select "Create I/NET shortcuts..." A folder is created with nested folders for individual controllers, but each shortcut point is renamed with the I/NET point name instead of the address.

Issue When using RS-232 port to download Menta program, the neuron ID of I/O modules can't be downloaded. When downloading Menta program to Xenta 280/300 (with /N/P) through RS-232 port, the LED besides Service Pin flashes red. When plug OP onto the controller, only “No Answer” shows. Environment Vista 5 Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta I/O modules Cause The network configuration can't be downloaded through RS-232 port. Resolution When downloading Menta program to Xenta 280/300 (with /N/P) through RS-232 port in Vista 5, the normal method can't download the network configuration information to the controller, such like the blueprint, the neuron ID of controller and I/O modules. Then the following steps can be followed: Create the Xenta 280/300 controller in the Workstation. The LTA interface can be the Xenta Server, Loytec port or Echelon Port. It does not matter. Assign the Menta file to the Xenta 280/300 controller. Also manually type the neuron IDs of the controller and I/O modules in the Workstation. Right click on the Xenta controller and click “Edit” to open the Menta interface. Press F12 and “Online” button to download the Menta program into Xenta 280/300 controller. The controller or I/O modules should work fine now.

Issue Values on graphic pages constantly showing 'down' momentarily The following message can be seen in the standard output. "duplicate server session kills" Environment I/A Series R2 Enterprise Server Cause There is another copy of the same Enterprise Server station running on the network. In this particular case, there is a another computer on the network that has been licensed as an Enterprise Server and it has a copy of the Enterprise Server station. This computer is meant as a standby computer and the Enterprise Server station should not be running.  Resolution In this particular case, there is a another computer on the network that has been licensed as an Enterprise Server and it has a copy of the Enterprise Server station. This computer is meant as a standby computer and the Enterprise Server station should not be running.  Stop the Enterprise Server station that is running on the standby computer. From the Admin Tool, connect to the localhost and right click on the Enterprise Server station. Make sure auto run is uncheck. 

Issue Cable needed to Direct connect a Laptop or Desktop to a PCU Product Line TAC INET Environment I/NET site Cause The first asynchronous port (P4) provides an RS232 port for direct connection to a PC or external direct dial (Hayes) modem. The RS232 port’s baud rate is set using the HHC. Resolution CBL072 for a 9-pin PC connection CBL073 for a 25-pin PC connection Refer to TCON 096 For CBL072 information, please refer to Cable Connectivity to I/NET.

Issue Copying the SHTTXT.REC file back onto a Sigma system into its correct location.. Environment Sigma server all version 4 releases. Cause Copying the SHTTXT.REC file into the incorrect location will prevent the short texts from being shown when an object is displayed. Resolution In the later versions of Sigma 4.0? there are two copies of the SHTTXT.REC file. The first SHTTXT.REC is located in the C:/Sigma/Data/Locality/English United_Kingdom (IF UK)/ folder and is used by Sigma. The second SHTTXT.REC file is located in the C:/Sigma/Data/ folder and is a copy used by SigmaX. When copying the SHTTXT.REC file back onto a Sigma system, it should be copied to both locations.

Issue Why is the Niagara G3 Time Sync Service not working with time.nist.gov? Environment Niagara G3 time.nist.gov Cause As of April 2007 the server time.nist.gov no longer responds to requests for time in the "Time Protocol" format defined in RFC-868. Resolution As an alternative, try time-a.nist.gov or time-b.nist.gov As of April 2007 the server time.nist.gov no longer responds to requests for time in the "Time Protocol" format defined in RFC-868. All of the other NIST servers (except for time-nw.nist.gov) will continue to respond to requests to either tcp or udp port 37 for time in the format specified in RFC-868. "Time Protocol" used by the TimeSyncService has been superseded by a more sophisticated and more accurate one known as "Network Time Protocol" (NTP for short) defined in RFC-1305 The newer protocol is supported in Niagara G3 version 3.4 and newer and it is configured through the platform service of the station.

Issue Lost CD Key, because the CD case is missing Environment Any Windows OS Cause The site has lost the I/Net CD case and for some reason they cannot log into the I/Net system anymore Resolution If this is the issue, please contact the Product Support Services Department in your area.

Issue Opening the Vista SmartStruxure Interface setup, found in the status box, message "service not found" is displayed. Product Line EcoStruxure Building Operation Environment TAC Vista server Vista SmartStruxure interface Cause Some dll may be missing causing the service could not start. Resolution Manually run the VistaInterface execution file. By default TACVistaSmartStuxureInterface.exe file is stored in C:\Program Files\Schneider Electric\TAC Vista SmartStruxure Interface 1.0.5. Double click on the TACVistaSmartStuxureInterface.exe file, if the service could not be started, it will pop out an error message window. If it is a dll file missing, can find the corresponding dll on the internet, and solve this issue. If the error message shows some other error, please make a copy of the error message and contact the local support team for further assistance.

Issue After connecting a new Optimum Living Space Sensor, the LCD is blank other than being backlit. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Optimum Building Operation Multi-purpose VAV fw 2.00.03.02000 or older Cause Only Living Space Sensor bases running application version 1.0 or later can read the Optimum cover models Resolution Upgrade EBO to v3.1.x or later and SmartX controller to fw v3.01.x or later. At the time of this being published, firmware revisions prior to 3.01.x are not compatible with the Optimum Living Space Sensors (SXWSCDPSELXB, SXWSCDPSELXW, SXWSCDXSELXB, SXWSCDXSELXW).

Issue Sigma 4.08 - Sigma server does not start, and an error message may be produced. Environment Sigma 4.08 Build 3.46.57 SigmsSvr.exe Cause Upgraded to Sigma 4.08 from Sigma 4.04 and the Sigma service SigmaSvr.exe would not run. Resolution This issue is caused by a valid licensing method not being available on the Sigma server. Sigma 4.08 (Build 3.46.57) can be licensed by one of the following methods; A valid Sigma dongle. A copy of StruxureWare Building Operation license Administrator software and valid license has been installed.

Issue Site looking for a sample program to monitor the thermostat and alarm if it stops updating the temperature. Environment AS PE Script MPM EnOcean Cause Documentation Resolution Write a PE script to monitor the temperature and alarm as necessary. Click HERE for sample PE Script program.

Issue After manually changing all the COV increments in a Niagara R2 station, the COV increment values never update. Environment Niagara R2 Cause The COV increment property is not fetched during a poll. To receive an update on this property use the Upload All command on the device object. Resolution Follow the steps below in WorkPlace Pro to perform an Upload All on the device object: Navigate to the workspace of the container where the BACnet device object exists. Right click the device object and select upload all. For further information on COV increment refer to the Niagara R2 BACnet Integration Reference manual 

Issue How should a Echelon Lon Talk Adapter (LTA) be configured if used in a Vista classic network? Why is the network and controllers offline in Vista Classic? Environment Vista 4.x.x Vista 5.x.x Echelon LTA (PCC-10, PCLTA-20) Cause The NI application of the LonTalk adapter needs to be configured as NSI not VNI (Virtual network interface) in the LonWorks Plug n' Play which configures the LTA. Resolution Change the NI application of the LonTalk adapter. Open the Windows Control Panel Select the LonWorks Plug N' Play. Change the NI Application For a PCC-10 LTA select NSIPCC For a LTA-20 LTA select NSIPCLTA Click Apply Start Vista Server.