-
Notifications
You must be signed in to change notification settings - Fork 21
Expand file tree
/
Copy pathBrowseVariablesComponent.hpp
More file actions
107 lines (92 loc) · 4.31 KB
/
BrowseVariablesComponent.hpp
File metadata and controls
107 lines (92 loc) · 4.31 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
#pragma once
#include "Arp/System/Core/Arp.h"
#include "Arp/Base/Acf/Commons/ComponentBase.hpp"
#include "Arp/Plc/Commons/Meta/MetaComponentBase.hpp"
//#include "Arp/System/Commons/Logging.h"
#include "Arp/Base/Commons/Logging/Log.hpp"
#include "Arp/System/Commons/Threading/WorkerThread.hpp"
#include "Arp/Plc/Meta/Services/IVariableBrowseService.hpp"
namespace BrowseVariables
{
using namespace Arp::Base::Acf::Commons;
using namespace Arp;
using namespace Arp::Plc::Commons::Meta;
using namespace Arp::Plc::Meta::Services;
using namespace Arp::System::Commons::Threading;
/// <summary>
/// ###########################
/// BrowseVariables example
/// ###########################
///
/// In this example, Forcing of GDS variables (including I/O) is demonstrated:
///
/// It is assumed that all operations succeed, so return codes are generally ignored.
///
/// Values forced by this component can be seen in the PLCnext Engineer project, using Debug mode.
///
/// </summary>
//#acfcomponent
class BrowseVariablesComponent : public ComponentBase, public MetaComponentBase, private Loggable<BrowseVariablesComponent>
{
public: // construction/destruction
BrowseVariablesComponent(ILibrary& library, const String& name);
public: // IComponent operations
void Initialize() override;
void SubscribeServices()override;
void LoadSettings(const String& settingsPath)override;
void SetupSettings()override;
void PublishServices()override;
void LoadConfig() override;
void SetupConfig() override;
void ResetConfig() override;
void Dispose()override;
void PowerDown()override;
public: // MetaComponentBase operations
void RegisterComponentPorts() override;
private: // BrowseVariables methods
void StartBrowseVariables(void);
void StopBrowseVariables(void);
void BrowseVariablesData(void);
private: // Plc event handlers
void OnPlcLoaded(void);
void OnPlcStarted(void);
void OnPlcStopping(void);
void OnPlcUnloading(bool onError);
void OnPlcChanging(void);
void OnPlcChanged(bool success);
private: // fields
// Service thread that reads and writes data and writes log messages
WorkerThread browseVariablesThread;
IVariableBrowseService::Ptr variableBrowseServicePtr = nullptr;
int16 step {0}; // Step sequencer
public: /* Ports
=====
Component ports are defined in the following way:
//#attributes(Hidden)
struct Ports
{
//#name(NameOfPort)
//#attributes(Input|Retain|Opc)
Arp::boolean portField = false;
// The GDS name is "<componentName>/NameOfPort" if the struct is declared as Hidden
// otherwise the GDS name is "<componentName>/PORTS.NameOfPort"
// If a component port is attributed with "Retain" additional measures need to be implemented. Fur further details refer to chapter "Component ports" in the topic "IComponent and IProgram" of https://www.plcnext.help
};
//#port
Ports ports;
Create one (and only one) instance of this struct.
Apart from this single struct instance, it is recommended, that there should be no other Component variables
declared with the #port comment.
The only attribute that is allowed on the struct instance is "Hidden", and this is optional. The attribute
will hide the structure field and simulate that the struct fields are direct ports of the component. In the
above example that would mean the component has only one port with the name "NameOfPort".
When there are two struts with the attribute "Hidden" and both structs have a field with the same name, there
will be an exception in the firmware. That is why only one struct is recommended. If multiple structs need to
be used the "Hidden" attribute should be omitted.
The struct can contain as many members as necessary.
The #name comment can be applied to each member of the struct, and is optional.
The #name comment defines the GDS name of an individual port element. If omitted, the member variable name is used as the GDS name.
The members of the struct can be declared with any of the attributes allowed for a Program port.
*/
};
} // end of namespace BrowseVariables