The requested software / document is no longer marketed by Saia-Burgess Controls AG and without technical support. It is an older software version which can be operated only on certain now no longer commercially available products.
PCD7 / Dxxx Terminals
Micro Browser Monochrome Display contrast changes (FAQ #100718)
When updating the Micro Browser Firmware to version 10701, the contrast settings in the monochrome panels PCD7.D457BTCF and PCD7.D457BMCF have to be changed. You'll have to increase the contrast for several steps.
With the new Firmware version we had to change the contrast adjustment on the Hardware and Firmware side to avoid any whistle (noise) and waves appearances.
Please note: The tone and brightness of each MB-Panel display is an individual characteristic and can be slightly different from one display to the other. At some contrast settings or with some images, flickering or differences in the brightness levels may appear.
On Microbrowser panels with harware version <$C it is not possible to store teq- and gif-files on the panel. (FAQ #100576)
If you are using a Microbrowser panel with HW-Version <$C you have to download all teq- and gif-files to the PCD.
PCD7.D7__ Ethernet Driver: error in commande function! (FAQ #100337)
When using the commande function which allows for example the writing of the hardware clock from PLC to Terminal PCD7.D7-- over Ethernet connection the 2 first words are swapped.
Normally the 1st word 0 contains the command the VT has to carry out and the 3 others word contain the parameters. This works well in S Bus driver but with Ether S Bus the two first words are swapped.
This means it is so with this error:
Word 0 is Parameter 1
Word 1 is commande
Word 2 is Parameter 2
Word 3 is Parameter 3
In order to solve that problem the attached file vtwindev.dbr has to be copied in the main directory PCD8.D81W software, this will replace the existing file.
Fkeys don't work on PCD7.D16_ with HMI editor! (FAQ #100175)
The FKeys flags available in HMI Editor (in Tag Internals) don't work on the PCD7.D16_.
Because those flags have a double functionality, they don't work for those small displays. It is necessary to use a bigger display as PCD7.D231 or PCD7.D232 in order to have this FKeys functionality!
PCD7 / D290
Experiences made with the internal sensors of the PCD7.D290 display (FAQ #101360)
When using the internal sensors of the PCD7.D290 it has been noticed that the the pratical measurement accuracy is below the indication of the corresponding manual (26/841).
Due to the fact that the sensors are mounted directly in the display which itselfs influences the measurement it has been stated that the precisision is not according to the manual of this PCD7.D290 display (26/841 version 4). The chapters 4.2.3 (Temperature sensor) and 4.2.4 (R.H. sensor) will be adapted accordingly in the next release.
4.2.3 Temperature sensor
Temperature sensor used in PCD7.D290 is active and supplies as output a voltage of 10.0 mV/°C; this sensor is directly calibrated in °C.
Embedded temperature sensor component is directly soldered on the main board of the PCD7.D290
Theoretical accuracy value: ± 0.5°C at 25 °C., Practical accuracy value: ± 1°C (± 1.5°C in the worse case)
4.2.4 R.H. sensor
R.H. sensor used in PCD7.D290 is capacitive and supploes as output a capacity in the range 161.6 pF at 0% R.H. and 193.1 pF at 100% R.H.
The evaluation algorithm is stored directly inside D290 firmware.
Embedded humidity sensor component is directly soldered on the main board of the PCD7.D290 --> Practical accuracy value: ± 5%
Communication in Bus Terminal topology doesn't work on PCDx.F2xx Module! (FAQ #101091)
When more than 1 displays of the same type (PCD7.D23x and PCD7.D290) are connected to a RS 485 port (Bus terminal) of a PCDx.F2xx module, the communication doesn't work. Only one of the displays is available, the other one(s) is (are) not accessible!
The ports 100 to 131 available on the PCDx.F2xx modules have different timing properties and are therefore not appropriate for PCD7.D23x and PCD7.D290 in bus terminal topoloy!
Use another RS 485 port (onboard or with F1xx).