Your search returned 817 results

641. Shall the terminal 16 of the PCD2/3.W745 be connected to ground?

     Relevance:

      

     9%

     The analogue input modules PCD2.W745 and PCD3.W745 do have a terminal 16 (GND) which is not documented in version 1 of the manual 27/796.

642. Software Watchdog mustn't be used with FW 0C1 on PCD2.M150!

     Relevance:

      

     6%

     If once the Software Watchdog is configured on a PCD2.M150, the system can't be started any more until the FW will be changed to either an older version (not recommended) or to the latest version 0E3 (recommended)!

643. Some PCD2.H31x aren't compatible with PCD2.M48x or PCD2.M170

     Relevance:

      

     11%

     The CPLD version < HQ4 of the PCD2.H31x (HW version ≥ B) is not compatible with the I/O bus of the PCD2.M170 and the PCD2.M480. The CPLD of the modules has to be updated in Murten in order to use the H31x module on a PCD2.M170 or a PCD2.M480.

644. State of the product MotionX

     Relevance:

      

     7%

     Years ago a commissioning tool for some motion modules (e.g. PCD2.H32x) has been developped and was set to the beta phase. Due to a lack of interest and feedback from the market this tool was never officialized and is not supported any more.

645. Supported PCD communication ports for EIB/KNX driver

     Relevance:

      

     11%

     For BCU1 protocol not all communication interfaces of a PCD3 or a PCD2.M5540 can be used. On the other hand there is no problem using the newer FT1.2 protocol which is supported by all RS232 interfaces of the PCD3 and the PCD2.M5540.

646. Supported baudrates and protocols on a PCD2.M480

     Relevance:

      

     10%

     The serial ports of the PCD2.M480 does allow to communicate up to 115 kB/s.

647. System Catalogue : BACnet Room Controllers

     Relevance:

      

     9%

     System Catalgue: Book A Chapter 3.2 PCD7.LRxx BACnet room controllers can be configured and commissioned via an Android app

648. T660: Ethernet

     Relevance:

      

     5%

     power calculation of the I/O modules the Device Configurator from PG5 2.0. SP2 or later is to be used. PG5 2.0 Device Configurator does also feature a label creator for the I/Os on the RIO [...] . When replacing the PCD3.T660 Ethernet RIO with a PCD3.T665 or PCD3.T666 , the user program of the Manager has to be adapted [...] . Why doesn't the PCD3.T660 accept any configuration anymore? (FAQ #101289) In case the Ethernet RIO stays in a state

649. T660: Ethernet

     Relevance:

      

     5%

     power calculation of the I/O modules the Device Configurator from PG5 2.0. SP2 or later is to be used. PG5 2.0 Device Configurator does also feature a label creator for the I/Os on the RIO [...] . When replacing the PCD3.T660 Ethernet RIO with a PCD3.T665 or PCD3.T666 , the user program of the Manager has to be adapted [...] . Why doesn't the PCD3.T660 accept any configuration anymore? (FAQ #101289) In case the Ethernet RIO stays in a state

650. T665 ¦ T666: Ethernet

     Relevance:

      

     19%

     101653 . Minimal firmware version for the Manager is 1.16.42 (PCD1.M2) and 1.16.45 (PCD2.M5 and PCD3), see FAQ 101640 . Minimal version of PG5 for configuring a PCD3.T665¦T666 is PG5 2.0 SP2 (PG5 2.0.200). When replacing a PCD3.T660 by a PCD3.T665 the user program needs to be adapted accordingly. I/O modules: The I/O modules are delivered per default with a spring clamp terminal [...] RIO PCD3.T66x there is a diagnostic flag available which can be used to detect whether the RIO Manager CPU is exchanging data with the RIO. However, when using PG5 2.0.200 this flag is not correctly