8/7/2022 7:49 PM | |
Joined: 7/30/2022 Last visit: 8/11/2022 Posts: 15 Rating:
|
Hello Duris, today I did just as you advised and that actually helped a lot! SO I forced values in VAT tables and actually now I see that addresses and communication between two master PLCs is not an issue. There is variable IW500 that should actually send that counter signal to the master PLC on one network and then that should go to another master PLC on the second network, but it is not doing that.. So right now, I believe I have an issue on slave PLC in network 1 (S200) that should generate that counter signal. However, today I also notices some faults in TIA portal regarding S1200 PLC. Looks like device or I/O error with message "error in lower level component". In attachment I have several pictures of tests as well as that error. Unfortunately for S200 I need to use MicroWin to see what is happening and that is not my strong side.. Do you have any suggestions I can try to locate that error or? Somewhere on the forum I saw that doing extended download to device helps. AttachmentTest pictures.zip (601 Downloads) |
8/8/2022 9:31 AM | |
Joined: 7/30/2022 Last visit: 8/11/2022 Posts: 15 Rating:
|
Hi Duris, so I took some pictured of diagnostic buffer for those 2 profibus devices (ACS rack being S200 PLC) and DP/DP coupler. When I open diagnostic buffer, all the fields are greyed-out. So just to put a bit of a perspective, S1200 CPU failed and that was changed, SW was loaded on CPU and ever since then it is not working. So now I am wondering is there any incompatibility between modules in the system, or something is not configured correctly? I have latest version of the program, but when I attempt to go online it says incompatible. But when I create new project and load software from PLC it is fine, with exception of those faults appearing for profibus modules (previously attached pictures). Yes, profibus network, connectors, terminating resistors are all good, no BF or SF red lights turned on or anything similar. Yes, there is EM277 PB Slave module attached to S200 and then it connects to the rest of the network. I am also bit confused because I was expecting some issue with DP/DP coupler, but data can go in both directions, but in my opinion it looks like S200 slave is not sending data to S1200, or S1200 cannot receive data from S200, what do you think? Also since CM1243-5 PB module was replaced I am wondering, could bad FW version of that module cause all these issues? I am asking because if data can be exchanged between 2 master PLCs on the network than it shouldn't cause all these issues? AttachmentDiagnostic buffers.zip (665 Downloads) |
8/8/2022 12:24 PM | |
Joined: 9/21/2012 Last visit: 9/10/2025 Posts: 4708 Rating:
|
Could you still show us the 1200 PLC diagnostics buffer, so we can see what the PLC thinks is not ok... |
8/8/2022 5:11 PM | |
Joined: 7/30/2022 Last visit: 8/11/2022 Posts: 15 Rating:
|
Hello Duris, I am not sure if I actually understand what you are suggesting. I tried forcing values from S1200 PLC to S300 and values are there. And values from S300 are coming to S1200. I will attached test pictures again. Data from S1200 going to S300 is in fact 0 unless I force value in from S1200 PLC. And I did that as you described using VAT/ Force tables. At this stage, I believe data is coming from S200 PLC (but in fact it doesn't) and goes to S300 (master on network 2). Unfortunately I cannot connect to that S200 with PPI cable for some reason it cannot detect device, and I have another system with identical CPU and I can connect and read without any issues, not sure if that can be related to this communication issue or not.. AttachmentTest pictures.zip (541 Downloads) |
Last edited by: TommyTommy123456 at: 08/08/2022 17:14:27 |
|
Follow us on