how can I connect the DeviceNet scanner module with a laptop to establish communication with micrlgx 1500 lrp ? What all things are required for the communication ?
micrologix 1500 connecting with device net for kuka krc2
-
AD3MIN -
March 2, 2023 at 11:50 AM -
Thread is Resolved
-
- Go to Best Answer
-
95devils
March 2, 2023 at 12:02 PM Approved the thread. -
how can I connect the DeviceNet scanner module with a laptop to establish communication with micrlgx 1500 lrp ? What all things are required for the communication ?
Hai everyone,
I am new with kuka,I have KUKA KRC2 with Version V5.5.16,other end I have Allen Bradly Micrologix 1500 which has devicenet scanner module 1769 SDN macid=63 also it has devicenet I/O module IL 2302 macid=10
I am trying to communicate these two modules from robot,
In DEVNET FILE I wrote as
In iosys.ini file I wrote as
I got error in the robot as
Configuration error I/O driver DN2DRV
Error on Writing,driver:DN2DRV
Can anyone provide your valuable suggestions.
Thanks in Advance
ADVMIN
-
- Best Answer
Scanner is another name for master. If your KRC is using DNET interface on MFC, direct communication is not possible because MFC is also a scanner. For this to work one of them need to be a master and other need to be a slave...workaround is to use suitable gateway. Each side of gateway would appear as slave to respective master
-
Another option is to not use MFC. Get LPDN card. This can act as master oe slave or both. .
-
Many thanks for your reply.
How can we make the MFC a 'SLAVE' ? Is that possible ?
cheers
-
Many thanks for your reply.
How can we make the MFC a 'SLAVE' ? Is that possible ?
No.
-
thanks for the reply.
Iam working on KUKA KRC2 with Version V5.5.16,other end I have Allen Bradly Micrologix 1500 which has devicenet scanner module 1769 SDN.
Today I counter another error message that is 'invalid$ tool : working envelope surveillance not possible'
What is this error means ?
cheers
-
It means that no Tool was active, and as such, workspace monitoring was not possible. Your active Tool Number was probably set to 0. This is fairly normal after a reboot or a program cancel/reset. The message should clear itself when you activate a valid tool.
-
Sorry for the late reply. Thankyou all for helping me out.
cheers.