Building Automation Knowledge Base

Issue Many customers still have a requirement to run Lonmaker 3.13, but have project specific issues related to software fixes in newer version of LNS Server, and an LNS Server upgrade is required. Product Line TAC Vista Environment Echelon Lonmaker LNS Cause Older versions of Lonmaker 3.1 and LNS server had multiple defects that were addressed in later version of Lonmaker Turbo and LNS Server Turbo. However, it is possibly to run Lonmaker 3.1 and only upgrade the LNS server engine to take advantage of software fixes over time. Resolution NOTE: Any LNS Server version older than 3.10 needs to first be upgraded to 3.2x before 3.2x service packs can be installed. Also, please take into consideration that after upgrading the LNS Server on a system that any other system that needs to open that same database will have to be at the same version or higher. For example: a database upgraded to 3.27 can not be opened on the machine running 3.08.   Please follow these steps for upgrading LNS server to 3.22 and finally up to 3.27: Identify what version of Lonmaker and LNS server are currently running on the system. Please see How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS Server currently running. As seen in the screen shot below the system is running Lonmaker 3.13.10 with LNS Server version 3.08. Download LNS Server 3.22. Once this file is downloaded please unzip all of the contents to the desktop of the local machine. Run setup.exe from the extracted files in the LNS Server 3.22.zip, and step through the installation process. Once the installation of 3.22 is complete please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.22. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.22 like below: Now that the system is upgraded from LNS Server 3.08 to 3.22, service pack 7 should be installed to upgrade the system to LNS Server 3.27. Please download LNS Server/Turbo edition Service Pack 7 file to your local machine. Unzip the contents of the LNSServerTurboSp7.zip to the desktop of the local machine, and run the LNSturboServerSp7.exe file. Step through the installation process. When the installation is completed please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.27. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.27 like below:

Issue When trying to add a Xenta 421A, 422A, 451A or 452A I/O module in Menta to a Xenta 300/401, the following warning is displayed. Tam32 Warning, IO modules of type TAC Xenta 421A, 422A, 451A and 452A requires at least system program version 3.6. Environment Menta Vista Xenta 301, 302, 401 Cause To utilize the full functionality of the "A" series I/O modules, the version of Menta and firmware in the associated programmable controller must be compatible. Resolution Use the Xenta 4XXA modules as old 4XX modules The I/O modules with an "A" in the name can be used with programmable controllers earlier than 3.61 as well as Menta earlier than 4.2.2 but the functionality will be limited. The functionality is limited to that of the modules' predecessors, modules without the letter "A" in the name (Xenta 421, 422, 451, 452). The TAC Xenta 421A/422A modules can only have digital inputs and the TAC Xenta 451A/452A modules can only have four 1.8k ohm thermistor and four limited universal inputs (digital input, 1.8k ohm thermistor or 0-10 V). In any running system with TAC Xenta 300/401 version 3.X, TAC Xenta 421, 422, 451, and 452 can be replaced with an "A" module the same way as an old module. The "A" module will detect that it is sitting in an old environment and behave as an old module. Use the full functionality of the Xenta 4XXA modules In order to gain full functionality of the "A" modules, the firmware in the Xenta 300/401 controller must be upgraded to a version 3.61 or higher and Menta must be version 4.2.2 or higher. Instructions on how to download a .MOT file can be found in Download an .MOT file into a Xenta Programmable controller. The additional features of these controllers include all inputs are universal inputs (0-10 V, 0-20 mA, 1.8k ohm and 10k ohm thermistor), universal inputs set as digital inputs can act as a pulse counter, and all configurations, inputs, and outputs can be accessed by means of the SNVT interface. Note: If updating the firmware in a Xenta 300/401 and the following conditions apply than see the Xenta Programmables section of The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Working on a database with multiple Xenta programmable controllers that reference the same device template A firmware version earlier than 3.52 is installed

Issue When installing the TAC Vista remote workstation, an error message is displayed. Details listed below: TAC Vista Workstation Remote Error 1935. An error occurred during the installation of assembly 'Integral.Common.SystemInfo, Version="7.0.70.0",Culture="neutral", FileVersion="7.0.70.0", ProcessorArchitecture="MSIL", PublicKeyToken="6853E3D8122788A2";. Please refer to Help and Support for more information. Product Line TAC Vista Environment TAC Vista 5.1.7 Workstation Remote (may happens to other version of TAC Vista Workstation Remote). Another version of Vista has been installed Cause When installing Workstation Remote the first time, it will automatically remove the other version of TAC Vista Workstation (ONLY) which has been installed earlier on the same computer. However, it will not remove other parts of TAC Vista (Vista Server, Menta, XBuilder, etc.) and causing the installation of Workstation Remote later crashes. Resolution Follow the instructions in How to uninstall and completely remove TAC Vista 5 to completely remove other parts of TAC Vista. NOTE: if you want to keep the SQL database, you can skip the SQL part.  Restart the computer.  Run the Workstation Remote installation file again. Now the issue should be solved. Corrupt Windows file system transaction log In some cases this error has been the result of the Windows file system transaction log becoming corrupt. Follow the steps found on the Microsoft support website forum to correct this issue.

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue After TAC Vista Server is started, logging into TAC Vista Workstation, an error "Ensure that Vista Server is started" occurs. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation TAC Vista Webstation Cause This issue is due to the DCOM permissions that Vista Server relies on and they must be manually changed. Resolution Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET contains a DCOM Utility that can automatically set the proper permissions to clear the issue. To manually alter DCOM parameters: Locate the DCOM config in Component Service > Computers > My Computer Right-click TACOS and selected Properties Select Security tab Click the Edit in Launch and Activation Permissions. Add the appropriate groups or user names of computer and Allow them permissions. After finishing the above procedures, the issue should be solved. Error: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. also discusses this issue.

Issue Switching from the Demo license to the Entitled License in Vista 5 Product Line TAC Vista Environment TAC Vista 5.X.X Cause In most cases the license will begin to work just fine after starting Vista and selecting "Use License Server" upon startup. For unknown reasons, Vista may need to be forced to ask you for a License File Or License Server option when Vista is first started after the license is switched. Resolution Unlike the Demo license, the site license must be placed in C:\Program Files\TAC\License Files (or C:\Program Files\Schneider Electric\License Files for TAC Vista 5.1.4 and above) and accessed via the License Server. It is imperative that the license file retains the .lic file extension, which importing to certain Windows environments may append a .txt extension to the filename The easiest way to force TAC software to use a License server versus pointing directly to the Demo License is to modify a registry setting of the Flexnet Licensing Software.   Start the Registry Editor from the Command prompt (type "regedit" in the start menu run box) and navigate to HKEY_LOCAL_MACHINE>SOFTWARE>FLEXlm License Manager.  Modify the TACLIC_LICENSE_FILE string and delete the Value data. By leaving this key empty, the next time you start any TAC software you will be prompted to "Specify the License Server System" or "Specify the License File".  Start a TAC Software package that requires a license.  Select "Specify the License Server System" and enter the computer name preceded by an "@" symbol. If the License Server resides on the local machine, "@localhost" can also be used. Note: In more recent versions of License Server, the "@" symbol is optional. If in doubt, putting it in will work with all versions. If the changes were successful, the registry entries should appear as follows (in a typical installation). If registry settings are different that the ones below, please contact Product Support Services.   If the above changes were performed but the License fails to read,  in some cases the License Server system will not work properly until rebooting the PC. If unable to read the license use LMtools utility located in the TAC Tools to troubleshoot the issue. If additional assistance is needed for using LMtools, watch the video overview published in Vista 5 Macrovision/Flexnet Licensing: Lmtools diagnostic utility overview. For help with Vista versions >5.1.7, see License troubleshooting in Vista 5.1.8 or greater

Issue View the current firmware version on a Xenta controller using the RS-232 cable Product Line TAC Vista Environment Vista 5.1.X Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B, 901 Cause While it is the best practice to match all of the firmware versions in your controllers, this is a quick and easy way to view the current version installed on your hardware.  Resolution Connect the RS-232 programming cable to your controller and your PC Open TAC Tools 5.1.X Open Download Wizard Click next Click the information button located directly above the help button For more information on how to update the firmware (.MOT file) on a Xenta controller, see Download an .MOT file into a Xenta Programmable controller. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue When updating the Vista database in the TAC Vista System Pug-In an error message is displayed that says "Could not connect to Vista Server. Unable to request license." Product Line TAC Vista Environment TAC Vista System Plug-In Cause This error message is a result of not having the Vista Workstation license in the permanent license file. The licensing for the TAC Vista System Plug-In is included with the Workstation license. Resolution The license for Vista Workstation must be purchased in order for the system plug-in to work. For more information about the license packages see Vista 5.1 License Packages. 

Issue When trying to download a 5/7/9xx in XBuilder you get "Error code 401 - Unauthorized". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause Password in XBuilder project does not match the password in the Xenta device. Resolution Select the 5/7/9xx in the Network panel The password is in the right hand panel of XBuilder under the TCP/IP Settings section. Change this to match the password in the 5/7/9xx. If the password is not known then refer to Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost.

Issue How can the TAC Xenta OP be used with a TAC Xenta 100-series controller? How can the TAC Xenta OP know which TAC Xenta 100 controller it is communicating with? Which OP mode should be used? Product Line TAC Vista Environment Xenta OP Xenta 101 Xenta 102 Xenta 121 Xenta 122 Cause The TAC Xenta OP panel can be used to connect to a TAC Xenta 100-series controller to access input and output signals. Identifying the TAC Xenta 100 controller to configure is accomplished with a Service Pin message. If connecting directly to a TAC Xenta 100-series controller, or to a STR100-series device connected to the TAC Xenta 100-series controller, the controller sends out a Service Pin messages automatically, If this is not the case, or you connect on another location on the network, you could manually press Service Pin on the TAC Xenta 100-controller you want to connect to. For troubleshooting connectivity to a Xenta programmable controller, see "No Answer" on an OP when connecting to a Xenta 280/300/400. Resolution Configure the TAC Xenta OP Plug in the TAC Xenta OP Hold the Back and Enter button for 3 seconds to access the OP Service menu. Scroll down to option 10 for OP Mode. Change "Xenta 100" to ON with the + key. Press Enter. Change "Mode" to TAC with the + key. Press Enter twice to restart OP Connect TAC Xenta OP to a TAC Xenta 100-series device Plug TAC Xenta OP into OP jack on the TAC Xenta 100 controller, or to a STR100 device connected to the TAC Xenta 100. At prompt "Press <ENTER> to access Xenta 100", press Enter. At "Connecting to Xenta 100 ...", wait, or press the Service Pin of the Xenta 100-series  controller. Press Down. View Network Variables Select the network variable index number in the NV Index? prompt with the - and + buttons. Press Enter to view the signal. If the value is an input you can use + or - to provide a new value and press enter to accept it. If the signal is an application options set of bits then press enter to navigate between the bit number, + to change the value, and enter to accept the value.

Issue TAC Vista installations prior to TAC Vista 5.0.1 cannot be upgraded to TAC Vista 5.1.9  version directly. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Cause When upgrading Vista to 5.1.9, certain steps need to be followed to ensure that the process works properly. Resolution Note: If upgrading from an older version of Vista where the LNS port is at the root level of the system tree, instead of underneath the Vista Server, then you will need to follow the steps in Graphics binding were broken after a Vista upgrade to 4.5 from an earlier version to fix the binding paths of root level objects. TAC Vista installations between 4.3.0 and 5.0.0 must follow these upgrade steps in order: Upgrade to a version between 5.0.1 and 5.1.6 Upgrade to version 5.1.9   TAC Vista installations prior to 4.3.0 must follow these upgrade steps in order: Upgrade to a version between 4.3.0 and 5.0.0 Upgrade to a version between 5.0.1 and 5.1.6 Upgrade to version 5.1.9   Note: In a situation with multiple databases on a computer, make sure all are upgraded in this manner. After the upgrades have been carried out make sure the master server is started first followed by the slave servers.

Issue Alarm queue in the Vista Workstation states "No license for LonWorks communication" Product Line TAC Vista Environment Vista Workstation Cause The simplest cause of the issue, and the one that should probably be checked first, is that the license for LonWorks communication was not present at the time the server was started.  Oftentimes, this is due to starting server, realizing the engineering or end user dongle was not plugged in (or license server was not started) and then plugging it in.  The server will not actively poll for this license, it must be present at startup. Resolution Stop the Vista Server Ensure the license dongle is plugged in, or the license file is activated and installed on the license server. Restart the Vista Server Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 TACOS startup delay utility

Issue What kind of controller can be used to get values from a Modbus device into TAC Vista? For example, getting data from a Modbus meter into a BMS system running Vista. Product Line TAC Vista Environment TAC Vista TAC Xbuilder TAC Xenta server 731/913 Cause TAC Vista can not talk Modbus directly so you need to use a gateway controller. Resolution Xenta firmware version 5.1.4 and earlier only two controllers had Modbus communication capabilities: Xenta Server 731  For details see TAC Xenta 711/731 Web Server and Controller Xenta Server 913 For details see TAC Xenta 913 LonWorks Gateway Starting with Xenta firmware version 5.1.5, all Xenta Servers are now capable of communicating on a Modbus network both via TCP/IP and RS-485.  This includes Xenta 511, 527, 701, 711, 721, 731, 913. Note: Older Xenta Server devices built before firmware 5.1.5 have the capability of using Modbus over RS-485 once they have been upgraded even though the terminals are not labeled on the device. For information on how to wire these devices to reference a newer Xenta Server that does have the RS-485 A terminals labeled or see Xenta Server wiring and pinouts.

Issue How to order more LonMaker credits in order to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LNS credits see Ordering more LNS credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To order more LonMaker credits: Echelon LonMaker v3.1 Open up a LonMaker database and go to LonMaker menu > LonMaker Credits Info... Here you can view how many LonMaker available credits that you have. Click on Add Credits... In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, click the Copy to Clipboard button to copy the PC key generated by LonMaker License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, open up the LonMaker License Wizard again. Click Next and paste the application key into the field titled "Application Key". Click Finish. Echelon LonMaker v3.2 Turbo Open up the LonMaker License Wizard by going to Start > All Programs > Echelon LonMaker > LonMaker License Wizard. Here you can view how many LonMaker credits that you have available. In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, click the Copy to Clipboard button to copy the PC key generated by LonMaker License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your Schneider Electric Buildings Business Order Entry Department (888-444-1311) so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, open up the LonMaker License Wizard again. Click Next and paste the application key into the field titled "Application Key". Click Finish.

Issue In the event of a hardware failure on a Xenta controller you may need to perform a proper replacement procedure in the TAC Plug-In to install the new device. Product Line TAC Vista Environment Vista Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Hardware failure in an LNS network Resolution In the event you have a piece of hardware fail on your LNS network you will want to follow the steps below to properly replace the device. Remove the bad controller and Install the new controller in its place Open your LNS network in LonMaker or NL220 Select to open the TAC System Plug-In in your network management tool In the Plug-In, locate the bad controller in the tree under the LNS Network pane and right click Select Replace... (the Replace TAC Xenta Device Wizard will open) Click Next Select the service pin button and press the service pin on the new controller Then click Next In the next window, click Next to update your Vista Database (NOTE: If you receive a warning during this process, see Warning about application file replacing a programmable controller in Vista System Plug-In) Once this process of updating your Vista Database is complete you will see the screen below confirming that the update was completed successfully Close the TAC Vista Load window Return to the Replace TAC Device Wizard and click Finish. This will complete the replacement process for your new device In some rare cases not all I/O modules will come online after this procedure. If this occurs a power cycle of the Xenta 400/300 will solve this issue.

Issue TAC ToolPack plug-ins (eg. STR 350 plug-in) do not show up Product Line TAC Vista Environment TAC Vista 5.1.4, 5.1.5, 5.1.6 Windows 7, Windows Server 2008, Visio 2010 TAC System Plug-in TAC Device Plug-in TAC Zbuilder TAC Xenta 100 Plug-in TAC Xenta 102-AX Plug-in STR 350 Plug-in Cause Not all plug-ins in the TAC ToolPack can run on Windows 7, Windows 2008 or Visio 2010. Resolution When installing TAC ToolPack on these operating systems only the supported plug-ins will be installed: TAC System Plug-in TAC Device Plug-in TAC Zbuilder TAC Xenta 100 Plug-in TAC Xenta 102-AX Plug-in If the desired plug-in is missing, configuration of your controller will need to be done manually in NL220, Lonmaker, or Vista. Read details about manually setup STR 350/351 in STR 350/351 manually setup without plug-in (nciOption1 and nciOption2).

Issue Is it possible to run TAC Vista 5.X.X in Windows XP compatibility mode (When TAC Vista Installed on Windows Vista, Windows 7, Server 2003/2008) Product Line TAC Vista Environment TAC Vista 5.X.X Windows XP Windows Vista Windows 7 Windows Server 2003/2008 Cause If TAC Vista 5.x.x is Installed on Windows 7, Windows Vista, or Windows Server 2003/2008, is it possible to run the Vista Workstation on Windows XP using Compatibility mode. Resolution TAC Vista has several other applications that work together with Vista. These applications do not support compatibility mode. Upgrade to Vista 5.1.4 or later which support Windows 7. If the operating system is a 64-bit version, upgrade to Vista 5.1.5 or later. For the compatibility matrix see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121, which does not have a D1 input. Product Line TAC Vista Environment Xenta 121 STR-150 Cause The correct terminal for the mode input from the STR-121 is labeled differently on the Xenta 121 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 121 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 6   The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 121. When the Xenta 121 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained inIs it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue Xenta Server is offline in Vista and can not be reached via web interface. Product Line TAC Vista Environment Vista 5.1.9 Windows 7 Cause The PC has proxies configured. Resolution Open Internet Explorer Go to Tools > Internet options > Connections > LAN settings Disable "use a proxy server" Related Article: Xenta Servers are offline in Vista, although they can be reached via the web interface

Issue Use the block DI to monitor an IO module, and generate an alarm when it is offline. But the above-mentioned function cannot be realized. Product Line TAC Vista Environment Menta Xenta 301, 302, 401 Xenta I/O Modules Cause If there is a configuration error in block DI, the right alarm cannot be generated. It is necessary to check and correct the configuration error. Resolution Create and configure the block DI and Alarm block according to the following procedure, then the IO module status can be monitored. When it is offline, an alarm will occur in the alarm window in TAC Workstation.   1. Create a block DI. (See the Figure 1) Figure 1 2. Edit the block DI and input DI identifier such as the monitored module name, Status_411 in instance. (See the Figure 2)           Figure 2 3. Click BIND in Edit window, select the Online Device in BIND TO column, and input the IO module number in DEVICE ADDRESS. (See the Figure 3)               Figure 3 4. The module number can be found in IO Expansion and Wall Module Table of DEVICE SPECIFICATION in Menta Options toolbar. In the under instance picture, the M1 module, TAC Xenta 411, its device address is 1; the M2 module, TAC Xenta 421A, its device address is 2; and so on, the M5’s device address is 5. (See the Figure 4)       Figure 4 5. After creating and configuring the block DI, the block Alarm should be created. (See the Figure 5)                Figure 5 6. Then connect the block DI and Alarm. When the IO module is online, the DI value is generally 1. So the block NOT must be used. (See the Figure 6)         Figure 6   You can also reference Monitor the online status of a base unit's associated I/O modules.