Final version: 5.1.6(): • Numericupdown Thousand Separator was added. • 46 different type SQL query added for reporting tools. • Print document function was update, Print screen command added. • Plc communication error function added. • Decimal place added for scale function. • Alternative Ip address added for Redundant and all plc communication driver.

5.1.2(): Multiple screen designer update, many function added. 5.1.1(): Redundant working style was added. Please visit our blog for more information. 5.0.4(): Scada object Backcolor, Forecolor, Enable, Visible and Text property compare method added. Omron Fins Ethernet protocol added. Webserver with password protection or without protection select function added.

5.0.0(): Please visit our blog for more information. Alarms and Warnings can be defined for process values. When alarm or warning occurred, it can be monitored in the Screen real time and informed to E-Mail and SMS recipients. • Easily creates detailed Reports from historical datas and saves them in Excel or PDF format. • With Recipe, previously saved values for the tags are send to the devices by one click. • For creating advanced Screen interfaces, WinTr contains; Symbol Factory software which contains 4000 symbol in 60 category, Dundas’s elegant Chart(Real Time, Historical, Pie, Line, Bar, 3D) and Gauge(Circular, Numeric, Linear, Knob) objects, •.

What is the main difference between WinTr Scada Software and other SCADAs? Why should we prefer WinTr?

• WinTr Scada Software is sold with 3 years free upgrade warranty. • WinTr Scada Software development is free, runtime and development are sold together.

Supervisory Control and Data Acquisition Supervisory. Latest crack software ftp download-2. V6.0 CITECT.SCADA.V7.1R2 /7.0 VIJEO.CITECT.SCADA V7.1 and.

• WinTr Scada Software users are given indefinite free technical support. (By email other than Turkey) • You buy WinTr Scada Software license when you deliver your project to your customer after the completing your project. (With Demo license only first symbol of symbol factory can be used.) • Many other scada softwares are not developed in.NET platform..NET platform born in 2003. However WinTr Software is developed at.NET 2008. Thus development is very easy.

Moreover it is compatible with Windows 7 and other operating systems that will be released. New Operating systems are released.NET framework compatible. • Many.NET objects that can not be found other SCADAs presented in WinTR. Thus your project get out of Windows 95 look and gets Vista apperiance. • We are taking to your service 2009 years award winning chart object dundas chart and gauge. WinTr is the only scada software that uses this variation and visuality. • Reaching Scada variables is very easy with SQL Input/Output tags.

You can reach easily with other programs that you developed or internet browsers or excel. Many scada software export data to excel. WinTr can do this too. But the method mentioned here is different. In this method, scada never reaches excel. Excel reaches to scada via excel macro. • VB and C# scripts are work completely different.

Scada softwares has a restrictions at script functions. However Wintr has no restrictions you can perform many operations by writing scripts almost as if developing program on.NET platform. • It is possible to reach and modify scada informations other than the scada tags with scripts. When such needs occur we provide information our customers freely. We develop needed scripts for our customers some case free some case with fee. • Scripts are compiled once at first then saved as.Net DLL. Then runs directly.

Thus they run faster. Even huge amount operations can run very fast in the script. • At many scada software, the function number which can be run by a button or other object are limited.

However 256 function can be run with WinTr Scada Software Also you can trigger this functions when alarm occured or gone. • Thousands WinTr scada may establish full or restricted access to each other via server and client functionality.

• Can be connected to automation devices via S7 MPI, PPI, Profinet, Host-Link and modbus RTU without OPC server. • E-mail and SMS sent when specified conditions occur.

• You can create many different recipe algorithms with categorized recipe. • Real time data monitoring and control can be done with real time working feature which achieved version 2.0.0 • First going Runtime mode at high number tags may be slow. Then all objects connects each other as interrupt and only works when values changed. Thus you can develop high tag count projects for slow computers. High number means 20000 tag and upper. • Beside many image file you can use animated gif images in scada pages.

• We present all of this excelent features with low price.

Hello All, I have an issue with a site that I am working on and could use your help. I will describe as best I can the before and after. This site has been running an older version of citect for 12 years on old Windows NT computers. It consists of 4 separate units and one master unit.

Each unit consists of a PLC talking modbus via serial cable to its own citect server. All 4 units / servers are connected to their own ethernet network also.

The Master citect server talks to its own master plc control via serial cable also. It is also on the the same ethernet network as the 4 units. The project is for us to upgrade the computers from NT to brand new computers running Windows XP Pro SP3 and using CitectSCADA 7.1 SP3. There is some data sharing between the master citect server computer and the 4 individual unit citect servers.

This data is transferred from the master citect server to the individual citect servers via the ethernet network. The old system used netbios and when all of the citect servers were running the data from the master would show up on the individual citect servers as designed. The four local citect servers also send some of their data to the master citect server for display on graphics screens. When we performed the upgrade to Citect 7.1 SP3 the individual citect servers could not receive their data from the master. Since each citect server gets its PLC data via a serial link I need help in setting up the ports, IODevices and the IOServer forms so that the master server shares the required data with the individual servers.

I have tried using the same setup the old computers and citect used but this did not work. I tried setting up the master server with the 4 IO servers pointing at the net addresses of the 4 individual computers but did not have any luck. I am not sure if I need some citect.ini entries or some other settings. The old system setup had each individual citect server setup with the required serial board, serial port and IODevice necessary for communication with its own PLC via serial link.

They also had the serial definition from the master defined in their ports, iodevices and ioserver section. The master citect server had all of the ports, iodevices and ioservers setup in its settings.

This worked due to the master associating the IOserver name and through netbios as far as I know. I would appreciate any help or direction you can provide. If more specific information is needed please let me know. Jim Spence Controls Engineer J.E.T.S. Technologies, Inc.

Hello, I am uploading a picture that shows the actual communications hookup for all of the computers and PLCs. Business Ethics A Textbook With Cases 7th Edition Pdf here. Each Unit server monitors its own PLC via serial link. The master server / PLC monitors equipment that each unit server needs to know about. So the master and unit servers exchange this data via the ethernet network. The old citect setup and version was able to share this data for display on the graphics screens but I am having problems with citect 7.1 and the communications setup.

I am able to get the servers to display all of the information that is coming over their individual serial links but I cannot seem to get any data from the master server over the network. On the unit servers I only see #COM wherever I am trying to display data from the master server. I believe the problem lies in my communications setup on the master server but I am not sure. Any suggestions would be appreciated.

Thank you for your time. Cherry Lisa Shaw Rare. Jim Spence J.E.T.S. Technologies, Inc.

Jim, You don't mention how you implemented clusters in the new project. I don't know if this is an issue in your site but it sounds like you might have multiple clusters (possibly one for each site). If you do, remember that you must fully qualify each tag name in the form cluster.tagname in order to get the data to be correctly identified throughout the system.

Failure to fully name the tag with its cluster when the tag is outside the current server will make it appear as a COM error. This may not be your problem but you did not mention clusters and in 7.1 if you have multiple clusters you have to fully identify the tag to get data. This is just the first thought I had as I read your description. Dennis Stewart Centric Energy Systems (208) 377-8418. Hello Dennis, Thank for the reply.

I understand what you mean about the use of clusters. At first I tried using a cluster for each unit plus one for the master but then decided to use only one cluster and just prefix all common tags with a unit identifier and assigned to the appropriate ioserver. Since I have screens on my master server that show data from all 4 units using multiple clusters seemed more trouble than it was worth. I have not had a chance to try the single cluster approach yet. The # com errors I saw were due to the master ioserver rejecting my connection. This was shown from the active hardware alarms. The master ioserver was generating a connection refused alarm on unit 1 Citect server.

I will be on site again next week to try the single cluster approach. In 7.1 what tells the unit 1 Citect server how to obtain data from the master server? Is it the use of the NET Address? This is the part I am confused about. Since all Server to PLC communications are done via serial link how do I set up unit 1 to look for some data over the Ethernet network from the master Citect server? Thank you for any info you can provide. Have a great day.

Take care, Jim Spence. Jim, I haven't built a system that is exactly like what you are doing. But I do have a redundant server system and I expect that there will be many similarities. In the redundant system it is necessary to define all the network addresses (IP addresses) for all the connected computers and then create server identities for all the servers on all the computers. In my case with a simple redundant server that meant two IP addresses and 8 servers (2 of each type). Extrapolating this to you case, I would expect that you would need the IP addresses for the unit and master in each unit and all the IP addresses in the master. Also you would need to identify the servers for each unit and the master.

In each case and computer/server that needed to talk to any other computer/server would need to be identified in the systems on both ends of the connection. If all the servers need to talk to each other then with four units and a master you would have 5 network addresses and 20 servers identified on every system. If the units don't talk to each other then you would have the 5/20 combination on the master and 2 addresses with 8 servers on each of the units; each unit having its identities and the master identities.

I think you could do this with a single cluster to simplify the tag naming issues across the system as long as the tags are unique in each case. Dennis Stewart Centric Energy Systems (208) 377-8418. To clarify, does each computer have its own project, so there are five projects in all? Networking basics done correctly?

I.e., can ping each other, see each other on the network, windows firewall off? The setup of the old to the new should be similar but as Dennis stated each computer/project should specify its own ip address. How are each unit projects setup to see the master project and vice-versa? You could use Project Editor - System - Include feature. Each unit project would include the master project, and the master project would include the 4 unit projects.

IOserver names, IPaddresses, IODevice names, all need to be unique across all five projects. The master could be the Trend-Alarm-Report server if all as one cluster. If each a different cluster, then each could be its own Trend-Alarm-Report server.

Regards, Greg Chamberland, CIP. Hello Greg, Yes, there are 5 separate projects. Networking basics are setup and I can ping in all directions. However, I did not ensure that the windows firewall was turned off on the master Citect server. I will make sure that is done for next test.

Each of the HMI computers will be acting as its own io server, trend server and alarm server to act on the data from its attached PLC. The master server is also its own server for its attached PLC. The only complication is the limited data sharing from the master to the unit servers. We are talking about 50 points in all that are being shared from the master to the unit servers. I have done this in the past on older versions of Citect with no issues but 7.1 seems to be a little more picky. I wonder if I can simulate a test at home. I have two computers that I can use to run the master server and unit 1 server and I have two demo keys.

It would be nice to be able to test this before going back on site next week. Thank you for your time and information.

Take care, Jim Spence. In order for each computer to have its own Report-Alarm-Trends (RAT), each will need to be in its own unique cluster, as you can't have multiple RATs in a cluster.

You can then 'Include' cluster 5 (master) to be part of cluster 1 (unit 1), for example. You should be able to test this with two machines, go through the computer setup wizard, have the Unit1 machine be a member of each cluster ( 1 & 5), have master be stand alone for now and on its own machine, setup tags either PLC or disk tags, change a value on the master and unit 1 should see it. Every tag will need to be assigned a cluster (easilty done in dbf editor), and each graphic will need to be assigned a cluster, if you have Master tags and Unit 1 tags on the same graphic, then the graphic is not assigned a cluster, but you'll need to prefix the tags w/ cluster.tagname. Again, ensure firewall is off on all machines (for now at least) Greg Chamberland, CIP.