The library exists and is being tested by some customers. Do not hesitate to contact us via the contact form of the website or contact [at] underautomation.com to have access to it
Posts by Alfred
-
-
RMI / RSI lack of features, for example it is impossible to servo on the robot, start a program by name, acknowledge errors, ...
-
Yes, but there is nothing to install on the robot, the goal is to implement the native communication interfaces in a fully managed .NET DLL.
-
ahah still alive
After discussion with Fanuc, PCDK is an old protocol whose sustainability in time is no longer guaranteed.
Fanuc advised me to look into "Robot Interface" instead. So I'm implementing it in .NET. There are almost the same features as in PCDK : access to I/O, remote control of the robot, access to the registry, robot status...
For your information, I just published this kind of library for Universal Robots (https://underautomation.com).
Next month, I will release the same one for Yaskawa. And then, I will industrialize the library for Fanuc. So no release before the end of this year.
-
I am in discussion with Fanuc, I am making progress and I think I will be able to legally market a .NET/Fanuc communication SDK
-
I just observed the frames with Wireshark and understood the principle of the protocol.
But ok, that's what it seemed to me, I don't think I'm going to dig deeper into this subject.
-
This is an interoperability issue. PCDK does not exist for Linux, I created it. Now I wonder if I have the right to deploy it and make it available to others.
-
I have opened a thread dealing with almost the same subject here : Fanuc PCDK reverse engineered for .NET
-
I have opened a thread dealing with almost the same subject here : Fanuc PCDK reverse engineered for .NET
-
Hi,
I have reverse engineered the Fanuc PCDK library. I now have a pure .NET DLL (no c++ native dependencies, compatible with .NET standard, framework and Core) able to retrieve the robot position (TCP and joints), the robot state (running program, alarm state, ...), read and write registers, transfer and trigger the execution of a program.
As it is .NET, it can also be used in LabView, Matlab or other... I tested it with .NET Core and it runs on Windows, Linux and MacOS.
I need these features for one of my projects, but I wonder :
- Do I have the right to retroengineer this library?
- Do you find it useful to have a pure .NET lib ?
- Can I legally sell this library (obfuscated version) ?
Here is an old Related thread and another here