Slovakia
Asked — Edited
Resolved Resolved by DJ Sures!

Invoke Custom Api From Project (Ez Script)

I would like to ask, whether it is possible to call custom API from robot. I would need to run several Microsoft's cognitive services, which are not supported directly by plugins. E.g. Face Recognition and Identification. Please is there a way how to invoke those from project built for JD Humanoid?


ARC Pro

Upgrade to ARC Pro

ARC Pro is more than a tool; it's a creative playground for robot enthusiasts, where you can turn your wildest ideas into reality.

PRO
Synthiam
#1  

Create a plugin. Here's the tutorial: https://synthiam.com/Tutorials/UserTutorials/146/1

However, if you just want to identify faces - use the object recognition built into ARC. The robot program shows you how. There's lots of activities, I recommend using the learn section.

Here's the tutorial for object recognition: https://synthiam.com/Tutorials/Lesson/106

Have fun!

Slovakia
#2  

Thanks DJ Sures, I started with the plugin. However I am not able to access JD's camera. This does not return the JD's camera. var cameras = EZ_B.Camera.GetVideoCaptureDevices(); Please what is the way, to discover it ? PS: I do not want to connect to existing camera control. Would like to access camera separately. Thank you!

PRO
Synthiam
#3  

Using the camera separately - download the EZ-SDK package and view the examples.

Otherwise, complete plugin tutorial is found here: https://synthiam.com/Tutorials/UserTutorials/146

Slovakia
#4  

Thanks DJ Sures. I have also found this example: https://github.com/ppedro74/ez-robot-form-application/tree/master/EZFormApplication which implements connection to camera. I would like to note however one problem I had using SDK. When I reference EZ_B.dll in my project, Visual Studio identifies dll to be in version 2015.7.28.0. It is however higher. File metadata states version 2017.07.22.00 . This causes problem when I want to build and run the project, as Visual Studio is not able to find 2015.7.28.0 version. Isn't there some versioning mismatch between metadata and the dll itself? PS: I do use do not copy setting when referencing dll. Thank you!.