@tier0/node-opc-da 1.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +171 -0
- package/docs/opcda.idl +1166 -0
- package/package.json +30 -0
- package/src/constants.js +212 -0
- package/src/enumString.js +161 -0
- package/src/filetime.js +79 -0
- package/src/index.js +62 -0
- package/src/opcAsyncIO.js +102 -0
- package/src/opcBrowser.js +285 -0
- package/src/opcCommon.js +84 -0
- package/src/opcGroupStateManager.js +248 -0
- package/src/opcItemIO.js +60 -0
- package/src/opcItemManager.js +415 -0
- package/src/opcItemProperties.js +102 -0
- package/src/opcServer.js +447 -0
- package/src/opcSyncIO.js +213 -0
- package/src/opctypes.js +116 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,171 @@
|
|
|
1
|
+
# opc-da
|
|
2
|
+
|
|
3
|
+
This library implements the OPC-DA specifications and allows to communicate with OPC Servers, relying on the [node-dcom](https://github.com/netsmarttech/node-dcom) library for DCOM/DCE-RPC for protocol implementation. Currently this lib support browsing calls and synchronous reads. The code overall strucuture was heavly based on [Utgard](https://en.wikipedia.org/wiki/Utgard_(software)).
|
|
4
|
+
|
|
5
|
+
This node was created by [Smart-Tech](https://netsmarttech.com) as part of the [ST-One](https://netsmarttech.com/page/st-one) project.
|
|
6
|
+
|
|
7
|
+
## Table of Contents
|
|
8
|
+
- [Install](#install)
|
|
9
|
+
- [Usage](#usage)
|
|
10
|
+
- [OPC Server](#opc-server)
|
|
11
|
+
- [Creating a Server](#creating-a-server)
|
|
12
|
+
- [Deleting a Server](#deleting-a-server)
|
|
13
|
+
- [OPC Browse](#opc-browser)
|
|
14
|
+
- [Flat browsing](#flat-browsing)
|
|
15
|
+
- [Tree browsing](#tree-browsing)
|
|
16
|
+
- [OPC Groups](#opc-groups)
|
|
17
|
+
- [Creating a Group](#creating-a-group)
|
|
18
|
+
- [Removing a Group](#removing-a-group)
|
|
19
|
+
- [OPC Items](#opc-items)
|
|
20
|
+
- [Adding an Item](#adding-an-item)
|
|
21
|
+
- [Validating an Item](#validating-an-item)
|
|
22
|
+
- [Reading with OPC Sync](#reading-with-opc-sync)
|
|
23
|
+
- [Disclaimer](#disclaimer)
|
|
24
|
+
- [Contributing](#contributing)
|
|
25
|
+
|
|
26
|
+
## Install
|
|
27
|
+
|
|
28
|
+
Using npm:
|
|
29
|
+
|
|
30
|
+
```bash
|
|
31
|
+
npm install node-opc-da
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
## Usage
|
|
35
|
+
|
|
36
|
+
### OPC Server
|
|
37
|
+
|
|
38
|
+
An OPC server is on object you will be using as the basis for every operation and object instantiation to communicate with a remote OPC server. Since OPC-DA relies on COM/DCOM for all it's features, to create a basic OPC Server object we'll need to create a few COM objects first.
|
|
39
|
+
|
|
40
|
+
#### Creating a Server
|
|
41
|
+
|
|
42
|
+
```javascript
|
|
43
|
+
// creates a COM Session from a domain, an username, and a password
|
|
44
|
+
let comSession = new Session();
|
|
45
|
+
comSession = comSession.createSession(domain, username, password);
|
|
46
|
+
|
|
47
|
+
// sets a global timeout for connections related to this session
|
|
48
|
+
comSession.setGlobalSocketTimeout(timeout);
|
|
49
|
+
|
|
50
|
+
// create a COM Server from a classid, an IP address and the previously created session
|
|
51
|
+
let comServer = new ComServer(clsid, address, comSession);
|
|
52
|
+
|
|
53
|
+
// star the COM Server
|
|
54
|
+
await comServer.init();
|
|
55
|
+
|
|
56
|
+
/* from the COM Server, we create a instance we'll use to create every other COM related object */
|
|
57
|
+
let comObject = await comServer.createInstance();
|
|
58
|
+
|
|
59
|
+
// with the comObjet created, we create an OPC Server object and call init()
|
|
60
|
+
let opcServer = new OPCServer();
|
|
61
|
+
await opcServer.init(comObject);
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
#### Removing a Server
|
|
65
|
+
|
|
66
|
+
To remove an OPC Server reference we call the ```end()``` function. This call only release objects created from the server object (opcBrowser, opcItemManager, opcGroupStateManager) and the server object itself. See the ```node-dcom``` library for more information on how to remove a COM session and server.
|
|
67
|
+
|
|
68
|
+
```javascript
|
|
69
|
+
opcServer.end()
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
### OPC Browse
|
|
73
|
+
|
|
74
|
+
Browsing function are used to explore the items stored in the server. OPC-DA offers mainly two types of browsing: flat browsing and tree browsing. Flat Browsing returns a flat list of all server items, ignoring any internal directory tree. Tree Browsing, walks throughout the internal directory tree and returns a list of directories, each containing a list of items.
|
|
75
|
+
|
|
76
|
+
#### Flat browsing
|
|
77
|
+
|
|
78
|
+
```Javascript
|
|
79
|
+
let opcBrowser = await opcServer.getBrowser();
|
|
80
|
+
let items = await opcBrowser.browseAllFlat();
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
#### Tree browsing
|
|
84
|
+
|
|
85
|
+
```Javascript
|
|
86
|
+
let opcBrowser = await opcServer.getBrowser();
|
|
87
|
+
let items = await opcBrowser.browseAllTree();
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
### OPC Groups
|
|
91
|
+
|
|
92
|
+
After an OPC Server is created, if you want to read one or more items you must first create a group. To achieve this we call the function ```addGroup``` giving a group name and a list of options as parameters.
|
|
93
|
+
|
|
94
|
+
#### Creating a Group
|
|
95
|
+
|
|
96
|
+
```Javascript
|
|
97
|
+
/* opts {
|
|
98
|
+
* {Boolean} [active]
|
|
99
|
+
* {Number} [updateRate]
|
|
100
|
+
* {Number} [clientHandle]
|
|
101
|
+
* {Number} [timeBias]
|
|
102
|
+
* {Number} [deadband] - until asyn read is implemented this does nothing
|
|
103
|
+
* {Number} [localeID]
|
|
104
|
+
* }
|
|
105
|
+
*/
|
|
106
|
+
let opcGroup = await opcServer.addGroup(name, opts)
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
#### Removing a Group
|
|
110
|
+
|
|
111
|
+
To remove a group from an opcServer we call the function ```removeGroup``` giving the group handle as paremeter, and a ```boolean``` value to indicate if the server must wait any ongoing operation to end before being removed or not.
|
|
112
|
+
|
|
113
|
+
```Javascript
|
|
114
|
+
/* {Number} [handle]
|
|
115
|
+
* {Boolean} [force]
|
|
116
|
+
*/
|
|
117
|
+
opcServer.removeGroup(groupHandle, force);
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
### OPC Items
|
|
121
|
+
|
|
122
|
+
#### Adding an Item
|
|
123
|
+
|
|
124
|
+
```javascript
|
|
125
|
+
// create a item manager from the group object
|
|
126
|
+
let opcItemManager = await opcGroup.getItemManager();
|
|
127
|
+
|
|
128
|
+
/* item {
|
|
129
|
+
* {String} [itemID] - the name of the item on the server, can be obtained through browser
|
|
130
|
+
* {Number} [clientHandle] - a locally generated number to identify this item
|
|
131
|
+
* }
|
|
132
|
+
* calls the add() function passing one or more item objects as parameter
|
|
133
|
+
*/
|
|
134
|
+
opcItemManager.add(item | itemList);
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
#### Validating an Item
|
|
138
|
+
|
|
139
|
+
```javascript
|
|
140
|
+
/* item {
|
|
141
|
+
* {String} [itemID] - the name of the item on the server, can be obtained through browser
|
|
142
|
+
* {Number} [clientHandle] - a locally generated number to identify this item
|
|
143
|
+
* }
|
|
144
|
+
*/
|
|
145
|
+
opcItemManager.validate(item | itemList);
|
|
146
|
+
```
|
|
147
|
+
|
|
148
|
+
### Reading with OPC Sync
|
|
149
|
+
|
|
150
|
+
```javascript
|
|
151
|
+
// create a reading object for the group
|
|
152
|
+
let opcSyncIO = await opcGroup.getSyncIO();
|
|
153
|
+
|
|
154
|
+
/* {Number} [dataSource] - from where it will be read
|
|
155
|
+
* {Number} [serverHandles] - one or more handles. An item handle is obtained by calling
|
|
156
|
+
* the add() function, which returns an array of properties for each item readed.
|
|
157
|
+
*/
|
|
158
|
+
await opcSyncIO.read(dataSource, serverHandles);
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
## Disclaimer
|
|
162
|
+
|
|
163
|
+
**This is a work in progress.** Expect things to break, crash and burn. We cannot be hold liable for any damage to any equipment or issues directly or indirectly caused by this library. You've been warned.
|
|
164
|
+
|
|
165
|
+
## Contributing
|
|
166
|
+
|
|
167
|
+
This is a partial implementation and there are lots that could be done to improve what is already supported or to add support for more OPC-DA features. Feel free to dive in! Open an issue or submit PRs.
|
|
168
|
+
|
|
169
|
+
|
|
170
|
+
## License
|
|
171
|
+
Copyright 2017 Smart-Tech, [Apache 2.0 license](LICENSE).
|