Issue After reinstalling VisiSat, all network and remote site information appears to be lost. Product Line Satchwell MicroNet Environment Visisat Cause During the uninstallation process, VisiSat removes the SITES.DAT file, which contains critical remote site configuration data. Resolution To preserve your remote site information during a VisiSat upgrade or reinstallation: Before Uninstalling: Navigate to C:\Satchwell\Binary\VisiSat\ . Copy the SITES.DAT file to a safe backup location. After Installing the New Version: Paste the backed-up SITES.DAT file back into the same directory: C:\Satchwell\Binary\VisiSat\SITES.DAT Verification: Launch VisiSat and confirm that your remote site and modem configurations are restored.

Issue After adding an ASD driver to a Niagara G3 station off-line, there are no device objects in the tacASD palette. Environment Niagara G3 Cause Not documented Resolution After adding the ASDNetwork to a station, right click on the ASDNetwork and use the ASD Device Manager to add devices.  With the ASD Device Manager open click the "NEW" button at the bottom of the screen and a "NEW" window will be displayed to define the device type, number of devices to add and a starting address.

Issue InfinityInput (digital) not changing value when dry contact on relay changes state. Tried disabling and changing value but will not change. On bacnet side the point is set to out of service and will not change. New input points created on the UI4 are also out of service on bacnet side and will not change. Tried powering down expansion module - no luck. Tried deleting point on Infinity side and saving to database on bacnet - works fine. But when recreating the input, comes up the same way.   Environment bCX, 4040, bCX4040,  XP Expansion Module UI4, UI-4  Cause InfinityInput (digital) not changing value when dry contact on relay changes state. Resolution Replace UI4 with bCX powered off. Delete the point on Infinity side, save controller to database on Bacnet side. Drag & drop input from another bCX on Infinity side.  Save to database on Bacnet side. Point starts updating and is no longer out of service.  See also

Issue On the delivery tab of the EventNotification editor there's a checkbox that says, "Send to all workstations". Why is it grayed out?   Environment CyberStation Cause On the delivery tab of the EventNotification editor there's a checkbox that says, "Send to all workstations". Why is it grayed out?   Resolution This was added to the editor many versions ago, expecting to be implemented. A decision was made to not implement it but it was never removed. One reason for not implementing this was that many large systems have many workstations spread over multiple sites and time zones. This checkbox would make it too easy to cause unwanted alarms sent to too many locations. It was decided that a better idea was to require the programmer to thoughtfully select individual workstations.   

Issue Not able to select the Find New BACnet Device option in the BACnet folder, to bring new devices online. Environment BACnet Cause Not able to bring online new BACnet devices. Resolution The "Find New BACnet Devices" option should be selected by right clicking on the Root folder. You can not perform this operation from under the BACnet Devices folder.

Issue What XML tags can be used with the Email and Paging format files to customize the Alarm Email messages? Environment Continuum Cause Not sure what attributes of the alarm can be used and displayed in the Alarm Email message being sent out. Resolution This can also be found in the Online Help file under the help Index topic "Preferences for Device Attributes". This shows the preference options to select the email format files and the XML tags that can be used in those files. The list of tags is below. XML Tag Description <\date> The date of the alarm. For example: Friday, October 9, 2009. <\time> The time of the alarm. For example: 4:37:59 pm. <\name> The name of the object that generated the alarm. <\value> The current value of the alarm. For example: 190.00 <\state> The state of the alarm. Values can be : Alarm, Return to Normal, Acknowledged, or Fault. <\priority> The current priority of the alarm. <\type> The type of alarm that was triggered. <\message> The text message of the alarm. This is the message that is entered in the Text Message field on the Feedback tab of the AlarmEnrollment Editor. <\eventnotification> The name of the event notification for this alarm. <\operatortext> The operator text for this alarm (set by those who acknowledged this event). <\useractions> The user actions for this event. <\acknowledgedby> The user name of the person who acknowledged this event. <\acknowledgeddatetime> The date and time of this acknowledgement. <\silencedby> The user name of the person who silenced this event. <\silenceddatetime> The date and time of this silence event.

Issue What modems are supported for Xenta 901 dial -up to TAC Vista? Environment TAC Vista TAC Xenta 901 Cause Want to use a dial-up to TAC Vista. The support for dial-up in TAC Vista is mainly for upgrading of older systems. We have not added any new modems to the list in many years Resolution These modems are supported Us Robotics,3Com 56k Sportster(V92) D-Link DFM-560E+ Siemens MC-35 (GSM modem) Siemens M-20 (GSM modem) SRT (GSM modem) Wawecom (GSM modem) SRT DIN 35 (Leased line) SRT DIN (Dial up)

Issue Is it possible to set software permissions for a Public Value in a Menta or Function Block program in EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Public values in Function Block Programs (FBP) or Menta programs are not seen as objects but as attributes of the FBP or Menta object. Resolution It is not possible to set software permission on point level for a Menta program or Function Block Program, only on the Module level. One workaround is to create a Search or Watch View and add the signals the user should be able to change or add the points to a graphic. Set permissions to the Search, Watch window, or graphic.

Issue I/NET to DVR interface communications port Environment TCP/IP Cause A firewall may prevent communication between a PC and the DVR Resolution Integral DVR communicates on port 18772.

Issue   An error occurred while setting the system language property. Please validate that your language resource files are valid. Invalid format. (Subsystem: LNS, #40) Product Line TAC Vista Environment LonMaker Cause Resource File Languages have become corrupt. Resolution Restore the Resource File Languages:  Shut down LonMaker. Go to http://www.lonmark.org/technical_resources/resource_files/ At the time of this article, the latest version is LonMarkResourceFiles1304.exe.  Download this file.  If a later version exists, download the latest file. Run the executable. Restart LonMaker.

Issue Import Vista Alarms and Events into an Excel file Product Line TAC Vista Environment Vista 5 SQL 2005 Cause Unable to import Vista Alarms and Events in to excel file from Vista Resolution Select Data > Import External Data > Import Data as shown in below screen capture.   Select New SQL server connection as shown in below screen capture.   Enter Vista SQL Server instance name as shown in below screen capture.   Select taclogdata from dropdown menu as shown in the below screen capture.   Select Event table as shown in the below screen capture.   Rename .odc as .dsn as shown in below screen captures.   Click finish button.   Select Edit Query as shown in below screen capture.   Select SQL as shown in below screen capture.   Paste the Query as shown in below screen capture. Click OK button to apply the query.   Click OK button as shown in below screen.   Click OK button as shown in below screen.   Events are imported in to Excel   Query for Events based on dates: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN '10/12/2009' AND '10/12/2009 23:59:59.997') Query for One Day Events: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE()) Query for Alarm based on dates: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (Event.EventDatetime BETWEEN '08/24/2010' AND '08/25/2010 23:59:59.997') Query for One Day Alarm: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE())

Issue Can a Netcontroller II be used to communicate directly to BACnet MS/TP devices? Environment BACnet MS/TP RS-485 XDriver Netcontroller 2, NC2 bCX9640 Cause No X Driver is listed for BACnet MS/TP. Resolution There is no X Driver available for the BACnet MS/TP protocol to allow a NC2 to communicate to 3rd party MS/TP devices. However a bCX1 4040 can directly communicate to BACnet MS/TP on its Comm2 and is BTL listed to confirm compatibility. Also a bCX1 9640 can be converted to a 4040 by flashing it with the 4040 flash file available on the Extranet.

Issue Request for technical documentation and data sheets for Senseair aSENSE m III Environment Senseair aSENSE m III 6553064000 Cause The requested documentation is not available through Schneider Electric. Resolution Since this is a Class3 product, the manufacturer is providing technical documentation. Please see www.senseair.com for details and download.

Issue Replacement Environment Current replacement. Cause Obsoletion of device Resolution The is no direct replacement for the DRT 3801, DRT3851 Sensors with fan switches. The sensor and setpoint can be replaced using a New Part No. STR612/004604700 The fan switches would need to be replaced using a four position switch. Click here to view the DRT3801/DRT3851 data sheet.

Issue Clarification on documentation which does not indicate the addition of an xPDI8 and an xPDO4 being a valid combination to add to a b3 or i2 controller.   Environment xP modules xPDI8 xPDO4 Cause An addition to a existing i2 controller with an expansion port requires (4) more digital outputs and (8) more digital inputs. However, the documentation does not list the combination of the xPDO4 and xPDI8 as valid. Resolution That combination of expansion modules is not a tested, valid combination. The only tested combinations are those in the attached pages from the i2 Technical Reference

Issue Does Security Expert meet "FIPS Compliance"  Product Line EcoStruxure Security Expert Environment Security Expert Cause Unable to locate documentation for the FIPS compliance. Need to verify before Continuum access control system is migrated to Security Expert. Resolution Security Expert Software is currently not FIPS compliant. See Transition Guide Security Expert - Continuum Access Control to Security Expert - Reference Guide for more more details on what is, and is not, supported with a Continuum Transition to Security Expert.

Issue Does I/NET 2000 launch "EqualCli" automatically? Environment I/NET 2000 Cause File equalization is required if you have more than one host workstation which will need access to any of the above files. One host workstation is designated as the filemaster. This designation is performed in the Configure program and is maintained in the configuration profile. When you select the Set as filemaster option, Configure automatically completes the filemaster name field with the Computer name (found in the Identification tab under Windows Network settings). The filemaster name field is read-only on the filemaster station and cannot be changed. Resolution Yes, EqualCli will launch automatically. For more information see TCON 209, The Filemaster, 1-13. When the workstation is designated as the filemaster, I/NET stores a master copy of each equalized file in the \MSTR directory. It is important that the designated workstation be constantly powered and that the EqualSrv program be running. EqualSrv will dock an icon in the system tray to indicate it is active. Both EqualSrv and EqualCli are launched automatically by I/NET on the filemaster workstation and stay running as background tasks, even when I/NET is shut down. If necessary, you can manually shut down EqualSrv from the system tray icon menu. Warning: If the filemaster workstation is powered off, or if EqualSrv is not available, file equalization cannot occur. Furthermore, other host workstations will not be able to modify any of the equalized files. It is recommended that the filemaster workstation be powered by a uninterruptable power supply (UPS). All other host workstations must enter the Computer name of the filemaster workstation in the Filemaster name field. I/NET launches the EqualCli program on the host workstations automatically. Before any host workstation can access an equalized file, the EqualCli program contacts the EqualSrv program running on the filemaster station to ensure that any modifications can be passed to the filemaster copy. If, for some reason, EqualCli cannot make contact with EqualSrv, the operator will receive an error message and will not be able to access the equalized file. This ensures that no updates to the file are lost. If EqualCli makes contact with EqualSrv, the operator is permitted to access and modify the equalized file. EqualCli passes the updates to EqualSrv, who then updates the filemaster copy. If the update is successful, EqualSrv will make the file available to all the host workstations. There are three events which trigger the file equalization procedure. When I/NET is launched on any host workstation. When an operator attempts to access an equalized file. When any operator successfully updates an equalized file.

Issue MNL-800 ramp object step change does not function if time value set greater than 164 seconds. Environment MNL-800 Cause The ramp object configured as "step change" incrementally increases or decreases the output at the level and rate defined by the step level and time values. The ramp will not perform the "step change" function if the time value setting is greater than 164 seconds. Resolution The workaround involves decreasing both the step level and time values by a common factor to obtain the overall result in the original timeframe required. For example, a step change of 1 every 1000 seconds can be performed with the same results if using a step change of 0.1 every 100 seconds.

Issue Question about what causes table modifications in the ContinuumDB Environment CyberStation 1.74 SP2 Windows XP pro SP2 SQL Cause Table modifications to the ContinuumDB take place when the database is updated. Resolution Table modifications to the ContinuumDB are normal as seen in the DatabaseUpdate.txt file in the Continuum installation directory. (typically c:\program files\continuum) Tables and other database components can also be modified directly by using SQL Management Studio or Enterprise Manager, but these are unsupported unless specifically directed by Product Support. Direct editing of the database can cause data corruption or unexpected results and cause the database to not function properly. (i.e. 'Error reading database table' or 'Attempt to create duplicate database row') SQL Profiler can be used to try to target the issue by running SQL profiler at the time the issue occurs and correcting it but if that fails then recreating and rebuilding the db is the only alternative.

Issue How to retain an AccessEvent history of visitor names when using a generic pool of visitor access cards? (personnel)  Environment Continuum Cyberstation Cause Need to record a history of access events for visitor cards with the visitor name and the card number assigned to them at the time. Resolution Using the Personnel Manager. Setup a Personnel Profile for Visitors with default areas assigned. For example, use the existing "Visitor" profile. Setup a Personnel Profile for Visitors with no areas assigned. For example create a new one called "Visitor No Access". This will allow just the required distributions to be sent down to access controllers when they are required. Create a new personnel object for each visitor assigning a dummy card number to them with the "Visitor No Access" profile you created in step 1. Save the object. Issue a temporary card for that personnel with the "Issue Tmp Card" button; using one of your visitor cards and add area access by using the "Reset Access Rights" button to assign the "Visitor" profile created in step 1. After applying the changes to the Personnel object they will then distribute access down to the controllers. When the card comes back, restore the original dummy permanent card with the Restore Tmp Card" button and reset the access rights back to "Visitor No Access"; freeing up the visitor card to be used again. Save the object.   This will provide you with an AccessEvent audit trail of the visitor card number and the personnel name associated with it at the time it was being used.