Problems resolved and optimization of configuration scenarios with this hotfix: ● The Reset bit is not reliably executed for the following HMI devices: – OP 73 – OP 73micro – OP 77A – TP 177A – TP 177micro – Basic Panels ● The opening times for screens on the TP 177A und TP 177micro have increased with WinCC flexible 2008. ● The hour glass is not shown when changing screens on the TP 177A and TP 177micro HMI devices. This can result in malfunctions. ● No 'Bit' data type tags should be configured in the 'R' area on the OP 77A, TP 177A and Basic Panels with Allen Bradley DF1, because incorrect values may occur. ● Sporadical interrupts of connection with TP 177micro. Hotfix 2 for WinCC flexible 2008. This hotfix corrects the following problems in the engineering system and optimizes configuration scenarios: ● Instance update of faceplates Some changes do not require an instance update of faceplates.

Microsoft Sql Server 2005 Instance Wincc Siemens. Use the following procedure to uninstall an instance of Microsoft SQL Server 2005. WinCC flexible 2008 SP3. This manual is valid for STEP 7--Micro/WIN, version 4.0 and the S7-200 CPU product family. SIMATIC HMI WinCC flexible 2005 Micro User s Manual ( English). 7 WinCC flexible 2008 SP3 Starting the Microsoft SQL Server 2005 Express Instance The WinCC flexible instance of Microsoft SQL Server no System Manual.

● Errors during compilation Deriving an instance from faceplates with formatted text results in errors during compiling. ● Error with dragging and dropping faceplates from a library ● Problems updating faceplates Using formatted text in faceplates results in errors when updating these faceplates. ● Using 'Undo' and 'Redo' on faceplates with formatted text and structures results in corruption. ● Errors during STEP 7 synchronization If you replace a CPU with another that has a different revision level, STEP7 synchronization may not function correctly. ● SIMOTION projects cannot be opened In some circumstances, HMI projects created with WinCC flexible 2007 cannot be opened in SIMOTION.

● Problems with DEMO mode No DEMO mode after removing valid compact keys. ● Error installing MSDE ● Error message when closing WinCC flexible If the last action you perform in WinCC flexible is changing the visibility of layers, an error message appears when you close WinCC flexible. ● Canceling 'Save as version' Depending on the computer load, 'Save as version' cancels without results. ● Save as version without administrator rights If you do configuration work without administrator rights, you cannot use 'Save as version'. ● Internal error If you delete a trend display that contains routing tags, internal errors occur.

● Illegal array lengths with TP177 6' and TP177 6' portrait devices ● USB PPI cable 6ES7901-3DB30-0XA0 as of Version 06 The 'Reset to default settings' fails with the following HMI devices: – Mobile Panel 277 – MP 277 – Mobile Panel 177 DP – Mobile Panel 177 PN – Mobile Panel 277 – TP 177B (without TP 177B 4') – OP 177B – TP 277 – OP 277 – MP 177 – TP170A – TP170micro This hotfix corrects the following problems in Runtime and optimizes its performance: ● After stopping Runtime and restarting the device, the last language to which you switched is no longer active. You have transferred a project to an HMI device and switched to a different configured language.

You then stop Runtime and restart the HMI device. When the HMI device has started and is ready to operate, the language to which you last switched is no longer active. All CE devices are affected ● After WinCC flexible Runtime 2008 has been removed, some ActiveX applications (for example, Automation License Manager) may no longer run correctly. Note It is imperative that the hotfix be installed before WinCC flexible Runtime 2008 is removed. ● Text fields are displayed truncated.

When you convert projects from WinCC flexible 2007 to WinCC flexible 2008, configured text fields may be shown truncated in Runtime, if the 'Adapt utomatically' option is disabled Hotfix 1 for WinCC flexible 2008 ( 19486 KB ) It is obligatory if you want use examples from official site. This hotfix solves the following problems in Runtime and optimizes configuration scenarios: ● Restart of HMI device or exiting the simulation The screen change from recipe view can result in a restart of the HMI device in some HMI devices. Certain configurations during simulation of HMI devices can exit the simulation.

Devices affected: – OP 77A – TP 177A – KTP 178 – KTP400 Basic – KTP600 Basic – KTP1000 Basic – TP1500 Basic Hotfix 2 for WinCC Flexible 2008 SP1 ( 72853 KB ). Problems corrected in Hotfix 2 This hotfix corrects the following problems in the engineering system and optimizes configuration scenarios: ● Incorrect display of graphical elements If you work with many graphical elements in WinCC flexible, the graphical elements are no longer displayed correctly. ● Error message while compiling You will see the following error message during compilation of a comprehensive WinCC flexible project: 'The WinCC flexible Engineering System does not have sufficient memory to continue and must be shut down. Close all unnecessary applications and restart the WinCC flexible Engineering System.' ● Failed project transfer If you have compiled a project with WinCC flexible Service Pack 1, it can no longer be transferred to the HMI device. The compiled project file '.fwx' is too large. Hotfix 1 for WinCC flexible 2008 Service Pack 1 ( 72694 KB ).

This hotfix corrects the following problems in the engineering system and optimizes configuration scenarios: ● Internal compiler error with tags with linked animations. If an error occurs with tags with linked animations, the affected location is displayed. ● Conversion error opening projects created prior to WinCC flexible 2008 SP1. Events at a tag with array elements are deleted during conversion. ● Incorrect references after conversion of projects created prior to WinCC flexible 2008 SP1. The events at a tag with array elements deleted as a result of the conversion error are restored. If you have configured a new event in a project that has already been converted, the old incorrect reference is deleted.

The affected tags are logged in the output window in either case. ● Long compile times in projects with numerous faceplate instances. Runtime problems resolved and optimization of configuration scenarios with this hotfix: ● The 'Transparent color' setting does not work on the 'Graphic view' screen object on the following HMI devices: – OP 270 – TP 270 – MP 270 – C7-636 ● Touch operation is not detected. Touch operation is sporadically not detected on the following HMI devices: – TP 177 4' – OP 177B – TP 177B – TP 277 – Mobile Panel 177 – Mobile Panel 277, Mobile Panel 277 IWLAN – MP 177 – MP 277 – MP 377 ● The sound does not work on some of the HMI devices of the MP 377 series. Add new images for fix problems. Support for Microsoft Windows 7 WinCC flexible with Step7 Integration under Windows 7 SIMATIC Step7 V5.4 is not released for the operating system Microsoft Windows 7.

It therefore is not possible to use WinCC flexible and Step7 in the integrated mode under Windows 7. For this a separate release will be carried out at a later time 2. After installing SP2 ALM shows me 4 missing keys( I have used Simatic_EKB_Install_2010_03_20, maybe there is a newer one). The missing keys: Family-----------------------------Product--------------------------Version SIMATIC HMI-------------WinCC flexible /Audit for PC--------------1.3 SIMATIC HMI-------------WinCC flexible /Recipes for PC-----------1.3 SIMATIC HMI-------------WinCC flexible /OPC-Server for PC-------1.3 SIMATIC HMI-------------WinCC flexible /Sm@rtAccess for PC-----1.3 EKB install has only Version 1.0. WinCCFlexible is running but maybe there some parts which doesnt work without these keys.

For testing Simatic_EKB_Install_2010_05_09.zip Size:6158 KB wait report! All previous versions may fail if the installed the new version of the ALM v5 keys - type v5! Error will be corrected in future versions.

Because of the new release ALM v5 may be many intermediate versions as far as finding new challenges. Support for Microsoft Windows 7 WinCC flexible with Step7 Integration under Windows 7 SIMATIC Step7 V5.4 is not released for the operating system Microsoft Windows 7. It therefore is not possible to use WinCC flexible and Step7 in the integrated mode under Windows 7. For this a separate release will be carried out at a later time 2. Support for Microsoft Windows 7 WinCC flexible with Step7 Integration under Windows 7 SIMATIC Step7 V5.4 is not released for the operating system Microsoft Windows 7. It therefore is not possible to use WinCC flexible and Step7 in the integrated mode under Windows 7. For this a separate release will be carried out at a later time 2.

You can determine the time of execution so that your devices are backed successively (To do this, go to AdminClient >Jobs >Job configuration >General >Schedule). Alternatively, you have the possibility to configure the number of uploads running in at the same time. To do so proceed as follows: • Open AdminClient >Ini files • Open the file Upload AgentStation.ini (Path to the file: vdServerArchive VD$A Configuration Upload) • Search for the section: [Common], or add it to the file with the key 4900 and value 1 (i.e. The number of uploads to run at the same time): [Common] 4900=1• Under this section specify type of upload and insert the key and value, e.g.: [FTP] 4900=1 The result of this is that uploads are done one after the other. You can configure the number of comparisons running at the same time. To do so, proceed as follows: • Open AdminClient • Open the file 'Compare AgentStation.ini' (Path to the file: vdServerArchive VD$A Configuration Compare) • Search for the section: [Common] • If the section does not already exist, insert it as follows: [Common] 4930=2• Under this section specify the type of upload and insert the key and value, e.

G.: [FTP] 4930=2 The result of the above example is that two comparisons are started at once. Note: • The [Common] section can contain multiple Upload class sections (such as UNC, FTP, SimaticS7 etc.) • The value in the [Common] section is the maximum. If any values for the key 4900 are greater than the value under [Common], then the value under [Common] will override them • Possible values: minimum = 1, maximum = 1024, default = 5 •. In order to automate the login procedure of UserClient and AdminClient, please proceed as follows: • Open the properties of the desktop shortcut of the UserClient and/or AdminClient by right-clicking on it.

• Go to the tab Shortcut and add the following parameters in Target: /account: /domain: /password: EXAMPLE D: VD vd VDogClient.exe /at:c '/rd:D: VD vdCA' /account:YourUserName /domain:YourDomainName /password:YourPassword Notes • Please be aware that security risks are related to this practice. Among other things passwords are shown in plain text. • The user must be previously registered in User management of the AdminClient. Error messages/error codes: • 31102 • 21053 • 21055 • 21053 EXPLANATION The logged in user lacks certain rights that are required when the SQL database instance needs to be edited. The role 'sysadmin of the SQL server' must be assigned to the user with restricted access rights. This means that the configuration described below must be carried out from an administrator account or another account with appropriate access rights.

SOLUTION 1 • In the case of 'WinCC flexible 2007' together with 'SQL server 2005', please proceed as follows: • Open the 'SQL-Server Management Studio' and establish a connection to the WinCC flexible instance. • Container 'Security'>open 'Logins' • Place mouse pointer on 'Logins' and press right mouse button >place mouse pointer on 'New login' and press left mouse button • Enter user name together with host or domain name or select user by deploying the search function • Focus on area 'Server Roles' and assign role 'sysadmin' to user Close dialog, log out of and back in to Windows Now the versioning will work for this particular user If further user accounts exist where access rights have to be adapted, the above procedure must be repeated accordingly.

SOLUTION 2 • Make the user with restricted rights become a member of an appropriate group (a group that has the rights needed for versioning) • An appropriate database instance and user group is created in 'WinCCFlexible' • The users with restricted rights must be members of the above group. PROCEDURE Button 'Start'>menu item 'Settings'>'Control Panel' >'Computer Management' >'User Management' •.

Create a new component type with the help of the AdminClient. In the component type editor the following options have to be set: • Option 'Enable transparency' (General ->Select) must be checked • In section 'Compare these files' you have to enter the following values: Specification Comparator Subdirectories *.zw1 Binary Include *. Elk Binary Include *.* Binary Include *.txt ASCII Include *.ini ASCII Include *.reg ASCII Include *.csv ASCII Include *.log ASCII Include *.rtf ASCII Include *.htm? ASCII Include In the section 'Store these files' you have to enter the following values: Specification Subdirectories *.* Include • Create a new component of the new type with the help of the UserClient. • Open the working directory of the created component (left-click button 'Open with file manager') • Open an EPLAN project with the EPLAN editor and create a '*.zw' file with the help of function 'Send as e-mail' • Version this file by clicking on the button 'Create new version' and check it in •. By default, the ReportClient will read metadata sets in batches of up to 10000.

This limit of 10000 may be too high for the available resources. To set a lower limit, proceed as follows: 1.Open the file 'Client.ini' (Path to the file: vdClientArchive >VD$A >Configuration >Client.ini) 2.Search for the section: [ReportClient] 3. If the section already exists, go to the key: 5540= If the section does not already exist, insert it as follows: [ReportClient] 5540= 4.Enter a new limit, e.g. 5540=7500 5.Save the changes 6.Close the file If you work with the ReportClient after the above change was made and if at the same time the number of data sets exceeds the limit that was specified by you, a message will inform you about the issue. When creating a job for backing up programs of a FANUC robot via FTP you need to be aware that the directory name ' mc:' has to be entered in the section 'FTP specific settings' >text field 'Sub directory'. EXPLANATION The operating system (OS) of Fanuc robots requires directory names to end with a ':' (colon).

This rule is in contradiction to the notation of commands of the File Transfer Protocol (FTP). FTP commands can or must include one or more colons, but it is not permitted that they end with that character. A FANUC robot or rather the data that is stored on its storage device have to be backed up via FTP (= upload type). When creating a job to backup the FANUC robots via FTP using the versiondog AdminClient every robot is specified by its IP address or (computer) name. Either IP address or computer name has to be entered in the named text fields which are located in the section 'FTP specific settings'. The text field 'Sub directory' can be found in this section too.

As long as no other directory is specified by a valid path entered into the text field 'Sub directory', only the data located in the directory ' md:' will be backed up. The directory name ' md:' represents the hard disk of the robot where the operating system is stored. If it is not the OS that you want to back up but the robot programs, these are stored in directory ' mc:'. Directory ' mc:' represents a flash disk that is incorporated into the file system when the robot’s OS is booted.

When creating a job for backing up programs of a Fanuc robot via FTP you need to be aware that the directory name ' mc:' has to be entered in the section 'FTP specific settings' >text field 'Sub directory'. Directory ' mc:' can only be accessed or rather its content can only be displayed if the corresponding flash card is located in the appropriate slot. If the flash card is NOT present and still an attempt is made to access data stored on it the following error message will be displayed: Error while calling a FTP function [Name: IwcdFtpDLXComPtr::GetFile][Errortext: Requested action not taken.

File unavailable (e.g., file not found, no access).][Details: /mc:/from00.img][40550] •. Lines are NOT excluded from comparison by their line numbers, but by character strings. If there are lines that you want to exclude from comparison, please follow the below instructions: • Open the UserClient • Go to the project tree • Right-click on the component that contains lines you wish to exclude • Select 'Edit component configuration' • The window 'Component properties' will be displayed • Click on the button 'Comparator configuration. Conexant Modem Driver For Linux there. ' • The window 'Compare configuration' will be displayed • Enter strings (either the whole line or using wildcards) in 'Exclude lines from comparison' When you enter a string in 'Exclude lines from comparison', all lines with that character string will be excluded from comparison.

WILDCARDS *a ->all lines are excluded that end with the character 'a' a* ->all lines are excluded that begin with the character 'a' *a* ->all lines are excluded that contain the character 'a' at any position Example: Actual value* *alarm* In the above example, all lines that begin with Actual value and all lines that have the word alarm anywhere in them will be excluded. Specific scenario The user wishes to create and Check-In a version of a component that is a Documentation component type. A file, whose name contains a hyphen with the shortcut (ALT + 0150), is added to the component. When creating a version of the component, a dialogue box appears, telling you that the 'unversioned changes will not be copied to the server'.

Explanation The dialogue box appears because the hyphen with the shortcut (ALT + 0150) is not recognised for this type of component and is thus replaced by another symbol. Solution If you click on 'Continue', the component will be saved on the server. However we strongly recommend, when naming files of components of the component type Documentation, that you do not use the shortcut (ALT + 0150). Explanation If the name of the instance of SQL Server installed on the affected client computer is different from the versiondog standard name (WINCC or WINCCFLEXEXPRESS), then versiondog cannot access the service. Versiondog expects one of these names because in the majority of cases they are the names given to SQL Server instances included with installations of WinCC/WinCC flexible.

Solution If the actual name of the SQL Server instance is not the standard name, then the actual name has to be provided to versiondog. Versiondog versions are archived as zip files to save disk space. The versioning process can be speeded up a little by reducing the compression factor. A lower compression factor means that more disk space is required for each new version.

Tested speeds: Amount of data [MB] Compression factor Time needed to create a version [s] 1000 0 125 1000 9 151 2000 0 242 2000 9 318 3000 0 300 3000 9 488 Compression factors are specified by component type. To change the factor for a component type, do the following: • Open the versiondog AdminClient • Open the module 'Component type editor' • Select a component type from the 'Component type library' • Go to 'Settings for saving' • Select the desired value from the dropdown list 'Compression factor' • •. Yes, it is possible to use versiondog on a terminal server. Vijftig Tinten Grijs Boek Gratis Downloaden.

Procedure: In order to use versiondog on a terminal server, you will need to edit the desktop shortcuts for the client applications (UserClient, AdminClient, and ReportClient): • Right-click on the versiondog client application shortcut • Click on 'Properties' • On the tab 'Shortcut', set the path to the local archive in the field 'Target', e.g.: C: Program files vdogClient VDogClient.exe /at:c '/rd:%USERPROFILE% vdogLocalArchive' • Change the versiondog client application shortcuts on the terminal server to match. To do this, go to C: Users Public Desktop on the terminal server and make the above changes to all the shortcuts. To change the directory of the ClientArchiv, proceed as follows: • Close all versiondog applications • Copy the vdClientArchive to the desire directory (for example: E: vdClientArchive) • Change the 'Target' in the properties section in all versiondog shortcuts (Right-click on one of the versiondog shortcuts, then click on 'Properties' and in the tab 'Shortcuts' enter the file location of the new target, for example: 'D: Programme vdogClient VDogClient.exe' /at:c '/rd:E: vdClientArchive' • Log on to a client application as usual. The new directory of the ClientArchive is now used. If you want to compare DOCX files, please note that versiondog has a suitable component type under Microsoft >Word.

For the comparison to be legible, your versiondog licence must include the component type Word/Winword, plus the software Microsoft Word must be installed on your PC. The same requirements exist for the component type Documentation. If these requirements are fulfilled and the versioning process still fails, it is possible that DOCX files in the component have write protection or access restriction. If this is the case, you could consider doing A.

Below: • To make a comparison possible, enter the DOCX file password in UserClient >Edit component configuration >Comparator configuration Please note that if the passwords for two DOCX files that you want to compare are different, the only kind of comparison that will be possible is a binary comparison. And this requires you to first change the comparator from 'Winword' to 'Binary' for this component type. This is done in the AdminClient as follows: • Open the AdminClient • Open the module 'Component type editor' • The 'Component type editor' window is displayed • In the 'Component type library', select the component type of the component concerned • Go to the table 'Compare these files' • Find the comparator type 'Winword', double-click on it and change it to 'Binary' in the dropdown list • Alternative solution: If it suits your situation to create versions of this component without running a comparison, you can use the 'Create version without difference' function. With this function, there is no comparison. In the UserClient, select the component, then go to the tab 'Extras' and click on 'Create version without difference'. Warning: 'This program contains F-blocks.

For security reasons is the restore function for F-blocks disabled by default. The function can be enabled on demand. Please talk to your Administrator if necessary. Now all blocks will be restored except the F-blocks.' Solution: A requirement for the complete restoration of an S7 project that contains F blocks is that the following section exists in the file AgentStation.ini in VD$A Configuration Upload: [SimaticS7] 5092=Y Result: The message will still be displayed when restoring a S7 project that contains F-blocks. You can however press OK to restore the complete project, including the F-bblocks. Please follow the instructions from Siemens for loading F-blocks/modules •.

To see only the versions a certain element was modified in do the following: • Select 'Lifecycle view' in the drop down menu, at the top of the project tree • Select the element you want to filter for in the project tree The change history will show only the version the selected element was modified in As long as 'Lifecycle view' is selected, the project tree will only show elements that were modified in at least one version in components. To see elements that are unchanged since the creation of the base version in the project tree in their respective component, select another view in the drop down menu. Example: There is a S7 project in the project tree that contains several blocks. You want to see only the versions of the project in which a specific block was modified. Proceed to select this block using the “Lifecycle view” as described before. The change history will now show only the versions of the project the block was modified in. Possible scenarios • Upload jobs with the H1 protocol selected as the access path suddenly stop working after further editors are installed (e.g.

TIA Portal or SIMATIC NET). • Upload jobs with the H1 protocol selected as the access path do not work at all. Explanation If you are using the H1 protocol for a device upload job, all H1 protocols apart from the INAT H1 protocol must be deactivated.

Solution Check to see whether in addition to the INAT H1 there are any other H1 protocols still activated (e.g. SIMATIC Industrial Ethernet (ISO)).

If so, deactivate them. To do this, go to: 'Local Area Connection' >'Properties'. To remove the feature for making passwords visible from all client applications, proceed as follows: • Go to AdminClient • Open the module 'INI files' • Open the file 'server.ini' • In 'server.ini', go to section [Common] and insert the following key and value: 5546=N• Save the changes • Open the UserClient, go to the tab 'Extras', click on 'Update from server' then close the UserClient • Open the application again, the feature is now turned off To reactivate the feature, delete the key and value from the file 'server.ini' and repeat steps 5-7. To find the 32 character job ID number, go to: • AdminClient >module 'Jobs' >middle pane 'Jobs' • Activate the column 'Job ID' • The job ID will be visible if the job has been run at least once To copy the 32 character job ID number to the clipboard, do the following: • Click anywhere on the job ID number and copy with CTRL C • Paste into a text editor such as Notepad and the 'Job ID' will be included among all the other information • Copy just the 32 character job ID carefully (for all uses of the job ID number, it is essential that it is exactly correct) •.

Possible cause: This problem could be occurring because the agent do not have the administrative rights required for an application that needs to be opened for the job to run. Solution: To ensure that the log-on account for the agent is correctly set, do the following: • Open the Windows Services console (Windows >Start >type in 'services.msc') • Double-click on the agent service ('VDog UploadAgent' or 'VDog CompareAgent') • Go to the tab 'Log on' • The option 'This account' should be selected. If not, select it and enter the username and password of an account which has the appropriate administrative rights. There are two possibilities: • The private key of the server archive has been deleted or changed This can happen when a server archive is restored from a backup or when the path to a new server archive is the same as one that has already been used. Solution: If they are available, restore the files VD$A Configuration SecureConnectPrivateKey and VD$A Configuration SecureConnectCertificate from a copy or backup of the last functioning version of the server archive, then restart the server.

If those files are not available, delete the file VD$A Configuration DataBases KNOWNHOSTS.FDB from the client archives of all the affected clients. • The connection between the client and server might be being manipulated If the private key of the server archive has not been deleted or changed, then it could be that SSL connections are being affected by a proxy or firewall (using man-in-the-middle techniques). Or it could be that a man-in-the-middle attack is actually ocurring! Necessary action: Carefully check the network connection between the affected clients and the server, especially for evidence of attack or tampering.

For SIMATIC S7 programs compiled without any changes, only the timestamp Time of last compilation will be changed. With the default settings of the S7 comparator, this difference will be detected during job execution (online/online comparison), but not when creating a new version or when comparing two versions (offline/offline comparison). If you still want to create a new version, you can either create a Version without difference or edit the Comparator configuration.