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

Modbus on TCP connection with FB-PNMODBUS in Simatic manager between the CPU315-2PN and third partydevices

Created by: TechAutomat at: 4/12/2021 10:35 AM (17 Replies)

Rating (1)

Thanks 0

Result pages:: |; 1 | 2; |

18 Entries

Entries per page: 10 | all

4/12/2021 10:35 AM	Rate (0)
TechAutomat Regular Member Joined: 1/4/2021 Last visit: 8/9/2025 Posts: 17 Rating: (0)	Dear all expert, We are trying to connect the Siemens CPU-315-2PN/DP with multi -third party devices which is supporting the Modbus communication . I read the instruction of available FB -MODBUSPN ( FB-900 is project) and configured the CPU parameter accordingly as a Client . initialization was also done . but the FB900n parameter was data_Type, start_address, Length is always 0000, even all these data type parameter was sequential wrote in same FC . buts after the all done ,I am not able to read the register from third party device register and even the communication also not established . I did below checked . The cable connection is okay as checked the modescan32 & data is received The register address and parameter assigned in respected DB. I observed that –status code #A090 And always shows Busy status–is changing high/ low Please find the attached project ( related block -FC 900, FB900 & DB from 800-903) I need your support for check the program and find error or undone remain in system if anybody can help ?? i can share the project if any body want close look in it.

Suggestion To thank Quote Answer

4/12/2021 10:48 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	Hi, when you want to read registers from the other device, then you must parameterize the MODBUSPN als client. Are you sure, that you configured the PLC as client in your parameter datablock? Check also the connection parameter in the modbus wizard. A090 is only a status information, that you don't have a valid license. But this is not a problem, for testing you can use the block without a valid license... Wüstenräuber
	Last edited by: Wüstenräuber at: 04/12/2021 10:53:18
Suggestion To thank Quote Answer

4/13/2021 12:15 PM	Rate (0)
TechAutomat Regular Member Joined: 1/4/2021 Last visit: 8/9/2025 Posts: 17 Rating: (0)	Please check the status of wizard configuration and VAT table actual feedback from -4 different devices Attachment Connection wizard setting.PNG (1092 Downloads)

Suggestion To thank Quote Answer

4/13/2021 12:22 PM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	Normally the client uses a port number from 2000 upwards... What is the status of the modbus blocks?

Suggestion To thank Quote Answer

4/13/2021 2:27 PM	Rate (0)
TechAutomat Regular Member Joined: 1/4/2021 Last visit: 8/9/2025 Posts: 17 Rating: (0)	VAT _for status current Attachment VAT_status of connection.PNG (1123 Downloads)

Suggestion To thank Quote Answer

4/13/2021 2:34 PM	Rate (0)
TechAutomat Regular Member Joined: 1/4/2021 Last visit: 8/9/2025 Posts: 17 Rating: (0)	one of weird problem is that FB900n parameter was data_Type, start address, Length is always 0000, even all these data type parameter was sequential control wrote manual in same FC . they are overwritten by FB900 in control parameter DB. But after disable the FB 900 , i can observe that these parameter succefully writing in control Parameter DB. CoDE is as below : A "Control_DATA_Comp_A".Init = #InitA_Save A #InitA_Save R "Control_DATA_Comp_A".ENQ_ENR // CALL the MODBUS-TCP/IP Communication with "Compressor A" CALL "MODBUSPN" , "MODBUS_Compressor_A" id :="MODBUS_PARAM_PN_A".ID1_ID db_param :="MODBUS_PARAM_PN_A" REG_KEY_DB :="LICENSE_DB" RECV_TIMEOUT :="Control_DATA_Comp_A".RECV_TIMEOUT CONN_TIMEOUT :="Control_DATA_Comp_A".CONN_TIMEOUT DISCONNECT :="Control_DATA_Comp_A".DISCONNECT ENQ_ENR :="Control_DATA_Comp_A".ENQ_ENR LICENSED :="Control_DATA_Comp_A".LICENSED CONN_ESTABLISHED:="Control_DATA_Comp_A".CONN_ESTABLISHED BUSY :="Control_DATA_Comp_A".BUSY DONE_NDR :="Control_DATA_Comp_A".DONE_NDR ERROR :="Control_DATA_Comp_A".ERROR STATUS :="Control_DATA_Comp_A".STATUS STATUS_FUNC :="Control_DATA_Comp_A".STATUS_FUNC IDENT_CODE := Init_Error :="Control_DATA_Comp_A".Init_Error Init_Status :="Control_DATA_Comp_A".Init_Status UNIT :="Control_DATA_Comp_A".UNIT DATA_TYPE :="Control_DATA_Comp_A".DATA_TYPE START_ADDRESS :="Control_DATA_Comp_A".START_ADDRESS LENGTH :="Control_DATA_Comp_A".LENGTH WRITE_READ :="Control_DATA_Comp_A".WRITE_READ Init :="Control_DATA_Comp_A".Init //reset after job done O "Control_DATA_Comp_A".DONE_NDR O "Control_DATA_Comp_A".ERROR R "Control_DATA_Comp_A".ENQ_ENR // AN "Control_DATA_Comp_A".Init_Error // S "Control_DATA_Comp_A".ENQ_ENR A "Control_DATA_Comp_A".DONE_NDR JCN err1 // Comm Job with Comp-A fnished without error L "Control_DATA_Comp_A".UNIT T "Control_DATA_Comp_A".Save_UNIT L "Control_DATA_Comp_A".DATA_TYPE T "Control_DATA_Comp_A".Save_DATA_TYPE L "Control_DATA_Comp_A".START_ADDRESS T "Control_DATA_Comp_A".Save_START_ADDRESS JU end1 err1: A "Control_DATA_Comp_A".ERROR JCN end1 //Comm Job with Comp-A fnished wit error L "Control_DATA_Comp_A".STATUS T "Control_DATA_Comp_A".Save_STATUS // Status_FUNC => SAVE _STATUS_FUNC CALL "BLKMOV" SRCBLK :="Control_DATA_Comp_A".STATUS_FUNC RET_VAL:=#retA DSTBLK :="Control_DATA_Comp_A".Save_STATUS_FUNC end1: NOP 0

Suggestion To thank Quote Answer

4/13/2021 2:45 PM	Rate (0)
TechAutomat Regular Member Joined: 1/4/2021 Last visit: 8/9/2025 Posts: 17 Rating: (0)	is port no need to be chnage ??/

Suggestion To thank Quote Answer

4/13/2021 4:02 PM	Rate (1)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	Hi, as client the parameter data_type, start_address and length are input parameters. When the parameters are overwritten, then the parameterization is wrong. Check the online values in datablock "MODBUS_PARAM_PN_A", it seems, that the parameter client_server is set to TRUE (so the block works as server). This make no sense: //reset after job done O "Control_DATA_Comp_A".DONE_NDR O "Control_DATA_Comp_A".ERROR R "Control_DATA_Comp_A".ENQ_ENR The telegram is started with a positive edge of ENQ_ENR. After the start of the telegram, ENQ_ENR should be set to FALSE. Have a look at the example project for a correct parameterization. Wüstenräuber
	Last edited by: Wüstenräuber at: 04/13/2021 16:03:14
Suggestion To thank Quote Answer

4/14/2021 9:27 PM	Rate (0)
TechAutomat Regular Member Joined: 1/4/2021 Last visit: 8/9/2025 Posts: 17 Rating: (0)	the paramerization is as below and the ENR_EQR bit is monetry set at network-1 as in attached pics N/w-: 4 parametrization code A M 30.1 / JCN E1 // read_coil L 1 L MB 210 ==I JCN j01 L 1 T "Control_DATA_Comp_A".UNIT L 1 T "Control_DATA_Comp_A".DATA_TYPE L 186 T "Control_DATA_Comp_A".START_ADDRESS L 40 T "Control_DATA_Comp_A".LENGTH CLR = "Control_DATA_Comp_A".WRITE_READ L 2 T MB 210 JU E1 //read_input j01: L 2 L MB 210 ==I JCN j02 L 1 T "Control_DATA_Comp_A".UNIT L 2 T "Control_DATA_Comp_A".DATA_TYPE L 170 T "Control_DATA_Comp_A".START_ADDRESS L 20 T "Control_DATA_Comp_A".LENGTH CLR = "Control_DATA_Comp_A".WRITE_READ L 3 T MB 210 JU E1 //Read Holding registor j02: L 3 L MB 210 ==I JCN j03 L 1 T "Control_DATA_Comp_A".UNIT L 3 T "Control_DATA_Comp_A".DATA_TYPE L L#40053 T "Control_DATA_Comp_A".START_ADDRESS L 128 T "Control_DATA_Comp_A".LENGTH CLR = "Control_DATA_Comp_A".WRITE_READ L 4 T MB 210 JU E1 //read input registor j03: L 4 L MB 210 ==I JCN E1 L 1 T "Control_DATA_Comp_A".UNIT L 4 T "Control_DATA_Comp_A".DATA_TYPE L L#30003 T "Control_DATA_Comp_A".START_ADDRESS L 64 T "Control_DATA_Comp_A".LENGTH CLR = "Control_DATA_Comp_A".WRITE_READ L 1 T MB 210 JU E1 E1: NOP 0 Attachment paramerization code.JPG (1009 Downloads)

Suggestion To thank Quote Answer

4/15/2021 8:25 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 9/8/2025 Posts: 996 Rating: (129)	Check or attach the modbus parameter block. It seems, that the parameterization in this datablock is not correct. If modbus block acts as client, the parameter DATA_TYPE, START_ADDRESS etc. are input parameters. If the modbus block acts as server, the parameters are output parameters. When these parameters are overwritten with 0, it seems, that the parameterization in the PARAM_DB is not correct...

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on