On a Profi S-Bus network when PCD7.D76_ terminals are connected to PCD3.Mxxx or PCD2.M480 PLC's over Profi S-Bus, the terminal loses the communication after some time and get even frozen. This problem is corrected in the new boot, FW and driver. The PCD8.D81 V 5.09 is needed , the attached files have to be copied in it (see procedure below). It is also necessary to update the PCD3.Mxxx and PCD2.M480 FW with the version PCD3.Mxxx_023.blk / PCD2.M480_$27 or newer! Ask the PCD technical support or your representation for it!
) 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 [...] With the web-panels mentioned below it's not possible to connect PCD's with S-Bus over RS485 to the web-panel and to display the web-pages stored on the PCD. The only possible connection type to [...] used the output telegram is send to only one RIO after a reboot The diagnostic Flags in S-Bus Master mode are not correct if there are collisions on the RS-485 network CSF CopyDBBytesToR crash when
With the web-panels mentioned below it's not possible to connect PCD's with S-Bus over RS485 to the web-panel and to display the web-pages stored on the PCD. The only possible connection type to display web-pages from PCD's is HTTPDirect (Ethernet connection). The following web-panels don't have an RS485 interface: - PCD7.D450WTPF - PCD7.D470WTPF - PCD7.D412DTPF The PCD7.D412DT5F has an integrated RS485 port. It's also possible to add a second serial port by means of a module PCD7.F1xxS but the serial ports can only be used from the PLC program, which is embedded in the device and not from
% 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! Workaround: Use
. How can an alarm be displayed on a RS485 network (bus terminal topology)? (FAQ #101544) When an alarm arises and the display (e.g. a PCD7.D23x) is connected on an RS 485 bus, the screen of the terminal can't be forced in order to display the alarm contained in the buffer. Symptom When an alarm arises and the display (e.g. a PCD7.D23x) is connected on an RS 485 bus, the screen of the terminal can't be forced in order to display the alarm contained in the buffer. Reason This restriction is due to
Product Category HMI Room operating device PCD7.D1000 General FAQ PCD7.D1000 Digital room operating device with Modbus or S-Bus
. If you use the default standby mode S-BUS PGU you have to choose full handshake. Normally the handshake is on default. Only in this special case you have to change it to full [...] while sending an S-Bus telegram (e.g. missing port assignation or invalid data array or media) Invalid mathematical operation (e.g. division by zero or value overflow after a multiplication) Index [...] the Online Debugger!). Hint: Also have an eye on the SASI FBoxes you used as well as on the HMI Settings tab. The port doesn't exist The SASI text isn't valid S-Bus support isn't enabled in
. If you use the default standby mode S-BUS PGU you have to choose full handshake. Normally the handshake is on default. Only in this special case you have to change it to full [...] while sending an S-Bus telegram (e.g. missing port assignation or invalid data array or media) Invalid mathematical operation (e.g. division by zero or value overflow after a multiplication) Index [...] the Online Debugger!). Hint: Also have an eye on the SASI FBoxes you used as well as on the HMI Settings tab. The port doesn't exist The SASI text isn't valid S-Bus support isn't enabled in
. If you use the default standby mode S-BUS PGU you have to choose full handshake. Normally the handshake is on default. Only in this special case you have to change it to full [...] while sending an S-Bus telegram (e.g. missing port assignation or invalid data array or media) Invalid mathematical operation (e.g. division by zero or value overflow after a multiplication) Index [...] the Online Debugger!). Hint: Also have an eye on the SASI FBoxes you used as well as on the HMI Settings tab. The port doesn't exist The SASI text isn't valid S-Bus support isn't enabled in
. If you use the default standby mode S-BUS PGU you have to choose full handshake. Normally the handshake is on default. Only in this special case you have to change it to full [...] while sending an S-Bus telegram (e.g. missing port assignation or invalid data array or media) Invalid mathematical operation (e.g. division by zero or value overflow after a multiplication) Index [...] the Online Debugger!). Hint: Also have an eye on the SASI FBoxes you used as well as on the HMI Settings tab. The port doesn't exist The SASI text isn't valid S-Bus support isn't enabled in
