.


Quick Start Guide
XMP-SynqNet Controller

Connect Hardware

Pick a Topology

The next step is to set up the hardware of the system based upon the selected topology. Currently, SynqNet supports the following three topologies:


 




For more information about the various topolgies, please see the Node, Cable, Motor, Drive Addressing section under the SynqNet Technology page.

 

Cable Connections: Controller to Node(s)

The type of cables needed to connect the controller to the node(s) will vary based upon the type of controller, the particular hardware features, and the type of nodes you are using in the SynqNet Network. However, regardless of these variables, the cables will be wired the same way. For example, you will always connect a cable from an OUT port and into an IN port. The following diagram will clearly illustrate this connection pattern. For more information about cables and connectors, see the SynqNet Hardware section.



Types of Connectors and Cables

Depending on the type of SynqNet ports (RJ45 or Micro D) on your Controller and Drive, you will need to use one of the corresponding cables to connect them to each other. Please see the Cables section for a list of the various cables.

The following table lists some of the common connectors and their matching cables

Feature
Connector
Cable
Controller I/O
N/A
Micro-D
RJ-45
Rear I/O Bus
N/A
CAN
N/A

Power On Nodes and Check LEDs

After all of the nodes have been connected with the proper cables, power-up the system. To verify that the Nodes have been connected correctly and that each node is receiving a network and power signal, inspect the LEDs at each connector.

Each controller will have four green LEDs:

        • Two LEDs (3 and 4) at the IN port.
        • Two LEDs (1 and 2) at the OUT port.
        • For more information, please see the Controller LEDs section.

Each node will have four green LEDs:

        • Two LEDs (1 and 2) at the IN port.
        • Two LEDs (3 and 4) at the OUT port.
        • For more information, please see the Node LEDs section.

On the Controller:

 

         LED 1 and 3 = Link Activity

 
  • On (Link Active)
  • Off (Link NOT Active)

         LED 2 and 4 = Network Activity

 
  • On (Cyclic Phase--Tx and Rx are Active)
  • Off (Shutdown Phase--Idle State)
  • Blink (Discovery Phase--only Tx is Active)

On the Node:

 

Node LEDs on
the RMB-10V2

  •  LED1 - Link Activity
  •  LED2 - Node State
  •  LED3 - Link Activity
  •  LED4 - Repeater
  •  LED5 - FPGA
  •  LED6 - FPGA Boot Status


The RMB-10V2-SynqNet is shown above.

Each LED has a particular function which is described in further detail below.

Node LED Table
LED
Port
Meaning
Controlled by
Meaning
LED1
IN
Link Activity
PHY
ON = Link active. Normal Operation.
OFF = Link inactive
LED2
IN
Node State
MAC
See Node State Table below.
LED3
OUT
Link Activity
PHY
ON = Link active. Normal Operation.
OFF = link inactive
LED4
OUT
Repeater
MAC
See Node State Table below.
LED5
FPGA
FPGA
MAC
(FPGA)
ON = no nodeAlarm. Normal Operation.
OFF = Unpowered or Reset
Blink = nodeAlarm. (node fault or network fault). See Node Alarm.
LED6*
FPGA Boot Status
FPGA Boot Status
Bowsprit
CPLD
ON (bright) = runtime image has been loaded.
ON (dimmed) = boot image has been loaded.
 
* - LED6 is for Bowsprit design only
    (not on RMB-10V Rev 1 & 2).


Node State Table
Node State
LED2
LED4
Repeater OFF
Repeater ON
Unpowered
OFF
OFF
OFF
Reset
OFF
OFF
OFF
Undiscovered
BLINK .37Hz
OFF
OFF
Discovered
BLINK .75Hz
OFF
BLINK
(same phase as LED2)
SYNQ operation
ON
OFF
ON
SYNQ lost
BLINK 1.5Hz
OFF
BLINK
(opposite phase to LED2)
 
- The repeater is OFF on all states when it is on the last node on the network.

 

Previous | Next

 

       Legal Notice  |  Tech EmailFeedback
       Copyright ©
2001-2010 Motion Engineering