Building Automation Knowledge Base

Issue I/A Series R2 station fails to send BACnet alarm to a third-party system.  The error indicates tridiumx.bacnet.BACnetException E_BACNET_UNRESOLVED_DEVICE_ADDRESS. Environment I/A Series R2, BACnet Cause A notification class and BACnet recipient have been configured with a BACnet device instance however an error is generated for each alarm attempt.  The error log indicates that there is an unresolved device address. tridiumx.bacnet.BACnetException E_BACNET_UNRESOLVED_DEVICE_ADDRESS   at tridiumx.bacnet.services.BACnetTransport.sendConfirmedRequestSimple (bytecode 21)   at tridiumx.bacnet.notification.BACnetNotification.sendRequest (bytecode 9)   at tridiumx.bacnet.notification.AsyncEventNotificationRequest.execute (bytecode 15)   at tridium.services.helpers.AsynchronousRequestHelper.processMsg (bytecode 4)   at tridium.services.helpers.MessageQueueHelper.run (bytecode 23)   at java.lang.Thread.run (line 5) Resolution For the alarm to work, the station must contain the associated BACnet device object for the target device.  This provides the information required to properly route the alarm (e.g. IP address, device instance, etc.).  In addition, the target device must be online and able to receive and process BACnet alarms.  Use the BACnet service BACnetUtility and learnNetwork command to create the BACnet device objects for the target devices. Additional details can be found in the I/A Series R2 BACnet Integration Reference Guide (Configuring for BACnet Alarm Generation) included with the R2 documentation.  These requirements and restrictions apply to Niagara BACnet alarm generation: Only Niagara objects that are exposed as BACnet objects can generate BACnet alarms. This means only alarms from Niagara AIs, AOs, BIs, BOs, MSIs, and MSOs can be routed to BACnet devices (Calendar and Schedule objects are not alarmable). This draws from the BACnet requirement that every alarm message must contain the BACnet object ID of its source. Only local objects in a station can generate BACnet alarms. Therefore, a Enterprise Server station cannot generate a BACnet alarm on behalf of an object in a subordinate station. If a subordinate station needs to generate a BACnet alarm, it must be configured with the BACnet service and the appropriate recipient(s). A separate BACnetRecipient must be created for each remote device to which BACnet alarms must be routed (one-to-one BACnetRecipient to device). Alarms are not regenerated. If a BACnet device is down when the Niagara system sends an alarm, the alarm is not saved for retransmission later. The Niagara system, of course, still maintains a record of the alarm in its buffer. The Niagara system does not support setting up a third-party BACnet system to receive BACnet alarms, configure its notification classes, and so forth. All alarm configuration and setup must be done using the system’s native tools.

Issue Previously the BACnet Device Id of the controller would default to the devices serial number, this is no longer possible due to the maximum BACnet Device Id being 4,194,303. Serial numbers greater than 800xxx can give an error 'Device Node id is out of range' (1 to 4,194,303) Environment Continuum BACnet Controllers Cause Concern about what the default BACnet Id will be set to a value higher than what is supported or to a value that has already been set to a previous controller. Will this conflict with existing controllers on a site when adding new controllers when all are using the default BACnet Device Id? Resolution There is an internal calculation done that uses the Serial number as a seed to then calculate the BACnet Device Id so that it falls within the 4,194,303 max. This calculated value will be unique to every other Continuum BACnet Devices default BACnet Device Id so you should be fine when newer controllers are being added to existing sites. If you want to ensure there are no address conflicts though you may want to set the value yourself when commissioning the controllers through creating the Device object manually and setting the BACnet Device Id at that time or if the device is already configured delete it from the BACnet side and then edit it from the Infinity side and enter a new and unique device id, then perform a find BACnet devices to bring the device back on the BACnet side with its new device id.

Issue Adding Web.Client to an existing site that has Continuum installed with the CFR compliance option. Environment Continuum with CFR Compliance Cause Can't find any part numbers for Web.Client with CFR compliance or an option to add it. Resolution We do not have an option for Web.Client with CFR. One of the requirements for CFR is the inclusion of operator text when performing certain actions; there is no way to prompt for, or supply, this operator text when using a Web.Client browser client.

Issue The message “Unsupported Unconfirmed service” is displayed in the Standard output Window of an UNC-520. Environment Niagara G3, R2, UNC-520, ENC-520 Cause Some manufactures’ BACnet controllers use unconfirmed service which the UNC/ENC does not handle so they are ignored by the UNC/ENC. Resolution These are nuisance messages which cause no issues. The messages can be ignored.

Issue The Forta M300 is no longer available and needs to be replaced. Environment TAC Forta M300: 8800210000 M310: 8800210010 8800210020 8800210030 Cause old actuator no longer available and is replaced by revised version. Resolution The Forta M300, part no 8800210000, is replaced by Fort M310, part no 8800210030.

Issue If an upgrade fails or a database becomes corrupt the model number or system variables may not match, what is the System Variable count for the various controller types? Environment All Continuum controllers System Variables. Cause For troubleshooting purposes it is often useful to know the number of System variables a controller has. If the numbers differ between on and offline states there is a mismatch or corruption in the database. Resolution The following list shows the default number of System Variable objects each model type should contain: Controller type # Objects bCX1-Inf (9640) 47 bCX1 (4040) 36 bCX1-R (4000) 36 Netcontroller II (9680) 58 or 61 Netcontroller (9900, 9940) 54 CX9400 (Eclipse) 38 CX9200 54 CMX9924 27 CX9702 41 ACX II (5740, 5720) 63 All i2 & b3 Controllers 35 DCX250 21 ACX700 25 ACX780, ACX781 26 i1 Controllers with LCD display support (SCX, LCX810) 19 i1 Controllers without display capability (LCX800, TCX) 18 * Note the Netcontroller II can have 58 or 61 variables depending on firmware version (V2.1x has 61).

Issue Is Microsoft SQL Server 2012 supported in Report Server 1.4?  Environment SmartStruxure Report Server Cause The Report Server 1.4 datasheet mention of SQL Server 2012 is an over sight. Resolution Report Server 1.4 does not support Microsoft SQL Server 2012.  When it may be supported is unknown at the time of this writing.

Issue Application requires a steam valve capable of 7 Bar pressure. Environment VG211 VGS211F V231 Cause application requirement Resolution The VG211 and VGS211F is specified for max 6 Bar ∆Pm. V231 is specified for med 8 Bar ∆Pm (saturated water), but with a max media temp of 120°C.

Issue Default IP address of a SmartStruxure Lite MPM Product Line EcoStruxure Building Expert Environment MPM Cause What is the default IP address of a SmartStruxure MPM? Resolution Out of the box, the default IP is 10.50.80.3 subnet mask 255.0.0.0 This should be changed to suit the project requirement. Log into the controller using the default IP address. Edit the Ethernet setting, changing the IP address, Subnet Mask and Default Gateway. Click save.

Issue At some point the Infinity controller object for a BCX4040 lost all it's owned objects, yet those objects still appear under the BACnet controller. Environment Save to Database BCX4040 Cause Empty controller was sent to database on the Infinity side.    Resolution Must either rebuild the controller from scratch, or restore an older backup that has this object on another PC and export the controllers contents for importing into the existing controller.

Issue Does the operation/accuracy of the 4-20mA Humidity sensor deteriorate over time? Environment SHR100 SHD100 Cause Accuracy deterioration over time? Resolution The documented deterioration/inaccuracy after 5 years is < ± 3% RH. For more details, see the data sheet for each sensor model respectively.

Issue What is SiteStat and where can I find documentation on this product? Is the SiteStat hardware supported by the Schneider Electric repair department? Environment SiteStat Cause SS-SCI controller has failed and a repair or replacement is needed. Resolution While the SiteStat product line is no longer sold or supported by Schneider Electric, a compatible replacement for the SS-SCI controller is the SS-NT-SSA16/CLK which is available on iPortal. https://ecobuilding.schneider-electric.com/search#keyword/SiteStat/tab/documents

Issue Do we have any leakage detection sensor in the Buildings portfolio? Environment Fluid leakage detection sensor Veris LD / SD Cause Request for leakage sensor Resolution No such sensor is available in the Buildings Sensor portfolio. However, Veris might cover this with their Leak detection sensor family. For more details, please see www.veris.com

Issue Needs a 230V actuator to replace existing actuator on customer installation Environment Forta M800 V211T Cause Application requirement Resolution The Forta M800, part no 8800310030 is suitable as 24V actuator for the V211T.

Issue Program going disabled when trying to write to infinity string Environment Continuum 1.9X Windows XP, 2008 server, Windows 7. Cause Simple program tries to do a data transfer like this:   KWH_Count_Str = KWH_January Program disables. Resolution The program should use the keyword:  numtostr   so the program should be like this: KWH_Count_Str = numtostr (KWH_January)

Issue When sharing the domain with the AS under an ES, the domain object appears but includes no Users or User Groups. Environment Domains Users User Groups Permissions Cause Need an efficient way to distribute and administer permissions to all Automation Servers. Resolution When you share a domain in the ES with an Automation Server, the Users and User Group properties apply to the AS However, the Users and User groups will not appear as objects under the domain in the Automation server as they do in the ES. Only the domain object will appears under the AS.  Nevertheless the permissions will be extended to the AS.

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 

Issue Ordering a specific controller with the options required seems complicated. What do each of the options mean and how do I build the part number for the controller I want? Environment ACX57xx Netcontroller II Cause The parts list is huge and there does not seem to be detailed information on how to organize each character in the part number to get the controller with the options that you want. Resolution ACX Series Part Numbering Scheme ACX Series part numbering has been structured to make it easier to choose and find the right corresponding part number. All part numbers consist of 13 characters. Configurable options use unique letters so that features cannot be confused. A zero, specifically a "0", is used when a feature is not enabled in the desired configuration. To order an ACX Series controller, follow the scheme described in the PDF here to determine the appropriate part number. (Note: you MUST login to Buildings Download Center to view/download the document)   NetController II Part Numbering Scheme NetController II part numbering has been structured to make it easier to choose and find the right corresponding part number. All part numbers consist of 15 characters. Configurable options use unique letters so that features cannot be confused. A zero, specifically a "0", is used when a feature is not enabled in the desired configuration. All NetController II units are configured to support 32 IOU modules, and will come standard with Ethernet and full use of 128 MB of memory. There is no need to specify this in the part number. To order a NetController II, follow the scheme described in the PDF here to determine the appropriate part number. (Note: you MUST login to Buildings Download Center to view/download the document)

Issue Unable to use "Object" as a keyword in SmartStruxure Script program.  Environment SmartStruxure Script Object Keywords Cause The Object keyword is not supported in SmartStruxure script language because the binding structure cannot accommodate this function. Resolution The Object keyword is not available nor is any compatible function. 

Issue Schneider Electric part number equivalent to Belimo NM24-US Environment Belimo NM24-US MD10B-24 part no 8751015000 Cause Cross reference for replacement of existing actuator. Resolution The Belimo NM24-US seems to be obsolete. The replacement today would be the MD10B-24, part no 8751015000.