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

licence for Modbus/TCP IP communication

Created by: Import-User-1 at: 2/1/2014 11:30 PM (42 Replies)

Rating (10)

Thanks 23

Result pages:: |; 1 | 2 | 3; |

43 Entries

Entries per page: 10 | 20 | all

3/31/2014 9:00 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Kaulquappe, attached my OB1. Take note that, in this program there are Modbus TCP and software redundancy, as you saw in my OB100. This morning I try again ... anyone have any suggestions is welcome Attachment OB1.pdf (627 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

3/31/2014 11:39 AM	Rate (1)
Kaulquappe Posts: 3093 Rating: (324)	Hello Valerio, I think now I got it! You use ID=1for both connections. You must use different connection IDs. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

3/31/2014 12:13 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	You got it Kaulquappe, I set for master cpu=A ID=3 and for spare cpu=B ID=2 and all SF led are now off. Champagne for everyone. Thanks a lot
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users S_Moderator Kaulquappe

4/3/2014 5:09 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Last question (I hope). Now I changed ID for modbus connection, but now it is not possible to check by means of modbus simulator. Is it necessary some change in OB100? L 1 or ID set by MODBUS TCP WIZARD? T "CONTROL_DAT".ID L T#500MS T "CONTROL_DAT".RECV_TIME L T#5S T "CONTROL_DAT".CONN_TIME CALL "MODBUSPN" , "IDB_MODBUS" ID :="CONTROL_DAT".ID DB_PARAM :="MODBUS_PARAM" RECV_TIME :="CONTROL_DAT".RECV_TIME CONN_TIME :="CONTROL_DAT".CONN_TIME KEEP_ALIVE := ENQ_ENR := DISCONNECT := REG_KEY := LICENSED := BUSY :="CONTROL_DAT".BUSY CONN_ESTABLISHED:="CONTROL_DAT".CONN_ESTABLISHED DONE_NDR :="CONTROL_DAT".DONE_NDR ERROR :="CONTROL_DAT".ERROR STATUS_MODBUS :="CONTROL_DAT".STATUS_MODBUS STATUS_CONN :="CONTROL_DAT".STATUS_CONN STATUS_FUNC :="CONTROL_DAT".STATUS_FUNC IDENT_CODE := UNIT := DATA_TYPE := START_ADDRESS := LENGTH := TI := WRITE_READ := UN "CONTROL_DAT".ERROR S "CONTROL_DAT".ENQ_ENR //INIT completed without error, enable data transfer SPB end L "CONTROL_DAT".STATUS_CONN T "CONTROL_DAT".Save_STATUS_CONN //for static display in VAT L "CONTROL_DAT".STATUS_MODBUS T "CONTROL_DAT".Save_STATUS_MODBUS //for static display in VAT // STATUS_FUNC => Save_STATUS_FUNC L DB100.DBD 38 T DB100.DBD 92 L DB100.DBD 42 T DB100.DBD 96 L DB100.DBW 46 T DB100.DBW 100 end: NOP 0
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/3/2014 5:39 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	or in the IDB_MODBUS, first row ID? or both IDB_MODBUS and OB100? others?
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/3/2014 5:42 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	You have to change the ID in the program as well as in the parameter DB (by using the Modbus TCP Wizard). This means if you use ID=3 for one connection and ID=2 for the other one in OB100, you need to have one connection with ID=3 and one connection with ID=2 in the parameter DB(s).

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/4/2014 10:41 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello I change ID in the OB100, by means wizard I compile DB MODBUS_PARAM, in the relevant DB IDS_MODBUS I set the correct ID but the result is that modbus works but license=false (A090). If I change again the ID the license=true but modbus doesn't work and the code error is A079. Where is the problem? Now I try with ID=100 to test any conflicts.
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/4/2014 1:29 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	I'm not sure if I understood the changes you made correctly. Assuming you use the IDs 2 and 3 and one DB_PARAM, the OB100 should look like this: ********************************************** // first connection L 2 T "CONTROL_DAT".ID ... CALL "MODBUSPN" , "IDB_MODBUS" ID :="CONTROL_DAT".ID DB_PARAM :="MODBUS_PARAM" ..... // second connection L 3 T "CONTROL_DAT2".ID ... CALL "MODBUSPN" , "IDB_MODBUS2" ID :="CONTROL_DAT2".ID DB_PARAM :="MODBUS_PARAM" ..... ********************************************** The parameter DB MODBUS_PARAM should look like this: OUCW_1 STRUCT block_lengthWORD W#16#40 id WORD W#16#2 ..... OUCW_2 STRUCT block_lengthWORD W#16#40 id WORD W#16#3 ..... I hope this helps. Regards, Sakura
	Last edited by: Sakura at: 4/4/2014 1:30 PM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/4/2014 3:09 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Sakura I have a connection for each CPU, anyway I've already tested your instruction but the problem is always the same, working modbus with no license, or license with no working modbus. So I think, are there some mistakes in my IDB_MODBUS? In my attached DB shall I to change address 0.0, 2.0, 348.0 and 350.0? Attachment IDB_MODBUS.pdf (624 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/4/2014 3:50 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	No, never change the values in the instance DB directly. This wouldmess up the functionality of the Modbus block. If you attach your OB1, OB100 and theparameter DB(s), I can check if I find the problem.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/4/2014 4:14 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Thanks in advance, please take note that ID=9 attachment: OB1 OB100 DB97 IDB_MODBUS DB99 MODBUS_PARAM Attachment OB1-OB100-DBs.pdf (579 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/4/2014 4:44 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	I think I'm a little confused now about the two different connections, probably because I don't know much about software redundancy... When using software redundancy, you have two different CPUs. And you have the same program on CPU, which means on both CPUs there is a CONTROL_DAT, IDB_MODBUS and a MODBUS_PARAM. On both CPUs you use the same ID for the connection. Is that correct? I'm asking that because I can only see one connection in the OBs / DBs that you uploaded and I'm wondering where the second connection is.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/4/2014 5:02 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello I have different ID, ID=8 for the first CPU, ID=9 for the second CPU. In the previous post I attached OBx and DBs for the second CPU. Now I am attaching also CONTROL_DAT DB. Modbus TCP is not in the software redundancy. Hence two CPUs, with two modbus, with two different ID, in order to avoid any problem with the redundancy. Attachment DB100.pdf (521 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/7/2014 10:54 AM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello I'm checking the Modbus example to try to find any errors, and I have found that FB104 is used both sw redundancy and MODBUS TCP, so I decided to use FB104 SWR_AG_COM (for sw redundancy) because my modbus is server (not client). Is it a problem? And if yes, what can I do? Attachment FB104.pdf (580 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/7/2014 11:44 AM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	I checked the OBs in your pdf-File and I couldn't find anything wrong. The DB97 IDB_MODBUS looked a little strange to me. The title says it's an offline DB, but there are a few online values in it (DB_PARAM, REG_KEY, IDENT_CODE). That's not how it is suppose to be. But to be honest, I have no clue what causes the problems in your project Have you contacted the support about the problem? They should be able to help you. If you already have another FB104 in your project, I would suggest to rewire the MOD_CLI block. You shold probably check if all the blocks that theMODBUSPN block calls are the correct ones. Just to be sure that this doesn't cause any problems.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/7/2014 12:01 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Sakura, don't worry, I call the support. How is it possible to rewire the FB104? I'm afraid to rewire, what happen in FB104 SWR_AG_COM? I see a FAQ that explain what I do but I'm not sure how to do, can you help me? Step by step if possible, see attachment Attachment rewire.pdf (611 Downloads)
valerio.albo Posts: 23 Rating: (1)
Suggestion To thank Quote Answer

4/7/2014 2:52 PM	Rate (1)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	This is how I usually do the rewiring: - create a new S7 program in my project (just temporary for the rewiring) - copy all Modbus blocks and the T-blocks to the blocks folder of the temporary S7 program - use the rewire function on the blocks in the temporary S7 program - check the reference data afterwards to make sure it worked properly - copy all the blocks back to the block folder I use for my actual program - delete the temporary S7 program Do you only want to rewire the FB104? In that case you just have to enter FB104 in the "Vecchio operando" and the new FB number in the "Nuovo operando" column. Regards, Sakura

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/7/2014 3:15 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello Sakura, perfect! License valid new code error A003, but in the manual it is not clear for me what I can do now, DB is too short ... what?
valerio.albo Posts: 23 Rating: (1)	Last edited by: valerio.albo at: 4/7/2014 3:40 PM
Suggestion To thank Quote Answer

4/7/2014 4:52 PM	Rate (0)
Sakura Silver Member Joined: 9/22/2010 Last visit: 2/10/2025 Posts: 225 Rating: (28)	It means that a DB that is used to store the Modbus datais too short. I can see in the parameter DB99 that you only use data area 1. You use DB90 to store input registers from 0 to 14. This means DB90 has to be at least 16 words long. 15 words are used for storingModbus data and 1 word is used for internal purposes.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users valerio.albo

4/7/2014 4:59 PM	Rate (0)
valerio.albo Posts: 23 Rating: (1)	Hello, I supposed the same problem and I tried with end address 30 but I have the same error, is it wrong?
valerio.albo Posts: 23 Rating: (1)	Last edited by: valerio.albo at: 4/7/2014 5:17 PM
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on