After replacing sm 1234 module, should it be set in Bo Tu software?

I believe many industrial controllers have been confused by Siemens software, and so have I. For Siemens software, there are three virtual machines installed on the computer at the same time, only for different versions of different software. Today, I want to comb the software for you, so that you can know more about Siemens Bo Tu and wincc.

Let me first talk about how my three virtual machines are set up:

1, WIN7 32-bit virtual machine: old version of STEP 7 V5.5 Chinese version+WinCC v7.0s3.

This version is the earliest software that supports S7-300/S7-400 programming, and now it has nothing to do with Bo Tu. Although most companies have eliminated S7-300/400 now, many projects we are undertaking now involve the transformation of old projects, and PLC can't replace them, so we still keep STEP 7 and WINCC V7.0. Now many people say that Bo Tu can also program 300/400, which is true and can be programmed. However, the conversion of the old project involves the need to open the old program. If you only use Bo Tu, this involves porting old programs. The second reason to keep it is that Bo Tu's programming function of the old PLC is not as complete as the old software, and some functions are not. After all, Bo Tu was not designed for 300/400.

2，WIN7 64。 Bo Tu V 15 professional edition. Note: After installing this version, it is not allowed to install WINCC V7.4 separately.

Before introducing this version, I want to talk about WINCC software. Now there are two versions of Siemens WINCC, with different download locations.

The first type: integrated in Bo Tu, that is to say, after you install Bo Tu, WINCC will be in it, so you don't need to install it again.

The second one: WINCC V7.4, which needs to be downloaded and installed separately. This version of WINCC can also be connected to the current PLC 1200/ 1500. This version of WINCC is the same as the earliest download and installation of WINCC, and you can understand it as an upgraded version of WINCC before Bo Tu.

WINCC of Bo Tu v 15 Professional Edition is not compatible with WINCC V7.4, which means that only one WINCC can be installed in a system.

Bo Tu's biggest improvement in software is integration. It integrates STEP7, WINCC Flexcible with touch screen and HMI WINCC with PC into one software, which makes it more convenient to inherit variables, instead of establishing variables separately for STEP7 and WINCC as before.

For the version of Bo Tu before V 15, STEP7 and WINCC can be installed separately, that is to say, for the version of Bo Tu before V 15, only STEP7 can be installed if you want STEP7, and WINCC can be installed separately if you want WINCC, which can solve the problem of WINCC incompatibility. In other words, some people arrange to install STEP7 from Bo Tu instead of WINCC from Bo Tu.

However, Bo Tu V 15 is not so prominent. Bo Tu V 15 is not allowed to install STEP 7 and WINCC separately now, which means that there is no option when installing Bo Tu V 15, and they must be installed at the same time. After clicking Settings, the two softwares will be installed directly. So there is no way. I installed the third virtual machine.

Summary: WINCC integrated by Bo Tu V 15 Professional Edition can no longer be installed separately. This version of WINCC is the most common WINCC. You can edit the touch screen HMI or configure the HMI on the PC. However, it is not compatible with WINCC V7.4 downloaded separately, and WINCC V7.4 cannot install Bo Tu V 15 Professional Edition.

3，WIN7 64。 Bo Tu V 15 Advanced Edition +WINCC V7.4

Although this version of Bo Tu can't install WINCC selectively, that is to say, STEP 7 and WINCC will be installed at the same time, this version, which integrates Bo Tu's WINCC, has weak functions, and can configure all the touch screen panels and advanced PCs when WINCC runs, but it can't run in SCADA system.

This version of Bo Tu is compatible with the traditional WINCC V7.4 and can be installed at the same time.

Conclusions 2 and 3: If only WINCC in Bo Tu is used to write touch screen software, and the PC end of SCADA system is not completed, and then the traditional WINCC V7.4 is used as the PC end of SCADA, only one virtual machine can be used.

Namely: Bo Tu V 15 Advanced Edition +WinCC V7.4, this configuration can realize the following functions:

1, PLC programming

2. Siemens touch screen panel configuration

3.WINCC SCADA PC client

If there are no personal suggestions and special needs, install as described above.

I installed two virtual machines for the following reasons:

The first virtual machine: Bo Tu V 15 professional edition. Because many customers now buy software only from Bo Tu, WINCC on PC side of SCADA system should be integrated with Bo Tu, and traditional WINCC V7.4 cannot be used alone, so this virtual machine is used to:

1, PLC programming

2. Configuration of touch screen panel

3.WINCC and Bo Tu integrate to realize SCADA PC.

The second virtual machine: Bo Tu V 15 Advanced Edition +WinCC V7.4

I still like this version. It's more traditional and easy to use. Implemented functions:

1, PLC programming

2. Siemens touch screen panel configuration

3. The traditional WINCC SCADA PC client is more convenient to connect to the database.

At the end of the article, the differences between different versions of Bo Tu are attached, which is also difficult to find on Baidu. Let me summarize it for you.

Bo Tu WINCC*** has four versions:

1, basic: used to configure simplified series panels (Siemens touch panels are divided into simplified version, smart version and mobile panel). This can only be configured in the simplified version.

2.WINCC Exquisite Edition: It is used to configure all touch screen panels, and its functions are improved compared with the basic edition.

3. Advanced Edition: You can configure all panels and PCs running WINCC Runtime Advanced Edition.

4. Professional Edition: used to configure all panels and PCs running WINCC Runtime Advanced Edition or WINCC Runtime Professional Edition in SCADA system. It is used to build Scada system with configuration ranging from single station system to multi-station system (including standard client Web client).