issues
search
OPCFoundation
/
UA-EdgeTranslator
An industrial connectivity edge application translating from proprietary protocols to OPC UA leveraging the W3C Web of Things (WoT) thing descriptions.
MIT License
28
stars
7
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add BACnet southbound interface
#36
barnstee
opened
6 days ago
0
Add new variable node called "SupportedWoTBindings"
#35
barnstee
opened
6 days ago
0
Add discovery method for asset that can be discovered
#34
barnstee
opened
3 months ago
1
Add diagnostic interface to connectivity software
#33
barnstee
opened
3 months ago
1
Add GetConfiguration/SetConfiguration methods
#32
barnstee
opened
3 months ago
2
Extra object node left in released Wo-Connectivity nodeset file
#31
barnstee
opened
3 months ago
0
Define how OPC UA type information is specified in WoT TDs
#30
barnstee
opened
6 months ago
7
Add Variable node to return the list of WoT protocol bindings a UA server supports
#29
barnstee
closed
3 months ago
6
Example Modbus TD file fails JSON-LD validation
#28
rlabbeptc
closed
7 months ago
2
Update the context content in the TD sample
#27
sebastiankb
closed
9 months ago
3
Update href value with the specified modbus address pattern + update base value at the top level
#26
sebastiankb
closed
9 months ago
1
Use the latest TD version in the context file
#25
sebastiankb
closed
9 months ago
1
Camel case of entity values
#24
sebastiankb
closed
9 months ago
1
change prefix of modbus-based terms in TD examples
#23
sebastiankb
closed
9 months ago
1
Add prefix of XSD types in TD example
#22
sebastiankb
closed
9 months ago
1
change opcua:type into opcua:datatype opcua:objecttype
#21
barnstee
closed
9 months ago
0
Define syntax of a path into an OPC UA complex type as a separate field in the protocol binding
#20
barnstee
closed
9 months ago
1
Add MQTT as alternative transport for the 3 commands?
#19
barnstee
closed
9 months ago
1
Add the benefits of WoT TD JSON vs. UA nodeset XML
#18
barnstee
closed
9 months ago
1
Don't make a separate namespace per asset a requirement
#17
barnstee
closed
9 months ago
1
Don't specify what types to use for the mapping
#16
barnstee
closed
9 months ago
1
Clarify use case and what WoT is used for
#15
barnstee
closed
9 months ago
1
Use File Transfer API instead of strings for sending the WoT Thing Descriptions
#14
barnstee
closed
4 months ago
1
Use expandedNodeIDs instead of GUIDS?
#13
barnstee
closed
9 months ago
0
Rename ConfigureAsset() and DeleteAsset() to AddAsset() and RemoveAsset() or CreateAsset() and DeleteAsset()?
#12
barnstee
closed
9 months ago
0
Update OPC UA methods diagram with GetConfiguredAsset()
#11
barnstee
closed
9 months ago
0
Review error codes returned
#10
barnstee
closed
9 months ago
0
Implement optional UA method GetConfiguredAsset()
#9
barnstee
closed
9 months ago
1
Fix issues with sample WoT TD
#8
barnstee
closed
9 months ago
1
Explanation of use
#7
alexmc1510
closed
11 months ago
1
IEC 61850 southbound interface
#6
JonasDaenzer
opened
12 months ago
3
Implementing WoT companion specification.
#5
jestun
closed
1 year ago
2
"Packages" is missing
#4
hansgschossmann
closed
1 year ago
1
reference namespace URI instead of download API call at top of WoT TD
#3
barnstee
closed
1 year ago
1
Add flexibility in source of Nodeset
#2
jwise-mfg
closed
1 year ago
0
Support local nodesets, CESMII cloudlib
#1
jwise-mfg
closed
1 year ago
2