Building Automation Knowledge Base

Issue Unable to get modbus to communicate with the automation server and LC&D GR2400 lighting controller. Environment Modbus Automation server LC&D GR2400 SmartStruxure Solution 1.5 Cause The LC&D GR2400 lighting controller will ONLY allow 1 stop bit in it's modbus communication. Normally the stop bit setting in a modbus slave device is an "at least number", meaning the GR2400 should except 1 or more stop bits, but it does not. The problem comes from the automation server by  default sends the 1 stop bit and addition "guard bits" for modbus communication. The guard bit setting was not available in versions prior to 1.5 and by default the automation server would send 3 stop bits causing the modbus communication to fail with the GR2400lighting controller. Resolution In SmartStruxure 1.5 right click on the Modbus Master Network and select properties. Click the advanced tab:         3. Here you see the guard bit setting. This value should be a 0 if the automation server is to ONLY send 1 stop bit. If this number is left at default the automation server will add the number of guard bits to the user       setting of stop bits. By default that makes 3 stop bits from the Automation Server. To properly communicate to the GR2400 the guard bit setting should be a 0 and the user selected stop bit should be a 1 in order to ONLY send 1 stop bit.

Issue Vista 5.1 license is not working.  Trying to launch Vista components results in error:  lc_checkout failed: Cannot checkout an uncounted license within a Windows Terminal Services guest session. Environment Vista 5 Terminal Services Virtual Machine VM Cause There is a special feature needed in the license which allows the use of Terminal Services. Resolution You must download the 14 day Demo TS Evaluation License on The Exchange Download Center. *note that Terminal Services are only supported in Vista 5

Issue Creating a bacnet schedule to control a 3rd party device generates the error:  “Bacnet operation rejected generated in response to a confirmed request apdu in which the service choice field specifies an unknown or unsupported service”  Environment Continuum 3rd party bacnet device Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The bacnet error occurs when dynamic creating of schedules is not supported in the 3rd party device and the packet gets rejected. Resolution An ethereal capture from the Cyberstation will show the packet getting rejected. A work around for this is to use a BCX to create the schedule and communicate to the 3rd party device.

Issue Notes from the field  on a Niagara R2 Modbus  RTU integration with an Eaton Series 2000 Xpert Power Meter. Environment I/A Series UNC licensed for the modbus asynch feature Eaton Series 2000 Xpert Power Meter Cause The 3rd party document is vague about  Modbus register-map differences between the IP and RTU protocols. Resolution 1. In order to obtain the Modbus RTU RS-485 map, you must look under the Eaton IQ-250/260 meter. The RS-485 map is NOT located anywhere under the Series 2000 meter. 2. There is also a utility in the "help" button when connecting to the embedded setup & monitoring software on the Eaton Power Meter. The Modbus map can be uploaded as an Excel spreadsheet, however, it is important to note that this map is the TCP/IP Modbus register map, not the RS-485 map. This can be accessed via a standard internet browser utilizing an Ethernet cable connection to the meter. The default IP address is 192.168.1.1. 3. The standard 5 digit Modbus register can be calculated form Eaton's Decimal register number by adding 40000 to the register number listed on their map For example, (register # 1000) (40000 + 1000 = 41000) for the Volts Phase A - Neutral value.  

Issue Date and time gets incorrect periodically in TAC Xenta Programmable controllers Time stamp in alarm list is incorrect Time stamp in alarm list is wrong  Vista Server local time and the local time in all Xenta controllers in the network go out of synch.   All local time settings are correct in TAC Xenta Environment TAC Xenta 30x/401/28x Cause The time in a TAC Xenta can be changed by TAC Vista TAC OP, note that a change of the time in one controller is broadcasted to the whole network. TAC Xenta group master will broadcast the time to it's group every 24 hours A Xenta Server (Xenta7xx, Xenta5xx, Xenta 913) Menta, this only affects the controller Menta is connected to. Most likely, the problem is a Xenta Server in the network that has the wrong time. It can be enough that a Xenta server is connected to the network, it does not have to be configured in this network.. Resolution Log in to Xenta server from the web interface. Go to Configuration-time If the date and time is incorrect set the correct date and time. Click on time synchronization, the lonworks time synchronization should only be set to enable  if this is a Xenta Server in TAC Vista or if this is a site that does not have TAC Vista on it and it is the only source to sync the time to.

Issue When starting the Vista Server, the splash screen displays the current state of the startup.  It gets to the "Trend Log Initialization" screen and then hangs. Product Line TAC Vista Environment Vista Server Cause Queued files in the $queues folder in the Vista database are being written to the SQL database.  If the queued files folder has grown very large, it can take a very long time (hours) to write this data to SQL.  If the connection to the SQL database has been broken, then it will take an infinite amount of time. Resolution Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. Allow time for the files to write the SQL Start Vista Server. Insure that TAC DSS Writer Service is running. When it gets to trend log initialization, leave the PC alone and allow time for the files to write to the SQL server.  If the size of the $queues folders are shrinking, then the process is working and after enough time, the server will start. Note: If you have cleared the $queues folder but it still hangs on trend log initialization, still allow plenty of time for the server to come up. There is a good chance that the Xenta controllers are passing all of their trend logs over to the SQL server. This could take hours or even overnight to complete. Delete the queued files If the data is not of dire importance, delete all the files inside both of the $queues folder.  For an efficient method for deleting many queued files, see An efficient method for deleting all queued files in the $queues folder. Check the SQL connection Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Remove TRL files This can also occur if the database has been upgraded from a lower versions, and still has information in the TRL files in the database. Stop the server Locate all TRL files in the $thisfil folder Delete any TRL file over 32Kb. Start the server again.

Issue An STR-104 can be used to monitor space temperature with a Xenta programmable controller. If a zone override is also required, the most straight-forward solution is to wire the override button to a digital input on the same controller. However, if those wires were not installed, or sufficient inputs are not available on the controller, the override button can be sent via the temperature sensor wires. Environment STR-104 Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause If enough wires were not run, or sufficient inputs are not available on the controller, the override button can be sent via the temperature sensor wires. Resolution The override signal sent via temperature sensor wires is accomplished by shorting the temperature sensor reading to ground. The Menta application senses this short and interprets it as a zone override. On the STR-104, short terminals 12 to 14 (Therm to Switch) On the STR-104, short terminals 11 to 15 (M to MX) Terminals 11 and 12 on the STR-104 go to M and B1 on a Xenta programmable (for example). Download this Menta macro for use in the programmable Menta application. While the button is pressed, the temperature will jump to a failed-shorted value of 300+ °F.  The attached Menta app will read in this jump, filter it out from a failed sensor, and enable an override for an adjustable duration.

Issue What TTS-SD-LED and TTS-SD-LCD Smart Sensors are available? Environment TTS-SD-LED Series • TTS-SD-LED-1 • TTS-SD-LED-B-1 TTS-SD-LCD-Series • TTS-SD-LCD-1 • TTS-SD-LCD-4-2 • TTS-SD-LCD-B-1 • TTS-SD-LCD-C-1-10P • TTS-SD-INFBUF Cause Some products in this range have become obsolete due to the discontinuation of some key components. Resolution Full details are on the attached Product Announcement PA-00171 TTS-SD-LED-1 Discontinued TTS-SD-LED-B-1 Discontinued TTS-SD-LCD-1 Modified TTS-SD-LCD-4-2 Modified TTS-SD-LCD-B-1 Replaced by TTS-SD-LCD-1 TTS-SD-LCD-C-1-10P Discontinued TTS-SD-INFBUF Discontinued

Issue If a binding variable is commended out in the program when the line is put back the binding is gone. Consider the following program... TheOUT3 binding variable is commented out... If the comment is removed and the line restored, the corresponding binding is NOT restored. Environment Workstation Script Cause Documentation Resolution This is functioning as designed, if the binding variable is removed in the program code, the associated binding is removed to avoid leaving an orphan binding. When the comment is removed and the binding variable is put back, you will need to re-bind it as SBO does not keep track of deleted bindings and can't automatically restore it.

Issue DC2000 series Optimiser / Compensator Controller requires replacement due to obsolescence. Product Line Field Devices Environment DC2000 series Optimiser / Compensator Controller installed to control Variable Temperature Mixing Valve, Boiler/s, Pumps etc. Cause Obsolescence of DC2000 series Optimiser / Compensator Controller. Resolution OVERVIEW DC2000 series Optimiser / Compensator Controllers are flexible with regard to the number and type of electrical inputs and outputs to which they may be connected, enabling the Controller to be applied to a wide range of control applications.  Overview details of the DC2000 Optimiser / Compensator Controller may be viewed here.    INSTALLATION AND COMMISSIONING In view of the numerous control applications to which the DC2000 series Optimiser / Compensator Controller may be applied, numerous wiring connection variations will also apply. Please therefore check the number of inputs and outputs connected to the DC2000 series Optimiser / Compensator Controller installed before proceeding, as this will assist in determining the suitability of the possible replacement Controller suggested below. Installation and Commissioning details of the DC2000 series Optimiser / Compensator Controller may be viewed here. POSSIBLE REPLACEMENT The most common control application to which theDC2000 series Optimiser / Compensator Controller may be applied comprises the following combination of inputs and outputs.  Outside Air Temperature Sensor Inside Air Temperature Sensor Compensated Heating Temperature Sensor Variable Temperature Heating Circuit Valve Actuator Boiler/s (2 maximum) H W S On/Off output (independent) Should such inputs and outputs be confirmed then the DC1100 Optimiser / Compensator may be installed in place of the DC2000 series Optimiser / Compensator Controller. Details of the DC1100 Optimiser / Compensator Controller may be viewed here. Drayton A7xx series Sensors connected to the DC2000 Optimiser / Compensator Controller are compatible with the DC1100 Optimiser / Compensator Controller and may therefore be retained. N.B. It should be noted that where a DC2000 series Optimiser / Compensator Controller is included in an installation of a more complex nature then an alternative solution utilizing different products may need to be considered. In such installations not only will the DC2000 series Optimiser / Compensator Controller need to be replaced but its associated Sensors will also need to be replaced. Resolutions to such installations may best be determined following a review of the control system installed by a member of the local Schneider Electric office.

Issue How to do alarm escalation in Continuum? Product Line Andover Continuum Environment PEAlmFunction, PERtnFunction Cyberstation Alarm Workstation PE function Cause The customer requires the ability to time how long an alarm is active, and based on its status (acknowledged-unacknowledged), escalate the active alarm, by email or other means. Should the alarm be acknowledged in time, the escalation does not occur. Resolution One method is to use the PEAlmFunction and PERtnFunction in a Workstation Program to capture the various alarm conditions off the alarm stack to trigger the activity that you want. As an example, the PEAlmFunction could be used to initiate a timer for the alarm by recording the time of the alarm and the alarm point. The PERtnFunction is then used to clear this recorded information if the alarm is acknowledged. A Workstation program is then used to constantly monitor this alarm information and comparing the recorded alarm time to the current time, if this is above the escalation time then a numeric is set to trigger another alarm that is then escalated. For details on how to configure the PEAlmFunction and PERtnFunction, consult Can Plain English interact with the Continuum Alarm Engine?

Issue Continuum ODBC Data Source does not appear in Windows ODBC Data Source Administrator. Continuum is operating normally in spite of this. Product Line Andover Continuum Environment CyberStation Windows 7 Cause Multiple possible causes Windows issue Known Continuum issue in 1.94 running in 64 bit machine. Resolution See Microsoft solution: System DSN Entries Do Not Appear in ODBC Data Source Administrator (odbcad32.exe) Continuum ODBC System DSN is not created on x64 Bit systems A workaround is to run c:\Windows\SysWOW64\odbcad32.exe and the Continuum ODBC is available.

Issue Site doors are configured for CARD+PIN but they have a short list of people that require the ability to access the door without a PIN Environment CyberStation Cause Documentation Resolution Click HERE for a sample PE program that will allow a list of Card Numbers to change the mode of the door to card only so they can gain access without a PIN, the program will switch the door back to CARD+PIN as soon as the special person goes thru the door.

Issue Processor % Loading and LAN % Loading; What do these mean and how can they impact my system. Processor % Loading -  This field displays the Controller processor (CPU) percent loading (0–100%). This number is an indication of how busy the controller is.  LAN % Loading - This shows the percentage of controller LAN communication attributable to this controller only. It is not the total control LAN loading figure. Product Line TAC INET Environment ALL I/NET Controllers (Controller LAN (CLAN) based) Cause A greater understanding of the values seen at each controller can greatly assist in having a more efficient I/NET network. Resolution The controller Processor % loading and LAN % loading are available from each controllers' configuration/status editor. You must be connected to the controller in order to use this editor. This information can also be obtained using the hand-held console, Code 3 (CPU %), and Code 4 (LAN %). These fields are display only. You cannot make changes. However, you can make changes to the database and observe the relative loading statistics after. The readings should be taken with all graphic pages and DCU controller point summaries closed. Processor % Loading This field displays the Controller processor (CPU) percent loading (0–100%).  This number is an indication of how busy the controller is.  If this number is 100, control actions may be lost or delayed. You should not let this reading go above 80%.  If kept to below 80% then if the processor peaks for some reason, it has 20% to peak in without locking up for a number of processor machine states. The conditions that affect the processor loading are as follows: Resident Point scan interval.  All resident points are processed by the firmware.  If you find that the processor loading is high, then edit all the AOs and DOs that do not have a calculation extension and adjusting the scan intervals to 255 seconds.  In heavily populated controllers this will bring down the processor % loading somewhat. Calculated Point frequency.  All resident points with a calculation extension will have their calculation processed at the scan interval of the target point.  If you find that the processor loading is high, then, on the calculation extensions that perform less important tasks, you may edit the target point’s scan intervals to a larger figure. Event Initiated Sequences.  A number of sequences that are in a loop, that is to say, running sequences with a skip back to themselves causing the sequence to run continuously, will cause the processor % loading to rise.  Edit and modify to create a more efficient database.  Ensure that a minimum of 1-second delay is implemented between each action within a sequence.  Do not leave all actions at the default value of zero.   DDC Module Sample Interval.  All DDC modules are processed at their respective sample interval.  If you find that the processor loading is high, then, on the DDC modules that perform less important tasks, you may edit the DDC module’s sample rates to a larger figure. Global or Indirect Traffic.  Naturally, large quantities of global and or indirect traffic to and from the controller will cause the processor % loading to rise.  See the next section “LAN % Loading” for more details. Graphic Pages and or Controller Point Summaries.  Graphic pages and or controller summaries with large quantities of points requesting information/data (solicited messages) from a controller will cause the processor % loading to rise.  This also includes the number of pages open either on the one host or multiple hosts.  You have a number of choices here; you could increase the host’s “Monitor Refresh Interval” to minimize the solicited traffic or you could rationalize the graphic pages to a more efficient use of points. Alarm or Messages.  Large quantities of alarm or message traffic (unsolicited messages) from the controller will cause the processor % loading to rise.  You will have to identify the cause.  Be aware just taking out the matching message masks from the host or from the point will not inhibit the message from transmitting to the LAN, the Resident Point’s Message and or Alarm priority must be set to “None”. SEVENTRENDS Data Uploads.  Large quantities of SEVENTRENDS data (unsolicited messages) being uploaded to the LAN from the controller will cause the processor % loading to rise.  You will have to identify the origin and alter the “Cell Sample Counts” and or the “Sample Control Interval” to relieve the condition.  Be aware just taking out the Host SEVENTRENDS Cell mask or the point’s Trend Sample SEVENTRENDS Distribution Mask will not inhibit the data from transmitting to the LAN, the SEVENTRENDS Distribution Priority must be set to “None”.  LAN % Loading This shows the percentage of controller LAN communication attributable to this controller only.  It is not the total control LAN loading figure.  Treat the control LAN as a 100% resource.  If this controller has a LAN percent loading of 23%, then the control LAN has only 77% of resources left to service the other controllers on the control LAN. Another way to look at it is, in the above example, out of every 100 token passes on the control LAN this controller has used the token 23 times. The best scenario is to have the lowest figure possible, e.g. 0%.  Just imagine a control LAN with 25 controllers connected, each controller with a ‘LAN % loading’ of 5 %.  The LAN is flooded and will cause messages to be lost and or buffered, graphic pages will not update as expected and the system will dramatically slow down. The empirical rule is as follows: The ‘LAN % loading’ is allowed to rise to a figure above 0%, but within 20 seconds, it must go back to 0%. The conditions that affect the ‘LAN % loading’ are as follows: LAN Reconfigures.  Every time a LAN reconfigures all global points in every controller on that control LAN transmit their values on to the LAN, and all indirect points request, at their scan interval, an update from their associated global points.  On an unstable control LAN, this could contribute heavily to a controller’s ‘LAN % loading’. Global Point Traffic.  Large quantities of global point traffic from the controller will cause the ‘LAN % loading’ to rise.  The conditions that affect the frequency of global traffic are: Global point’s “Broadcast Change Counts”.  Remember that multiplying the analog point’s conversion coefficient’s ‘m’ value with the broadcast change count value will be the resolution of the analog value to be exceeded to cause a broadcast onto the LAN. Just imagine a globalized analog point with a ‘m’ value of .05 and a Broadcast Change Counts set at 1.  Then this sensor will globalize its value every time the value exceeds 0.05 creating globalized traffic. The faulty sensor being globalized.  The sensor’s value being unstable to the extent that the point’s value changes exceed the “Broadcast Change Counts”, in extreme cases creating globalized traffic. Controller’s Power Line Frequency, HHC function [Ctrl 92], not set correctly.  This is for setting a notch filter to filter out power supply noise being imposed over the sensor’s input signal thereby helping to eliminate the sensor’s value appearing to fluctuate.  These fluctuations could send a global sensor’s value change to exceed the “Broadcast Change Counts” in extreme cases creating globalized traffic. Pulsed Input (PI) points.  The PI points “Scans between Broadcast” incorrectly assigned. Beware: a PI point with a “Scan Interval” of 1 second and a “Scans between Broadcast” set at 1 second will cause the controllers ‘LAN % loading’ to rise by 10% and stay there, even though the PI point’s value may not have changed. Indirect Point Traffic.  Large quantities of indirect point traffic from the controller will cause the ‘LAN % loading’ to rise.  The conditions that affect the frequency of indirect point traffic are: LAN Reconfigures.  Every time a LAN reconfigures all indirect points, at their scan interval, request an update from their associated global points.  On an unstable control LAN, this could contribute heavily to a controller’s ‘LAN % loading’. Indirect Point scan intervals set incorrectly.  If an indirect point does not see a change in its state/value from the global point after 2 scan intervals then the indirect point will request an update from its associated global point to be reported at the indirect point’s 3 rd scan.  With global points that are reasonably static, i.e. not altering a lot e.g. status points, etc., the associated indirect points will carry out their requests for updates.  Therefore the indirect points scan intervals should be staggered system-wide, not just controller-wide.  If all the indirect points have the same scan interval they could conceivably request at the same time and queue and hang onto the control LAN’s token. Graphic Pages and or Controller Point Summaries.  Graphic pages and or controller summaries with large quantities of points requesting information/data (solicited messages) from a controller will cause the ‘LAN % loading’ to rise.  This also includes the number of pages open either on the one host or multiple hosts.  You have a number of choices here; you could increase the host’s “Monitor Refresh Interval” to minimize the solicited traffic or you could rationalize the graphic pages to a more efficient use of points. Alarm or Messages.  Large quantities of alarm or message traffic (unsolicited messages) from the controller will cause the ‘LAN % loading’ to rise.  You will have to identify the cause.  Be aware just taking out the matching message masks from the host or from the point will not inhibit the message from transmitting to the LAN, the Resident Point’s Message and or Alarm priority must be set to “None”. SEVENTRENDS Data Uploads.  Large quantities of SEVENTRENDS data (unsolicited messages) being uploaded to the LAN from the controller will cause the ‘LAN % loading’ to rise.  You will have to identify the origin and alter the “Cell sample counts” and or the “Sample Control Interval” to relieve the condition.  Be aware just taking out the Host SEVENTRENDS Cell mask or the point’s Trend Sample SEVENTRENDS Distribution Mask will not inhibit the data from transmitting to the LAN, the SEVENTRENDS Distribution Priority must be set to “None”.  

Issue Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server Shadow Schedule in the ES syncs successfully to Lead Schedule in the AS Lead and Shadow Schedules in different AS are syncing successfully Product Line EcoStruxure Building Operation Environment SmartStruxure 1.x Cause Traffic is blocked by Windows Firewall.  Resolution Disable Windows Firewall. Disabling the firewall may not be possible due to security concerns, Exceptions can be added to Windows Firewall for ports that are used by SmartStruxure. Refer to Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port for details. If this doesn't work, please refer to Shadow Schedule in AS isn't synchronized with the Lead Schedule in ES.

Issue Personnel does not have access. Invalid Attempt messages stating "Personnel record is not yet active" seen in the Access Events. Product Line Andover Continuum Environment Continuum Access Control Cause Personnel object Activation Date attribute is set to a future time. Resolution Open the Personnel object and confirm the Activation Date and Expiration Date fields are realistic. Make sure the Activation Date is in the past. Check that the time on the Controller and Cyberstations are synchronised properly. See Configure Time Zone and UTC Offset settings so that time is synchronized across your system for how.

Issue When viewing WebReports within WorkStation or Internet Explorer the report data is not shown. All that is seen is a blank screen even though the menu items are still displayed (as shown in Figure 1 below). Figure 1:: Report viewed through WorkStation (Or Internet Explorer) When viewing the same WebReport through a different browser, Chrome or Firefox the report displays correctly Figure 2:: WebReport viewed using other Browsers (such as Chrome and Firefox) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebReports EcoStruxure Building Operation WorkStation Cause The issue has only been seen with Internet Explorer since the other browsers appear to work. Since Building Operation WorkStation uses Internet Explorer as its internal browser, the problem is seen when displaying WebReports within WorkStation. To confirm that this is the issue you can check the Windows Event Log contents (Application Log Warnings) related to: <Provider Name="ASP.NET x.x.xxxxxxx.x" /> ... <Data>/LM/W3SVC/1/ROOT/SchneiderElectric/WebReports-1-131958191596842252</Data> <Data>Full</Data> <Data>/SchneiderElectric/WebReports</Data> <Data>C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation WebReports\WebReports\</Data> <Data>CultureNotFoundException</Data> <Data>Culture is not supported. Parameter name: culture 4096 (0x1000) is an invalid culture identifier. at System.Globalization.CultureInfo.InitializeFromCultureId(Int32 culture, Boolean useUserOverride) at Microsoft.Reporting.WebForms.ReportDataOperation..ctor(IReportServerConnectionProvider connectionProvider, Boolean requiresFullReportLoad) at Microsoft.Reporting.WebForms.HttpHandler.GetHandler(String operationType, IReportServerConnectionProvider connectionProvider) at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)</Data> Resolution To correct this issue ensure that the Windows Regional Language, found in the Windows Control Panel matches between the Workstation PC and the Reports Server.

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries   Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier'  field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue Necessary Accounts for DCOM and Firewall Security Settings. Product Line TAC Vista Environment TAC Vista Webstation TAC Vista Remote Workstation DCOM Configuration Cause DCOM Parameters must be set to allow for remote connectivity to the Vista Server. Resolution You will notice in the "Security Settings for MS Windows XP SP2 and MS Windows Server 2003 SP1" instructions that several changes are needed for the accounts "ANONYMOUS LOGON" and "Everyone". If these accounts do not exist, they must be created and set to allow local launch and remote activation permissions. See also Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for an automatic DCOM utility.

Issue Transfer pressure values with units of inches of water between I/NET and LON with a 913/527/731. Environment I/NET Xenta 913/527/731 XBuilder Cause When reading pressure from LON, the value is always in metric units, Pascals, on the LON wire. When the value comes into I/NET, it will be a large, unexpected number. Resolution To read in a LON pressure value into I/NET: Create two internal points in I/NET. AO to receive the raw pressure value in Pascals AI to perform the conversion to inches of water Add a calculation to the AI to perform the conversion: P0*C0 P0 = AO created to receive the raw pressure value in Pascals C0 = 0.004 to convert value from Pascals to inches of water Set the connection object in XBuilder: From = LON SNVT_press To = AO to receive the raw pressure value The AI should be reading the correct value in units inches of water. To write a setpoint value out of I/NET to LON: Create two internal points in I/NET: AO where the user enters desired static setpoint in inches of water AO to perform the conversion to Pascals Add a calculation to the AO to perform the conversion: P0*C0 P0 = AO created to enter desired static setpoint in inches of water C0 = 249 to convert value from inches of water to Pascals Set the connection object in XBuilder: From = AO to perform the conversion To = LON SNVT_press The SNVT should be reading the correct value in desired units.