By default, you see the Front Panel, which is the user interface of the VI.A VI is used to create a user interface and executable graphical code. This creates a new virtual instrument or VI. From the Project Explorer, right-click My Computer and select New»VI.You now have access to Modbus data natively in LabVIEW through the shared variables This publishes the shared variables, making them available on the network to other computers. Deploy the shared variables by right-clicking on ModbusDemoLibrary and selecting Deploy All.Note: The LabVIEW DSC Module enhances shared variables by adding the ability to log data, alarms, and events directly to a database without ever writing a LabVIEW application. Then select 000001-065535, and click on Add Range. Leave the default of Data Item as 000001 and Number of items as 1. Hit OK.In the Create Bound Variables window, expand the tree down to the Modbus1 in order to select the desired address range.Right-click the newly created ModbusDemoLibrary and select Create Bound Variables….Create new shared variables that are bound to the Modbus addresses.With the shared variable you can share data across LabVIEW applications on a single computer or across the network. In this section, you will learn to create shared variables bound to the Modbus addresses, giving you native access in LabVIEW to PLC data. Save the project as ModbusDemoProject and the library as ModbusDemoLibrary by selecting File»Save All from the project explorer window.īind Shared Variables to Modbus Addresses Through the I/O Server.Select OK. A library is automatically created in your Project Explorer window to manage the I/O Server.In this example we are running the Modbus Slave on the same computer as the master, so we use the localhost IP address, 127.0.0.1.
Q lab master slave control how to#
If you don’t know how to determine a computer’s IP address refer this web page: External Link: How to Find IP Information. Enter the IP Address of your target Modbus Slave in the IP address field.Figure 2: Configuring Modbus Master I/O Server
0 kommentar(er)
