TX2 NX failed to use industrial camera

    We used the self-developed loading board equipped with TX2-NX, the system can be started normally, and the interface can also be used normally.
    However, when we used hikvision's industrial camera, we found that the camera could not collect images when it was connected to the INTERFACE of USB3.0, but could collect images when it was connected to the interface of USB2.0.

Hikvision’s industrial camera has a 3.0 USB port.

You’d better investigate kernel log messages to find out what’s happen at the camera

Hi,
We suggest check if compliance test is done. Please refer to
https://developer.nvidia.com/jetson-tx2-nx-tuning-and-compliance-guide-application-note

The default setting is for devkit and needs to be adjusted for custom boards.

Thank you for your prompt reply.
I checked the log information. After connecting the industrial camera to the USB3.0 interface, I could see the camera equipment. Using the software provided by Hikvision, I could also connect the camera, but I could not collect images.

I think it’s important to check the log information, but I don’t know how to deal with it.

[ 4.976591] usb 2-2: new SuperSpeed USB device number 2 using tegra-xusb
[ 4.999900] usb 2-2: LPM exit latency is zeroed, disabling LPM.
[ 5.000722] usb 2-2: New USB device found, idVendor=2bdf, idProduct=0001
[ 5.000725] usb 2-2: New USB device strings: Mfr=5, Product=3, SerialNumber=6
[ 5.000727] usb 2-2: Product: MV-CE120-10UC
[ 5.000729] usb 2-2: Manufacturer: Hikvision
[ 5.000731] usb 2-2: SerialNumber: 00E92409187
[ 5.499252] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.517577] CPU1: shutdown
[ 5.521063] psci: CPU1 killed.
[ 5.577285] CPU2: shutdown
[ 5.580024] psci: CPU2 killed.
[ 5.700893] zram: Added device: zram0
[ 5.701291] zram: Added device: zram1
[ 5.701633] zram: Added device: zram2
[ 5.702632] zram: Added device: zram3
[ 5.728666] zram0: detected capacity change from 0 to 502312960
[ 5.769214] Adding 490536k swap on /dev/zram0. Priority:5 extents:1 across:490536k SS
[ 5.771940] zram1: detected capacity change from 0 to 502312960
[ 5.795028] Adding 490536k swap on /dev/zram1. Priority:5 extents:1 across:490536k SS
[ 5.797768] zram2: detected capacity change from 0 to 502312960
[ 5.810876] Adding 490536k swap on /dev/zram2. Priority:5 extents:1 across:490536k SS
[ 5.813502] gpio tegra-gpio-aon wake51 for gpio=47(AA:7)
[ 5.816341] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.818497] zram3: detected capacity change from 0 to 502312960
[ 5.845408] Adding 490536k swap on /dev/zram3. Priority:5 extents:1 across:490536k SS
[ 7.402735] tegradc 15200000.nvdisplay: unblank
[ 7.402743] tegradc 15210000.nvdisplay: blank - powerdown
[ 8.506263] fuse init (API version 7.26)
[ 10.533487] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.533499] Bluetooth: BNEP socket layer initialized
[ 11.937685] tegradc 15200000.nvdisplay: unblank
[ 11.937693] tegradc 15210000.nvdisplay: blank - powerdown
[ 12.731792] eqos 2490000.ether_qos: changing MTU from 1500 to 9000
[ 13.061275] gpio tegra-gpio-aon wake51 for gpio=47(AA:7)
[ 13.419338] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 19.650276] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 19.651790] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 19.670044] eqos 2490000.ether_qos: Got unsupported MTU size 9014, MAX supported MTU size is 9000 bytes
[ 19.687138] eqos 2490000.ether_qos: Got unsupported MTU size 9014, MAX supported MTU size is 9000 bytes
[ 21.267509] eqos 2490000.ether_qos: Got unsupported MTU size 9014, MAX supported MTU size is 9000 bytes

Thank you for your prompt reply.
Usb3.0 is available and I can use the wireless mouse and keyboard with USB3.0.The log also shows that the device connected to USB3.0 is normal.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.