Configuration Issues with DeviceNet and Beckhoff

  • Hello Guys,

    I'm running to kind of similar problem on this tread:

    Configuration Issues with DeviceNet

    I tried to use last conversation but still could not figure it out . i'm using the same setup and coupler, (KRC2 ed05 and Beckhoff BK5250 with 4 DI and 4 DO modules). i have 120 ohm resistors at both ends and using devicenet card channel 2 LPDN.

    so already make sure about connectivity and resistors.

    These are my INIT files :

    ****dnsc_2sl*****


    [MODULE_STARTUP]

    INACTIV= ; Example: 1,5,6

    CONTINUE_WITH_WARNING= ; Example: 8,25

    [SCANNERCFG]

    NET_EPR=75

    NET_ISD=5

    NET_BACKGROUND_POLL_RATE=1

    NET_TX_RETRY_COUNT=1

    [1]

    MAC_ID=11

    VENDOR_ID=0108

    PRODUCT_TYP=0012

    PRODUCT_CODE=5200

    POLL_RESPL=2

    POLL_CMDL=2


    ***dnsc_2co***


    [CONFIG]

    MAC_ID=0

    LOGFILE=log/dnsc2.log

    DEBUG=1

    BAUDRATE=500

    OPTIONS=0

    SCANLIST_COMMENT=1



    ****devnet***

    [KRC]

    DEBUG=1

    BAUDRATE=500

    LOGFILE=log/devnet.log

    [1]

    MACID=11



    *****IOSYS****


    [CONFIG]

    VERSION=2.00

    [DRIVERS]

    DIAGDRV=22,cp_DiagInit,diagdrv.o

    ;DNSC6=20,dnsc6Init,dnsc6drv.o

    ;DNSC5=19,dnsc5Init,dnsc5drv.o

    ;DNSC4=18,dnsc4Init,dnsc4drv.o

    ;DNSC3=17,dnsc3Init,dnsc3drv.o

    DNSC2=13, dnsc2Init, dnsc2drv.o

    [DIAGDRV]

    ;COMMENT=Configuration not required

    [RSI]

    [DNSC1]

    [DNSC2]


    INB2=11,0,x1

    OUTB2=11,0,x1


    [DNSC3]

    [DNSC4]

    [DNSC5]

    [DNSC6]

    [IOLINKING]

    [ERX]

    [END SECTION]



    in my devicenet tool shows the "device ID doesn't match "i don't know what that means but i cant figure out where can i find this information which i just copied from last thread?

    VENDOR_ID=0108

    PRODUCT_TYP=0012

    PRODUCT_CODE=5200


    Any help would be thoroughly appreciate.

  • AD
  • Back up.


    First off, do you have an LPDN two-channel DN card in your KRC2, or are you trying to use the X801 DN socket on the MFC card?


    Second, do you have power on the DN cable's 24V and 0V lines?


    Third, what are the states of the indicator LEDs on the KRC2's DN port, and on the remote devices?

  • Solid green or blinking green?


    Also, "already have power on the channel"? What does this mean? There should only be one 24VDC power supply on the DN bus. The LPDN card in the KRC has to get its power from the DN cable, it does not draw power from the KRC's motherboard.


    The DEVNET.INI file is not relevant if you are using the LPDN card. DEVNET.INI only applies to the X805 on the MFC card.


    What are the contents of the DNSC2.LOG file?


    Both channels on the LPDN card appear to be occupied. But the light for one is red, the other is dark. So one is not running, the other has no power.

  • it's solid green and every 10 sec turn to red(right one)-green(left one) blinking.


    about power supply, i connected my power supply to 24+ and 0 .

  • ****dnsc2****

    30/ 7/20 : 21:23:37, DNch(2): >---------> Start LPDN-Scanner driver (channel 2)

    30/ 7/20 : 21:23:37, DNch(2): Debugging : enabled

    30/ 7/20 : 21:23:37, DNch(2): Serial : 9600 KBaud, 8*data,no parity, 1*stop, hardware

    30/ 7/20 : 21:23:37, DNch(2): Scanlist comments : enabled

    30/ 7/20 : 21:23:37, DNch(2): LPDN MAC_ID : 0

    30/ 7/20 : 21:23:37, DNch(2): Baudrate : 500 KBaud

    30/ 7/20 : 21:23:37, DNch(2): WatchDog : enabled

    30/ 7/20 : 21:23:37, DNch(2): PCI memory : 0x14A18000

    30/ 7/20 : 21:23:37, DNch(2): PCI IO : 0x4400

    30/ 7/20 : 21:23:38, DNch(2): SW-ver. drv/fw/PLX : 3.00B2/3.11/2

    30/ 7/20 : 21:23:38, DNch(2): HW-ver. serial/board : 2528/0

    30/ 7/20 : 21:23:38, DNch(2): No slaves in scanlist-file projected

    30/ 7/20 : 21:23:38, DNch(2): LPDN-Scanner state: running (channel 2)


    30/ 7/20 : 21:23:39, DNch(2): ERROR: [11]: No device

    30/ 7/20 : 21:23:40, DNch(2): ERROR: [11]: No device


    ****LPDN2***

    LPDN_Scanner : Log Date 30/ 7/20 : 19:40:14


    30/ 7/20 : 19:40:14, DNch(2): >---------> Start LPDN-Scanner driver (channel 2)

    30/ 7/20 : 19:40:14, DNch(2): Debugging : enabled

    30/ 7/20 : 19:40:14, DNch(2): Serial : 9600 KBaud, 8*data,no parity, 1*stop, hardware

    30/ 7/20 : 19:40:14, DNch(2): Scanlist comments : disabled

    30/ 7/20 : 19:40:14, DNch(2): LPDN MAC_ID : 1

    30/ 7/20 : 19:40:14, DNch(2): Baudrate : 125 KBaud

    30/ 7/20 : 19:40:14, DNch(2): WatchDog : enabled

    30/ 7/20 : 19:40:14, DNch(2): PCI memory : 0x14A18000

    30/ 7/20 : 19:40:14, DNch(2): PCI IO : 0x4400

    30/ 7/20 : 19:40:16, DNch(2): SW-ver. drv/fw/PLX : 3.00B2/3.11/2

    30/ 7/20 : 19:40:16, DNch(2): HW-ver. serial/board : 2528/0

    30/ 7/20 : 19:40:16, DNch(2): No slaves in scanlist-file projected

    30/ 7/20 : 19:40:16, DNch(2): LPDN-Scanner state: running (channel 2)


    30/ 7/20 : 19:40:17, DNch(2): FlushOutputs

  • ok,


    I got ESD file from Beckhoff technical team includes all required setup.

    but after i corrected my product ID, the error message change to " data size doesn't match" ??


    ****BK5250.eds***


    $ EDS


    [Device]

    VendCode = 108;

    VendName = "Beckhoff Automation";

    ProdType = 12;

    ProdTypeStr = "Communications Adapter";

    ProdCode = 5250;

    MajRev = 1;

    MinRev = 1;

    ProdName = "BK5250 V01.01";

    Catalog = "BK5250";



    [IO_Info]

    Default = 0X0001; $ Poll Connection is default

    PollInfo = 0X000F, 1, 1;

    StrobeInfo = 0X000F, 1, 1;

    COSInfo = 0X0007, 1, 1;

    CyclicInfo = 0X000B, 1, 1;



    $ Input Connections

    $ Assemblies


    Input1=

    0, $ 0 bytes length, see terminal configuration

    0, $ all bits are significant

    0x000F, $ Poll, BitStrobe, Change of State and Cyclic

    "A+D Inputs with Status byte", $ Name

    6, "20 04 24 6F 30 03", $ Assembly Inst. 111

    "Mapping, see EDS-File or Manual"; $ Help String


    $ Mapping Info:

    $ Byte 0 to (n-1) :Analog Inputs

    $ Byte n to (m-1) :Discrete Inputs

    $ Byte m :Vendor specific status byte

    $ bit0 = Internal bus error

    $ bit1 = Config error

    $ bit2 = reserved

    $ bit3 = reserved

    $ bit4 = reserved

    $ bit5 = reserved

    $ bit6 = Bus Sense Error

    $ bit7 = Fieldbus error / idle mode




    Input2=

    0, $ 0 bytes length, see terminal configuration

    0, $ all bits are significant

    0x000F, $ Poll, BitStrobe, Change of State and Cyclic

    "Discrete Inputs with Status byte", $ Name

    6, "20 04 24 70 30 03", $ Assembly Inst. 112

    "Mapping, see EDS-File or Manual"; $ Help String


    $ Mapping Info:

    $ Byte 0 to (n-1) :Discrete Inputs

    $ Byte n :Vendor specific status byte

    $ bit0 = Internal bus error

    $ bit1 = Config error

    $ bit2 = reserved

    $ bit3 = reserved

    $ bit4 = reserved

    $ bit5 = reserved

    $ bit6 = Bus Sense Error

    $ bit7 = Fieldbus error / idle mode


    Input3=

    0, $ 0 bytes length, see terminal configuration

    0, $ all bits are significant

    0x000F, $ Poll, BitStrobe, Change of State and Cyclic

    "Analog Inputs with Status byte", $ Name

    6, "20 04 24 71 30 03", $ Assembly Inst. 113

    "Mapping, see EDS-File or Manual"; $ Help String


    $ Mapping Info:

    $ Byte 0 to (n-1) :Analog Inputs

    $ Byte n :Vendor specific status byte

    $ bit0 = Internal bus error

    $ bit1 = Config error

    $ bit2 = reserved

    $ bit3 = reserved

    $ bit4 = reserved

    $ bit5 = reserved

    $ bit6 = Bus Sense Error

    $ bit7 = Fieldbus error / idle mode




    $ Output Connections

    $ Assemblies


    Output1=

    0, $ 0 bytes length, see terminal configuration

    0, $ all bits are significant

    0x000F, $ Poll, BitStrobe, Change of State and Cyclic

    "Analog + Discrete Outputs", $ Name

    6, "20 04 24 65 30 03", $ Assembly Inst. 101

    "Mapping, see EDS-File or Manual"; $ Help String

    $ Mapping Info:

    $ Byte 0 to (n-1) :Analog Outputs

    $ Byte n to m :Discrete Outputs



    Output2=

    0, $ 0 bytes length, see terminal configuration

    0, $ all bits are significant

    0x000F, $ Poll, BitStrobe, Change of State and Cyclic

    "Discrete Outputs", $ Name

    6, "20 04 24 66 30 03", $ Assembly Inst. 102

    "Mapping, see EDS-File or Manual"; $ Help String


    $ Mapping Info:

    $ Byte 0 to n :Discrete Outputs


    Output3=

    0, $ 0 bytes length, see terminal configuration

    0, $ all bits are significant

    0x000F, $ Poll, BitStrobe, Change of State and Cyclic

    "Analog Outputs", $ Name

    6, "20 04 24 67 30 03", $ Assembly Inst. 103

    "Mapping, see EDS-File or Manual"; $ Help String


    $ Mapping Info:

    $ Byte 0 to n :Analog Outputs

  • That means that your POLL_RESPL or POLL_CMDL values do not match the hardware. The fastest way to resolve this is to use the Telnet diagnostics (see the PDFs) to query MAC-ID 11 directly and ask it what it's IO Size is. It will respond with a number of bytes In and Out.

  • okay, i finally figure it out:


    POLL_RESPL=2

    POLL_CMDL=1


    i don't know why but it works with 1 DI and 1 DO module.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account
Sign up for a new account in our community. It's easy!
Register a new account
Sign in
Already have an account? Sign in here.
Sign in Now