YOU DO NOT HAVE TO RUN THE NETWORK TOOL UNLESS U ARE USING USER ALLOCATION FOR IO. Power cycle the CPU, and the error should be cleared! Hope this helps!ĭon t over complicate the Devicenet setup unless required. When all units which are actually connected to the CPU have a Local network number assigned, transfer the routing table to the CPU (has to be in program mode). Again, this is just an identifier so whatever you like. Do the same for the DRM21 and every other SIOU unit you have (only FINS communication modules, not analog units etc), specify a different network number for every unit. This is just an identifier so it doesn't matter what you enter but lets say 1. Right click Unit 01 and select Insert CPU SIOU (Special I/O Unit). Unit number 1 is automatically claimed by the built in ETN module.
0 is the CPU, and 1-10 are the unit numbers "slots" for the special I/O units. Now go to Tools > Start routing table You will see a tree with unit numbers 0-10. In CX-Programmer, connect to the CPU and set it in program mode. Do you have any other communication units in the PLC? Following is the procedure to assign a local network routing table. I see you have a ETN cpu, this means you will also have to assign a network number to this unit. If they do not have this number assigned the CPU does not know how to route FINS messaging.
Basically you would only have to assign a different local network number for every PLC module which can communicate according to FINS messaging. See this post for some basic info on routing tables.
That is why you need to define a routing table, so the CPU unit "knows" where to route messaging to this unit. This error means the CPU unit is unable to exchange data with the DRM21 because it can not identify it on the CPU bus as more than one unit is present which communicates to the CPU unit according to FINS messaging. Hi Scott, welcome to ! FYI this error has nothing to do with the actual Devicenet network or communications.
0 kommentar(er)
