Description
If project texts and picture objects are displayed shifted on a PC Runtime station, this might be due to one of the causes below.

• "Normal size (96 DPI)" is set for the DPI setting on the configuration computer.
• The DPI setting is set to "Large size (120 DPI)" on the visualization PC on which PC Runtime is running.

The "Large size (120 DPI)" setting for the DPI setting on the visualization PC causes all the fonts in the project to be displayed enlarged. Thus the fields configured are too small for the character strings.
 

Original with 96 DPI	Enlarged with 120 DPI
The example has been created, generated and displayed with 96 DPI.   Fig. 01	The example has been created and generated with 96 DPI, but enlarged through the operating system setting (120 DPI). Fig. 02

The "Large size (120 DPI)" setting for the DPI setting can also cause shifting of the picture elements.

Note that you must always have the same DPI setting and the same font size set on the configuration PC and on the visualization PC on which PC Runtime is running.

Windows CE-based operator panels like the MP 277, for example, use the DPI setting "Normal size (96 DPI)". 
The configurations should therefore be made on a configuration computer with the DPI setting "Normal size (96 DPI)" and font size "Normal".

Setting in the different Windows operating systems:

• Windows 7
• WinXP
• Win2000
• Win98 
• WinNT

Windows 7

• Open the dialog: "Start > Control Panel > View: Small Symbols > Display".
• Here you select "Less than - 100% (standard)" and confirm with "Apply".
  
  Note
  If you want to check the actual DPI settings, click the link on the left: "Define user-defined font size (DPI)". The DPI value is output under the ruler.
  
  The display is shifted in PC Runtime with Windows 7 only if the option "Use DPI scaling in Windows XP style" is active.
  If you do not activate this option, the Runtime is scale linearly like a graph and is therefore displayed slightly out of focus. The display is not shifted.

WinXP

• Open the dialog: "Start > Settings > Control Panel > View > Tab: Settings > Button: Advanced > Tab: General".
• Under "Display" you select "Normal size (96 DPI)" for the DPI setting.

Fig. 03

• Now start the dialog: "Start > Settings > Control Panel > View > Tab: Appearance".
• Select "Normal" for the font size.

Fig. 04

Win2000

• Open the dialog: "Start > Settings > Control Panel > View > Tab: Settings > Button: Advanced > Tab: General".
• Under "Display" you select "Small Fonts" for the font size.

Fig. 05

Win98 

• Open the dialog: "Start > Settings > Control Panel > View > Tab: Settings > Button: Advanced > Tab: General".
• Select the "Small Fonts" setting for the font size.

WinNT

• Open the dialog: "Start > Settings > Control Panel > View > Tab: Settings".
• Select the "Small Fonts" setting for the font size.

Keywords
Truncated, Incomplete, In part

QUESTION:
What is the meaning of the $044 transfer error 8 when storing a recipe?

ANSWER:
When you store your recipe the $044 transfer error 8 appears. In addition to your CPU a FM357 has a connection to an OP17. In this case every time the recipe is stored this transfer error appears. If you remove the FM357 from the OP17 configuration, the error message no longer appears.

Background:
This transfer error always occurs with functions that execute a write to flash in conjunction with an FM. As far as is known at the moment you can forget this error message. It has no effect on the function.

QUESTION:
Why do I receive the message "160000 connection to control open-loop control_1 is disconnected" with a connection between ProTool/Pro and WinAC?

Figure 1: Message

ANSWER:
For a connection between WinAC and ProTool/Pro do not switch the operation to "SIMATIC S7 WinAC v6.0", but to "SIMATIC S7-300/400 V6.0".

Connection settings in ProTool/Pro

• Select "Open-loop control" and doubleclick on your control.
• Under protocols, select "SIMATIC S7- 300/400 V6.0" and click on "Parameter".

Figure 2: Compile protocol

• Connect the PC to the WinAC via profibus.

Figure 3: Control connection

Note: 
If you run the WinAC and ProTool/Pro Runtime on two different PCs, the interfaces of both PCs have to be configured at "PG-PC-interface settings"(e.g. settings at WinAC-PC: "WinLC_0 --> CP5611" and at ProTool/Pro Runtime-PC "S7ONLINE --> CP5611 (PROFIBUS)").

QUESTION:
Why do I get a gray border in Runtime mode?

ANSWER:
You have either created your configuration in subimage mode and are now running it as full image, your images have been created smaller than your screen, which is why the rest of the image is gray.

OR

you have configured a lower screen resolution (640*480 pixels) and are running Runtime on a PC with a resolution of 800*600 pixels.

QUESTION:
How can I protocol messages line by line in ProTool Pro RT V5.10?

ANSWER:
By replacing the "FwPrintr.dll" file with the new version of this DLL that is attached you will be able to have line-by-line protocols of the messages with the Runtime version V5.10 under Windows NT 4.0 SP4.

Note:
This DLL is only for use with ProTool Pro RT V5.10 under Windows NT.

• Click the attached file <Fwprinter.exe> and copy the file into your installation directory for ProTool Pro RT.
• When copying you are asked whether the present DLL is to be overwritten. Answer with "Yes".

Archive file with the new DLL for ProTool RT V5.10
Fwprintr.exe (48 KB)

QUESTION:
What does the error message mean that appears while starting ProTool/Pro Runtime, saying that the structure of the configuration file "*.fwd" is incompatible and I should generate the configuration file again?

ANSWER:  
While starting ProTool/Pro Runtime, an error message appears, saying that
the structure of the configuration file "*.fwd" is incompatible and asks you to generate the configuration file again.

After creating the project again, however, the error message appears again.

A possible cause for this behaviour is that on your PG/PC there have been installed different versions of "ProTool/Pro CS" and "ProTool/Pro RT".
Please see that there is always the same version of "ProTool/ProCS" and "ProTool/ProRT" on your PG/PC.

QUESTION:
What is the meaning of the error message "GET INSTANCE ERROR" when calling the FWD file?

ANSWER:
You call an FWD file and get the following error message "GET INSTANCE ERROR". In this case you have installed the RunTime V5.10 in a directory with blanks. If the RT V5.10 is installed in a directory that contains a blank, the SP1 is not recognized at installation. But no error message appears during installation. The recipe DLLs were copied into the RT directory. But they were not registered. As a result you could not load any FWD files that contained recipes. The Runtime behaved as if SP1 were not installed. Upon installation of the common files (entered by default in Siemens\Common\....) you have the same effect. The files are installed, but not registered. Therefore with the RT you cannot load any FWD files that you have created with PT V5.10 SP1.

1. Deinstall ProTool Pro RT V5.10.
2. Install ProTool Pro RT V5.10 in a new directory without blanks in the name.
3. Install the Service Pack SP1.

QUESTION:
My fault and operating messages are only printed upon terminating runtime. What do I have to set to have each message printed as soon as it comes?

ANSWER:
This a setting of the Windows printer driver. Set the printer such that the print jobs are not queued. Windows will then print the messages immediately.