Building Automation Knowledge Base

Issue MN-Sx, MN-SxHT sensors calibration Environment I/A Series MicroNet Sensors (MN-Sxxx series) Cause Sensor readings inaccurate Resolution 1. Calibration in WorkPlace Tech application program Calibrate the temperature and / or humidity offset in the Hardware Wizard. Enter a positive or negative offset value. For examples, -0.5 or 0.5. The WorkPlace Tech application has to be compiled and downloaded to the controller for the offset to take effect.   2. Calibration via sensor's Diagnostic Mode (only available in MN-S3xx, MN-S4xx, MN-S4xx-FCS, and MN-S5xx) To enter the sensor's Diagnostic Mode, press the Up and Down buttons simultaneously until the sensor enters the Diagnostic Mode. Press the Override button (while still in Diagnostic Mode). This will lead you to a display where you can enter an offset for sensor calibration. Allow the sensor to return to the normal display (takes about 30 seconds).

Issue In Niagara G3, a Learn Nv command on a MNL controller generates the following error: Environment Niagara G3 LON Cause Attempting to learn the new snvt profile from a controller that is already assigned a lnml file. Resolution If a LearnNv command is required on a controller already assigned a lnml file, the only way to avoid the error is to remove the lnml file assignment such that the file assignment is null. Then the LearnNv command will successfully complete. Access the Property Sheet of the LON controller and clear the 'Xml File' and Save.  The file name will be replaced with 'null'. Note:  Performing a Learn Nv on any Lon device previously using a Lon Xml file, LonComponent data from any manufacturer-defined type info is removed (lost).

Issue TCP/IP ports used in Niagara G3 (AX), various drivers, features, and functions - Quick Reference Table Environment Niagara G3 all versions Cause quick online reference for the ports used in Niagara G3 Resolution

Issue What I/A Series G3 object can be used to retrigger a write a value to a Modbus controller? Environment I/A Series G3, Modbus Cause Various Modbus controllers require the rewrite of values to maintain use of remote values versus local values.  This fallback mechanism allows the local Modbus controller to maintain control in the event of a BMS controller failure or loss of communications. Resolution The I/A Series G3 Modbus driver utilizes Modbus preset components to perform the rewrite function.  Presets allow writing preset values to the target addressed data items upon right-click action (command). If required, the “Write” action of any preset container can be linked into other control logic. For example, the “Trigger” slot of a TriggerSchedule can be linked into a ModbusClientPresetRegisters container component for periodic writes of child registers defined under the parent.  The same is also true using a periodic trigger object found in kitControl.  Preset components can be found in the modbusAsync palette and modbusTcp palette in the “Presets” folder. Note: Modbus client preset components are not proxy points or proxy extensions.  Modbus client preset components are not polled and do not read data from the device.  Modbus client preset components are only used to write data to the device. Presets exist for both Modbus coils and holding registers. Reference the I/A Series G3 Modbus Guide (About Modbus preset components) included with G3 documentation for more details.

Issue A Niagara R2 UNC station fails to start, producing the following error in the standard output window: FATAL: Cannot boot station from sns java.lang.ClassNotFoundException: tridiumx.webuser.WebUserAdminService Full Error Message: Environment Niagara R2 Cause Missing a supporting jar file Resolution Install the webuser jar file and reboot the UNC.

Issue Unable to add a new user in a G3 (Niagara) ENC station accessed via web browser. There is no "New" tab displayed under the Services / UserService / right-click, User Manager page. Environment I/A Series ENC-520, ENC-410 Embedded Workbench feature, part number ENC-WB Cause The ability to add a user to the ENC via web browser requires the Embedded Workbench feature be enabled. Resolution To determine if the ENC has the Embedded Workbench feature enabled, open the Platform, License Manager, view the license, and the feature name = "web" ... ui.wb.admin = true indicates that the feature is enabled.  See the high-lighted lines in the screen capture below. If the feature is not enabled, it can be ordered and added to the ENC license.  

Issue A Niagara G3 DMS driver is being used to integrate an existing DMS system with Microsmart controllers.  Setpoint values are provided to LOOP points in the Microsmart with Application Type 7 points (AP7) which can also be referred to as Chain Calculation points.  The AP7 points are not linked to the DMS database.  They are learned into the Niagara G3 station as Numeric Points and do not have the option to be writable. How can this be achieved? Environment Niagara G3 DMS Microsmart Cause Microsmart AP7 points are learned into a Niagara G3 as Numeric points and are not writable. Resolution Learn the AP7 point's PVALU element into the database: Go to the Property Sheet of the object above and add a Command String: An action option will now appear on the Wire Sheet (transferable to a graphic):

Issue Belkin Bluetooth adapter (F8T01n) on WIN 7 32-bit computer won't connect to MNB-ROAM-IA. Environment PC with Windows 7, 32-bit operating system Belkin Bluetooth adapter, model # F8T016 - F8T017 MNB-ROAM-IA WorkPlace Tech 5.x, configured for BACnet/ MSTP communications with MNB-ROAM-IA Cause The instructions for installing the Belkin Bluetooth adapter as documented in F-27578, TAC I/A Series ROAM-IA Quick Start Guide, "Windows XP-Specific Instructions for Bluetooth Installation", do not apply to installing the adapter on a computer with the Windows 7 operating system.  The procedure is substantially  different in "look and feel" on a Windows 7 computer than on a Windows XP machine - the instructions for Windows XP are not much help on a Windows 7 installation. Resolution The following series of screen captures will illustrate the procedure for installing a Belkin Bluetooth adapter on a Windows 7, 32-bit machine. 1. According to the Belkin FAQ shown, "Most Belkin Bluetooth USB adaptors install automatically without any extra software on Windows 7. Simply plug the device into a spare USB Slot. Windows 7 should automatically recognize the device and install the necessary drivers and software."  This was the case on the laptop PC tested, a Dell Latitude E5500. Screen prompts indicated that the drivers were loaded successfully, and the device was ready to use. 2. Open the Device manager, and there will be a folder for Bluetooth Radios. Expand the node, see the Generic Bluetooth Adapter. 3. Switch on the MNB-ROAM-IA. A Bluetooth icon will be added to the Windows Toolbar. 4. Click on the icon to bring up a menu. From the menu, select "Add a Device". The wizard will search for Bluetooth devices within range, should find the tac-RoamIA:nnnnnnn, where nnnnnnn is the serial number of the MNB-ROAM-IA. This should match the label on the back of the MNB-ROAM-IA 5. Pressing the "Next " button will bring up the "Select Pairing Option" screen. 6. Select the middle option, "Enter the device's pairing code", and press "Next". This brings up the following screen.  Type the pairing code "tac" in the box. The code is case-sensitive, must use lower-case as shown. 7. When the MNB-ROAM-IA has been successfully added and paired, the wizard will display the status. 8. Click on the hyperlink for Devices and Printers to verify that the device has finished installing properly, as follows. 9. In the Windows Device Manager, a Bluetooth Radios folder should be displayed. Expand the folder to see the Generic Bluetooth Adapter. 10. Right-click on the Generic Bluetooth Adapter, go to its Properties, Driver tab. The driver shown (6.1.7600.16385) was installed when the adapter was first plugged into the USB port   11. In the Device Manager, expand the ports folder, and two "Standard Serial over Bluetooth link" ports are shown, COM15 and COM5 12. Use the port with the lower number in the WorkPlace Tech communications setup for the MNB-ROAM-IA. In the example shown, COM5 is selected. Press the "Test and Configure Connection" button. 13. When communications are successfully established, the blue LED on the MNB-ROAM-IA will be ON continuously.

Issue My I/A Series R2 UNC station idle time is about 5%.  How do I improve it? Environment I/A Series R2 UNC (410, 500, 510, 520, 600, 610) Cause Station processing was not optimized to maximize the processor idle time. Resolution Run the System Spy by entering http:// :3011/system/spy into browser and specifying the IPAddress of the UNC. When the display comes up, scroll to the bottom of the page and click the 'Reset Counters' link. Wait 45 seconds for the counters to be updated before clicking the link to return to the spy statistics screen. Note the displayed idle time.  If it is above 20% no further action is required.  If below 20%, continue with the steps below to optimize the timing.  Please be aware that these steps are only suggestions.   Increase the cycleTime on the UIEngine Service properties--config screen from the default of 500 ms to a value in the range of 2500 to 5000 ms.  This value controls the update frequency of point values on the WorkplacePro and Graphic screens, both locally and via web browser access.  This timing affects the update rate for points on graphic screens.  Remember that regardless of how fast the update rate is specified, updates will only occur when new values are received from point or device. All LOG objects that have a log interval of greater than 2 minutes should be configured with an execution frequency of "minutely".  In addition, any objects being logged or used in calculations for a logged value, if not being used for other purposes, should be configured for "minutely" execution. Any objects that are involved with passing or using low priority values such as outdoor air temperature/humidify (and using/passing any other low priority value objects) should be assigned an execution frequency of "slower". Verify that there are no "custom program" objects that could be replaced with standard objects or combinations of standard objects.  In any case where the station contains more than the recommended maximum number of program objects, an effort should be made to reduce the number of program objects by as much as possible. Repeat steps 2, 3 & 4, above.  If the idle time is still less than 20% continue with the steps below to optimize the execution frequency time intervals.   Review status screen for the Control Engine service noting the following four sets of corresponding values.  If any of the four "Overruns" counters shows a significant number of overruns, note this fact for use in step 15 below. Compare each of the four "...AverageExecuteTime" values to the corresponding execution frequency value (on config tab) and if the value exceeds 50% of the configured execution frequency note this for use in the step 14. Open the Config tab of the ControlEngineService Properties screen. Referring to the values noted in step 12, the "normal" execution frequency needs to be set to a time value that is at least double the value of the "normalAverageExecuteTime".  If this time value exceeds the setting for the "slower" execution frequency, the "slower" execution frequency should be increased so that it is at least 50% greater than the "normal" execution frequency.  Adjust the fastest and faster executionFrequencies proportionally to the change made in the normal execution frequency.  For example if the "normal" execution frequency was increased from 2 to 5 seconds, the "fastest" execution timer would be increased to 1.3 sec and the "faster" execution timer increased to 3 seconds.  If any corresponding "overruns" counter shows a significant percent of overruns, as compared to the corresponding cycle counter, and you did not already increase the corresponding execution frequency to at least double its original setting, increase it appropriately.  Refer to step 14, above, regarding the suggested changes for the other execution frequencies. Apply the settings, save the station and restart it to force the changes to become effective.

Issue JACE-6 Application Director output indicates error: "Unable to init ndio device at ioPort".  After rebooting the JACE, the I/O modules work for a few hours and then appears to drop offline again. Environment I/A Series G3, JACE-6, IO-16 and IO-34 module Cause The ndio watchdog mechanism is used to return the NDIO outputs to known default conditions if the I/O module detects an issue or fails. When a JACE is booted, the NDIO processor starts and enters a default state.  At the same time, the NDIO daemon starts and establishes communications with the NDIO processor.  The mechanism monitors communications between the modules and the JACE and triggers a watchdog if the processor doesn't receive any messages from the daemon.  By default, this timeout is 30 seconds. Depending upon the NDIO Ping Monitor configuration, multiple resets of the watchdog will eventually cause the JACE to reboot. Resolution Depending upon the overall load of the JACE (other tasks and services utilizing the engine threads) the timeout may need to be increased to prevent a false watchdog condition. The first step is to increase the Keep Alive Timeout property within the ndio Monitor from 30s to 40s. Once increased, monitor the operation to see if this corrects the issue. If this does not correct, the timeout can be increased to 45 or 50 seconds maximum.  In addition, review services and tasks that may be consuming CPU usage and adjust as required.

Issue How to override a block output (DO or AO) in a MicroZone II controller on the ASD bus under a G3 ENC. Environment I/A Series ENC-520 with an ASD bus under it. Network 8000  ASD controller (LIM1, MicroFlow II, MicroZone II, PEM1) Cause Need to document the process for discovering controllers, the blocks they contain, and  adding the block attributes to the G3 station so that the desired points can be over-ridden. Resolution The complete process of discovering a MicroZone, the blocks it contains, and adding the block attribute to the database is illustrated in the following series of screen captures. While the DV of a DO block in a MicroZone II application is shown, the same procedure will work with other blocks in the other ASD controllers. NOTE*     Step 11 is not documented , and is commonly over-looked. 1. The MicroZone II is connected to the ASD bus, but it has not been added to the AsdNetwork in the station yet.   2. Right-click on the AsdNetwork, select Asd Device Manager from the menu.   3. In the Asd Device Manager, the 2 devices that have already been discovered are shown in the upper pane. To discover the MZ2, click on the Discover button at the bottom of the pane.   4. This brings up the Discovery Filter, where the type(s) of controller(s) and their address range(s) can be selected for discovery. In this case, only MZ2s will be searched for, in the default address range of 1 -32. 5. The Microzone II with address = 1 has been discovered by the Asd Device Manager, and "Success" is indicated in the status bar. The device has not been added to the database yet. 6. To add the MZ2 device to the database, click on the Mz2 device in the upper "discovered" pane, then click on the "+ Add" button at the bottom of the Database pane. 7. Pressing the "+ Add" button brings up the Add window, where the attributes of the device are displayed and can be edited.  In this case, the default values are all used. 8. A device object for the mz2_1 has been added to the AsdNetwork and is displayed in the tree on the left side pane. Expand the mz2_1 object, right-click on the "Points", and  select the Asd Block Manager from the Views menu. 9. In the Asd Block Manager, no blocks are shown yet for the mz2_1 device. Click on the Discover button at the bottom of the Database pane to discover the blocks in the MicroZone II controller. 10. When the blocks have been learned, "Success" is displayed in the Asd Learned Blocks status bar, and 25 objects have been discovered.  Expand DO 1 to expose the DV block attribute under it. This is the controller output that will eventually be over-ridden. 11. Click on the DV to highlight it, then press the "+Add" at the bottom of the database pane to add the DO 1 block's DV attribute to the station database. This will bring up the Add screen as shown below. Click OK to add the object. 12. Now the DO1 block and it's DV output have been added to the station database as a Boolean point. In the tree on the left expand the Points folder under the mz2_1 object. Right-click on the DO1_DV point, and select "override" from the Actions menu. 13. The override window is displayed, where the Time and Value of the override can be set. In this case, DO1_DV will be overridden ON (true) for 10 minutes when the OK button is pressed. Note: Entering a time of 0 minutes will result in a permanent override. 14. The block output has been overridden, and is displayed in the Database pane of the Asd Block Manager view.

Issue All of the nodes are yellow and when they are clicked on the error below is displayed even though the database is attached to the network (OnNet), the network interface is on the correct channel, and the network interface passed all applicable tests. Environment NL220 Cause When the nodes appear yellow, this means that the LNS database has been corrupted. Resolution It can be attempted to repair the database using the Echelon LNS Database Validator. Follow these steps. If NL220 is still running, shut it down. Go to the Start menu > All Programs > Echelon LNS Utilities > LNS Database Validator. Select the corrupt database in the "Network to Validate" drop down box. Check the box next to Repair Database. Now click on the button called Validate.   If these steps do not repair the database, send the LNS database backup to Echelon support to see if they can correct the problem.

Issue On startup, OPRIF 11.6 does not reach the blue sign-on screen. The program locks up and the computer must be rebooted to terminate the program. Environment DMS OPRIF 11.6 Cause The COM port assigned in OPRIF cannot be located.  As the result, OPRIF remains suspended in a locked state waiting to initialize the COM port. This situation typically occurs when OPRIF was previously used for tunneling.  A virtual COM port is assigned for tunneling to work. Resolution Prior to starting OPRIF, locate the SETDMS.PAR file in the DMS folder on the hard drive.   Edit the file with Wordpad.  The contents will appear as follows:  A=3 B=9600 P=E S=1 W=7 M=N The first variable listed is the COM port number which OPRIF searches to initialize on startup.  Change the number from 3 to 1 (if 1 is the physical COM port on the computer). Save and close Wordpad. OPRIF will now start, initialize with COM port 1, and display the sign-on screen.

Issue I/A Series G3 Modbus TCP communications to Siemens Moore 353 controller stops updating after a period of time after ENC/JACE reboot or station start.  The controllers do not drop offline and the associated Modbus proxy points no longer appear to update. Environment I/A Series G3, Modbus TCP 3.6.47 and lower Cause Modbus TCP transaction Identifiers are used to associate the future response with the request.  The transaction ID is a two byte value that can range between 0 and 65535. The Siemens Moore 353 controller appears unable to process Modbus transaction IDs at or higher than 1024. Resolution The I/A Series G3 Modbus TCP driver has been modified to allow the configuring of the maximum transaction ID for each device. Download the following modules from The Exchange Download Center: modbusCore-3.6.47.1.zip modbusTcp-3.6.47.1.zip Install to the appropriate I/A Series G3 Workbench modules folder and upgrade the modules in the ENC/JACE. Modify the transaction ID to a value lower than 1024 and reboot the ENC/JACE station.

Issue New hardware was supplied by the end customer for an existing InVue-installed computer.  InVue was installed from the original installation CDs.  The site backup was restored successfully.  Launchpad opens, Project Manager and Application Manager start properly.  When Communications is started, a pop-up error appears as shown below: Environment Wonderware for Intelligent Building Systems (WIBS) version 1.1 Cause This error is caused by one step of the installation process that does not complete. Resolution To correct the error, 1. Stop / close all WIBs programs. 2. Install CD#1 from the WIBS CD set. 3. Override pre-requisites and click on “Upgrade Operating System”.  Allow this step to finish.  When it is done, it will ask if the computer can be rebooted.  Select Yes.  If the computer reboots successfully, then move onto step 4.  If, after selecting Yes, the computer “hangs” and it needs to be manually forced into a reboot, then this step did not complete successfully.  Re-do “Upgrade Operating System” until the computer reboots successfully on its own.  Then move on to step 4. 4. Re-install WIBS1.1 service pack 3. 5. Open Launchpad.  Select the Job (in Job Manager).  Select the Application (in Application Manager).  Start Communications.

Issue Attempting to upgrade an I/A Series R2 Enterprise Server station and the database conversion fails: java.lang.OutOfMemoryError Environment I/A Enterprise Server R2 (all versions) Cause The issue is related to the limitation of the Java Virtual Machine (JVM). The conversion process is attempting to perform the upgrade on the station database and is exceeding the 1GB Java heap during the process. This typically occurs on an Enterprise Server station where the station database (db) contains a large number of log objects and associated logged data records.  Even though the records are archived in the SQL, the running station (log objects) still maintains records within each object. Resolution Verify that the Java heap is configured to allocate the maximum memory. Use the Windows Explorer and locate the nre.properties file (\niagara\lib directory). Edit with a text editor and verify the setting is Java.options=-Xmx1024MB. If not, change and save then restart the Niagara service and try to upgrade again. If the upgrade or conversion still fails (out of memory error), logs will need to be cleared in the running station to decrease the number of logged records. Restart the station in the current version (prior to the upgrade). Open the station and save the current records to the associated SQL database.  Select the Log Service (double click) and perform an archiveAll command (WorkPlace Pro menu items - Command).  The archiveAll command causes the data currently held in every log object to be immediately archived (sent to the LogService archive destination). Note this applies even to logs that are not configured to archive (daily and/or near full). There are two methods of clearing the logs.  The first method involves selecting each log object (double click) and perform a clear command (WorkPlace Pro menu items - Command).  The clear command clears all log data currently held in the object’s log buffer. The second method utilizes the AdminTool object to globally modify the log buffer sizes to temporarily decrease the buffers that will subsequently remove records that currently exist in the log object.  The AdminTool object is a special “utility” apps object, available in the Local Library (tridium/apps/AdminTool). This object provides an admin-level command to “Search and Replace” property values for objects in the station database. Config properties define the property name to search, new value to write, plus other parameters for filtering and recursion. This operation automates what would otherwise be a manual process of opening and modifying multiple objects’ property sheets. Note: The adminTool will globally apply the changes to objects defined within the utility.  Multiple iterations of this process may be required if log objects are configured with different buffer sizes. Open the local library and copy the AdminTool object to the station's root directory. Open the AdminTool properties and select the Config tab. rootNode -- Configure the swid of the starting point (upper hierarchy) of the station database in which the AdminTool function operates. This can range from the station’s root (/db/stationName) to any container or primitive object in the station’s database. If the recurseChildren property is True, the AdminTool function applies to any and all objects under the rootNode swid.  In Tree View, a right-click “copy” on any object under the station captures its swid. Use CTRL-V to paste the swid into the rootNode field of the property sheet. propertyName -- The target property name, exactly as shown on the object(s) property sheet(s). The property should be a read-write type.  In this example, configure the propertyName to bufferSize. elementName -- Not required for most properties that specify a single value of type float, integer, boolean, or string.  In this example, leave unchanged "-". newValue -- The new value assigned to all matching properties in (and under) the specified rootNode.  In this example, configure the newValue to 1 (bufferSize temporarily changed to size of 1). recurseChildren -- Defines if the search-and-replace function is extended to all children (and subchildren, etc.) of the specified rootNode.  In this example, configure the recurseChildren to True. objectTypeFilter -- Defines a match filter, meaning only objects of this matching type are affected. The asterisk (*) is used as a “wildcard.”  Partial strings of object types are supported, for example, AnalogO* will apply to object types AnalogOutput and AnalogOverride.  In this example, configure the objectTypeFilter to *Log (modify all logs e.g. AnalogLog, BinaryLog, IntegerLog, MultistateLog, and StringLog).  Note: The entire log type could be specified to only apply the changes to a specific type. nodeNameFilter -- Defines a match filter, meaning only objects with matching name are affected.  The asterisk (*) is used as a “wildcard.”  In this example, leave unchanged "wildcard." propertyValueFilter -- Defines a match filter, meaning only objects with this exact value are affected.  In this example, leave unchanged "wildcard." Execute the search and replace command (WorkPlace Pro menu items - Command). Return the newValue to the required buffer size and execute the search and replace command.  The smaller database can now be saved and upgraded or converted as required.

Issue In Niagara R2, when using the chart/log servlet in a browser, can the legend size be extended or widened? Environment Niagara R2 Cause The name of log objects selected for a chart are truncated in the legend. Resolution The legend size cannot be adjusted manually.  However, the descriptor used for the logged object can be customized somewhat. When using the /chart/log servlet, use "Logs Only (Description)" or "Logs Only (Swid)", the Log Object's description displays in the Legend. There are about 26 digits available excluding units which can be used for customizing.   The descriptor field can also be cleared of any text and the /chart/log servlet will use the object's name in the Legend.

Issue The elaspedActiveTime property of the DiscreteTotalizerExtension is displaying the time in hours, minutes, seconds and milliseconds. How do we not display the milliseconds? In the example below, the composited elaspedActiveTime shown is 7 minutes and 33.687 seconds. Environment I/A Series G3 Workbench Cause This is the default display of the elaspedActiveTime property Resolution Follow these steps to configure how the elaspedActiveTime property should be displayed. The elaspedActiveTime property of the DiscreteTotalizerExtension should already be composited. Go to the Slot Sheet of the DiscreteTotalizerExtension parent object. The example below is shown with a BooleanWritable object. Right-click on the elaspedActiveTime property and select 'Config Facets'. The Config Facets window will pop up. Add in the Key 'showMilliseconds' and Type 'Boolean'. The value should be set to 'false' since we do not want to show the milliseconds. Click OK. The elaspedActiveTime property will now be displayed only in hours, minutes and seconds.    

Issue Using PS-OPRIF version 11.6 and it is configured for COM1.  After a few seconds, the error "C350 PORT is NOT FOUND" appears and OPRIF fails to reach the Connection screen. Environment PS-OPRIF 11.6 Cause The background program - ntvdm.exe - was prevented from starting up properly.  It is likely missing from Task Manager. Resolution Determine what is preventing ntvdm.exe from starting.  Possibilities include: Anti-virus software Firewall or other security settings Lack of adequate RAM Conflict with another program accessing the same COM port Uninstall any recent Windows updates (June 2012)

Issue Modbus integration to Data Industrial Series 3050 BTU monitor Environment I/A Series G3 ENC-520 Modbus Asynchronous (Async) driver Cause Required to read the values in the BTU monitor via Modbus Async. Resolution The below Modbus registers table is provided by the BTU monitor manufacturer. Here are the basic procedures and settings in an ENC for this integration. Add a ModbusAsyncNetwork to the station database.   In the ModbusAsyncNetwork properties, configure the Serial Port Config. Port Name: COMX (where X is the COM port number of the ENC used for this integration). Baud Rate: As per baud rate setting in the Modbus device. We recommend the baud rate of 9600 as this appears to work best with this device. Data Bits: 8 Stop Bits: 1 Parity: None Flow Control Mode: No   Other properties of the ModbusAsyncNetwork to be left at its default values.   Add a new Modbus Async Device to the ModbusAsyncNetwork. The device address is as per address set in the BTU monitor device.   Leave all properties in the Modbus Async Device object as their default values.   Go to the Points folder of the Modbus Async Device and add the required Modbus objects. Configure the properties of each object as per the following. Address Format: Decimal Address: Refer to the table above. If reading register 30002, use 2 as the address. Reg Type: Input Data Type: Long   Set the Facets for the object