Performance Motion Devices CME N Series, User Manual

Page: 42 / 70

42 ION/CME N-Series Digital Drive Developer Kit User Manual
2
The Pro-Motion link is generally always present during CME code development and execution.
Host Network Link
Many N-Series ION units in the actual application will be linked to a host/supervisory network to receive commands
and report results and status. An example of a host network link is a factory floor network.
The host network link often uses an application-specific custom protocol or end-industry specific standard protocol
to command the N-Series ION. Examples of commands that might be sent on such a host network are “Arm Extend”
or “Move indexer to slot #15”. The protocol and interpretation of such commands are specific to the end application
and so the user code downloaded into the N-Series ION, among other things, will have the job of interpreting and
responding to such commands. It is also possible that the host network utilizes PRP for communication, particularly
if all of the devices on the network are PMD based products such as ION/CME or Prodigy/CME boards.
Not all systems executing user code on the CME will have a host network. For example some applications are fully
standalone and do not have a host network.
For examples of different network topologies and applications supported by N-series IONs refer to the “Typical
Applications” section of the
ION/CME N-Series Digital Drive User Manual .
Console Link
The final link in a typical CME code development setup is the console channel. This function is discussed in more
detail in the
ION/CME N-Series Digital Drive User Manual but provides a convenient pathway for sending printf type
statements from the user code running on the N-Series ION to a separate monitor or to the Pro-Motion debug
console window.
The console link does not have a protocol as such and transmits in ASCII whatever messages are sent using printf
commands executed in the CME user code.
While a console port connection may be useful, particularly in the earlier stages of user code development, not all
systems will need or use a console channel link.
2.5.2 Development Connections by ION Unit Type
The table below provides information on typical connections, for each N-Series ION host interface type, for the above
three link types. As noted earlier not every application will require all three connection links.
* Pro-Motio n and console traffic are carried via PRP on the PRP node ID. The Host node ID is user selected but must be different than
the PRP node ID to avoid a conflict. If it is preferred that no additional CAN traffic is introduced to the Host CAN Network, Serial3
may instead be used for Pro-Motion and Console traffic.
** Serial3 carries Pro-Motion communications along with console traffic (using PRP’s virtual console connection peripheral type). An
alternative is to use the RS232 Serial2 connection for raw console traffic.
ION Host
Interface Type Pro-Motion Link Host Network Link Console Link
CAN/SPI CAN - PRP node ID* CAN - Host node ID CAN - PRP node ID*
CAN/SPI Serial3 SPI Serial3
Serial Serial3 RS232 - Serial1 Serial3**
Serial Serial3 RS422 - Serial1 Serial3
Serial Serial3 RS485 - Serial1 Serial3
Ethernet TCP port 40100 TCP port 0-65,535 except
40100 UDP