Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

CPU 312C, CP 343-1 Emulation

Created by: Ronny Seth at: 7/16/2007 11:16 PM (6 Replies)

Rating (0)

Thanks 0

7 Entries

7/16/2007 11:16 PM	Rate (0)
Ronny Seth Posts: 4 Rating: (0)	Hello all, Thank you J_Bell for your earlier help. I am not trying to emulate a PNIO device working with CPU 312C with CP 343-1 (Please see attachment) The purpose is: - Send data block to the device - Recieve data block from device For emulation I have 2x CPU312C and 2x CP343-1. I would prefer to use PNIO commands for tis purpose. I observed that I could not connect second CP 343-1 with Profinet Ethernet when I declare first one as PNIO Controller. To solve this, can someone suggest me the best way? I tried many many possible solutions (please see attachment) like I added one more CPU and CP in present project with one CPU and CP and tried with ISO-on_TCP (although not preffered) but I do not know how can I write SEND/RCV program or download fresh configuration in in newly added CPU? Please note that I am using a normal Ethernet LAN Cable (not crossover) as automatic crossover detection is added feature to CP (suggested in Siemens manual) Attachment CPU_CP_emulationTest.pdf (716 Downloads)
Ronny Seth Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

7/16/2007 11:38 PM	Rate (0)
Late Platinum Expert Joined: 1/7/2006 Last visit: 12/23/2024 Posts: 2705 Rating: (320)	Hi Ronny, If you want to do this you need at least one controller, that you can realise with a CP343-1EX30, the 2nd one could also be a CP343-1EX30 or a CP343-1CX10 as device. The device have to be placed in the S7-312C-station and then have to be placed in the hardware configuration on the Profinet of the controller. When you place the device on the Profinet of the controller then you can give the amount of bytes that the device have to communicate with the controller. After that you have to place the amount of communication bytes to/from the device and also from/to the controller with the PN_IO_SEND/PN_IO_RECV.
	I hope that the answer will help, if you have still questions, don't hesitate to ask me. All the best, Late Never say never, think in solutions, not in trouble......
Suggestion To thank Quote Answer

7/17/2007 9:21 AM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hello, well... now I am lost... What do you plan to do? As I remember you wanted to exchange data between two Ethernet Nodes, do you really want to use PROFINET for this? ISO on TCP or ISO Transport or UDP or TCP are much better choices to communicate than PROFINET is. If you keep the ISO on TCP Connection you will have to use the Functions FC 5 and FC 6 (AG_SEND / AG_RECV) to communicate. You can pass up to 8 kB of Data on one request with this type of communication... and you are quite fast on Ethernet. So why do you insist on PROFINET? Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

7/17/2007 9:57 AM	Rate (0)
Ronny Seth Posts: 4 Rating: (0)	Thanks Late, You are right J_Bell, but this has been told by my boss just on Monday because later we would be using PNIO device only. a.)As suggested in last post, I placed device(CP_device)in CPU 312C_device station b.)then I added another station in the project, CPU controller with CP_controller c.)then I added another profinet IO system and to this profinet IO system I attached one CP_device Couldyou please tell me: 1. How can I make sure that CP_device in stepa.) andc.) are same (please see attachment)? 2. Having done all this I have to download hardware config. in controller and device and write program in it, does this mean that I have to plug MPI cable first to controller and dowload HW config of Controller first and thenunplug this cable and plug it indevice and do the same? 3. Do I have to repeat step 2 when I write program for controller and device because I want to write Send/Recv programs in both of them? Sorry, if these questions are stupid. Kind regards, Ronny Attachment HW_Config.jpg (594 Downloads)
Ronny Seth Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

7/17/2007 1:53 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Dear Ronny, I am sorry, but I still think that PROFINET it the false solution for your communication, but who listens to me... anyway. To answer your questions: to 1. To make sure that the Device is the same you have to make sure that the IP Address and the Device Name of the CP in the HW Config of the Device and in the HW Config of the Controller are the same. to 2. You should always be able to access the CP and with that the CPU even if the PN IO Communication runs, this should be possible due to the structure of RT Communication in PN IO. So if you have configured the IP Addresses of both you should be able to program both on Ethernet without changing the Connectors. Please make sure that you use Fast Ethernet Switches, at best SCANALCE X,if you use PROFINET IO. Do not forget that you have to use PNIO_SEND and PNIO_RECV Functions on both sides if you use PN IO on the CPs. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)	Last edited by: J_Bell at: 17.07.2007 14:10
Suggestion To thank Quote Answer

7/17/2007 5:16 PM	Rate (0)
Ronny Seth Posts: 4 Rating: (0)	Dear Bell There are many in this forum who listen to you I did at my best what you adviced me and the present condition is better but not good to start programming: - both CPUs are in RUN mode - CP_controller: SF on, BF blinks, RUN on, RX/TX blinks and P1(port I am using)is on (yellow) - CP_device: SF OFF, rest every LED has same statu as of controller I dont knowbut would it be possiblefor you to please have a look at HW config of my program and tell me what I am doing wrong. Regarda Ronny Attachment PNIO_tes.zip (545 Downloads)
Ronny Seth Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

7/18/2007 9:35 AM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Dear Ronny, try this Project, I guess it should work. Best regards J_Bell Attachment PNIO_tes2.zip (705 Downloads)
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on