Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Cannot load communication drivers (S7 Protocol Suite.chn)

Created by: Bilal Moolla at: 9/20/2008 12:52 PM (7 Replies)

Rating (0)

Thanks 0

8 Entries

9/20/2008 12:52 PM	Rate (0)
Bilal Moolla Posts: 133 Rating: (9)	Hi good people Problem : I cannot load the S7 Protocol suite driver in tag management of WinCC V7.0 1. I have loaded WinCC V7.0 2. When I do a search for .CHN I find all the communication drivers in C:\Program Files\Siemens\WinCC\Bin* 3. In WinCC when I right click on Tag Management >> Add New Driver and point to C:\Program Files\Siemens\WinCC\Bin I do not see the SIMATIC S7 Protocol Suite.chn Has anyone experienced this problem before? Attachment WinCC V7.0 Cannot Load communication drivers.pdf (268 Downloads)
Bilal Moolla Posts: 133 Rating: (9)
Suggestion To thank Quote Answer

9/20/2008 2:50 PM	Rate (0)
DimiCamp Posts: 168 Rating: (49)	Hi Bilal (hum he hum hum he), tell us something: 1. If you create a new project, S7 Protocol Suite is already in it? Because it should be there without any configuration action... 2. Which windows are you using?
DimiCamp Posts: 168 Rating: (49)
Suggestion To thank Quote Answer

9/20/2008 3:11 PM	Rate (0)
playerslight Posts: 1064 Rating: (72)	try amending the system info with .chm and see if you can find it , i see that they are there when you look in the directory but there are none when you try and load the s7 protocal suite
playerslight Posts: 1064 Rating: (72)
Suggestion To thank Quote Answer

9/21/2008 1:25 PM	Rate (0)
Bilal Moolla Posts: 133 Rating: (9)	Hi guys I am running Windows XP Professional SP2 I cannot change the extension to .chm as.chn isthe only one available. This is very strange because: 1. The channel drivers are availabe on my machine when I create a new project (SIMATIC S7 Protocol SUITE) is available. Project ICE01 (Origanaly created on another machine) 1. I archived the project and loaded it onto my machine However the project ICE01which was created onthe another machine cannotadd the communication drivers.
Bilal Moolla Posts: 133 Rating: (9)
Suggestion To thank Quote Answer

9/21/2008 3:59 PM	Rate (0)
DimiCamp Posts: 168 Rating: (49)	In this case, that's what I would do: 1. Try to open the project on another machine running wincc 7.0. If it opens and everthing is ok, the problem is on your machine. Try to reinstall WinCC 7.0 and if it doesn't work, format c:\ If it opens and S7 protocol suite still missing, the problem is on your application. Try to migrate or duplicate it with project "duplikator" and if it doesn't work, create a new application and copy everything that is possible to it. Tip: if you need do it, the option "project configurator" can help. With it you can export alarm messages, tag loggin configuration and another things to excel and then, from the new application, get all of it via "import" command. Another tip: last friday I had a fight with WinCC 7.0 too. It was exactly the same with WinCC 6.0, could not deal with it till SP1 was released. Best regards, Dimitri.
DimiCamp Posts: 168 Rating: (49)	Last edited by: DimiCamp at: 9/21/2008 4:01 PM
Suggestion To thank Quote Answer

9/22/2008 11:28 AM	Rate (0)
Bilal Moolla Posts: 133 Rating: (9)	Hi Guys What I figured out is that I created a Client Project. This is why I cannot view add a new communication driver. But what I do not understand is how would I configure the tags in this case? Does this mean that all the tags will be configured in a Server machine?
Bilal Moolla Posts: 133 Rating: (9)
Suggestion To thank Quote Answer

9/22/2008 1:17 PM	Rate (0)
April Posts: 1776 Rating: (95)	Hi, thats correct. see WinCC Information System for client project
April Posts: 1776 Rating: (95)
Suggestion To thank Quote Answer

9/22/2008 3:32 PM	Rate (0)
JMJ Posts: 487 Rating: (45)	Bilal Moolla But what I do not understand is how would I configure the tags in this case? Does this mean that all the tags will be configured in a Server machine? Yes, only servers can have process tags. Client can have its own internal tags but not process tags. That's why you only need a 128 licese for client as it does not have any process tags of its own.
JMJ Posts: 487 Rating: (45)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on