Issue Is SysManSMS Server and VISTA 5.1.7 tested on Windows 2008 R2 running in a Marathon EverRun Level 3 Solution? Environment TAC Vista 5.1.7 SysManSMS Server Cause  The Server software is running on any Windows platform and release, including Embedded Windows.. Resolution The SysManSMS Server is written is C and has no special requirements for the Windows platform. The Server software is running on any Windows platform and release, including Embedded Windows. The software has been certified by Microsoft for Windows 7, and tested for Windows 2008 R2.It will run in both 32-bits and 64-bits (compatibility mode) environments. The compatibility with TAC/Vista is no issue at all. The clean interface between Vista (writing Alert Files) and SysMan picking up the files to process will always work, We have more than 500 TAC/Schneider installations used with Vista. No reported problems. Marathon EverRun Level 3 we do not know at all. As long as this software does not alter the above environments, it will for sure run.

Issue The transmit and receive lights on BCX comm 2 stay lit continuously minutes or hours after the Infinet bus is connected. Environment BCX9640 i2920 Infinet Cause Electrical interference or noise being introduced into the Infinet bus. Resolution Removed the to i2920 controllers from the infinet.  Since these were the only controllers powered by 120 volts it seemed likely that they were a potential source of interference from the power wiring to the Infinet cable. 

Issue Workstation program functions while logged on to Continuum but stops functioning when the user logs off. The program disables with the error ''You do not have sufficient access to do the requested operation.'' being displayed in the Run Time tab of the program properties. Environment Continuum Cyberstation Cause When Continuum is logged off, the access rights of the default ACC user are used for things such as when Workstation programs run. If the ACC user has had its security settings restricted then these restrictions are applied when the correct user (who may not have these restrictions) is logged off of Continuum. This could then result in a workstations program trying to read / write or do some other action that it is not allowed to do under the current restriction. Resolution Modify your security restrictions on the ACC user to allow for actions that your Workstation Program is trying to perform.

Issue The R2 ASD (IbsASD) driver may fail to communicate correctly with ASD devices if not configured properly. Product Line TAC IA Series Environment R2 ASD (IbsASD) driver (all revisions) Cause Incorrect driver configuration settings can lead to intermittent or failed communication with ASD devices. Resolution Configure the driver using the following recommended settings: General / Engineering retryCount = 3 responseTimeout = 2 sec Poll / Config cycleTime = 333 ms × number of devices on the ASD bus (Approx. 3 devices per second) Comm / Config commPort = COM4, COM5, COM6, or COM7 (depending on port used) maxBaudRate = 19200 (Use 9600 if PEM1 controllers exist on the ASD bus) DeviceStatus / Config deviceStatusPingDelay = 60000 ms Tip: Always verify baud rate compatibility with connected devices and ensure proper port selection for stable communication.

Issue CZU4201 not controlling. Always in cooling mode. Environment CZU4201 CZU DRT3451 STR611 STR612 STR Cause The CZU controller is not controlling. Resolution A DRT3451, STR611 or a STR612 is used as both temperature sensor and setpoint adjust. Check that the internal setpoint adjust within the controller is set 10'C. If not, set it to 10'C, then the internal setpoint is ignored and the remote setpoint is used.

Issue What operation modes should be used in zone control then the area is not being used? Environment Xenta 121 FC Xenta 121 HP Cause The TAC Xenta 120 device does not have any internal clock. The actual operation modes has to be sent from another device such as a Xenta 401. The following values could be sent to the nviManOccCmd SNVT: 0=OC_OCCUPIED 1=OC_UNOCCUPIED 2=OC_BYPASS 3=OC_STANDBY other values=OC_NUL 255=OC_NUL Resolution Normally, OCCUPIED mode is used when there are people in the zone. During night time, or short periods without people in the zone STANDBY may be used. If someone enters the area and triggers a motion detector or presses the Bypass button, the mode changes to BYPASS. UNOCCUPIED mode is most appropriate if the area is no longer rented or during some other long period without anyone in the area.

Issue Auto Generated Reports not running in 64-bit Environment Environment I/NET 2.43 64-bit I/NET 2.42 64-bit Cause Issue with windows scheduler is causing Auto Generate reports to fail. Resolution Modify existing or newly created auto generate reports. Click on the Recurrence button On the "Task" Tab, modify the "Run" string. At end of the string you will notice sch=<ScheduleName>. Add the characters"/T0" or "-T0" as shown below Before:   After:

Issue Is there a replacement RJ-11 to BACnet MSTP cable for I/A Series Roam IA? Environment Roam IA, MNB-ROAM-IA Cause Need to replace cable. Resolution The part number for the replacement RJ-11 to BACnet MSTP cable for Roam IA is MNB-ROAM-CBL.

Issue When using multiple monitors, the autocomplete popup in the Script Editor may appear off-screen, typically when the editor is placed on the right-hand display and in full-screen mode     Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause This behavior is influenced by how Windows identifies and arranges your monitors. It can depend on: The physical connection order of the monitors to the docking station or PC The logical arrangement of displays in Windows display settings Resolution To resolve the issue: Adjust Monitor Arrangement in Windows Settings Right-click on the desktop and select Display settings Drag the monitor icons to match your physical setup (e.g., left to right) Click Apply to save the changes Swap Monitor Cables If using a docking station or multiple video outputs, try swapping the cables between monitors This can help Windows reassign the primary and secondary display order more intuitively Avoid Full-Screen Mode If the issue persists, consider using the Script Editor in windowed mode rather than full screen as a temporary workaround

Issue Is there a legend for the icons displayed in I/NET Seven? Environment I/NET Site Cause Where is the legend for the icons displayed in I/NET Seven? Resolution Look in the “Getting Started” I/NET Seven TCON298.

Issue Can NPR 2000s be installed on a token ring network Environment I/NET site Cause Can NPR 2000s be installed on a token ring network? Resolution NO - Although INET hosts may work, NPR 2000s only have Ethernet NIC cards in them. Even then, token ring networks are not officially supported for the hosts.

Issue Forced inputs in Xenta 121s return to default values Environment LonMaker NL220 Cause Every time you hit "Apply" or "OK" in Zbuilder, the Xenta 121 will get a reset command. When the controller receives the reset command, the inputs lose their forced status and return to default values. Resolution After the Xenta 121 controller has been rest, the overridden points must be forced again.

Issue On a MNL-800 controller, are resistors required on the universal inputs when wired for pulse counting? Environment MNL-800 controller Cause Knowing the resistor requirement helps implementing pulse count using universal inputs. Resolution UI1 does not require an external resistor. If using UI2 through UI8 as a pulse input, an external 10K resistor to +5.1 V is required.

Issue LonMaker makes you wait in a 'transaction queue' before it will process any commands that require communications to the network. Environment Echelon LonMaker Cause This problem seems to arise when changes are made to the structure of a large network in which the majority of controllers have been commissioned, but not yet installed. LonMaker then tries to continuously update these controllers of the network changes that have been made, but it can't since they are not online. Thus, when any requests are made by the user, they must wait in line until LonMaker gets to their requests. Resolution The problem has two solutions: The first, and most simple, is to bring all of the commissioned controllers on the network online. This will allow LonMaker's updates to be propagated to them all, causing an end to the cycle. The second solution is to decommission any controllers on the entire Network that are not online, but have been commissioned prior to the network changes. This will eliminate LonMaker's desire to update these controllers. These solutions must be applied to the entire network, and not just the channels that have actually had the network changes performed on them.  

Issue Can the MNB controllers be powered by DC voltage? Environment MNB controllers DC voltage input Cause Using DC voltage is not recommended or supported. Resolution The MNB controllers are not specified for DC operation and all agency approvals were submitted using a power source of 24 VAC 50/60 Hz.

Issue After restarting Sigma, the Alarm Manager fails to start. Product Line Satchwell BAS & Sigma Environment Sigma release 4.04 Cause In Sigma release 4.04, the archiving process may occasionally fail. As a result, the AlarmsLog.rec file can grow excessively large—sometimes exceeding 2 GB—which prevents the Alarm Manager from running properly. Resolution To resolve this issue, follow these steps: Stop both the Sigma Client and Sigma Server. Open Windows Explorer and navigate to the following directory: C:\Sigma\Data Locate the file named AlarmsLog.rec. Perform one of the following actions: Rename the file (e.g., AlarmsLog_old.rec ) OR Delete the file (if no longer needed). Restart the Sigma Server and Client. Note: A new AlarmsLog.rec file will be automatically created when the next alarm is received by the server. Alternative Solution Consider upgrading to the latest release of Sigma, which includes improvements to the archiving process and prevents this issue from occurring.

Issue On a database with a large number of personnel records, an 'Unknown error' is received when searching personnel using Personnel Manager Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There is a default maximum limitation to the number of records that can be display when searching for records using Personnel Manager. The default maximum is set to 50. If you attempt to increase this number in the New Search screen in Personnel Manager it reverts back to 50. Resolution In order to allow a higher number to work around this error, perform the following steps: Shut down Cyberstation Make a copy of the existing PersonnelManagerCtrlDll.Config (C:\Program Files\Continuum\Common) Use Textpad or Notepad and open the PersonnelManagerCtrlDll.Config file Change the number in the line SearchSection MaxSearchResult=50 (Change this to a larger number closer to the max search results you would expect from the site) Too large of a number can affect system performance of the search. Restart Cyberstation Note: Repeat this procedure for each Cyberstation as needed.

Issue Every time the trendlog data should be viewed an alarm saying" The digital signature does not match, values might not be reliable". How can we avoid this? Environment Vista 4.4.2 Cause In old Vista versions like Vista 4.4.x we had something called Digital signature to check that the data in the SQL database had not been tampered with. This have been taken away in later Vista version as it slowed down and caused problems with trendlogs. The alarm indicates that someone have done something in the SQL database and the digital signature does not match.   Resolution It is possible to turn off the Digital signature in the Vista server setup under the SQL tab and then restart the Vista server. Then Vista will not do this check and the alarm should not appear.

Issue Can I assign an IP address to each NPR after I place it on the network? Environment I/NET site Cause Can I assign an IP address to each NPR after I place it on the network? Resolution No. A unique IP address must be entered for each NPR before it is connected to the commercial network. (TCON209 2-27)

Issue Error when starting I/NET: "System page does not exist" Environment I/NET Host PC, all versions of I/NET Windows XP, Windows Vista, etc Cause Graphic page link is not set correctly in the Host Configuration. Resolution Start I/NET Go to Edit > Host Computer > Configuration Click on the "..." button on Default system page Browse to the required page and then click on the okay button Restart I/NET and the message should not come up again.