VxWorks® includes optimized support for the important APIs and standard protocols you require to build robust, real-time platforms.
Wind River SocketCAN
Controller Area Network (CAN) is a communication protocol widely used in real-time control applications in automotive, medical, and industrial environments. Wind River® SocketCAN allows a socket abstraction to CAN bus and provides a uniform interface where multiple sockets can be opened at the same time to listen and send frames to CAN identifiers (IDs). Additional protocols, such as CANopen (available from Wind River partner IXXAT) and DeviceNet, are integrated on top of the SocketCAN layered interface.
Wind River DCOM
Wind River DCOM is an implementation of Microsoft®’s DCOM, scaled for device software. Wind River DCOM enables application distribution between VxWorks-based devices and non-real-time devices, such as desktops. It allows developers to seamlessly integrate device software applications with Windows applications such as data analysis, database storage, or graphical user interface (GUI) running. Wind River DCOM provides a compact, performance-focused solution specifically targeted toward the strict requirements of devices. Wind River DCOM also provides the foundation for management protocols, such as OLE for process control (OPC).
Wind River OPC
Wind River OPC is an implementation of the OPC specification for the VxWorks operating system. OPC is a non-proprietary technical specification that defines a set of standard interfaces based on Microsoft's OLE/COM technology. The OPC standard protocol makes interoperability possible between automation/control applications, field devices, and business/office applications by enabling clients and servers from different vendors to speak the same standard language. OPC streamlines development of device interfaces, increasing connectivity and interoperability between custom applications and enabling applications to easily access subsystem data. The Wind River OPC implementation is specifically designed to support devices with high performance and small footprint requirements.
Wind River USB
Wind River USB enables developers to quickly incorporate standard universal serial bus (USB) connectivity in VxWorks-based embedded devices and their attached peripherals. Wind River USB supports up to version 3.0 of the USB specification, including the universal host controller interface (UHCI), the open host controller interface (OHCI), the enhanced host controller interface (EHCI), and the extensible host controller interface (xHCI) covering low-speed (1.5Mb/sec), medium-speed (12Mb/sec), high-speed (480Mb/sec), and super speed (625 Mb/sec) data rates. All four USB modes of data transfer are available with Wind River USB: control, interrupt, bulk, and isochronous. These data transfer modes enable the simultaneous transmission of asynchronous and isochronous data. Asynchronous data is typically error-rate-critical data, while isochronous data is typically used in multimedia applications, such as real-time audio or streaming video.
Host-class drivers provided with Wind River USB allow developers to connect a wide range of peripherals, from the common to the most advanced. Out-of-the box class drivers are included in the product support keyboard and mouse human interface devices (HIDs), printer, speakers (audio-isochronous), mass storage (bulk-only and control-bulk-interrupt), and communications (END and ACM). The mass storage and communications class drivers enable developers to establish USB connections between embedded devices and advanced peripherals, such as Ethernet networks, modems, digital cameras, and portable storage devices.
Wind River TIPC
With multiple CPU cores comes the challenge of segmenting applications across multiple OS instances, as well as separate memory spaces within each OS. Message channels are a new connection-oriented, bidirectional messaging mechanism that allows tasks to communicate across OS and memory boundaries. This method complements traditional communication mechanisms provided in VxWorks and Linux.
Tasks located in different processes in different cores, or in the kernel, can establish connections with each other independent of their locations. Communication can take place between tasks in different processes or kernels of different OS instances on separate cores, or between tasks in the same process.
« Return to middleware page