General Description
19
www.ocularrobotics.com
Ocular Robotics Pty Ltd
3.4.3
Network Topology
It is recommended that the system be used on a private network to avoid large amounts
of (unwanted) data potentially being sent to all computers on the network (see Figure
3.9). Multiple REV25 Vision Units/Systems can be connected on a single network.
However this should be done using a switch to avoid data collisions on the network (see
Figure 3.10).
The REV25 is configured to allow any number of clients to receive data when in
broadcast mode. The REV25 will only accept commands from the Primary Client
however. This is to ensure that multiple clients cannot simultaneously send conflicting
commands to the sensor. The Primary Client is determined by the REV25 in a very
simple manner, it is the client that first sends data to the REV25 after it is powered up.
For a more detailed explanation of the network behaviour of the REV25 System see the
RobotEye UDP Communications Specification available for download from the Ocular
Robotics website.
In most situations use of a Cat5e Ethernet cable will be sufficient for operation of the
REV25 Vision Unit/System, however it is recommended that a Cat6 cable be used over
long distances to avoid packet loss due to the large volume of data.
The REV25 System enclosure has an IP68/69K rated (when used with the mating cable
plug) RJ45 connectors for use when environmental conditions require the use of extra
protection. The mating cable plug is a Souriau UTS6JC18RJN and can be purchased as an
Ethernet cable assembly from Ocular Robotics or through various suppliers of
electronic connectors.
