By downloading this software, the user acknowledges that it is unsupported, not reviewed for security purposes, and that the user assumes all risk for running it. Users accept all risk whatsoever regarding the security of the code they download.
This Software is not officially supported by PTC. PTC will not accept technical support cases logged related to this Software. PTC R&D will not be responsible for any code on the PTC GitHub repository. PTC has not performed its full breadth of testing and quality assurance on this software.
This Software may not be compatible with any existing or future commercial release versions of PTC software. PTC is not responsible for any maintenance for this software.
Review License for more information.
Kepware's Universal Device driver (UDD) accelerates creating user-defined custom driver profiles using JavaScript enabling greater visibility to Tier 2 and Tier 3 niche manufacturing devices including barcode readers, weigh scales, various sensors, simple web servers and RTUs. The introduction of a self-describing and generic development framework and scripting engine gives the writer flexible control over managing driver aspects like basic communication types as well as build and parse messaging. Users can create UDD profiles and configure multiple instances of the profile to connect with their devices.
Example profiles for various hardware and protocol use cases can be found in this repository. Also refer to the UDD Development Guide by the Kepware Solutions Consulting team for more information about the UDD environment and references to official documentation and manuals.
Profiles in this repository target the UDD v2.0 design included in Thingworx Kepware Server (TKS) and KEPServerEX (KEP) v6.11 or later. Please follow the link below for a short summary of changes to upgrade from a UDD v1.0 profile to UDD v2.0 profile:
UDD v1.0 to v2.0 Upgrade Instructions
As stated in the disclaimer and license of this repository, these profiles are provided "as-is". For any questions or problems that are encountered, please open an Issue within the repository. See Repository Guidelines for more information.
Visit: