Advanced controls
Create operator controls beyond a small local panel.
Legacy compatibility guide
Maintain an InduSoft connection to a Velocio PLC.
Preserved setup guidance for existing InduSoft Web Studio installations that communicate with Velocio PLCs through the MODBU driver and vBuilder tag addresses.
Historical use case
Why teams connected Velocio PLCs to InduSoft.
The original integration used the InduSoft MODBU driver and vBuilder’s Modbus tag mapping to connect one or more Velocio PLCs to a larger HMI or SCADA project.
Data and event logging
Collect machine values and events for review and reporting.
Remote monitoring
Monitor and control an installation from supported remote stations.
Mixed PLC systems
Build a project that includes multiple Velocio PLCs and controllers from other vendors.
Before you start
Record the existing system before changing it.
Back up both projects
Save the InduSoft project, vBuilder project, PLC program, tag map, and known-good screenshots.
Verify the PLC and firmware
The historical page referenced firmware 1.09 Beta or later. Treat that as archival context, not a current firmware recommendation.
Confirm software support
Check whether the installed InduSoft release, MODBU driver, and Windows version remain supported.
Preparation resources
Verify the software and controller before making changes.
Preserved setup sequence
Configure the MODBU driver in four steps.
Menu names and screens belong to the legacy InduSoft Web Studio release shown. A newer AVEVA product may use different drivers, dialogs, or configuration steps.
- 1
Open the driver manager.
Create or open the project, select the Comm tab, right-click the Driver folder, and choose Add/Remove drivers.
- 2
Add the MODBU driver.
Select MODBU in the available-driver list, add it to the project, and confirm the dialog.
- 3
Set the communication port.
Right-click the MODBU folder and open Settings. Use Windows Device Manager to find the COM number beside VelocioComm, then apply that port to the legacy driver configuration.
- 4
Create the driver sheet and map tags.
Open a MODBU driver sheet. Use the vBuilder Modbus PLC ID as the Station, enter each mapped tag in the I/O Address column, and choose the required read or write action.
Legacy address format
Translate vBuilder tags into driver-sheet addresses.
The historical driver sheet used a type prefix, a colon, optional signedness, and the Modbus address assigned in vBuilder.
0xBit tagsUse for Boolean values.4xUI8, UI16, I16Use for 8- and 16-bit register values.DWI32Use for signed 32-bit integer values.FPFloatUse for floating-point values.Signedness and access
Finish each row with the correct data behavior.
Address rules
- Use U for unsigned UI8 and UI16 tags.
- Use S for signed I16 and I32 tags.
- Append the Modbus address assigned to the same tag in vBuilder.
- Set the Action column to read, write, or the required combination.
- Mark the vBuilder tag Writable before permitting an external write.
Bench-test first:
Confirm one tag of each data type against known values before mapping the full system. Pay special attention to multi-register word order, station IDs, signedness, and write permissions.
Next steps
Keep the legacy setup isolated from current product claims.
Use vBuilder to inspect the PLC-side mapping. Use AVEVA’s current material only to evaluate a supported migration path; this preserved guide does not establish compatibility.