Building Automation Knowledge Base

Issue The I/A Series G3 ENC ASD driver tunnel is enabled however the Status indicates {fault} Environment I/A Series G3, ASD Driver, ENC-520 Cause The {fault} typically occurs when two or more tunnels are configured and simultaneously enabled for the same communications port and/or tunnel identifier. Resolution Add the tunnelService to the ENC station Services.  Note: Do not add a SerialTunnel object to the tunnelService for tunneling to the ASD devices. The ASD driver includes the necessary tunnel software components that operate with the tunnelService. Verify the tunnelService is enabled (true) and the Status indicates {ok}. View the Property Sheet of the AsdNetwork and expand the Tunnel settings.  Verify the Tunnel is enabled (true), the Identifier indicates IbsAsd, and the Status indicates {ok}.

Issue What is the best way to retrieve Logged data. Environment Logged data Logging Log retrieval Cause Sigma logged data is not always available to view, what is the best way to retrieve logged data from the Sigma controllers? Resolution Sigma controllers and IC's have the ability to upload logged data to the Sigma server when required, this is carried out when the controller data tracks are a certain percentage full. This is the best way of retrieving logged data. However this can be random and there will be occasions when a user wishes to see data that has not yet been uploaded. If the user wishes to retrieve logged data from the controllers, there are two methods that can be used. 1 -The first method is to manually instruct the controller to upload its logged data. Using "System Diagnostics" select the required controller, and from the "Options" menu choose to upload "All Logged data" or "Selected Logged data". This action will return the data, which can then be reviewed. 2 - The second method is to create a scheduled retrieval. Enter "System Setup" and choose "Scheduled Actions".  This option allows you to set the time that action occurs and can specify which controllers are affected. Select "Actions" and add a new one. The screen shot below shows that "Retrieve Controller Logs" has been selected, and this will apply to "All Controllers" Depending on the number of controllers present on this site, it may be better to retrieve the logs from groups of controllers at a time. The screen shot below shows the configuration for controllers 1-20. Having created the action, a schedule must be added. If a number of schedules are created it is suggested that they are timed to run at least 15 minutes apart.

Issue Using a Sigma DNN (Distributed Network Node) as a repeater Environment Satchwell Sigma ARCnet communications Cause There is no repeater in the Sigma products range to increase the maximum distance of a Sigma ARCnet LAN. See below tables for the maximum distances for various baud rates.  Resolution From an additional Sigma DNN on the backbone LAN, an ARCnet cable is run for up to x number of meters (distance depends on the baud rate and cable used) to another Sigma DNN (DNN port1 to Sigma DNN port6). Note: No Sigma controllers on the joining LAN. DNN has to be dual trunk version

Issue 7718 and Expansion Modules Environment I/NET Site Cause What Expansion Modules come with the 7718 controller? Can those be bought separately? Can the ribbon cable or stand-offs be purchased separately from the P16UI expansion module also referred to as the P16UISO Resolution P16UISO 16 Point Universal Input Module 7718 PCU module, 8.6” x 3.4” (21.8 cm x 8.6 cm). Standoff mount. The Sixteen Point Universal Input (P16UI) expansion module provides sixteen universal (analog or contact) inputs. The expansion module card is 3.25"L x 8.60" W (8.25 x21.8 cm). It attaches on top of the 7718 with standoffs supplied with the module. Signals are passed from the P16UI through a ribbon cable type connection between the terminals of the two boards. The input points on the Sixteen Point E16UI Expansion Board occupy point addresses 0100 through 0107 and 0200 through 0207. Please find the 7718 Expansion board Input testing procedure below. Also here is the Datasheet Below is the part number from iPortal: This is the Model numbers and brief description:  Expansion Board Testing Procedure: 7718 Expansion board Input testing All 8 AIs (TBX1-1,4,7,10 and TBX2-1,4,7,10) come in thru the same analog multiplexer IC U3. The only components in front of the Mux is a .47uF capacitor on each input and a 100K resistor on each, and then the user plug-in resistors. I assume reference to TBX1 is associated with 1st input channel on pin 1 and 249 ohm is being plugged in to SIP socket RS3 position A1. Assuming no other resistors are plugged in to any of the Bx, Cx or Dx positions, there isn't much left that can be wrong. Get the specifics of what input signal level is causing what count to be seen. Use M & B of 1 & 0 to report straight counts. Make voltage measurements on the TBX1-1 and TBX2-1 terminals with signal being injected, and record the counts seen on the HHC, or PC, for a low medium and high level signal. An external power supply can be used in place of the sensor to easily set a 0V, 2.5V and 4.90V signal input. We want something less than 5V so we don't get the high end max count of 4095 which can mask a high end + error. If they don't have a supply, differing values of resistance can be plugged in to positions A1 (pull down) and B1 (pull up) with J10 set to B-C position so the B positions are pulling up to 5V. 1K in A1 position and B1 open produces 0V input. Measure and confirm volts and counts 1K in both A1 and B1 positions produces mid scale of approx 2.500. Measure and confirm volts and counts 10K in A1 and 1K in B1 positions produces high end of approx 4.545V Measure and confirm volts and counts This can be repeated on TBX2 using resistor positions A5 and B5 The A/D Counts should equal (measured volts / 5 * 4095) 2.500V = 2047 counts 4.545V = 3722 counts See what the above shows as a possible indication of where something is going awry. An A/D count that is correct on one input and wrong on another with only the specified resistances plugged in, or no resistances plugged and an external voltage source being used, would suggest a faulty multiplexer chip (on only specific selected channels) or a faulty capacitor. Return for repair.  

Issue When controlling I/NET DO point in Vista, for example changing the value from "0" to "1", the value of the point won't stay. It changes back to "0". Environment I/NET integrated to Vista (I2V) Cause There are several attributes of an I/NET DO point (shown below in Vista). Usually the "control" attribute is used to manually control the DO point, while "value" is used to monitor the current state of the DO. If the "control" attribute is changed from "0" to "1", the real DO point will be on, but value of this "control" property point will change back to "0". Resolution Use the "control" attribute to manually control the DO point. Use the "value" attribute to monitor the current state of the DO point.

Issue Selecting the tick box option for the VisiSat server to update the time on the LAN connected, does not work. On an SNP LAN the controller time is not updated even if the VisiSat server is restarted. On a VisiView installation this means the controller time is not automatically updated. Environment VisiSat VisiView SNP IAC LAN Server Time Update Cause Unknown at this time, no fix planned. Resolution The suggested work around would be to supply a Touchscreen (IAC-TS) and possibly a Remote mounting kit (DDC 2601), if the site does not currently contain a Touchscreen. The Touchscreen can then update the time in the controllers on the SNP LAN with the time contained in the Touchscreen. Updating the time in the Touchscreen would have to be done manually. The controllers would have to be re-addressed and the VisiSat project would require reconfiguring for the new controller addresses. Additionally if the site is running a VisiView project, the VisiView project would also need to be re-engineered to align it with the new controller addresses.

Issue The stop watch object operates erratically when set to days. If you set the stop watch to issue a pulse once a day it can issue a pulse 2 or 3 times during the day. Environment VisiSat Bubbleland Stopwatch   Cause Software/firmware error. No fix planned. Resolution When programming a stop watch do not use days. Instead of 7 days  use 168 hours  Instead of 14 days  Use 336 hours  If there is a requirement to convert the value back to a day for MicroNet View graphical representation, A suggested method follows: -   In VisiSat find the stopwatch object.  Add the Stopwatch Rollover to the VisiSat points list. Under the menu topic Tools Export your points list to MicroNet View.   In the MicroNet View project manager and load the new points. To view the hour value received from the controller as weeks on the graphical interface. Open MicroNet View in Development mode (Window Maker) Open the window that the value will be added too. Add some text to the Windows you want to display the value. For example “###” To view the rollover value, add the tag for the stop watch rollover value. To show the value as weeks add /24 after the tagname. Below is an example of both showing the results. This can be achieved using a data change script. In MicroNet Window Maker (Development mode) add a tag and data change script. The tag could look something like this. The minimum and maximum values of the tag can be changed to provide limits. The data change script could look something like this.  To display and allow the user to change the value in weeks. Add some text to the Windows you want to display the value. For example “###” Inside the "###" should be set for "user inputs Analog" (Analogue)  Click on "user inputs Analog and select the data change tag created earlier.  Using the example from above, the window will now look like this  To set the rollover in days click the days set area.  Change to the required amount of days. Hit the return key to enter the value.  The Rollover is now set to 14 days. It is important to remember the rollover value in the controller its not 14 it is the hour value 336. It is just at the MicroNet View front end/user interface window where it is displayed as days.

Issue Questions on the relationship between the area links in a personnel template and the links in derived personnel objects. Environment CyberStation Cause Documentation Resolution Q.  Personnel already has a Template assigned...What happens to the Area list when a different Template is assigned? Specifically, to the Areas already listed, will only the new Templates Areas be left or Is it a union or something else?  A. When the template is re-assigned the personnel objects will drop all areas that come from the template and pick up the areas from the new template. Areas that were assigned separately from the template (loose areas) will remain. Also, when changing the template the system will prompt you with several options to choose from for how to handle the attributes that are linked to the template.   Q. 2 Personnel has some Areas already assigned...What happens when that Personnel is assigned to a Template? A. Those areas that are not associated with a template (loose areas) will remain, the areas from the template are added to the person’s area list. Q. 3 Personnel has a Template already assigned...What happens when Areas are added individually? A. Those areas added individually (loose areas) are simply added to the person’s area list, template manipulation has no effect on loose areas.

Issue The nviStPointOffset in the Xenta 102-AX controller will not hold a value when it is entered in Vista Workstation or through the browser in LonMaker/NL220. Environment NL220 LonMaker Vista Workstation Xenta 102-AX Plug-in Cause There are two possible reasons for this issue: If there is a SNVT bound to nviStPointOffset, then the value that is manually entered will be pushed out every time the SNVT value is sent across. The Stat Adjustment Range in the Xenta 102-AX plug-in may be set to low causing the value too not hold. Resolution First check in LonMaker/NL220 if there is a SNVT bound to nviStPointOffset. If there is a binding here then it will either need to be broken or the point will not be able to be overridden. If there is no binding then move on to step two. Open up the Xenta 102-AX plug-in and click on the Operating Parameters tab. Check what value is set in the Stat Adjustment Range field. This value needs to be set high enough to accommodate the setpoint offset range that is desired. In order to enter a positive or negative offset of 5°F, then a value of 5 needs to be entered into the Stat Adjustment Range. If the value is set to 5°F and an offset of 6°F is entered, the entered value will revert back to the maximum amount allowed by the range, 5°F. Note: Keep in mind that this setting is also used to set up the range for wall stats that have an adjustment feature. In this case the range is divided by two to give the wall stat the capability to go negative and positive. For example if 5°F were entered into this setting, the wall stat will only be able to adjust up and down 2.5°F unlike nviStPointOffset that will be able to move up and down 5°F.

Issue In Menta simulation mode, when changing the RI block (using the button on the left hand side), the TSCHI will get the same value When changing the TSCHI block, nothing will happen at all  Environment TAC Menta Xenta 701, 711, 721, 731 Cause This happens due to a bug in TAC Menta. Resolution Create the TSCHI block before the RI block (this issue will only occur when the RI block is created first). Please note the this issue only affects simulation mode of Menta, you won't notice it  when the project is downloaded to the device.

Issue Trendlogs with a log period of 24 hours don't work. Environment TAC Vista 5.1.X Vista server trend logs. Cause This is only an issue in countries and states that don't use Daylight Saving Settings! There is an issue with Daylight savings settings in regions that don't have daylight saving. This is a bug that has been fixed in HF51715 (which will be released shortly). Resolution - Option 1: for Vista 5.1.7 - install HF51712 (or upgrade to 5.1.7 and install 51712) - Option 2: For older versions where it's not possible to upgrade: Double-click on the PC's clock in the task bar. Select the tab Time Zone. Change to a time zone that does observe daylight saving. Adjust the clock to the correct local time in you region. Uncheck the Automatically adjust the clock for daylight saving changes check-box. Click OK and close the dialogue. Restart Vista to apply the settings to Vista.

Issue Get "Not enough storage is available to complete this operation", could not connect to Vista message in workstation. The message appears periodically in Workstation without any operator input. Environment Vista 5.1.X Workstation 5.1.X Cause There are at least 2 possible causes for this. 1. Over utilisation of the PC's resources - in other words there is not enough physical memory on the PC. 2. Incorrect DCOM settings. Resolution Check the memory usage in the Task Manager. Is there RAM memory available when Vista is idling (not running reports and retrieving logs)? If the physical memory is used up then the only solution is to increase the memory on the PC/server. Alternatively, if there is memory available, check the DCOM settings for Vista. These can be found in the TAC Vista installation manual

Issue When installing Loytec NIC software the USB driver installation fails. Installing USB Drivers Failed LOYTEC NIC Driver Installer Error Installing USB Drivers: Could not pre-install Drivers Environment Windows Server 2003 setup on a domain. Cause The admin rights of the user is causing driver installation failure Resolution Even though you are logged on as a domain administrator the installation process fails at the USB driver stage. If you run the installation process by right mouse click on the exe file and then select run as. Then select the local administrator account the USB drivers will be installed correctly. Here are the screen captures of this process  

Issue AS-P is restarting on its own intermittently. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (All Versions) Cause Log entries found within the system_log.txt file confirm that the intermittent restart issue is caused by power interruption. See the below example of what to look for: Apr 08 19:03:34 AS-P-04619A kernel: pmem: shutdown interrupt: pid=0, comm=swapper/0 Apr 08 19:03:34 AS-P-04619A kernel: [<80013920>] (unwind_backtrace+0x0/0xe0) from [<801f569c>] (pmem_shutdown_irq+0x54/0x74) Apr 08 19:03:34 AS-P-04619A systemd-journal[1360]: Journal stopped -- Reboot -- Apr 08 19:03:54 cpud pmem_util[656]: Found SyncBlock Partition at sector 0x5dc00, 192000 sectors long. pmem_util[656]: ---------------------------------------------------- pmem_util[656]: SyncBlock Header summary (from previous power fail): pmem_util[656]: Sequence number:             94 pmem_util[656]: Exit critical regions:       0ms pmem_util[656]: SyncBlock file systems sync: 20ms pmem_util[656]: SyncBlock write map:         0ms pmem_util[656]: SyncBlock write speed:       6399kB/s (Wrote 128kB) pmem_util[656]: Total power fail time:      ~130ms pmem_util[656]: ---------------------------------------------------- pmem_util[656]: Finished moving 240 sectors (120kB) pmem_util[656]: Exit Resolution When an AS-P detects a power outage, regardless of how brief, it will initiate the process to backup the run-time and configuration data from memory to storage and reboots itself.  Check the power source connected to the AS-P and take appropriate actions to improve uninterrupted power delivery. An example would be to deploy a UPS solution.

Issue How to open an I/A Series G3 station in offline mode. Product Line TAC IA Series Environment I/A Series G3 WorkBench (all versions) Cause There is a need to configure/program an I/A Series G3 station without the station running. Resolution In Workbench, expand My Host: Navigate to My File System > Sys Home > stations Look for the name of the desired station and expand it Find 'config.bog'. Expand this and the station can be configured/programmed offline. Below is a screenshot showing an example for accessing the demo station offline. After making changes to the station, make sure to save the changes by right-clicking on 'config.bog' and selecting 'Save'. If this is not done, the changes will not be there the next time the station is run and opened online.

Issue The new scheduled SQL maintenance functions don't appear to defragment the events table, whilst the trendlogvalues table has been defragmented. Environment Vista 5.1.7 SQL 2008 R2 SP1 Cause A Microsoft SQL Server database is prone to data fragmentation and this is also true for the new TAC Vista SQL database layout introduced. It is recommended to keep the SQL database index fragmentation level at a low level to ensure performance in the TAC Vista system. A new feature has been added to TAC Vista Server to schedule regular maintenance tasks on the TAC Vista SQL database to prevent the index fragmentation level to obstruct performance deterioration; this feature is called SQL Maintenance. The SQL Maintenance feature is supported for both the new and the previous database layouts and is found in the TAC Vista Server Setup tool. TAC Vista Server Setup will also display the database layout used by TAC Vista. An event will be created in the TAC Vista Workstation event log when the maintenance task starts and ends. This event is created by TAC DSS Writer Service which launches the maintenance task. If a slave node is down in a TAC Vista network these events will not be captured by the Master node. Resolution TAC Vista SQL Maintenance feature will only execute if the total amount of data pages exceeds 1000 for the database. Maintenance should not be run when there is a low amount of data pages in a table. The total amount of data pages for a table is found in the index properties which can be seen using Management Studio. Open SQL management studio and connect to the tacvista database instance. Locate the taclogdata (default) database and expand the database in the tree. Under tables\event\Indexes locate PK_Events(clustered) and right-click on it. In the Index properties dialogue, under Select a page, select Fragmentation. The pages property can be seen in this page. Repeat the process for tables\trendlogvalue\Indexes\PK_Trendlogvalue(Clustered).

Issue An  "A cached program cannot be opened while it is being written"  error is displayed when attempting to open a program on a controller.  When attempting to remove the program it does not delete and an error is shown in the distribution Properties - 'A cached program cannot be saved because the synchronization lock times out'.  Environment Continuum Controller Cause The program has not compiled properly in the controller and is in a locked state. Resolution Take the Workstation into offline mode. Export the program to a dump file to back it up. Still in offline mode, delete the program. Reload the controller. Once the reload is complete, create the program again and then add the code from your dump file backup. Save the program and test.

Issue During the installation of the WorkPlace Tech Tool release 5.8 software, the following error is displayed: Environment Windows 7, Visio 2007sp2 WorkPlace Tech Tool release 5.8 installation Cause The message will be displayed if no Microsoft Office 2010 components have been installed on the computer. Resolution If Microsoft Office 2010 or any of its individual products including Word-2010, Excel-2010, Visio-2010, etc.,  have not been installed on the computer, the message can be ignored.  The Microsoft Office 2010 component upgrade failed because the no upgradable components were not found by the installer.  Click the [Yes] button to continue the installation.

Issue Adding an alarm filter. Environment Alarm filters Adding a new filter Cause How is a new system alarm filter added to the Sigma Alarm Manager? Resolution A new system alarm filter is added as follows; Open the Sigma Alarm Manager and select "Configure", then select "System Filters", the standard filters are shown. Select "Add" and name the new filter. Highlight the new filter and select "Edit". Set the filter configuration as required. From the "Configuration" menu select "Controls" and enable the new filter. Restart the Sigma client to show the Alarm Manager filter changes.

Issue As a part of the drive to improve information regarding our products, this document has been created to assist and clarify methods of connecting Touchscreens to newer and older series MicroNet controllers, and the controllers on the sub LAN under the Touchscreen unit. Product Line Satchwell MicroNet Touchscreen Environment Touchscreen wiring Cause Connecting MicroNet Touchscreen to microNet controllers. 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Remote Mounted Touchscreen (NCP) Connected to MN550/MN650 Controllers. Fig.1  Fig.2 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 3)  Fig. 3                                                                             Fig. 4 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 4) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. If the option of an isolated LAN for the 50 series controllers on the sub LAN is to be utilised, then a separate 24 Volt power supply should be used to supply the Touchscreen. Touchscreen (NCP) Directly Mounted on MN550/MN650 Controllers.   Fig.5  Fig.6 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 7)  Fig. 7                                                                           Fig. 8 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 😎 A visual check should be carried out to insure the jumpers, are fitted to the two auxiliary pins and they have a good physical connection. The MN50-TS-NCP specification of the Touchscreen differs from other variants and only has these 2 pairs of pins. This is to allow the Touchscreen to mount directly onto the controller; the other auxiliary pins are not fitted when manufactured. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. These are fitted at the factory, and should be removed. Connection to other controllers on the sub LAN should be done via LAN B of the base controller to LAN A of the other controllers on the sub LAN.  If the option of an isolated sub LAN, using 50 series controllers, needs to be fully utilised, the Touchscreen would need to be mounted remotely with a separate 24 Volt power supply. If the Touchscreen must be mounted directly onto a controller, that controller and the Touchscreen would not be fully isolated, but provided the Touchscreen /controller has a separate supply to the rest of the sub LAN, other controls on that sub LAN could be isolated. Remote Mounted Touchscreen (NCP) Connected to MN500/MN620 Controllers. Fig.9 Fig.10 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 11) Fig. 11                                                                                 Fig. 12 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 12) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. The controller on the sub LAN needs to have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. Touchscreen (NCP) Directly Mounted on MN500/MN620 Controllers.    Fig.13 Fig.14 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 15)  Fig. 15                                                                           Fig. 16  The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 16) A visual check should be carried out to insure the jumpers, on the Touchscreen, are fitted to the auxiliary pins and they have a good physical connection. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN should be done via LAN B of the base controller to LAN B of the other controllers. Caution to be taken when replacing an MN500 or MN620 controller if a Touchscreen is directly mounted on the unit. When replacing an MN500 or an MN 620 controller that has a Touchscreen directly mounted with a 50 series MN550 or an MN650 controller. The Touchscreen auxiliary pins 6 and 7 foul components on the controllers back plate, and will need to be cut. Pins 6 and 7 are identified in figure 17 below, will need to be cut close to the isolation strip A Once this modification has been carried out to the Touchscreen, the unit will no longer be suitable to run ARCnet communications. Fig. 17 An option would be to replace the Touchscreen at the same time as replacing the controller, with specification number MN50-TS-NCP. The MN50-TS-NCP specification of the Touchscreen has been modified, in production, starting Q2 2007, to allow direct mounting onto the MN500, MN 620, MN 550 and MN 650 controllers. Note: The 50 series controllers can be on the same LAN as the old 100 series of controllers. The LAN connections previously described, for the particular controller should be observed. Further information regarding these controller can be found in the product data sheets. See MicroNet 100 series controller MLi's and Data sheets See MicroNet 50 series controller MLi's and Data sheets