Can't get any images under Linux

Questions & Answers
1

General Information

  • Product: e.g. N46-804-16-BL, C57-6-S
  • Ensenso SDK Version: 4.2.1821
  • Operating System: Linux Ubuntu 22.04
  • Problem / Question

Hello,

All the sensors work under Windows.

Under Linux I can’t receive any images and I get the following error:

An NxLib error occurred while executing the command:
ComputeDisparityMap:
CommandComputeDisparityMap: Camera has invalid piped model
Current node value:
{
“Command”: null,
“Parameters”: null,
“PersistentParameters”: false,
“Result”: {
“ErrorSymbol”: “CommandComputeDisparityMap”,
“ErrorText”: “Camera has invalid piped model”,
“Execute”: {
“Command”: “ComputeDisparityMap”,
“Parameters”: {
“Cameras”: null,
“OpenMP”: {
“Dynamic”: 1
},
“StaticBuffers”: 2,
“Threads”: 14
}
}
},
“Status”: {
“LatestMessage”: null,
“Messages”: [
],
“Progress”: null,
“Time”: 0.066886000000000015
}
}

Can you please help me figure out the issue?

Thank you

Best regards,

Alessandro

2

Hi Alessandro,

“Invalid piped model” occurs if no images have been captured and NxLib then tries to compute a disparity map. What camera are you using?

Kind regards
Benny

3

Hi Benjamin,

I tried with N46-804-16-BL and C57-6-S.

Best regards,

Alessandro

4

Sorry, I overlooked the different N-Series model name. The camera types looked suspiciously like the default text of our question template.

If both cameras show the same erroneous behavior then you might have to do some network configuration. We have a guide on network performance that helps you make the correct settings under Linux. Let me know if that fixes your problem. If not, please provide us with some details on your network setup.

5

I tried with Ensenso C.

By reducing the network bandwith, I get the images, but I need about 1 s (1 Gb/s, MTU 9000, TX/RTX 4096, no energy saving). Instead in Windows 200/300 ms are sufficient.

I don’t get why there is this difference.

6

Hi Alessandro,

could you please provide us with some details on your network setup?

  • Are you using a switch?
  • Are you using PoE?
  • Did you use the same network cables?
  • Does your network adapter report it is at 1Gb/s?

Kind regards
Benny

7

Hi Benny,

I’m using a direct connection at 1 Gb/s (verified with ethtool). The N device is powered by PoE, instead the C device by means of an external power supply able to deliver more than 200 W.

The setup is the same as in Windows.

Best regards,

Alessandro

8

Hi Alessandro,

could you please record a log file while the camera is running and trying to receive the images? You can send me a PM with the log file if you don’t want to post it here publicly.

Kind regards
Benny

9

Hi Benny,

I just sent you a PM.

Best regards,

Alessandro

10

There seems to be a problem with your network adapter. The packets are arriving, but with some pauses in between, so that the overall capture duration is exceeded. Do you have a chance to test another adapter on that machine or even on another Linux machine? Could you also tell us which adapter you are currently using?

11

Hi,

Here you can find the adapter information:

description: Ethernet interface
product: Ethernet Connection (16) I219-V
vendor: Intel Corporation
physical id: 1f.6
bus info: pci@0000:00:1f.6
logical name: eno1
version: 01
serial: 5c:60:ba:c9:29:39
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.15.0-160-generic firmware=0.5-4 latency=0 link=no multicast=yes port=twisted pair
resources: irq:144 memory:84180000-8419ffff

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-V (rev 01)
DeviceName: Onboard Ethernet
Subsystem: Hewlett-Packard Company Ethernet Connection (16) I219-V
Flags: bus master, fast devsel, latency 0, IRQ 144, IOMMU group 13
Memory at 84180000 (32-bit, non-prefetchable) \[size=128K\]
Capabilities: 
Kernel driver in use: e1000e
Kernel modules: e1000e

At the moment I don’t have a different adapter or a different PC to test, I’ll try to find one.

In any case, in your experience is the behavior under Linux expected as the behavior under Windows, so that this issue is related to a particular HW/SW configuration on my PC?

Best

Alessandro

12

Hi Alessandro,

yes, if the camera properly works on Windows we also expect it to work on Linux. There is always the possibility of a bug in our firmware which could lead to diverging behaviors between the two OS, but since the packets are arriving on your machine as I stated above, this looks like the problem is linked to your current machine.

A quick search led me to this: https://askubuntu.com/questions/1376155/intel-i219-experiencing-huge-package-loss. There is, however, no proposed solution. Neither in other posts/questions I could find. Do you also see the packet loss when doing a ping with 1Gb/s?

Let me know if you had the change to try another adapter or machine, which I think is most promising right now.

Kind regards
Benny

13

Hi,

I made a test on a different PC (desktop, the first was a laptop) equipped with:

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10) 
       DeviceName: Onboard - Ethernet 
       Subsystem: Dell Ethernet Connection (7) I219-LM 
       Flags: bus master, fast devsel, latency 0, IRQ 135, IOMMU group 11 
       Memory at 92000000 (32-bit, non-prefetchable) \[size=128K\] 
       Capabilities: <access denied> 
       Kernel driver in use: e1000e 
       Kernel modules: e1000e

and the acquisition worked properly.

I assume that the problem on the first PC must be related to some low level issue in the packet management.

Should you find out something more, please let me know.

Thanks for your assistance.

Best regards,

Alessandro

14

Hi Alessandro,

I am glad to hear that it works with a different PC. Since the problem is not related to our hardware, there won’t be any further investigations done by us. If something similar will come up in the future and there seems to be a solution, we might remember and update this issue.

Kind regards
Benny