collinsd70

Sorry for the delay. Okay so basically you want to simulate your Plant System using your DCS system and the PLC. Without the gateway- your physically removing the communication path between them, your best bet is to see if your DCS system can support a direct connection (or even an Ethernet/IP driver) directly to your PLC. Doing this means you could simulate the entire system (you might have to make a few mods in your PLC for this...but nothing serious).   Regards Daniel.

You will need to wire your inputs to the anode and cathode terminals on your LEDs. Polarity is obviously very important, you will also need a resistor in series if it is not already built into the module. And your supply voltages to and from your input/ output cards needs to be DC Current.   Regards Daniel.

Okay. So what do you want to achieve from this setup? Are you wanting to simulate the Modbus TCP Protocol so you can get data to and from your DCS to your PLC?   Regards Daniel.

Hello Anthony. Okay; you have 2 ways of changing this. 1. Using your DF1 connection; change the IP Address of your PLC to 192.168.1.x (x being anything except 6, so 1-254). ControlLogix dont need a power cycle after this but not 100% sure about CompactLogix integrated ethernet. If it pings OK then you obviously dont need to do this. OR 2. Change your PC IP Address to 10.10.50.x (x can be any except 131, so 1-254). Once this is done, check your can ping OK. Next you need to create a new Ethernet Driver in RSLinx Classic then you should be able to navigate into your Controller Tree.   Regards Daniel. 

Okay- thanks for the explanation. What hardware is the ProSoft Module communicating with? (On the Modbus TCP).    

Hi Anthony. There are 2 quick ways to do this. 1. Open you controller tree in RSLinx Classic and select your CPU/Ethernet Module- in the properties dialog it will display the current IP Address. 2. In your current project, go online with your controller and select your controller properties via the Controller Organizer- in the tab (I think its 'Internet Protocol') there will be the current IP Address with an option to change it then 'set'. There is also the BOOTP utility but the above 2 should get you sorted.   Regards Daniel.

Hi Timalg. Im assuming this is Modbus TCP? I do not believe there is any way to emulate the Prosoft Module, however; According to the Rockwell Forums- Compactlogix and ControlLogix can communicate directly across Modbus TCP via some additional code/AOI, if you have this equipment available and have a supported CPU and firmware revision; this may be worth looking at. https://rockwellautomation.custhelp.com/app/answers/detail/a_id/470365 Regards Daniel.

Your first 2 BYTES here will contain real IO Statuses. The last 2 BYTEs is of type Unsigned Integer which contains the serial number for each module.   Regards Daniel.

You need to enter a Subnet Mask.. After just change the IP address to your liking then download PLC Pamameter file.   Regards Daniel.

Your welcome. Good luck.     Regards Daniel.

Hi Face Book. You will have to consult the manual and individual modules in more detail for this. If you have eletrical schematics this will be easy to cross reference with the SIMATIC Manager.   Regards Daniel.

You have 2 options. 1. Cross Reference your IO in the LAD/FBD Editor and your Symbol Table. 2. Read the associated manual here https://www.br-automation.com/en-gb/products/io-systems/x67-system/bus-controller-modules/x67bc6321/   Regards   Daniel

Check your symbol table.....   Regards Daniel

Well done Paolo. Glad you got it all sorted.     Regards Daniel.

X67BC6321 is your PROFIBUS SLAVE Module- the profibus cable will enter here and terminate; or move on to the next node PROFIBUS node. X67DM1321 is an 2 BYTE I/O Module that is connected directly on the above module- this then passes on to Slot 2 on the X2X Expansion Port. So in brief, the answer to your question is that they are 'local expansion modules' on your BR&R Slave...not profibus.     Regards Daniel.

See attached.   Regards Daniel.

They will be in a 'daisy chain' like Profibus. The data between these module is passed back to X67BC6321 who in turn passes the IO Status to and from the Profibus.

The reason you have more BYTES than required is because maybe they are reserved for Diagnostic Bits. For this information you will have to test online with a VAT table or consult the documentation. The ET200 slices also have this sometimes.

Those should correspond to Head Module part number.  Are you saying those numbers dont correspond to your actual hardware part numbers?  If you cant find them in your catalog, chances are you need a .GSD file update.

Hi Paolo. I want to help but dont have any info on your MES Module. I will built you a configuration for 2 CPUs now and test on my hardware- you 'should' then be able to change the type to your MES Module. Give me 20mins and ill be back.   Regards Daniel

What do you mean by concept? The way your Slave Hardware is laid out is all dependant on your field wiring and the requirements of this.

Welcome Heuve. Found this manual with some examples in LAD and IL, hope it helps. http://www.accs.cz/Files/FA/PLC/QnUCPU_User_s_Manual_Communication_via_Built_in_Ethernet_Port.pdf   Regards   Daniel

Hi Face Book. You have configured your Slave as Node 6. Your Modules have different amount of Bytes depending on the slice/ module configured in your real hardware.  You should check this then ammend as required.

Do you still have the link par error?  I cant vouch for the MES Module- as I cant find the manual; and dont have access to the hardware but I can create you a multi-cpu configuration that runs 2 CPUs then you should be able to change the 2nd CPU Type?   Regards Daniel.

If the above fails...I will create you a working GXWorks2 configuration on a Multi-CPU and test on my hardware. Let us know how you get on..