Display MoreHi,
I was able to connect to KUKA OfficeLite and KUKA Office PC (real PC that runs KSS) through the Y200 interface and I hope my experience can help somebody. Please, see the detailed communication diagram attached.
Briefly about the main thing: the Server is a service program, which, in connection with the Y200 Interface, allows the coupling between the OLP application and the virtual robot controller (VRC) application KUKA.OfficeLite over TCP/IP network.
From my experience:
1. Y200 does not have to be licensed.
2. The VRC and Y200 interfaces cannot be installed together on the KRC virtual image, otherwise the Y200 interface will not work properly.
3. Y200 interface only works with KSS 8.5 and higher.
4. Use network address translation (NAT): the virtual machine and the host system share a single network identity that is not visible outside the network.
5. C:\KRC\User\Y200Interface.config file contains the Y200IpcName - the shared-memory name to access the KRC data.
6. The following data are stored on the shared memory: Inputs $IN[], Outputs $OUT[], Axis-specific position $AXIS_ACT, Cartesian position $POS_ACT, Current base $BASE and Current tool $TOOL. The Inputs can be read/written, but the outputs are only read access.
Sorry, I cannot share the source code, but feel free to ask any specific questions.
Hi Mischa,
I would come back to your offer with the specific questions
Recently I set up a C# application which connects via TcpClient to the Y200 Server. Unfortunatly the Y200 Server displays an error message "wrong telegram format" when I try to exchange data. Until the message is sent, I receive a few bits, but nothing that makes any sense to me (compared to the IO, Base and tool data bits).
So my question: did you have the telegram format error as well any can share any tips to solve it / how does the telegram look like?
Or didn't you have to built everything from scratch by using the InteropWMCommLib? If so: any tips here? I'm having trouble with the interop components.
Thanks in advance!