Difference between revisions of "Communication/FastData"
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
| − | |||
The FastData UDP server allows a UDP client to retrieve from the MC data about specific axes and variables. | The FastData UDP server allows a UDP client to retrieve from the MC data about specific axes and variables. | ||
| + | The server is initialized upon MC startup and is immediately ready to respond to clients. | ||
<br/> | <br/> | ||
| + | =Server Functionality= | ||
| + | The server will receive client requests from any IP address, on port 60000.<br/> | ||
| + | The server will send axes data ONCE upon a SINGLE request of the client, and will send<br/> | ||
| + | data only about axes that were specifically requested by the client.<br/> | ||
| + | |||
| + | Meaning the server is blocked on receive( ) and anticipates data from the client that indicates which axes data to send back. | ||
* IP Address (''to be completed'') | * IP Address (''to be completed'') | ||
* TCP/IP Communication (''to be completed'') | * TCP/IP Communication (''to be completed'') | ||
Revision as of 14:57, 11 June 2014
Introduction
The FastData UDP server allows a UDP client to retrieve from the MC data about specific axes and variables.
The server is initialized upon MC startup and is immediately ready to respond to clients.
Server Functionality
The server will receive client requests from any IP address, on port 60000.
The server will send axes data ONCE upon a SINGLE request of the client, and will send
data only about axes that were specifically requested by the client.
Meaning the server is blocked on receive( ) and anticipates data from the client that indicates which axes data to send back.
- IP Address (to be completed)
- TCP/IP Communication (to be completed)
- Setup
- softMC as TCP Client
- softMC as TCP Server
- UDP Fastdata
(to be completed)
Automation Bus
- CAN (to be completed)