Your search returned 817 results

31. Why does the user program no longer work correctly after a restore from flash?

    Relevance:

     

    9%

    In case user program is restored from flash with a PCD3 or PCD2.M5540 with firmware 1.16.xx it is possible (depending on the device configuration) that the restored user program is not complete.

32. Why does the data exchange to the RIO not work after the program has been restored?

    Relevance:

     

    8%

    In case the Smart Ethernet RIO manager is a PCD2.M5 or a PCD3 (with firmware 1.16.42) the data exchange between the RIO station and the manager is not running after a program restore has been executed on the manager.

33. Why does the S-I/O communication no longer work on a PCD3 or a PCD2.M5?

    Relevance:

     

    13%

    If there is a SIO-Master and a DP-Master configured the SIO-Master does not go in the "Operate" state to make the data exchange.

34. Why does the PCD7.F7500 does not work on the PCD2.M5540?

    Relevance:

     

    10%

    In some cases it is possible that a PCD7.F7500 is not correctly detected on a PCD2.M5540 with hardware version 'C' without modification '6'.

35. Why does the PCD2/3.H210 generate too few pulses in high temperature environments?

    Relevance:

     

    9%

    In case of high environment temperatures together with a configuration of very low frequencies, the PCD2.H210 or the PCD3.H210 could generate an incorrect amount of output pulses.

36. Why does the PCD2.R6000 not work if a PCD2.C2000 is used on the same system?

    Relevance:

     

    12%

    In case a PCD2.R6000 (with a hardware version / modification before B1) is plugged on a PCD2.M5 which is extended with a PCD2.C2000 the file system on the SD card is not accessible.

37. Why does the PCD2.M5540 show the history error message 'FABINFO CRC FAIL' or the entry 'Fab. Date (year/week): 2000/00; BAD PROD INFO CHECKSUM' in the diagnostic file and in the hardware info of the PG5 Online configurator?

    Relevance:

     

    7%

    Due to a production error it's possible that PCD2.M5540 which have been produced in 2020 may contain a wrong production date with year 2000 and calendar week 0. This wrong production date leads to an error message being entered in the PCD history: 'FABINFO CRC FAIL' and in the PG5 Online configurator hardware info and in the diagnostic file the warning: 'Fab. Date (year/week): 2000/00; BAD PROD INFO CHECKSUM' is displayed.

38. Why does the FB Home not work on a PCD2/3.H210?

    Relevance:

     

    10%

    There has been a bug in the FPGA versions older than HD6 that caused the FB Home not to work if a limit switch was active on power up of the PCD.

39. Why does the Error LED of my PCD2.M127 blink?

    Relevance:

     

    9%

    The Error LED of the PCD2.M127 does blink in case a PCD2.F7xx module is configured but the communication (Profibus or LON) is not working (e.g. because the module itself or a configured Profibus DP slave is not present).

40. Why does the CPU crash when reading the diagnostic buffer?

    Relevance:

     

    10%

    On PCD2.Mx57 and PCD2.M177 the request can cause a crash when requesting more than 20 entrys. The problem is corrected in firmware version 3.118