-
Notifications
You must be signed in to change notification settings - Fork 218
2.x to 3.x Migration
If you are upgrading an existing 2.0 installation, there are a few manual steps. From the project directory in unactivated mode:
- rm -r env
- rm -r volttron/platform/control
- python bootstrap.py
An overview of changes can be found at: VOLTTRON Primer Overview
Drivers are no longer tied to smap. Please see the drivers page.
Previously, all driver setup was done in an smap.ini file with sections for each device. Now, this setup is done in two parts: the Master Driver Agent and individual drivers. The sections from the smap ini are now contained in their own files. These files are tied together by the master-driver.config
:
{
"agentid": "master_driver",
"driver_config_list": [
"/home/volttron/git/config/bacnet-device1.config",
"/home/volttron/git/config/bacnet-device2.config"
]
}
The following portion of the file is no longer needed for the driver but could be used to setup an sMAP Historian
[report 0]
ReportDeliveryLocation = http://\<IP\>/backend/add/\<KEY\>
[/datalogger]
type = volttron.drivers.data_logger.DataLogger
interval = 1
Setting up paths for the collection and devices are now handled in the driver config file:
[/]
type = Collection
Metadata/SourceName = MySource
uuid = <UUID>
[/Campus]
type = Collection
Metadata/Location/Campus = My Campus
[/Campus/Building]
type = Collection
Metadata/Location/Building = Building
[/Campus/Building/device]
type = volttron.drivers.bacnet.BACnet
target_address = IP
self_address = IP:PORT
interval = 60
Metadata/Instrument/Manufacturer = Manufacturer
Metadata/Instrument/ModelName = Model Name
register_config = /home/volttron/git/volttron/config/my-bacnet-config.csv
Becomes bacnet-device1.config
:
{
"driver_config": {
"device_address": "13200:56"
},
"campus": "Campus",
"building": "Building",
"unit": "Device",
"driver_type": "bacnet",
"registry_config": "/home/volttron/git/volttron/config/my-bacnet-config.csv",
"interval": 60,
"timezone": "US/Pacific"
}
These files are almost unchanged from v2.0. The sole change is the renaming of "PNNL Point Name" to "Volttron Point Name" This was a legacy label from the initial version of the platform and has now been updated.
Point Name,PNNL Point Name,Units,Unit Details,BACnet Object Type,Property,Writable,Index,Notes
Becomes:
Point Name,Volttron Point Name,Units,Unit Details,BACnet Object Type,Property,Writable,Index,Notes
The rest of the file remains the same.
Please look through the page Historian to see the support storage solutions. sMAP can still be used but is now optional.
The Actuator can now be accessed via RPC which greatly simplifies the code needed to work with devices. The following shows how the old SchedulerExample agent was upgraded. The use_rpc method contains examples for replacing all the code for the pubsub interaction.
- Platform Agent
- VOLTTRON Central Agent
- Platform Commands
- Platform Configuration
- [Platform Hardening Security Recommendations] (Linux-Platform-Hardening-Recommendations-for-VOLTTRON-users)
- ...
- [Building VOLTTRON] (Building-VOLTTRON)
- Example Agents
- Agent Development
- [Shortcut Scripts] (Scripts)
- [VOLTTRON Conventions] (Conventions)
- [sMAP Test Server] (sMAP-Test-Instance)
- [Design Discussions] (Design Discussions)
- VIP
- VIP - VOLTTRON Interconnect Protocol
- RPC by example
- VIP - Known Identities
- VIP - Authentication
- VIP - Authorization
- Protecting Pub/Sub Topics
- Setup Eclipse for VOLTTRON
- Deployment Walkthrough
- Forward Historian Walkthrough
- [Create New Historian Agent] (Developing-Historian-Agents)
- [Create New Driver Agent] (Develop-Driver-Agent)
- [Developing With Eclipse] (Eclipse)
- Migrations
- [2.x to 3.x Migration](2.x-to 3.x-Migration)
- 1.2 to 2.0 Migration
- [Deployment Recommendations](Recommendations for Deployments)
VOLTTRON Versions and Features
Transactional Network Platform Overview
- Established Topics
- Working with the Actuator Agent
- Logging
- [Multi-Node Communication] (MultiBuildingMessaging)
Information Exchange Standards