Building Automation Knowledge Base

Issue Basic test of communication port on the Carrier DataLink, as accessed by the Network 8000 SIM-CCN. Environment Carrier DataLink communication gateway to a bus with CCN controllers Network 8000 SIM-CCN (Systems Integration Module for Carrier Comfort Network) Terminal emulator, such as HyperTerminal Click here for the SIM-CCN Installation Instructions, F-26167-2. See Figure 6 for detail of the serial cable required. Cause In some cases it is necessary to verify that third-party equipment is functional, independent of the SIM-CCN. Resolution Unplug the serial cable from the SIM, leave the other end connected to the Carrier  DataLink. Set up HyperTerminal: 8 data bits, no parity, 1 stop bit, 9600 baud, no flow control. Type " RT 1 DPTCONFG",  expect a "?" prompt.  If a prompt is returned, the port on the DataLink is functional; if no prompt is returned, the port may not be functional. If necessary, change the baud rate used by the terminal emulator to 300, 1200, 2400, or 4800 bits per second and repeat the test step 3. If the test fails at all of the possible baud rates supported by the DataLink, the port may not be functional.

Issue If one Input is required to activate an Output and another Input to de-activate the Output, this Output can be defined by Input Types. The below is a simple scenario where when the first Input turns ON the Control Output turns ON, when the second Input turns ON the Control Output turns OFF. In this scenario we are activating a Duress alarm when an Input goes on and resetting that Alarm when the reset Input is triggered. Product Line Security Expert Environment Security Expert SP-C Cause Require detailed instructions on how to program a latching duress alarm scenario. Resolution Objects required:   1x Area - "Duress_Area" 2x Input Types - "Duress Enable", "Duress Reset" 2x Inputs - "VI Duress Trigger", "VI Duress Reset" 1x Output - "VO Duress Alarm"   Note: The above object names are what is used in this example, you can set these to whatever you require.     Instructions:   Creating the Area 1. Navigate to Programming > Areas. Add a new area (Duress Area), set the Entry and Exit Delay Times to 0. All other settings can be left default.   Creating the Input Types 1. Navigate to Programming > Input Types. Create a new Input Type (Duress Enable) 2. Set the Control Output to your Output (VO Duress Alarm). 3. Under Options 1 enable Generate Alarms. 4. Under Options 2 enable Activate Control Output on Alarm . 5. Set any other options that may be required. 6. Create a new Input Type (Duress Reset) and redo steps 2 - 5 above except under Options 2 enable Deactivate Control Output On Alarm.   Configuring the Inputs 1. Navigate to Programming > Inputs select the Input (VI Duress Trigger) and set the following: 2. Set the Area to the Dummy Area (Duress_Area) created earlier. 3. Set the Input Type to the Input Type (Duress Enable). 4. select the Input (VI Duress Reset) and set the following: 5. Set the Area to the Dummy Area (Duress_Area) created earlier. 6. Set the Input Type to the Input Type (Duress Reset).   Testing 1. Arm both portions of the Area 2. Activate the Input (VI Duress Trigger) to confirm Alarm is generated and Output Activates. 3. Activate the Input (VI Duress Reset) to confirm Alarm is generated and Output Deactivates. 

Issue Are username and passwords encrypted during transmission from the remote client or the web client to the Sigma server? Product Line Satchwell Sigma Environment Sigma Remote Client WebClient Cause Are username and passwords encrypted during transmission from remote client to the Sigma server? Are username and passwords encrypted during transmission from web client to the Sigma server? Resolution Usernames are not encrypted during HTTP transmission from the remote client and web client to the Sigma server. Passwords are encrypted during HTTP transmission from the remote client and web client to the Sigma server.

Issue Downloads to some, or all, controllers are not working. Controllers are online to Security Expert but do not receive updates to Users or other changes and forcing a download does not work. Product Line EcoStruxure Security Expert Environment Security Expert Cause One of the Controllers download files has become corrupt. Resolution On the Security Expert Server browse to ..\ProgramData\Schneider Electric\SecurityExpert\Download. Review the Controller .dat files, there is one file for each Controller Id in the Database. Check if any of these files have a 0 bytes file size. Shut down Security Expert. Shut down the Security Expert Download Service. Delete each of the .dat files that does have a 0 bytes file size. These will be automatically recreated from the data in the Database. Start the Security Expert Download Service. Start up and login to Security Expert. Attempt to perform a forced download to the controllers and review the Download Server Diagnostics Window to confirm the controller has been downloaded and .dat file created.

Issue I/NET Server (Remote Client Configuration) can not connect to I/NET network even though the workstations (other Hosts) can. All workstations (I/NET hosts) transactions are not updating, but alarms and messages are. Product Line TAC INET Environment I/NET Seven Remote Client Configuration Remote Desktop / Terminal Services Cause Unless the Remote Desktop is configured for a single user session, it's extremely likely that multiple instances of the INetIoSrv.exe will be established. This will cause issues with I/NET, such as described above. It is strongly recommended that an alternative method of remote connection be used. Resolution An alternative remote connection should be used. We recommend VNC, Ultra VNC, WinVNC, or a similar protocol. This will ensure that multiple user terminal sessions do not open. Remote Desktop can also be configured for single-user operation, but the above software packages are the preferred remote connection method. See the following external site on "How to force a single session Remote Desktop session per user." http://remotedesktoprdp.com/Force-Single-Session-Allow-Multiple-Sessions-Per-User.aspx  

Issue When polling data from the Modbus IP and RTU X Drivers, how fast can data be retrieved? Product Line Andover Continuum Environment Modbus RTU, Modbus IP X-Drivers bCX1, Netcontroller II, ACX57xx Cause Polling data too fast particularly with the Modbus RTU XDriver can cause the controller Scan time to rapidly rise to excessive levels. Resolution The Modbus RTU X Driver can typically make 2 polls per second. These polls can be for single values or block reads. As this X Driver operates outside the regular controller scanning process, polling too many points or many points that are offline can cause the scan time to rapidly rise. Use a single Plain English program to schedule the polling of all points. See Helpful Modbus register Information for advice on how to handle offline devices. If 2 off Modbus RTU X Drivers are used on the same controller, then again use a single Plain English program to poll across both ports and do not exceed the recommended overall rate of 2 polls per second.  For the Modbus IP X Driver, only one port can be used to load this driver on any controller. It can typically make 8 polls per second for single or block reads. Also see What should be considered when analyzing the performance of a Modbus TCP/IP implementation?on analyzing the performance of the Modbus IP X Driver.  NOTE:  The ability to enable 2 comm ports using Xdrivers can be done, but is not recommended by the Xdriver developers nor supported by PSS. The RTU Xdriver is poll on demand. This type of driver can request a lot of data and starve the CPU on the controller which then makes the polling irregular. If 2 ports are being used then there are typically more devices being added and therefore more points increasing the requests and demand on the controller's CPU. Use one program to control the polling on both ports. Two programs attempting to control the polling asynchronously will cause communication issues.

Issue What has to happen for CyberStation to generate an offline controller alarm. Product Line Andover Continuum Environment CyberStation Infinity Controller Offline alarms Cause Receiving offline controller alarms yet controller appears to be online. Resolution Controllers can be offline for many reasons, such as a broadcast storm or will not come online, but consider the following points: In order to determine whether a controller is offline, a CyberStation will send out a probe to the controller.   The frequency with which CyberStation sends out the probe is determined by the value of the Probe Time field on the General Page of the workstation configuration. If an Infinity Controller does not respond to a probe, CyberStation will wait until a probe can be sent to all other Infinity Controller nodes in the system.  If the controller fails to respond to a second probe the controller is designated as Offline by CyberStation. Each CyberStation evaluates the commstatus of all controllers and reports alarms to the database.  Occasionally a CyberStation will show a controller as being offline while another CyberStation will show the same controller in an online state. When more that one workstation detects that the same controller is offline, this information is negotiated so that there will normally not be multiple offline alarms for the same controller.  Some versions of Continuum handle this better than others.  When an offline controller responds to a probe it is marked as Return to Normal. The controller may also be marked as Return to Normal if the workstation receives some other communication from the controller.

  Issue Cannot communicate to an ADV3 connected to the USB port of an AS-P or AS-B. The error message “Website not available” is displayed. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Advanced Display v3 (AD v3) Cause The AS-P or AS-B’s USB port uses a IP network connection to the ADV3 that defaults to 192.168.42.116. If the AS-P’s primary port is in the same range, for example the main LAN network range is 192.168.42.* there is a conflict with the USB IP network. Resolution Change the sites main LAN, which the AS-P or AS-B primary port connects too, to another network range.

Issue Needs to know how often Vista (or Xenta Servers) do online/offline polls for Modbus and MBus devices Product Line TAC Vista Environment Xenta Server Modbus Mbus Cause The devices may go offline for several different reasons. It's not possible to give a precise answer to this question, since it depends on your setup and the number of devices. Resolution In general, if a Modbus device has been detected as offline by the Xenta Server, it will wait 60 seconds until it tries polling that device again. That doesn't mean that a device will come online after 60 seconds if it has been offline because as described below, other factors comes into play, such as the number of devices and registers, and invalid registers. Mbus: The Mbus protocol is designed so that all information in the device will be received at every poll, regardless of what is defined in the device template. If the Xenta Server doesn't receive any information it will retry twice and if still no reply it will set the device to offline. All offline devices will be transferred to an offline queue in the Xenta Server, and at every new poll one device (the oldest) will be moved to the poll queue again. The reason for not retrying all is that if you have lots of devices that are offline at the same time, each poll would take very long time to complete and if using a short poll interval it may not be finished in time before the next poll. That will also mean that if you have many offline devices and have set a long poll interval in Xbuilder (default 1 min) it may take quite a while until all devices are online again. Note: In Xbuilder 5.1.9 and later it's possible to set the number of offline devices to poll each cycle. In some cases, for example when there are few meters and/or long poll times you may want to increase this number. Modbus/TCP: You will have a Server address for the TCP Client and if that server's ip address can't be reached all the Modbus devices below it will go offline. However as soon it can be reached again (will be tried constantly), it will scan all devices below it, and if they reply they will be set to online. If there's no response from a single device, it will retry twice before it's set to offline. The time it will take depends on the slave timeout setting in Xbuilder (default 3 seconds). As for Mbus, you have an offline queue where 1 device will be moved to the poll queue every poll cycle. The total poll time also depends on how many devices and registers you have defined (many devices/registers = longer poll time = longer time to detect if a device is offline/online). Modbus/RTU: It works similar to Modbus IP, except for the server part (which is not present). Besides that, you also have the "transmit delay" setting in Xbuilder (default 0 ms, max 1000 ms) which may effect the time it takes for a device to be reported as online/offline

Issue Not able to find information on the DO-20, DIO-20, or DM-20 IOU modules. Environment DM-20 DIO-20 DO-20 Relay Cause Unable to find documentation. Resolution Below are documents that have information on the DM-20 IOU module, DO-20 board, and DIO-20 Eclipse board. DO-20 -> Here.  DIO-20 Eclipse Module Datasheet -> Here. Continuum I/O Modules Datasheet Continuum I/O Installation Guide Continuum I/O System Reference (start pg.80) DIO-20 Installation Guide   Note: The Eclipse product line is now discontinued, but the DIO-20 is available for the DM-20. The part number is 01-9000-DIO20.

Issue BACnet Service does not start after enabling BACnet IP on a UNC station. The following error messages are seen in the UNC standard output. ERROR: Error initializing IP link layer. [IpLinkLayer.updateLocalAddress] java.lang.NoSuchMethodError: tridium/nre/Platform.getLocalHost()Ljava/net/InetAddress; ERROR: Cannot startService [Sys: BACnetService [12] BACnetService] java.lang.NullPointerException ERROR: Run error [BTrprt] java.lang.NullPointerException Product Line TAC IA Series Environment I/A Series UNC running at version r2.301.5xx prior to version r2.301.535 with BACnet 2.305.535a. Cause Most I/A Series R2 Niagara JAR files are backward compatible. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330? for details.  There were some changes to the BACnet service IP to support the new JACE-603/645 platforms. Because of these changes to the R2 core, the BACnet 2.305.535a JAR file is not backward compatible.  Resolution Upgrade the UNC to version r2.301.535. Refer to the Installation Instructions for upgrade procedure. 

Issue Where can we find the LON xif files for SE72xx, SE73xx, SE76xx controllers? Product Line EcoStruxure Building Expert,EcoStruxure Building Operation,Field Devices Environment SE7200 / SE7300 / SE76000 Room Controllers Cause xif files are needed for LON applications. Resolution All LON related files for these controllers are available for download on The Exchange Download Center:   XIF files and plug-ins Resource files (DRF kit)

Issue Resistance against temperature Product Line Field Devices Environment TC300 thermostat range TC900 thermostat range RS-03 remote sensor Cause Remote sensor compatibility Resolution The TC thermostat range use a 10K type 3 (3950) Negative Temperature Coefficient (NTC) thermistor. Whilst this is similar to the 10K type 3 thermistor used in the other BMS field device sensors such as the SpaceLogic SLA range, it has a different resistance curve and the temperature read will be different.   The table below shows that at typical room temperatures the error is 0.6°C or less. T(°C) RS-03 R(KΩ) SPA R(KΩ) Error % Error °C 0 31.77 29.575 6.91% 1.736 5 24.94 23.504 5.76% 1.366 10 19.68 18.809 4.43% 1.052 15 15.62 15.146 3.03% 0.812 20 12.47 12.271 1.60% 0.63 25 10 10 0.00% 0 30 8.064 8.195 -1.62% 0.3872 35 6.538 6.752 -3.27% 0.3052 40 5.327 5.592 -4.97% 0.2422 45 4.363 4.655 -6.69% 0.1928 50 3.592 3.893 -8.38% 0.1542   Click here to view the TC thermostat's RS-03 remote temperature against resistance chart. Click here to download the chart that provides the temperature against resistance reading for the TC thermostat's RS-03 remote temperature sensors.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue No events are transferred to the Report Server SQL database. Trend logs are transferred just fine. In the report agent log you can see this message "Sequence contains no elements" Product Line EcoStruxure Building Operation Environment Report Server Cause The Enterprise Server has been renamed before the Report Server has been installed or before the Report Server Agent has started collecting data. Resolution This issue will be fixed in a future version, but until that, do the following to correct the issue: The fix is split into two sections. First, a section working with the "event.db" file from the SBO database, and second a section working with the "StruxureWareReportsDB" from SQL Management Studio. "event.db" from the SBO database Download http://www.sqliteexpert.com/download.html (Just take the personal one) Stop the Enterprise Server Copy the "event.db" file to a safe location Attach the "event.db" file to "SQLite Expert Studio" Get the first event from the event.db using the following query in the "SQL" tab: SELECT SEQNO,TimeStamp,EventGUID,SourceServer FROM t_7E_2FSystem_2FEvents_2FEventLog_2FEventRecords ORDER BY SeqNo LIMIT 1; Convert the TimeStamp with this "SBO TimeStamp Converter" tool "StruxureWareReportsDB" using SQL Management Studio Write the following SQL query in SQL Management Studio, using the converted time stamp, and the Guid you found previously. INSERT INTO StruxureWareReportsDB.dbo.tbEvents (DateTimeStamp,SeqNo,OriginalSeqNo,Guid) VALUES ('2014-04-17 08:35:23.857','1','1', '380d1c4c-c60b-11e3-8ecb-b8ac6f81243c') Start the Enterprise Server again Restart the Report Agent and let it run for a while.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue A system Format of the file system will remove all files to return device to a factory condition. Product Line TAC Vista Environment TAC Xenta 5xx TAC Xenta 7xx TAC Xenta 9xx Xenta Server Cause A need to reset to factory defaults exists Resolution These actions clears the filesystem and remove all files and information in it. Make sure you have IP and any other information you need to save from the file system. All files and configurations will be lost. Access Xenta using a serial interface via the RS232 port and a HyperTerminal program. obtain a connection to the dsh> prompt Type format. Wait for formatting to be ready , then enter command setip to enter DHCP enable ,ip-address , subnet mask , default gateway , DNS , local name. Default user/password will then be root/root. Remember to change password. Restart system to accept new ip-address. Install Xenta using the install kit. Use ftp transfer and alternative A (We have just formatted the system). Download WebTool project and user defined files. Update bindings using LonMaker.

Issue How do I locate the latest patch files (modules) for the I/A Series G3 maintenance builds (3.6.407, 3.7.108, 3.8.41) Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.407, 3.7.108, and 3.8.41 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution The latest consolidated patch files for I/A Series G3 maintenance builds 3.6.407, 3.7.108, 3.8.41 are listed below.  The files contain updated modules and a set of release notes.  The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric EcoBuildings Exchange Extranet and enter Consolidated_Patches in the search area or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes bacnet3.6.407.2 baja 3.6.407.3 eibnetip 3.6.407.1 hx 3.6.407.1 mbus 3.6.407.3 ndriver 3.6.407.1             Consolidated_Patches_3.7.108.2.7_SE_02092016.zip   ...  Click here for Release Notes     Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes   Consolidated_Patches_3.7.108.2.7.1_SE_06282016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1 weather 3.7.108.1   Consolidated_Patches_3.8.41.2.9.1_SE_06282016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 weather 3.8.41.1 web 3.8.41.1           ********* Previous Release History ********* Consolidated_Patches_3.7.108.2.7_SE_02092016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1       Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes bacnet 3.8.41.12 baja 3.8.41.2 bajaui 3.8.41.1 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.1 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1 Consolidated_Patches_3.8.41.2.9_SE_04052016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1   Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes

Issue Clearing IP address in the 527 routing table Product Line TAC INET Environment I/NET TCP/IP Cause Routing Tables build themselves by self discovery. Resolution Routing tables build themselves by self-discovery on the network. If there is more than one device/host PC, similar function(s) may need to be performed on each device. Telnet utility for Host PCs, I/NET NPR2000 are examples. NOTE: Anytime you use the I/NET Command Line: inet(space) and the command you want to use for example; inet ip. Steps to clear a 527 routing table. Log into X527 with your web browser. Select the utilities folder. Select I/NET folder. Select I/NET Command Line. Make sure the word inet is in the command line and press submit. Then type inet delall to delete all the routing tables for the Xenta 527. You can type in inet help and this command will list all the all Web Shell Commands. ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all listsv ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records  

Issue The MN300 with a SLink sensor supported setpoint adjustments of 0.1 unit resolution. MN350, MN450, MN550 and MN650 with firmware version 2 and 3 only supported setpoint adjustments of 1.0 unit resolution. Product Line Satchwell MicroNet Environment MN350 MN450 MN550 MN650 MicroNet Cause 0.1 unit resolution is not supported on MN350, MN450, MN550 and MN650 with firmware version 2 and 3. 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------- MicroNet 50 controller firmware version 5 released August 2008, when used with an updated SLink2.FCG file for VisiSat 2.1 Build 148 now supports 0.1 unit resolution changes. Slink2.FCG File for Micronet 50 Controllers Firmware v5 file. Additional information can be found in TPA-LOND-09-0029.00 - Touchscreen TS0H Firmware.

Issue How do I configure oBIX (Open Building Information Exchange) to integrate a Niagara R2 station and a Niagara G3 station? Product Line TAC IA Series Environment Niagara R2 version 5.22 and later Niagara G3 version 3.4 and later Cause This document provides an overview of the integration of an R2 UNC to a G3 Enterprise Server using oBIX (Open Building Information Exchange). Resolution The R2 UNC must be licensed for "obix" and the obix jar file must be in the remote library of the UNC. Add the "ObixService" to the Services container of the UNC. Re-boot the UNC. The G3 Enterprise Server must be licensed for obix. Double-click the Drivers Component in the G3 Enterprise Server to open the Driver Manager. Add an Obix Network. Double-click the new Obix Network to open the Obix Client Manager. Click the "New" button at the bottom. Add a new "R2 Obix Client." Double-click the new R2 Obix Client. Enter a name for the UNC. In the Lobby field, enter http://, followed by the IP Address of the UNC, followed by "/obix". Enter the UNC's station username and password. Click OK. After a few seconds the state of the client should be "Attached." Expand the UNC Device in the Nav Tree. Double-click the points component to open the Obix Point Manager. Click the "Discover" button. After the points are discovered, expand "Lobby" and then "Config." (The Lobby is the root of a Server's oBIX object tree.) You can now scroll to see the containers and objects in the UNC's station. You can add UNC points to the G3 Enterprise Server's database in the usual manner. If you wish to have "link control" of objects in the UNC from the G3 Enterprise Server, then add an "Obix Export" object in the R2 Logic. These Obix Export Objects (analog, binary or multistate) are found in the Obix jar file in the remote library of the R2 UNC. Link pOut of the Export Object to pIn (if available) of the object you wish to control. Then link sOut of the R2 object back to the feedbackInput (fIn) of the export object. If no Priority Input is available on the R2 object, simply link the sOut of the Export Object to the sIn of the R2 object. No link to the feedbackInput of the Export Object is required. Return to the G3 Enterprise Server and discover the points in the R2 UNC. When adding the Export Point to the obixNetwork, the Export Objects default to type "Numeric Writable" so they can be commanded from the G2 Enterprise Server.

Issue Lost/Forgot/Modify the SysAdmin SQL default password created during the installation of TAC Vista 5.X.X in typical mode. Product Line TAC INET, TAC Vista Environment TAC Vista 5.x.x SQL 2005 Express Microsoft SQL Server Management Studio Express: (http://www.microsoft.com/download/en/details.aspx?id=8961) Local Admin rights Required. Cause Procedure if SQL Password is Lost/ Forgotten or Modification required. Resolution When you click on Microsoft SQL Server Management Studio Express, it will open the below page and require you to choose the way you want to log in: either by “Windows Authentication” or “SQL Server Authentication”. If you want to log in using Windows Authentication, choose this option and go in. (It uses the Windows login credentials). If you want to log in using SQL Server Authentication, choose this option and enter Login and password. If you want to change this Login and Password: Enter using the Windows Authentication Choose Security > Logins > Select the login ID Right click and go to Properties Change the password and re-login using the new password. Below is an example where the password for the login 'sa' has been changed: