Kuka KRC1 devicenet not working

    Hello,

    im struggling to communicate with my BK5200 bus coupler and MFC on krc1..

    I got it working 2 days ago after some cussing and trying again, realized eventually that one connection was too loose and the CAN-L cable was hanging out. Also I adjusted the iosys.ini syntax which worked.


    Then decided to move and mount the modules and some I/O more neatly on a board and now the communication stopped working.

    green light on MS connect is on, I/O error and OVERFLOW blinking red

    Perhaps it has something to do with wiring, I measured CAN-L and CAN-H 2.6V with respect to ground. Also I used a ethernet cable as these wires are twisted. I fastened it with tay-rip, could it be that I damaged the cable?, I measure 0.6 Ohm of 1.5 meter cable.

    Also across CAN-L and CAN-H I measure 60ohm on cable both ends.


    Any help is much appreciated!


    Telnet dnWho response:


    Iosys.ini:

    DEVNET=2,dnInit,dn2drv.o

    [DEVNET]

    INB10=5,0

    OUTB10=5,0


    devnet.ini:

    [krc]

    debug=0

    buadrate=500

    LOGFILE=1

    [1]

    macid=5

    Edited once, last by Rikkoman (August 11, 2024 at 7:41 AM).

    The dnWho is finding the device (MAC 5), so it's not a communication issue. It's a config issue. The Beckhoff modules rely on the I/O "slices" to be in certain orders. So probably this:

    Quote from Rikkoman

    Then decided to move and mount the modules and some I/O more neatly on a board and now the communication stopped working.

    Changed the order or number of Input and Output bytes the BK is reporting to the KRC. Try a dnShow command and see what the module reports back.

    Ok thanks for response,

    I read in beckhoff doc about the blinking err code I had:

    I have 4 pulses and as argument (second sequence) 1 pulse, meaning second module(0 is first)?

    Im not sure what break behind terminal means.

    (bk52x0en.pdf)


    Thanks very much, your answer helped, I played around a bit with removing I/O modules and adding, it works fine now.

Advertising from our partners