Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Connection ModbusTCP with error on AG_LSEND

Created by: C. Reyes at: 3/28/2014 10:49 AM (5 Replies)

Rating (1)

Thanks 2

6 Entries

3/28/2014 10:49 AM	Rate (0)
C. Reyes Posts: 33 Rating: (0)	Hello!! I'm trying to comunicate via ModbusTCP a CP443-1 (Client) with an ABB PLC (Server). I have the next: OB100: CALL FB108 , DB108 id :=W#16#1 //according to NETPRO laddr :=W#16#1FFF //according to HW-Config MONITOR := REG_KEY := server_client:=FALSE // S7 is Client single_write :=FALSE // no use of FC5 and FC6 data_type_1 :=B#16#3 // Holding register db_1 :=W#16#A // DB 10 start_1 :=W#16#8 // from register 8... end_1 :=W#16#20 // ...to register 32 data_type_2 := db_2 := start_2 := end_2 := data_type_3 := db_3 := start_3 := end_3 := data_type_4 := db_4 := start_4 := end_4 := data_type_5 := db_5 := start_5 := end_5 := data_type_6 := db_6 := start_6 := end_6 := data_type_7 := db_7 := start_7 := end_7 := data_type_8 := db_8 := start_8 := end_8 := ENQ_ENR := LICENSED := BUSY := DONE_NDR := ERROR :="CONTROL DAT".ERROR STATUS :="CONTROL DAT".STATUS STATUS_FUNC :="CONTROL DAT".STATUS_FUNC IDENT_CODE := UNIT := DATA_TYPE := START_ADDRESS:= LENGTH := WRITE_READ := OB1: CALL FB108, DB108 id := laddr := MONITOR :=T#1s200ms REG_KEY := server_client:= single_write := data_type_1 := db_1 := start_1 := end_1 := data_type_2 := db_2 := start_2 := end_2 := data_type_3 := db_3 := start_3 := end_3 := data_type_4 := db_4 := start_4 := end_4 := data_type_5 := db_5 := start_5 := end_5 := data_type_6 := db_6 := start_6 := end_6 := data_type_7 := db_7 := start_7 := end_7 := data_type_8 := db_8 := start_8 := end_8 := ENQ_ENR :="CONTROL DAT".ENQ_ENR LICENSED :="CONTROL DAT".LICENSED BUSY :="CONTROL DAT".BUSY DONE_NDR :="CONTROL DAT".DONE_NDR ERROR :="CONTROL DAT".ERROR STATUS :="CONTROL DAT".STATUS STATUS_FUNC :="CONTROL DAT".STATUS_FUNC IDENT_CODE :="CONTROL DAT".IDENT_CODE UNIT :=B#16#1 DATA_TYPE :=B#16#3 //Holding register START_ADDRESS:=W#16#8 //From register 8 LENGTH :=W#16#18 //24 Words (From register 8 to register 32) WRITE_READ :=TRUE U "CONTROL DAT".ENQ_ENR R "CONTROL DAT".ENQ_ENR In DB10 I have de data that I want to send to PLC ABB. I configurated in NetPro the another station (PLC ABB) and I created the connection between PLC ABB abd CP443-1 in the S7-CPU. But when I try to comunicate a failure about AG_SEND appears, the failure is W#16#8304, this means that "The connection is not establsihed", but how can i to establish the connection? Thanks
C. Reyes Posts: 33 Rating: (0)
Suggestion To thank Quote Answer

3/28/2014 10:58 AM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello, my first idea is: wrong IP-address, wrong port number. When the connection parameterization from NetPro is transferred to the CPU, the CP itsselftries to establish the connection. No action is required in the user program. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

3/28/2014 11:09 AM	Rate (0)
C. Reyes Posts: 33 Rating: (0)	Kaulquappe Hello, my first idea is: wrong IP-address, wrong port number. When the connection parameterization from NetPro is transferred to the CPU, the CP itsselftries to establish the connection. No action is required in the user program. Regards, Kaulquappe Hi Kaulquappe! Thanks for your answer! The IP-address are not wrong, and I put the port number the 2001 for the CP and the 2002 for the ABB PLC. Is this correct? If i enter in NetPro and I click on "Active/Desactive the link status" then in the chart below on the "Status link" appears something like that: "Active link set up" (In spanish "Establecimiento activo de enlace en marcha") And I dont know whats the meaning of this.
C. Reyes Posts: 33 Rating: (0)	Last edited by: C. Reyes at: 3/28/2014 11:24 AM
Suggestion To thank Quote Answer

3/28/2014 11:34 AM	Rate (1)
Kaulquappe Posts: 3093 Rating: (323)	Hello, the server usually uses port 502 for ModbusTCP communication. So set the remote port to 502 in NetPro. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users S7 AUTOMAN

4/1/2014 9:43 AM	Rate (0)
C. Reyes Posts: 33 Rating: (0)	Kaulquappe Hello, the server usually uses port 502 for ModbusTCP communication. So set the remote port to 502 in NetPro. Regards, Kaulquappe Thanks!! This was the problem!
C. Reyes Posts: 33 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Kaulquappe

5/8/2018 11:14 AM	Rate (0)
Jen_Moderator Diamond Member Joined: 6/19/2017 Last visit: 9/6/2024 Posts: 8175 Rating: (174)	New question published by Dsouza is split to a separate thread with the subject Problem with WinCC communication - Getting error code: 8304 . Best regards Jen_Moderator

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on