Pyramid Solutions - NetStaX - ESDK

ADDITIONAL FEATURES INCLUDE:

• ESDK stack was tested with ODVA CT21*
• Supports TCP/IP object
• Supports Ethernet Link object
• Flexible and scalable, allowing users to specify the number of connections, requests, etc. from build time parameters
• Supports “Big 12” diagnostics
• Full support for dynamic assemblies
• ESDK-SECURE option available
• ExDK-SAFETY option available
• EtherNet/IP Scanner Class Protocol Stack ‘C’ source code for cross-platform development and portability
• ESDK Scanner DLLs (32 & 64bit) with C++ function call API, C# API for .NET Applications, and a legacy (no longer being updated) COM API for using the ESDK stack with Windows and VB6 applications
• A Scanner Class example application executable with source code that demonstrates use of the ESDK’s Scanner Class API and functionality
• ESDK Getting Started, software reference manuals, and porting guide
• Application notes and code samples that demonstrate specific stack features
• Example STC file to edit for use with your product when pre-conformance testing
• Example EDS file that demonstrates the ESDK stack as
a Class 1 connection target by remote tools, such as RSNetWorx for EtherNet/IP or other configuration tools
• Sample platform files that act as mapping examples for different platforms

* To test the latest ESDK stack, we create a pseudo-device and run the latest ODVA conformance software against the pseudo-device.

PERFORM FUNCTIONS, SUCH AS:

• Start the stack
• Establish an event callback
• Allocate a NIC
• Populate the product identity object
• Instantiate assembly instances (if operating as an Adapter)
• Originate an implicit or connected explicit connection
• Check the connection status
• Originate an unconnected explicit message
• Respond to an external connection
• Consume data from a connection
• Produce data on a connection
• Process an object request
• Stop the stack

Note: The above is an example subset of the ESDK APIs.

DEFINING YOUR DEVICE

When you define your device, you determine what application objects are needed to interface to the outside world for data exchange and configuration.
The ESDK ships with a set of standard objects, but by using the included object templates, you can create your own application objects as well. You can include these when compiling your target code and then instantiate at runtime.
You also determine what connections your device needs to originate and any assembly instances your device needs to expose and instantiate at runtime. These features are controlled by your application code based on the configuration of your device.
Regarding your platform, we ship example “platform files” with our ESDK to assist you in getting the kit ported to your target platform. We use the platform files for mappings so the stack can stay intact, making it easier to integrate stack updates in the future.