Building Automation Knowledge Base

Issue Setting up ID Works on a Remote Client PC Product Line TAC INET Environment I/NET Seven ID Works Windows XP Windows 7 32-bit Windows 7 64-bit Cause Configuring the I/NET System to be a “Server/Remote Client” format and the ID Works software is going to be on a Remote Client PC. Resolution The first procedure is to modify the ODBC Data Source. The steps for this are very dependent upon the PC's operating system. Reference page 2-14 through 2-23 of TCON 301, the chapter named Modifying TAC I/NET Seven's ODBC Data Source.  Once the ODBC Data Source is configured, proceed with the steps below: Go into the ID Works Administrator Editor and select the System tab. Scroll down to the Photo Path option. Direct the current path to the PC that is going to be the Server. In this example, the PCs Name and Photo location is: \\TPServer\CDrive\I7photos   Go into the ID Works Designer Editor open each of the site badge templates and modify them for the Server PC link. Open one of the templates. Highlight the Image path square and do a right mouse click. Go to the Field Properties option. Set the path to the Server PC location for the badge photos. See the example below for further information.   In this example the server PC is named TPServer. Badge photos are in the C:\I7photos\Thumbnail directory. There are only eight pictures entered at the time these captures were made. The jpegs for those eight individuals were saved to the folder using the CardNumber as the name shown below:

Issue Audible alarms not sounding when there are active alarms. Workspace has multiple tabs for graphics navigation and a tab for Alarm View. If a user is not on the alarm tab when an alarm is activated, the audible alarm is not heard, and the user does not know that an alarm has been activated. The audible alarm works when the user navigates to the alarm tab.  Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation Cause The Workspace content does not have an Alarm Pane added.  Resolution Edit the Workspace to add an Alarm Pane to the Workspace content. If the user does not wish to display the Alarm View due to screen space etc., configure the Alarm Pane Default visibility to Hidden.  Note: Audible alarms are available in WebStation from 3.2 onward.

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 An ACX5740/CX9680 does not provide access events to Cyberstation 1.81. Environment Cyberstation 1.81 or earlier version SQL Server 2005  Cause The ACX 5740/CX9680 was running version 1.1xxxxx/2.1xxxxx firmware. This version of firmware is incompatible with Cyberstation versions 1.81 and earlier. Resolution The site was offered the option of upgrading the version of Cyberstation to 1.9x, or down-reving the ACX 5740/CX9680 to version 1.0xxxxx/2.0xxxxx. Flash down-reving the controller was chosen and did resolve the access event delivery issue.

Issue ACCTrace and Windows error log show multiple DBFaultDetection, SQLSTATE ERROR CODE:  S1000, ERROR MESSAGE:  [Microsoft][ODBC SQL Server Driver][SQL Server]Warning: Fatal error 823 occurred Environment CyberStation Cause Device (disk) error. Resolution Recommended course of action from Microsoft: Error 823 Severity Level 24 Message Text I/O error %ls detected during %S_MSG of %S_BUF. Explanation Microsoft SQL Server encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. The parameters in the error message refer to internal structures and don't often help determine which device is involved. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved. Action Check the accessibility and condition of the device in question. After you have identified and corrected the problem, execute DBCC CHECKDB to ensure that no other damage was caused by the bad device. For information about using DBCC CHECKDB, see "DBCC CHECKDB" in Microsoft SQL Server Transact-SQL and Utilities Reference. Important If executing DBCC CHECKDB with one of the repair clauses does not correct the index problem or if you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider. In addition, run hardware diagnostics and correct any problems

Issue When browsing to the LNS database on the new NL220 project screen, an error message says, "Setting NeuronID of router <%s> ..._O" Product Line Other, TAC Vista Environment Lonmaker Newron NL220 Cause The name of the database folder is over 12 characters. For example, C:\LM\Db\367_Collins_St Resolution To correct this error, rename the folder containing the lonworks database to 12 characters or less. The above example folder name in the Cause heading could be renamed to  C:\LM\Db\367CollinsSt

Issue Some X Drivers on the Third Party Interface datasheet are classed as 1st Generation and others are 2nd Generation, which drivers should I use? Product Line Andover Continuum Environment All X Drivers Any controller with XDrivers enabled on a Comm port. Cause Sometimes the incorrect file is being used on a controller and this will stop the X Driver from working correctly. Resolution You can only use a 1st Generation X Driver on a 1st Generation controller and a 2nd Generation X Driver on a 2nd generation controller. - 1st Generation controllers are: CX9200, CX9400, CX9900, CX9940, CMX9924 - 2nd Generation controllers are: Netcontroller II (CX9680), bCX1 (4040 or 9640), ACX II (5740, 5720)   Download the Third Party Interface datasheet Note: Not all X Drivers are available for both generations of controllers, consult the above datasheet for availability.

Issue Is a license required for the S4 BACnet to N2 Routers? Environment S4 BACnet to N2 Router-16 S4 BACnet to N2 Router-32 S4 BACnet to N2 Router-64 S4 BACnet to N2 Router-128 S4 BACnet to N2 Router-256 I/A Niagara R2 I/A Niagara G3 I/A BACnet Metasys N2 network Cause Additional information on 3rd party router Resolution No license is required. But you will need to fill out the S4_Group_Order_Form and send it to CCC at the time of ordering. Link to S4 BACnet to N2 Routers for additional information

Issue In the TAC Vista System Plug-In, a programmable controller is configured through the Xenta Device Plug-In. Browsing to a Menta file on the hard drive should associate that application with the controller to be uploaded to the database later. Instead, an error message is displayed:   TAC Xenta Device Plug-In Could not generate MTA application Environment TAC Vista System Plug-In TAC Xenta Device Plug-In Xenta programmable controller Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause An error in the Menta file is keeping it from generating the necessary background files for the download to occur. Resolution Open the Menta file Go to Options > Simulate If no error occurs, choose Commands > Generate Either at simulation or at generation, an error should be highlighted in the Menta file that is responsible for the failure to generate. Fix this error and save the Menta file back to the hard drive. Attempt to browse in the Menta file again.

Issue In WorkPlace Tech can a SNVT exist in a Custom Object? Environment I/A Series WorkPlace Tech 4.0 and higher. Cause Custom Object Rules Resolution Nearly all types of WP Tech shapes may be included on the Definition page of a Custom object, There are several exception and  "SNVT objects"  is one of them. This object must be on the top page of any control logic drawing instead. For  additional  exceptions see WorkPlace Tech Tool 4.0 Engineering Guide (F-27254-3), Chapter 3 "Custom Object Rules"

Issue Transformer for I/NET Controllers Environment XFMR1, XFMR2, XFMR3, XFMR4, XFMR5, XFMR6, XFMR7, XFMR8, XFMR9, XFMR10, XFMR11 IRB8, IRB8HC Relay boards 7700, 7740, 7741 DCUs 7750, 7760, 78XX, 72XX UCs, 7716 7718, 7780, DPU3100, DPU7910A, DPU7920 78XX TAPs 7780 DLCU 7728 I/SITE I/O Cause The following table describes each transformer, the primary power required, the secondary power supplied by the transformer and the products each transformer model supports. Some of these transformers have two secondary outputs and these are shown in the table. Resolution Download the attached PDF document here. Model Number Description Comments XFMR1 Transformer, 120Vac Primary, 20Vac @ 3.4A Secondary IRB8, IRB8HC Relay boards XFMR2 Transformer, 120Vac Primary, 10Vac @ 3.6A and 36Vac @ 0.7A Secondaries 7700, 7740 7741 DCUs XFMR3 Transformer, 240Vac Primary, 10Vac @ 3.6A and 36Vac @ 0.7A Secondaries 7700, 7740, 7741 DCUs XFMR4 Transformer, 120Vac Primary, 13.5Vac @ 2A and 24Vac @ 2A Secondaries 13.5Vac for baseplate mounted 7750, 7760, 78XX. 24Vac for 72XX UCs, 7716 XFMR5 Transformer, 240Vac Primary, 13.5Vac @ 2A and 24Vac @ 2A Secondaries 13.5Vac for baseplate mounted 7750, 7760, 78XX. 24Vac for 72XX UCs, 7716 XFMR6 Transformer, 120Vac Primary, 24Vac @ 2.4A Secondary 72XXUC, 7716, 7718, 7780, DPU3100, DPU7910A, DPU7920 XFMR7 Transformer, 240Vac Primary, 24Vac @ 2.4A Secondary 72XXUC, 7716, 7718, DPU3100, DPU7910A, DPU7920 XFMR8 Transformer, 120Vac Primary (plug-in), 13.5Vac Secondary (DIN connector) 7750, 7760, 78XX TAPs XFMR9 Transformer, 277Vac Primary, 24Vac @ 2.4Vac Secondary 7780 DLCU XFMR10 Transformer, 120Vac Primary, Dual 24Vac @ 2A Secondaries 7728 I/SITE I/O XFMR11 Transformer, 240Vac Primary, Dual 24Vac @ 2A Secondaries 7728 I/SITE I/O

Issue Replacement of Satchwell Sunvic control devices. Environment On / Off temperature control applications  Domestic installations. Cause Satchwell Sunvic control device requires replacement.. Resolution Satchwell Sunvic Ltd. was a sister company of Satchwell Control Systems Ltd. Satchwell Sunvic Ltd. primarily manufactured domestic Thermostats and Central Heating Programmers etc. Satchwell Sunvic Ltd. was sold to another group of companies and left the Satchwell Group of Companies. At that time all Satchwell Sunvic Ltd. ON/OFF control devices were transferred to that group of companies.   There are currently no equivalent products in the Schneider Electric / TAC / Satchwell range of products. Satchwell Sunvic Ltd. now trade as Sunvic Controls Ltd. and may be contacted as follows :- Sunvic Controls Ltd. General Enquiries :- T: +44 (0) 1698 812 944 F: +44 (0) 1698 813 637 Email. enquiries@sunvic.co.uk Technical Helpline :- T: +44 (0) 1698 810 945 Email.  technical@sunvic.co.uk

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 User can’t disable the fan in heating mode Product Line EcoStruxure Building Expert Environment   SER7000 | SER8000 Cause  Misconfiguration of the thermostat Resolution SER7300 In some application, the device may control baseboard heat or different controls and the user may want to stop the fan in heating mode. The user shall set the Pulsed HT parameter to ON and Fan Cont to Off Auto and this will solve the issue. SER8300 The user shall set Fan Cont to Off Auto and this will solve the issue.

Issue Badge layout (.dgn file) is set for landscape orientation. Print preview looks good. Attempt to print  a badge on a MagiCard Rio 2E. Badge prints with portrait orientation. Environment CyberStation MagiCard Rio Cause Magicard Rio driver properties has a selection for "Application Determines Orientation". If this printer properties setting is selected and the printer properties orientation setting does not match the application orientation setting (Continuum Make/Edit Badge, i.e. EPIDesigner ), the printout may not be what is desired.  Resolution Check the Magicard Rio driver properties setting for "Application Determines Orientation". Make sure, if this printer properties setting is selected, that the printer properties orientation setting matches the application orientation setting in EPIDesigner. 

Issue Troubleshooting guide for LON bus communications Environment MNL controllers (MNL-50, MNL-100, MNL-110, MNL-130, MNL-150, MNL-200, MNL-V1R, MNL-V2R, MNL-V3R) Cause Troubleshooting guide for LON bus communications Resolution TPA-RKFD-09-0011.00 is a checklist which provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document.

Issue Customers wanting to use a Barcode Reader for door access Environment Access Control site wanting to use Barcode Readers Cause Barcode Readers often are a higher  Resolution I/NET The SCU is the best you could have so that makes it easier with memory requirements and so forth. Since you have the SCU, set it up for 26-bit Wiegand (2 parity bits and 24 data bits). It would look like this: e eeeeeeee eeeeooooooooooooo o That is a 1-bit starting bit, even parity, 8-bit facility code, site number, card number, 16-bit segment, and the 1-bit ending parity (26 bits all together). That is how many data bits the reader normally takes. 26-bit Wiegand is typical and most common. The true bits are the facility code, site and card number. The beginning and end is the parity. For more information, see TCON300, beginning on page 9-59. This is the key card translations section, and may be valuable in figuring out the solution to the bar code reader. Lastly, one idea is to contact a company called RFIDeas.com. They make a bar code reader that may be a solution. If the bar code reader is outputting a card number larger than 16 digits, convert it to 26-bits of Wiegand data (it can handle up to 64-bitWiegand). If it goes over 64-bit, they have a special firmware which allows up to 254 bits of wiegand data. With the SCU, the 26-bit is the standard. Code 128 is used to barcode INET products. The Cypressworld CVX-1300 is an alternate solution for connection between the I/NET SCU and the Barcode Reader. Continuum Code 39 is used to barcode the serial number on Continuum and Pelco boards.  Most readers can auto switch between these and other code types.  

Issue A GCM / LCM stops working and displays the error message "Insufficient System RAM".  It no longer responds to information requests via the front panel keyboard/display nor via XPSI software connected on either of the available serial ports. A power cycle restores functionality but only for a limited amount of time (ie: hours or days). Environment Network 8000 GCM-84000 series GCM-86000 series LCM-84000 series LCM-85000 series LCM-88000 series Cause Free system ram drops below minimum requirements: Any GCM with sys ram below 18k Any LCM with sys ram below 10k Resolution The amount of free system ram must be kept above minimum requirements. Use Tech Bulletin 95-33 for troubleshooting the GCM / LCM.  It is a comprehensive guide providing both hardware and software suggestions that will increase free system ram.

Issue When changing an ARM/X/E type actuator that was mounted on an MB or MBF valve a new linkage kit is required. Environment Valve MB MBX MBF ARE ARX ARM Linkage Actuator MD Cause When fitting a new stype actuator to an MB/MF valve a new linkage kit is required. Resolution MD20a/b Linkage kits MB-914-1071-000 MBF-914-1070-000 (Use self tappers that came with the act to fix the linkage) If you have auxiliary switches you will also need to purchase the aux SW kit for the MD10/20 b = MD-S2 Click here to view the data sheet for the MD20 B actuator, where you will find further information.

Issue RM3601 / XRM3201 Wiring connection details. Environment RM3601 3601 XRM3201 3201 Actuators Wiring connection details Cause Actuator wiring details. Resolution The RM3601 actuator is a 230 volt actuator, its connection details are as follows; Terminal 1 - Connection for open signal (230V live) Terminal 2 - Connection for close signal. (230V live) Terminal 3 - Connection for Neutral. Terminal 1T - Transfer connection, passes 230V to other devices when actuator is open. Terminal 2T - Transfer connection, passes 230V to other devices when actuator is closed. The XRM3201 actuator is a 24 volt actuator, its connection details are as follows; Terminal 1 - Connection for open signal (24 volts) Terminal 2 - Connection for close signal. (24 volts) Terminal 3 - Connection for zero volt. Terminal 1T - Transfer connection, passes 24V to other devices when actuator is open. Terminal 2T - Transfer connection, passes 24V to other devices when actuator is closed. To review the data sheet please select HERE.