HILFE PB Fehler 5614A2 CPV14-GE-DI02-8 CP-E16-Cl-KL

  • Hallo zusammen und :hilfe:


    Habe seit gestern Probleme meinen Profibus zum laufen zu bekommen.
    Fehlermeldung:


    "Fehler beim Lesen Treiber CP561DRV" und "Profibus: Kommunikationsfehler in Modul3"


    Habe meine .ldb mit NCM 5.4 erzeugt.
    Alle Stecker und Kabel wurden nochmal geprüft. Daran liegt es nicht.
    Da noch keine SPS vorhanden ist , ist auch nur der PB1 auf der 5614A2 gesteckt.
    von da geht es auf die Ventilinsel und zum zusätzlichen EAModul.


    Kann mir jemand helfen ????
    Danke im Voraus
    ;==========================================================
    ; IOSYS.INI - Configuration file for the IO-System
    ;==========================================================
    ; For configuration help go to the end of this file.
    ;----------------------------------------------------------


    ; ATTENTION !!!! Since V5.0 Build13 we have removed the DeviceNet
    ; driver "dndrv.o". Now you have to use the driver
    ; "dn2drv.o" and the appropriate syntax (form 2)


    [CONFIG]
    VERSION=2.00



    [DRIVERS]
    ;MFC=0,mfcEntry,mfcdrv.o
    ;INTERBUS=1,ibusInit,ibusdrv.o
    ;DEVNET=2,dnInit,dn2drv.o
    PBMASL=11,pbmsInit,pfbmsdrv.o
    ;DNSC1=12,dnsc1Init,dnsc1drv.o
    ;DNSC2=13,dnsc2Init,dnsc2drv.o
    ;DSEIO=14,dseIoInit,dseiodrv.o
    ;INTERBUSPCI=15,ibsCPPciInit,ibpcidrv.o
    ;CNKE1=16,cnke1CPInit,cnke1drv.o
    ;DNSC3=17,dnsc3Init,dnsc3drv.o
    ;DNSC4=18,dnsc4Init,dnsc4drv.o
    ;DNSC5=19,dnsc5Init,dnsc5drv.o
    ;DNSC6=20,dnsc6Init,dnsc6drv.o
    ;CNKE2=21,cnke2CPInit,cnke2drv.o


    [PBMASL]
    INB47=3,0,x2
    OUTB47=3,0,x2


    [IOLINKING]





    [CP_5613/14]
    DEBUG=1
    LOGFILE_PATH=log/pfbms.log
    ERROR_TEXT=German
    FORCE_RESET=0
    OLD_ERROR_DB=0


    [MASTER]
    MASTER_USED=1
    DATABASE_PATH=init/festo.ldb
    FIRMWARE_PATH_A1=drivers/FW_5613.bin
    FIRMWARE_PATH_A2=drivers/FW5613A2.bin
    WATCHDOG_TIME=3
    MAPPING_USED=0
    MAPPING_PATH=init/
    ;DEACTIVATED_SLAVES=
    WAIT_FOR_SLAVES=1


    [SLAVE]
    MODUL_USED=0
    MODUL_ADDRESS=
    START_TIME=60
    ERROR_ACTION=1
    STANDBY=0
    SLAVE_TIMEOUT=0
    CHECK_CONFIGURATION_DATA=0
    ACCEPTABLE_INPUT_LENGTH=244
    ACCEPTABLE_OUTPUT_LENGTH=244
    IO_DATA_BASE=0
    CONSISTENCE=0

  • ANZEIGE
  • FILE_PTR_POS=007958
    29/10/11 05:57:55 : Logfile for Profibus CP5613/14 (V2.04 Build5 for Rel5.6 )
    29/10/11 05:57:55 : Downloading Firmware and Database.........
    29/10/11 05:57:56 : CP5613/14 started!
    29/10/11 05:57:56 : Master Application registered at the CP!
    29/10/11 05:57:56 : Accessed pointer to DPR from CP!
    29/10/11 05:57:56 : Hardware version: 8.04
    29/10/11 05:57:56 : Firmware version: 6.03
    29/10/11 05:57:56 : Master baudrate : 1,5 MB
    29/10/11 05:57:57 : next CP state: DP_STOP
    29/10/11 05:57:57 : DP_Master has changed mode to: DP_STOP
    29/10/11 05:57:57 : next CP state: DP_CLEAR
    29/10/11 05:57:57 : DP_Master has changed mode to: DP_CLEAR
    29/10/11 05:57:57 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:57 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:58 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:58 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:58 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:58 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:57:59 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:00 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:01 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:02 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:02 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:02 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:02 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:02 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:02 : CP_IO_RESTART: Waiting for all modules being in state ready!
    >
    29/10/11 05:58:02 : next CP state: DP_OPERATE
    29/10/11 05:58:02 : DP_Master has changed mode to: DP_OPERATE
    ===== LAST_ENTRY =====

  • 29/10/11 05:58:02 : next CP state: DP_OPERATE
    29/10/11 05:58:02 : DP_Master has changed mode to: DP_OPERATE


    Der Bus läuft

    Wolfram (Cat) Henkel

    never forget Asimov's Laws at the programming of robots...

    "Safety is an integral part of function. No safety, no production. I don't buy a car without brakes."


    Messages und Mails mit Anfragen wie "Wie geht das..." werden nicht beantwortet.

    Diese Fragen und die Antworten interessieren jeden hier im Forum.


    Messages and Mails with questions like "how to do..." will not be answered.

    These questions and the answers are interesting for everyone here in the forum.

Erstelle ein Benutzerkonto oder melde dich an um zu kommentieren

Du musst ein Benutzerkonto haben um einen Kommentar hinterlassen zu können

Benutzerkonto erstellen
Neues Benutzerkonto für unsere Community erstellen. Geht einfach!
Neues Benutzerkonto erstellen
Anmelden
Du hast bereits ein Benutzerkonto? Melde dich hier an.
Jetzt anmelden