Your search returned 817 results

91. BIM - Saia PCD2 modular programmable controllers

    Relevance:

     

    6%

    CPU base units for up to 4 plug-in I/O modules PCD2 processor unit with Ethernet TCP/IP, web and FTP server, file system, 2 MByte user program, 1 MByte RAM DB/Text, 128 MByte Flash memory, 4 I/O module sockets, expandable up to 1024 I/O, clock (RTC), interfaces: Ethernet, USB, RS-485 (187.5 kbits/s), RS-485 (1.5 Mbits/s), 1 slot A for PCD7.F1xxS, 1 slot C for Profibus or CAN

92. BIM - Saia PCD2 modular programmable controllers

    Relevance:

     

    9%

    CPU base units for up to 4 plug-in I/O modules PCD2 processor unit with Ethernet TCP/IP, web and FTP server, file system, 512 kByte user program, 128 kByte RAM DB/Text, 8 MByte Flash memory, 4 I/O module sockets (2 for PCD2.F2xxx), clock (RTC), interfaces: Ethernet, USB, RS-485 (187.5 Kbits/s), 1 slot A for PCD7.F1xxS

93. BIM - Serial interface module Current Loop

    Relevance:

     

    11%

    Serial interface modules and function modules for Saia PCD controllers Serial interface module current loop 20 mA Compatible with older PCDs (PCD1.M1xx/PCD2.M1xx/PCD2.M48x/PCS1)

94. BIM - Universal analogue input module

    Relevance:

     

    7%

    Analogue input modules for Saia PCD3 controllers Universal analogue input module, 8 channels, 13 bits (12 bits+sign), selectable by software, 0…10 V, ±10 V, 0…20 mA, ±20 mA, Pt/Ni 1000, 0…2500 Ohm, 0…300 kOhm (for NTC sensors) (2 connectors type K included)

95. Bad capture of Index Position with PCD2.H310

    Relevance:

     

    11%

    With HW version < A2 of the PCD2.H310 it could happen that the Index position isn't captured properly.

96. Booter update on PCD2.M150

    Relevance:

     

    11%

    This FAQ applies in case the booter of a PCD2.M150 needs to be updated.

97. Bug report concerning EIB library: BCU might "hang"

    Relevance:

     

    8%

    Using PG5 1.4 with the EIB library < 2.5.121 the BCU might "hang" when colliding messages (from and to the PCD) with a certain traffic level occurs. This does happen with any CPU used.

98. Bus topology with PCD7.D23x need an added delay with some PCD3.Mxxxx FW!!

    Relevance:

     

    6%

    The use of the HMI in bus protocol mode (RS485, "FTP" mode) on all PCD3 RS 485 ports (also on ports F2xx) must TEMPORARY be done with a special setting in the Advanced section of the SW Settings of the PG5.

99. Bxxx-xx0

    Relevance:

     

    44%

    MC5 mode on F2xxx module All PCD’s: RS485 driver keep holding bus after a while All PCD’s: Http request ‘is modified’ is not handled correctly on the PCD Web-Server which lead to the effect that [...] (CVE-2017-9628) All PCD's: The Modbus CSF CloseSRPort does not free the port then a open/SASI call give an error and the port does not work. PCD1.M2xx0 PCD1.M22x0 PCD2.M4x60: PCD can crash while power down [...] PG5 2.1 and 2.2 with E-Line S-Bus communication library < 1.2.110, why the S-Bus communication on the master PCD stops either after a certain time? (FAQ #102009)

100. Bxxx: Combined digital I/O

     Relevance:

      

     6%

     Documentation Good to know Minimal requirements for the PCD3.B160 are PG5 2.0.210 and firmware 1.16.52 on the PCD3. For accessing a PCD3.B160 the media mapping must be used (direct access to the I/Os from the DDC Suite is not supported). It is not possible to use the PCD3.B160 on a PCD3.T760. PCD3 / Bxxx How to configure a PCD3.B100 on a