mfc 3 error (Drive Bus DSE 1 for participant no. 8-9 not configured)

Hello,

I have bought a delta PLC that acts as a slave can bus module (DVP SA2 + DVPDT 01-s) to extract a digital output from my kuka KR c2 robot (with a MFC 3 card installed). After setting up the connections, I did the first step that was configuring DEVNET.INI. After that, when I go to configure> I/ODriver>Reconfigure I/O Driver, it displays an error no 29 saying ' Drive bus DSE 1 participation no. 8 - 9 not configured' .

Checking this message error states that there is an Interbus configuration and physical structure do not match. what are the possible mistakes that may lead to this error?

.

PS:

- the robot has 2 other cards installed besides the mfc 3 card (one is for serial communication and the other is for.

- I tried to ignore this error and continue setting up the devicenet but the same error still appears.

- when I enter the Telnet window to use dnSetBaudRate or dnWho, it replies with undefined symbol.

- devicenet module (my plc) leds are stating that everything is fine

- some pictures (including log files of devnet and iosys) and a video are found in this link:

https://drive.google.com/drive/folders/…adJ?usp=sharing

Quote from panic mode

definitely MADA related. how many external axes you have there?

Hi Panic,

I am using it for 3d Printing, so I only need a 1 digital output signal to turn on and off the extruder.

- Something to add, the devicenet module is a regular PLC with a slave can bus extension (not a remote i/o module where the pins is directly linked to the kuka operating system). Does that affect the operation? or it has another way to be configured?

Many thanks

Quote from panic mode

definitely MADA related. how many external axes you have there?

Correcting my self,

I have 2 external axis labeled 7 and 8.

Quote from SkyeFire

Okay... Those white cables that run from each servo module to the one beside it? Those are Interbus connections. The way Interbus works is by daisy-chaining each node to the one upstream and downstream of it, and the "address" of each node on the bus is determined by it's position on the daisy chain.

So, your error message refers to DSE 1 Participants 8 and 9. Those would be the N7 and N8 modules, for external axes E1 and E2 respectively. The reason they are Participatns 8&9 instead of 7&8 is because Participant 1 is the power module. If you trace the white cable from the MFC/DSE card to the first module, it's the power module. The next connection is from the power module to the N1 (Axis 1) module, then from there to N2 (Axis 2) and so on.

The error message, IIRC, is b/c the DSE is detecting N7 and N8 on the bus, but has no configuration data for them. The quick way to test this would be to shut down, disconnect the cable going from N6 to N7, then power the robot back up. If the error message goes away, then that error is resolved.

(Unless, of course, you end up needing one or both of those external axes, in which case they'll have to be completely configured)

Dear SkyeFire,

much appreciated for your answer, I will try it tomorrow.

I have another question btw, the devicenet module I am using is a regular PLC with a slave can bus extension (not a remote i/o module where the pins is directly linked to the kuka operating system) and it does receive and send 4 bytes (double word). Does that affect the operation? or it has another way to be configured than the regular remote i/o devicenet?

It is Delta (DVP SA2 + DVPDT 01-s)

thanks in advance

Quote from SkyeFire

I assume you are using the MFC DeviceNet port on the KRC2?

That port can only act as a DN Master, not Slave. It should work with any other DN device that acts as a simple polled-I/O Slave. Most PLCs can be configured to act as either M or S on DN.

Thank you dear, the network in working well So I just have to reconfigure the external drives later because I will be using them.

Many thanks