Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Redundan Modbus RTU communication via 2 CP341 and 2 Dongles

Created by: Jean-Francois at: 8/30/2010 10:41 PM (11 Replies)

Rating (0)

Thanks 0

Result pages:: |; 1 | 2; |

12 Entries

Entries per page: 10 | all

8/30/2010 10:41 PM	Rate (0)
Jean-Francois Posts: 36 Rating: (0)	Hello I need to use 2 CP341 with Modbus RTU Dongle and communication block in the same CPU rack. I succeeded making 1 working well at the beginingbut nowi'm not sure which part i should double in my cpu program to enable both module for Modbus RTU Slave connection Both CP341 (6es7 341 1ch02-0ae0 ) with dongles (6ES7 870 1AB01 0ya1) Are installed on a remote i/o rack using IM153 Profibus to a S7-315 -2DP Doubling only the call for Modbus blocks in OB1 with respective module adress seem too easy to me but it is hard to see what can work with only 1 instance and what needs to be doubled while everything is securised from Siemens. Any idea or anyone ever do that succesfully ?
Jean-Francois Posts: 36 Rating: (0)
Suggestion To thank Quote Answer

8/31/2010 10:50 AM	Rate (0)
Kaulquappe Posts: 3093 Rating: (324)	Hello Jean-Francois, even if it seems too easy, you need a second call of FB80 with a second IDB. The only difference when calling the FBs is the address of the CP. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer

8/31/2010 2:11 PM	Rate (0)
Jean-Francois Posts: 36 Rating: (0)	thanks but just to be sure what do you mean by IDB ?
Jean-Francois Posts: 36 Rating: (0)
Suggestion To thank Quote Answer

8/31/2010 2:27 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (324)	Hello Jean-Francois, IDB is the short form for instance DB. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer

8/31/2010 8:21 PM	Rate (0)
Jean-Francois Posts: 36 Rating: (0)	last 1: about the M180 register, can i also use 2 times the same as it will initialise both or i should make another set and manageboth inOB1 and OB100like the first set Manny thanks
Jean-Francois Posts: 36 Rating: (0)
Suggestion To thank Quote Answer

9/1/2010 9:22 AM	Rate (0)
Kaulquappe Posts: 3093 Rating: (324)	Hello Jean-Francois, I expect that you talk about the register values which are transferred. I recommend to use the same Modbus addresses because you are setting up a redundant communication. When you use different Modbus address ranges, you have to do a lot of work in the S7 program to be sure that you use the current values. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer

9/1/2010 2:34 PM	Rate (0)
Jean-Francois Posts: 36 Rating: (0)	Ok you comfirmed something else usefull and, no problem, i'm using the same adress mapping in both CP The register values that i was talking, is the intialisation command and status of CP configuration and also feeback error register.I'm more familiar with ladder programming than list butthis part looks like abloc call with external data result.Again i can't verify if anyof the securised blocis using any M180xxx anywhere else than inside ob1 and ob100. I expect not but.... OB1 START_TIMER :=T120 // ! I: Timer for "Timeout initialisation" START_TIME :=S5T#5S // ! I: Time value "Timeout initialisation" OB_MASK :=TRUE // ! I: Mask access errors CP_START :=M180.0 // ! I/O: Start of CP initialisation CP_START_FM :=M180.1 // ! I/O: Edge flag for CP_START CP_NDR :=M180.2 // ! I/O: Info: New write job from CP CP_START_OK :=M180.3 // ! I/O: Initialis. finished without error CP_START_ERROR:=M180.4 // ! I/O: Initialis. finished with error ERROR_NR :=MW182 // ! I/O: Error number ERROR_INFO :=MW184 // ! I/O: Error additional info OB100 AN M 180.0 // Set initialisation flag CP_START S M 180.0 A M 180.1 // Reset edge flag CP_START_FM R M 180.1 Am i right by replacing M180xx by M190xx for the second CP and using T121 wouldn't affect any other function inside Siemens Modbus blocs? I
Jean-Francois Posts: 36 Rating: (0)
Suggestion To thank Quote Answer

9/1/2010 4:18 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (324)	Hello Jean-Francois, yes, you need a second group of flags for the status of FB80. It would be ok to use 190.x. The flags are used to initialize the FB and to show the status of FB80. You can verify them if you want to, e.g. to recognize via which connection the master is communicating. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer

9/10/2010 11:56 PM	Rate (0)
Jean-Francois Posts: 36 Rating: (0)	ok i got mypanel built and i tested my work...working almost great... Hardware: CPUA = 315 2DP (channel 0 = MPI for redondency and ch 1 for Profibus conection to common rack) CPUB = 315 2DP (channel 0 = MPI for redondency and ch 1 for Profibus conection to common rack) Remote rack on a IM153 with i/os and CP341(1) (Modbus adress id 5) with modbus slave dongleand CP341(2) (Modbus id 6) with modbus slave dongle The objectiveis to have 2 redondant CPU in case of 1 failing and the same for CP in case of 1 connection fail... When i only use the cpu that was in control of the remote rack during the power up of everything,bothModbusRTU Slave CP works fine. When i switch to the other CPU, only theLast CP still work.If i switch back to the first CPU: Still only the last CP works to get the first CP to work again, i need to switch power on the panel again.... At this point i think it may be something to do with the initialisation sequence...? Event if program and config is identical in both CPU, i think the first CD reject the new juste Switched CPU.....Can i re-do an initialisation when a new CPU take control of the remote rack where my CP is located ? Is there anything you may think about i can do to solve ths issue ?
Jean-Francois Posts: 36 Rating: (0)
Suggestion To thank Quote Answer

9/11/2010 12:31 AM	Rate (0)
Jean-Francois Posts: 36 Rating: (0)	I got my answer, it works when i mannually re-init the CPs.... [schnippschnapp] new question is transferred to is there a status bit on the 300 that tells when the remote i/o rack if communicating ?.
Jean-Francois Posts: 36 Rating: (0)	Last edited by: O_Moderator at: 9/20/2010 12:38 PM
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on