Summary
The Solar Panel Demo showcases a distributed application example by simulating a solar panel solution's data collection, publishing, and viewing processes. This Demo uses a distributed software architecture to handle and process real-time data from multiple sources. It illustrates the practical application of technology in monitoring and managing renewable energy resources. This hands-on demonstration highlights how distributed applications can enhance efficiency and transparency in energy management systems.
There are 2 versions of SolarPanel demo.
The first version, 'SolarPanel.dbsln' included in the software distribution requires only one solution file, with the data is defined in tags in the solution itself and a simulated communication driver populating the values.
Download the solution file: SolarPanel.dbsln
The other version, 'Distributed Application Demo', is composed the files 'fxMonitor.dbsln' and 'fxEdge.dbsnl', one one simulating the edge device publishing data and the other one with centralized monitoring of the entire system. This second version, requires Canary Historian. Download the solution files: SolarPanel.dbsln and SolarPanel.dbsln
This page will highlight the features of both versions.
On this page:
Solar Panel Demo
Asset Selection
The key display in that demo is the left panel, with the TAssetTree Control.
That control allows the operator to select that area he wants to monitor, and that information is saved on the built-in variable Client.Context. The key properties of the Client.Context are listed in the following table.
Client.Context Properties Updated by the TAssetTree UI control | |
|---|---|
Property | Description |
AssetName | The complete path for the asset. Example: \SolarPanels\Tripoli\Tripoli[1].PanelVoltage. |
AssetPath | Path of Parent Node (excluding final attribute) |
AssetNodeName | Name of parent folder. Example: Tripoli |
AssetNodeDepth | The Depth of the node in the treeL Example: 2 |
If you add Client.Context.AssetName to dynamic UI properties in the display, it will show that string value, like: "SolarPanels\Tripoli\Tripoli[1].PanelVoltage"
To show the VALUE of attribute use the syntax Asset(<string with asset name>). Example: Asset(Client.Context.AssetName)
For advanced applications instead of using the Client.Context.AssetName variable, you can create any expression that results the string with the AssetName you want to monitor.
The properties presented in this table are automatically populated when a TAssetTree in loaded in any display. In order to use that features, you must design your Operator UI having only AssetTree active at any given time.
Map Update with Geo Location
The display showing the map, uses the TMapsOSM control, available for both WPF and HTML5 pages.
When running only in Windows, it also available the TMapsESRI control and the TMapsGMap control.
The DisplayIsOpen() task monitors the Client.Context.AssetName and when ti changes, it uses the map control API to zoom to the coordinates of the selected city.
This demo was created settings the Displays to the option StretchFill, which will resize to use the entire client area, but will distort the image with you resize to other aspect radios.
You can also setup the system to various other OnResize options: StretchUniform, NoAction, Responsive, and ResizeChidren. For more information go to Display Settings page.
Detailed Information about the Asset
Distributed Application Demo
In this section: