RTA PU410 Connecting and disconnecting continuously
We have 800XA 5.1 HMI connected to MB300 network via RTA PU410, the link between MB300 and RTA made through Ethernent 10Base2 to 10BaseT converrer.
The system were working propely until power fail happend then the RTA Board Configuration (OnLine Builder) tool of the connectivity server continuously gives system messages tells that RTA connected then disconnected(OnLine Builder messages attached).so system cannot reach all MB300 nodes.
Any one can help me solve this problem?
The system were working propely until power fail happend then the RTA Board Configuration (OnLine Builder) tool of the connectivity server continuously gives system messages tells that RTA connected then disconnected(OnLine Builder messages attached).so system cannot reach all MB300 nodes.
Any one can help me solve this problem?
Asked 2 years ago
Answers
0
Please be sure or check again, there is no other same node number with Rta board on the mb300 network. Seems it is 50. Was it same before or it changed after power fail?
Answered 2 years ago
0
Repeated ”17 3” (node down) followed by ”17 7” (node up) system messages indicates a physical problem with the Ethernet connection between the different nodes on MB300.
I recommend to break up the network in smaller pieces (segments) to try to isolate which segment is not working well (or contain disturbances blocking the network). I’d try to make a minimal MB300 net with only PU410, a switch and one (1) AC400 controller connected via an AUI to fiber optic/twisted pair converter. If that works, slowly add more nodes until the problem return.
You write 10BASE2 (thin coaxial 50 Ohm cable) which ”should work” but was never approved officially. Only 10BASE5 (thick coaxial 50 Ohm cable) was approved.
If you have coaxial segments it is important to:
ABB recommend replacing coax with a switched Ethernet using twisted pair or fiber optimal connections. Installations where electrical interference is likely (=most...) should use fiber optic connections to eliminate ground currents to travel the network (which may cause interference).
I recommend to break up the network in smaller pieces (segments) to try to isolate which segment is not working well (or contain disturbances blocking the network). I’d try to make a minimal MB300 net with only PU410, a switch and one (1) AC400 controller connected via an AUI to fiber optic/twisted pair converter. If that works, slowly add more nodes until the problem return.
You write 10BASE2 (thin coaxial 50 Ohm cable) which ”should work” but was never approved officially. Only 10BASE5 (thick coaxial 50 Ohm cable) was approved.
If you have coaxial segments it is important to:
- Only use thick Ethernet (10BASE2) 50 Ohm cable. Avoid thin Ethernet (10BASE2). There is a 75 Ohm variant of thin coax used e.g. for video or older monitors with BNC connectors which should not be used at all.
- Terminate each end of a coax segment with 50 Ohm end resistors. With two resistors connected the impedance should be 25 Ohm when measured with an instrument (disconnect all nodes when measuring).
- Have one (1) end resistor grounded to Protected Earth (PE).
- Allow no other galvanic connection to the coax or transceivers.
- Have all nodes on the same coax segment on same voltage potential/PE to avoid ground currents to travel the coax
ABB recommend replacing coax with a switched Ethernet using twisted pair or fiber optimal connections. Installations where electrical interference is likely (=most...) should use fiber optic connections to eliminate ground currents to travel the network (which may cause interference).
Add new comment