Request for Ensenso SDK Compatibility with ARMv7 (armhf) Architecture

General Information

  • Product: Ensenso S-10
  • Serial Number: 245229
  • Ensenso SDK Version: Ensenso SDK 4.1.1023
  • Operating System: Linux

Problem / Question

My robotic arm motion controller runs on an ARMv7 32-bit architecture with ARM hard-float (armhf) support. However, the available Ensenso SDK packages, which contain the software executable files, are not compatible with this architecture.

Could you please assist us by providing a compatible SDK build for our system or suggest any possible workarounds?

Unfortunately the SDK is not available for 32 bit ARM, since such systems usually don’t have the performance necessary to handle stereo matching. Matching for the S-series is only supported on x64 at the moment.

I would say it is very unlikely that our software will ever run on 32 bit ARM, since that is becoming less widespread in general. Could you provide more information about your system and use case?

Thanks for the update. Our initial goal was to connect the camera directly to the motion controller (a 32-bit system) via an Ethernet port. However, since that doesn’t seem feasible, we are considering using a 64-bit Windows PC as an intermediary. The plan is to retrieve data from the camera on the PC and then relay it to the motion controller via TCP/IP.

The use case involves using coordinate data from the camera to trigger the motion controller, which will then move a robotic arm.

We’d appreciate any further insights, suggestions, or potential blind spots you might identify in this setup.

I understand that NxView cannot be installed on a 32-bit system. However, I’m curious—would it still be possible to use the SDK provided for Linux to control the camera on this 32-bit system using Python, even without running the ensensosdk.deb installer?

would it still be possible to use the SDK provided for Linux to control the camera on this 32-bit system using Python

No, we don’t provide any executables running on this system. Even the Python interface forwards all of its operations to libNxLib64.so or libNxLibRemote64.so, which don’t exist for this system.

The NxLib does have a HTTP API which is used by libNxLibRemote64.so and which you could potentially use to remote control the NxLib on the Windows system. However, this would still require you to process a point cloud on a very low power system. If you have the additional Windows system anyway it probably makes more sense to do all computations there and send only the result to the motion controller.

Thanks a lot for your quick response and providing me more clarity on this.