- #CITECT SHOW HIDDEN PAGES DRIVERS#
- #CITECT SHOW HIDDEN PAGES MANUAL#
- #CITECT SHOW HIDDEN PAGES SOFTWARE#
- #CITECT SHOW HIDDEN PAGES WINDOWS#
All tags are located in the order of declaration, with all PLCs, and internal tags, mixed in together. Citect holds all of its tags in a single file, with no structure. These allow you to put together a set of tags in a pre-defined structure, making declaration of a large number of tags quite easy. Another nice feature of the WinCC package is the Structured Tags. Internal tags are handled the same way within an internal tag folder. You cannot have two tags with the same name within the same PLC, the group system is only to make it easier to structure your project. Also, you can make sub folders (groups) within the PLC to make navigation and structuring easier. Each PLC is like a folder, with the tags located inside that PLC folder.
#CITECT SHOW HIDDEN PAGES WINDOWS#
WinCC locates its tags within the Tag manager, with a structure similar to Windows Explorer. The tag setups for the two systems also show the age of Citect. Overall, WinCC has the advantage of user friendliness, with Citect having the advantage of flexibility.ģ, Tags.
#CITECT SHOW HIDDEN PAGES SOFTWARE#
This lack of user friendliness in setting up the Citect comms is simply due to the age of the software and that the communications setup hasn’t changed for at least 10 years, longer than WinCC has even been around. So the added difficulty in setting up has an advantage in being able to communicate with almost any PLC. Citect does have an advantage if you have to communicate with a mix of Modicon and Siemens, like we do. Luckily you only have to setup each device once on either system, and once it is working you don’t have to mess with it. A small mistake can lead to comical results, at least it is funny if you are watching and it isn’t you who is trying to get the system up and running.
#CITECT SHOW HIDDEN PAGES MANUAL#
Each setup is different for each type of PLC, and you must carefully check your setup with the Citect manual to ensure you get it exactly right. You have to setup the IO server, and a range of Boards, Ports and IO devices manually. Citect, on the other hand, probably originated its communications setup in the early days of Windows 2.0 running on DOS. The tags for the PLC are shown with in the PLC folder, all very similar to navigating in Windows explorer and using the file structure. You simply navigate to the “Tag Manager”, right click to add a protocol, then navigate down the protocol to setup comms to your PLCs. WinCC is quite easy, as long as you want to communicate to a Siemens PLC.
#CITECT SHOW HIDDEN PAGES DRIVERS#
Setting up the communications to the drivers tends to show the age of the Citect SCADA system. Overall, Citect tends to be better for non Siemens PLCs, with the two SCADA packages even for S7 range PLCs.Ģ, Communications. This limitation of 8 PLCs also affects our plant WinCC installation when we are running the backup server while servicing the main server. This product costs less than the Siemens driver, and seems to have no trouble communicating to a large number of PLCs simultaneously, un-like the Siemens NCM software which seems to need special hardware to get more than 8 PLCs on the network. This used to be NCM S7 purchased directly from Siemens, but now Citect market a product known as “PSDirect”. To run with Siemens PLCs, you need to purchase a separate driver. Citect, on the other hand, is designed to run with most PLCs on the market. For that reason, I would probably count WinCC as a Siemens only SCADA package. I am also told that it can be used to communicate with other brands of PLC, such as Modicon and AB, however the drivers for these PLCs do not come with the standard package, and Siemens literature does not mention them as possibilities. It can communicate with the S5, S7, TI and S7-200 range. WinCC is designed for the Siemens stable of PLCs. From a practical point of view, WinCC generally needs double the memory, a better CPU, and a far better graphics card than you need for an equivalent Citect machine.ġ, PLC choices. However, this does not seem to work out in practice. Of the two systems, SQL should have less limitations and be more flexible. I actually noticed the same thing when I loaded Citect Plant 2 Business on my PC, which also runs off a MS SQL database. It slows the computer it runs on quite noticeably. WinCC uses far more resources to do the same job. From the point of view of running the SCADA systems, the major difference between the two databases is mainly the amount of computer resources they use. For your entertainment, and possibly to help others make good choices for SCADA systems, I present my impressions of the two systems.Īfter initially posting this, I found it too long to be accepted by, so I will break it into parts.Ġ, Database Systems. As a long time Citect user, I recently had the pleasure of attending a WinCC training program, the idea was that I could then train the rest of the people at our plant on this new SCADA/HMI system.
0 kommentar(er)
