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

Open communication with the 315 2 PN/DP

Created by: ashvir at: 6/25/2009 9:18 AM (24 Replies)

Rating (1)

Thanks 0

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

25 Entries

Entries per page: 10 | 20 | all

6/26/2009 10:13 AM	Rate (0)
ashvir Posts: 28 Rating: (0)	Hi I have made the changes you suggested but I still dont achieve comms to both devices, Is there maybe another problemthat I have. Attachment modbus.zip (474 Downloads)
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/26/2009 10:19 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Did you execute a restart of your CPU after the change?
	Last edited by: Wuestenraeuber at: 6/26/2009 10:24 AM Last edited by: Wuestenraeuber at: 6/26/2009 10:23 AM
Suggestion To thank Quote Answer

6/26/2009 10:25 AM	Rate (0)
ashvir Posts: 28 Rating: (0)	Yes I did,
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/26/2009 10:36 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Ah, now I found the reason. It's in OB100 the first network. UN "control data 2".ERROR BEB The first modbus instance is called without an error and so you finish the block immediately. So the second modbus instance is not called. Change it to: UN "control data 2".ERROR SPB sec and in the second network you write: sec: NOP 0 .... Wüstenräuber
	Last edited by: Wuestenraeuber at: 6/26/2009 10:39 AM
Suggestion To thank Quote Answer

6/26/2009 10:49 AM	Rate (0)
ashvir Posts: 28 Rating: (0)	With ID#1 and DB2 having Modbus Parameters and Instance DB 102 I do get comms and its working. With ID#2 and DB5 having Modbus parameters with instance DB 103 I get Modbus status A090 and status connection is 0000. If I use Db 102 for ID#2 I get Modbus status A080 and status connection is 0000. Then I restart the CPU but the Modbus staus of A080 remains.
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/26/2009 11:01 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	The connection ID, the DB_PARAM and the instance DB have to be fixed. You have: First connection: ID = 1 IDB: DB103 (symbol name is "instance db 102" - not so good) DB_PARAM: DB2 control dat 2: DB4 Second connection: ID = 2 IDB: DB102 (symbol name is "IDB_MODBSUS") DB_PARAM: DB5 CONTROL_DAT: DB1 This parameters you shouldn't exchange with each other. Change the BEB in the first network in OB100 and the error code A080 will occur no more. Wüstenräuber

Suggestion To thank Quote Answer

6/26/2009 11:26 AM	Rate (0)
ashvir Posts: 28 Rating: (0)	Ah, now I found the reason. It's in OB100 the first network. UN "control data 2".ERROR BEB The first modbus instance is called without an error and so you finish the block immediately. So the second modbus instance is not called. Change it to: UN "control data 2".ERROR SPB sec and in the second network you write: sec: NOP 0 .... Wüstenräuber === Edited by Wuestenraeuber @ 6/26/2009 10:39 AM [GMT ] === I dont understand how to change this as I am not too clued up with stl. Please explain a bit more how to fix.
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/26/2009 12:09 PM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Your program is: Network 1: ... call FB102, DB103 ... L 500 T "control data 2".CONN_TIME L T#5S T "control data 2".CONN_TIME UN "control data 2".ERROR BEB L "control data 2".STATUS_CONN T DB4.DBW 90 .... Network 2: ... call FB102, DB102 .... This means, if the value of "control data 2".ERROR is FALSE (the first modbus initialization has no error), then the OB1 is finished immediately with BEB (BausteinEnde Bedingt/ BEC: Block End Conditional). So the second call of modbus block is not executed. In OB1 the second modbus block is called but in the instance db there are not validinitalization parameters (ID, PARAM_DB...). That is why the errorcode A080 occurs. Change as follows: Network 1: ... call FB102, DB103 ... L 500 T "control data 2".CONN_TIME L T#5S T "control data 2".CONN_TIME UN "control data 2".ERROR SPB sec L "control data 2".STATUS_CONN T DB4.DBW 90 .... Network 2: sec: NOP 0 .... call FB102, DB102 .... With this change the second modbus block is initialized as well. Wüstenräuber
	Last edited by: Wuestenraeuber at: 6/26/2009 12:12 PM
Suggestion To thank Quote Answer

6/26/2009 12:29 PM	Rate (0)
ashvir Posts: 28 Rating: (0)	Im Sorry for being sily but STL is just not for me. I am typing SPB sec in Netwrok 1 but it comes up red 'error'. In netwrok 2 I am able to write sec: nop 0. Could you change it in OB 100 and send back to me as I am not winning with changing it.
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/26/2009 12:39 PM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	I think you have the english syntax: JC sec Try this and if it doesn't work then I will send you the OB100. Wüstenräuber Attachment Serial_3.zip (542 Downloads)
	Last edited by: Wuestenraeuber at: 6/26/2009 12:43 PM added the changed project Last edited by: Wuestenraeuber at: 6/26/2009 12:40 PM Not BEC but JC
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on