12/3/2022 8:28 AM | |
Joined: 8/22/2016 Last visit: 10/30/2023 Posts: 12 Rating: (0) |
Hi i have similar issue with my system. I am testing setup in office with hardware as below
i am using simatic manager v5.6 and for modbus blocks i am using Modbus_RTU_V1.3 library. I am able to successfully read slave (meter - PowerLogic PM750) with modbus poll on my laptop with RS485 converter with settings (slave id-1, 9600, none , 1 ) . But i am not able to have successfull communication with my PLC even though i can see Tx/RX led blinking fastly i receive error 8280 on modbus_master block. i tried changing Modbus_comLoad port address in decimal and hex also but get same error. (8280) i tried changing slave address and fetching diffrent data from slave but get same error 8280. is there chance that my cpu 315-2pn/dp fw v3.2.3 is not supporting this modbus working or et200sp properly? ------------------------------------------------------------------------------------------ AttachmentNew folder.zip (291 Downloads) |
Last edited by: Jen_Moderator at: 12/05/2022 05:22:49New subject after splitting |
|
12/4/2022 9:42 AM | |
Joined: 4/28/2015 Last visit: 2/7/2024 Posts: 10533 Rating: (820)
|
Hello, pls do some help to me in this case, I see some more problems probably: 1. your Comm_Load block REQ is still in TRUE. I expect maybe set it to FALSE after read that DONE is TRUE -> OK of cfg. 2. MODE parameter I see you have set to 0, I expect MODE parameter set due internal interface specification or it is depended to Modbus request type (Read/Write)? Ok, I see you have success with some read of values, from this point pls start investigate, with actual parameters. Can you pls also attach screenshot of Master block when you have success, with actual Online parameters to see? Link to helpful manual: Communication via CM PtP with Modbus RTU protocol Update: if your CM PtP support more types of interface (RS232, 485 2w,...) I expect also here problem, is clear from history that some error can be set to cfg internally with incorrect definition of HW interface type. Check carefully inside your prj everywhere where it is relevant that you're use f.ex. RS485 2w interface. I expect maybe some MODE or similar parameter somewhere, it need to be set with value indicated expected interface type (like some ENUM data type). |
Last edited by: Duris_I at: 12/04/2022 09:50:43Last edited by: Duris_I at: 12/04/2022 10:19:13Last edited by: Duris_I at: 12/04/2022 10:19:55Last edited by: Jen_Moderator at: 12/05/2022 05:25:15Link optimized. With best regards... |
|
Follow us on