Re: Issues in getting started with SceneScan Pro

Post Reply
saurabheights
Posts: 7
Joined: Fri Nov 03, 2023 7:52 pm

Issues in getting started with SceneScan Pro

Post by saurabheights »

Hi,
I am working with SceneScanPro with 2 ALVIUM 1800 U-507m cameras on Ubuntu 22.04. The SSP is connected directly to my system with LAN wire.

Majority of the time, I am unable to get even basic camera preview. Using web api -

1. Network - Tried with TCP and UDP. Jumbo frames are enabled and eno1 interface is set to mtu 9000.

Code: Select all

ip link show | grep mtu
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
2. I have set Active Output Channels to Left Image only,, Left and Right, Left and Disparity and only disparity. None helps.

3. Tried preset with and without Jumbo frames.

4. Preview Tab keeps getting stuck at - "One moment please ..."

5. Camera Selection - I even moved to use example, just to verify if everything works with virtual cameras. But here it shows left camera with lots of artifacts.Image

6. Upgraded firmware version to 9.3.1, still shows same issues.

I did a clean reset to reproduce above issues and followed these steps:-
A. Hard RESET.
B. Change Jumbo FRAMES.
C. View Camera at http://192.168.10.10/calibrate/ (Shows memory virtual camera with artifact).
D. Change camera to ALVIUM cameras.
E. View Camera at http://192.168.10.10/calibrate/ - shows nothing.
Attachments
settings.tgz
(231.27 KiB) Downloaded 105 times
saurabheights
Posts: 7
Joined: Fri Nov 03, 2023 7:52 pm

Re: Issues in getting started with SceneScan Pro

Post by saurabheights »

I am not using any external trigger wires. I have used nvcom and it shows same artifacts as in above image when using virtual cameras.

In web ui, I see following error logs:-

Code: Select all

00:49:11 daemon.info stereod: Using cameras 05GR2; 05GR3
00:49:11 daemon.info stereod: Daemon stopped
00:49:11 daemon.err stereod: Exception: Error opening cameras (left: 0; right: 1)
00:49:11 daemon.err stereod: /usr/bin/stereod(__cxa_throw+0x108) [0xaaaae7e9e2cc]
00:49:11 daemon.err stereod: /usr/bin/stereod(_ZN13AravisCapture10initializeEii+0x8b8) [0xaaaae7ef8ee8]
00:49:11 daemon.err stereod: /usr/bin/stereod(_ZN13CameraManager11openCamerasEv+0x3a4) [0xaaaae7ee9a54]
00:49:11 daemon.err stereod: /usr/bin/stereod(_ZN13CameraManager10initializeEb+0x2c) [0xaaaae7eea27c]
00:49:11 daemon.err stereod: /usr/bin/stereod(_ZN13CameraManager19subsystemInitializeEv+0xd0) [0xaaaae7eea5b0]
00:49:11 daemon.err stereod: /usr/bin/stereod(_ZN14SubsystemStore15checkSubsystemsEv+0x404) [0xaaaae7f5e054]
00:49:11 daemon.err stereod: /usr/bin/stereod(_ZN10DaemonMain3runEiPPc+0xf84) [0xaaaae7f678c8]
00:49:11 daemon.err stereod: /usr/bin/stereod(main+0x40) [0xaaaae7ea1120]
00:49:11 daemon.err stereod: /lib/libc.so.6(__libc_start_main+0xe8) [0xffffa2a80878]
00:49:11 daemon.err stereod: /usr/bin/stereod(_start+0x38) [0xaaaae7ea33f8]
But the system later recovers from this error, with a full reset:-

Code: Select all

00:50:01 daemon.err watchdogd: Process stereod stalled for 10.7373s! Restarting!
00:50:01 daemon.info stereod: Caught signal 15
00:50:03 daemon.info nvparamd: D-Bus client name com.nerian.stereod was removed
00:50:03 user.notice root: Performing USB reset
00:50:03 user.info kernel: [ 2022.389064] usb 2-1: USB disconnect, device number 24
00:50:03 user.info kernel: [ 2022.394450] usb 4-1: USB disconnect, device number 24
00:50:07 user.info kernel: [ 2026.109745] usb 2-1: new SuperSpeed Gen 1 USB device number 25 using xhci-hcd
00:50:07 user.info kernel: [ 2026.116896] usb 4-1: new SuperSpeed Gen 1 USB device number 25 using xhci-hcd
00:50:07 user.info kernel: [ 2026.134147] usb 2-1: New USB device found, idVendor=1ab2, idProduct=0001, bcdDevice= 1.00
00:50:07 user.info kernel: [ 2026.142332] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
00:50:07 user.info kernel: [ 2026.149467] usb 2-1: Product: ALVIUM 1800 U-507m
00:50:07 user.info kernel: [ 2026.154089] usb 2-1: Manufacturer: Allied Vision
00:50:07 user.info kernel: [ 2026.158706] usb 2-1: SerialNumber: 05GR2
00:50:07 user.info kernel: [ 2026.163742] usb 4-1: New USB device found, idVendor=1ab2, idProduct=0001, bcdDevice= 1.00
00:50:07 user.info kernel: [ 2026.171963] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
00:50:07 user.info kernel: [ 2026.179097] usb 4-1: Product: ALVIUM 1800 U-507m
00:50:07 user.info kernel: [ 2026.183724] usb 4-1: Manufacturer: Allied Vision
00:50:07 user.info kernel: [ 2026.188337] usb 4-1: SerialNumber: 05GR3
00:50:08 user.notice root: USB reset complete. All devices reconnected
However, the stereo preview or calibrate fails to show camera view/disparity.
Last edited by saurabheights on Fri Nov 03, 2023 10:16 pm, edited 1 time in total.
k.schauwecker
Posts: 120
Joined: Mon Mar 25, 2019 1:12 pm

Re: Issues in getting started with SceneScan Pro

Post by k.schauwecker »

Hi,

I apologize for the difficulties. Could you provide the serial number of the device?

Best regards,
Konstantin
saurabheights
Posts: 7
Joined: Fri Nov 03, 2023 7:52 pm

Re: Re: Issues in getting started with SceneScan Pro

Post by saurabheights »

Hi Konstantin,
The SSP device has a plastic tag on it with "00406" written on it, but I dont think that is it. Any idea where I can get the serial number?
k.schauwecker
Posts: 120
Joined: Mon Mar 25, 2019 1:12 pm

Re: Re: Issues in getting started with SceneScan Pro

Post by k.schauwecker »

Hi,

I think my colleague has already reached out to you. Could you please return the device so we can address the issues.

Best regards,
Konstantin
saurabheights
Posts: 7
Joined: Fri Nov 03, 2023 7:52 pm

Re: Re: Issues in getting started with SceneScan Pro

Post by saurabheights »

Dear Konstantin,
I have returned the device yesterday. Thank you for the assist.

Best Regards,
Saurabh.
Post Reply