interface (ftp.cgi or ftp.json) if that file starts with a white space character (either a space or a tab) CSF CopyDBBytesToR crash when destination is bigger than last Register Diagnostic Flags in S-Bus [...] PCD crash if a BITI is executed with number as FB parameter PCD crash when use Profi-S-Bus Master Sometimes the program is lost when update FW from 1.24.xx to 1.26.xx MOVX/DIVX function where [...] 6x5 module and the I/O slot where the W6x5 module is plugged in, it’s possible that the analog output signal supplied from the W6x5 is not stable and is oscillating. Symptom The outputs of the PCD
measured PT100 temperature values of the 8 channels are not correct. ‘Power PCD’s’ are: PCD1.M2x20, PCD1.M2160, PCD1.M2220-C15 PCD2.M5540, PCD2.M5440, PCD2.M4160, PCD2.M4560 PCD3.Mxx60 To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed. On the ‘old’ PCD’s like PCD2.M170 or PCD3.M5540 the PCD internal power supply V+ was at 24V On the ‘new’ ‘Power-PCD’s’ and the PCD2.C1000 and PCD2.C2000 the V+ is 16,5V The electrical design of the PCD2/3.W220Z18 was done in that the
Software / Tools S-Label Creator FAQ restricted area [...] W6x5 module and the I/O slot where the W6x5 module is plugged in, it’s possible that the analog output signal supplied from the W6x5 is not stable and is oscillating. Symptom The outputs of [...] the Device Configurator or the Profi-S-I/O (or Profibus DP) Network Configurator, the PCD2/3.W525 does need two registers for the analogue outputs and 8 registers for the analogue inputs
interface (ftp.cgi or ftp.json) if that file starts with a white space character (either a space or a tab) CSF CopyDBBytesToR crash when destination is bigger than last Register Diagnostic Flags in S-Bus [...] ) Improvements New Conversation Table for W380 Ni1000 and PT1000 Temperatur S-Bus Serial UART Diagnostics not correct Various Open Data Mode fixes: Read Timeout enhancement, Client Connection timeout [...] PCD crash if a BITI is executed with number as FB parameter PCD crash when use Profi-S-Bus Master Sometimes the program is lost when update FW from 1.24.xx to 1.26.xx MOVX/DIVX function where
interface (ftp.cgi or ftp.json) if that file starts with a white space character (either a space or a tab) CSF CopyDBBytesToR crash when destination is bigger than last Register Diagnostic Flags in S-Bus [...] ) Improvements New Conversation Table for W380 Ni1000 and PT1000 Temperatur S-Bus Serial UART Diagnostics not correct Various Open Data Mode fixes: Read Timeout enhancement, Client Connection timeout [...] PCD crash if a BITI is executed with number as FB parameter PCD crash when use Profi-S-Bus Master Sometimes the program is lost when update FW from 1.24.xx to 1.26.xx MOVX/DIVX function where
interface (ftp.cgi or ftp.json) if that file starts with a white space character (either a space or a tab) CSF CopyDBBytesToR crash when destination is bigger than last Register Diagnostic Flags in S-Bus [...] ) Improvements New Conversation Table for W380 Ni1000 and PT1000 Temperatur S-Bus Serial UART Diagnostics not correct Various Open Data Mode fixes: Read Timeout enhancement, Client Connection timeout [...] PCD crash if a BITI is executed with number as FB parameter PCD crash when use Profi-S-Bus Master Sometimes the program is lost when update FW from 1.24.xx to 1.26.xx MOVX/DIVX function where
the 8 channels are not correct. ‘Power PCD’s’ are: PCD1.M2x20, PCD1.M2160, PCD1.M2220-C15 PCD2.M5540, PCD2.M5440, PCD2.M4160, PCD2.M4560 PCD3.Mxx60 To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed. On the ‘old’ PCD’s like PCD2.M170 or PCD3.M5540 the PCD internal power supply V+ was at 24V On the ‘new’ ‘Power-PCD’s’ the V+ is 16,5V The electrical design of the PCD2/3.W220Z18 was done in that the way, that the internal power V+ of 24V was required
the 8 channels are not correct. ‘Power PCD’s’ are: PCD1.M2x20, PCD1.M2160, PCD1.M2220-C15 PCD2.M5540, PCD2.M5440, PCD2.M4160, PCD2.M4560 PCD3.Mxx60 To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed. On the ‘old’ PCD’s like PCD2.M170 or PCD3.M5540 the PCD internal power supply V+ was at 24V On the ‘new’ ‘Power-PCD’s’ the V+ is 16,5V The electrical design of the PCD2/3.W220Z18 was done in that the way, that the internal power V+ of 24V was required
-Line PCD1 / E-Line Why the RS-485 S-Bus communication [...] the some of the S-Bus telegrams transferred from the PCD S-Bus master to the S-Bus slaves over RS485 are malformed, and the S-Bus slave does reject the request from the master. This could lead to the situation that for example the PCD S-Bus master don’t receive actual values from E-Line RIO’s or that the program download of a PCD program from the PC to a Slave PCD which is located behind a
communication errors when connecting a PCD/PCS in "Secure S-Bus Data Mode"? (FAQ #101180) In case a "non Saia PCD® COSinus" PCD or PCS1 system is connected with "Secure S-Bus Data mode" (e.g. over a serial cable or over modem) from time to time a telegram is not answered correctly. Symptom A PCD or a PCS connected with another system (e.g. PC or another PCD system) using the "Secure S-Bus Data mode" does not answer a telegram from time to time. This can e.g. be seen by a red LED on transmit or receive FBoxes
