Rating (7)

Thanks 2

18 Entries

In answer to the other questions, I originally had a protool file the vendor had emailed me. we used that and did a conversion with wincc flexible service pack 2. we then downloaded that to the screen. I went out and double checked the profibus cable at the plc and the cable leaving it is on A1B1. Also, I do have step 7 Microwin on one of our older laptops. I couldn't get it to work on my new laptop (Windows 10).

Last edited by: Jen_Moderator at: 07/18/2019 11:04:53

I had a pdf document to post that better explained my situation but it's to large. so I have the one plc s7 200 which a profibus cable goes from there to a local screen by the plc. from that local screen I have the profibus cable from the plc coming in, then another cable going out to the remote screen over by the operator panel. the screen that I programmed won't work at the remote station or the local station. everything looks right as far as the different screens go but just no communication.

Hello,

if you invert the panels, the panel that works on one side then also works on the other side?

In answer to the other questions, I originally had a protool file the vendor had emailed me. we used that and did a conversion with wincc flexible service pack 2. we then downloaded that to the screen. I went out and double checked the profibus cable at the plc and the cable leaving it is on A1B1. Also, I do have step 7 Microwin on one of our older laptops. I couldn't get it to work on my new laptop (Windows 10).

Hello,

or....... can you post to us the protool file, I have an old Field PG with Protool, then I can see which address have the panel..... but i can see tomorrow ..

Last edited by: Ste39 at: 07/17/2019 17:51:49

Last edited by: Ste39 at: 07/17/2019 17:52:46

I just tried the test that you recommended and if I take the original screen (local one) and plug it into the remote spot, it works fine. the one I programmed (remote screen) still doesn't work in the local spot. so it's definitely something I did, lol. Here's the file that the vendor originally sent me that I tried to convert. i'll play around with it some more today if you can let me know what your friend think tomorrow. thanks for all your help.

Attachment

I played around with the address setting for the hmi and when I set it to 10 and downloaded the program I found that I could actually see some of the data from 1 or 2 screens but everything else showed 0. The ####'s were all gone though. it looked like it was communicating but only parts. I started going through the tags for the HMI program and noticed that 3/4s of them were all set the same address VD0. went back to the original protool file and did the conversion with wincc service pack 2 again and verified the tags and now they all had addresses. converted to service pack 3 and the addresses were still there now. apparently when I first did the conversion something happened and only about 1/4 of the tag addresses transferred over. downloaded the newly converted file and I now have all of my data on the screen. Thanks for all of your help with this issue.

I played around with the address setting for the hmi and when I set it to 10 and downloaded the program I found that I could actually see some of the data from 1 or 2 screens but everything else showed 0. The ####'s were all gone though. it looked like it was communicating but only parts. I started going through the tags for the HMI program and noticed that 3/4s of them were all set the same address VD0. went back to the original protool file and did the conversion with wincc service pack 2 again and verified the tags and now they all had addresses. converted to service pack 3 and the addresses were still there now. apparently when I first did the conversion something happened and only about 1/4 of the tag addresses transferred over. downloaded the newly converted file and I now have all of my data on the screen. Thanks for all of your help with this issue.

Hello Hutch,

I'm really glad you solved the problem , however your panel has the following addresses: