@ LowerCaseDream forse questo aiuterebbe. Basta smontare l'app client di esempio. E afferra il concetto. Lo provo solo a scopo didattico.
Hi,
very good! can you share that cliet code?
@ LowerCaseDream forse questo aiuterebbe. Basta smontare l'app client di esempio. E afferra il concetto. Lo provo solo a scopo didattico.
Hi,
very good! can you share that cliet code?
Display More(Edited!!!)
Hi,
I was able to connect to KUKA OfficeLite and KUKA Office PC (real PC that runs KSS 8.6) 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.
7. The server and the client mentioned here are developed by myself. Y200 is not a server, but only an interface used to exchange the data between KRC and shared memory.
Sorry, I cannot share the source code, but feel free to ask any specific questions.