LabVIEW 2020 and D455f not work

[Fateluck]

-RealSense for Labview ver. 2.33 (Latest SDK)
-LabVIEW 2020x64
-Win10x64

All demos do not find the RealSense when launched. The RealSense is launched in the Intel RealSense viewer. At the same time, Python demos work successfully.

Is 455f supported in LabVIEW SDK?

[MartyG-RealSense]

Hi @Fateluck A D455f should behave like a D455. However, D455 support was not introduced into the RealSense SDK until version 2.38.0.

A RealSense user at #7920 who had this version problem with their D455 copied the more modern realsense2.dll file to the LabVIEW folder and updated their camera firmware driver and it worked for them.

If you are using SDK 2.33 then you could copy the realsense2.dll from 2.55.1 and make sure that your camera firmware driver version is 5.16.0.1.

On Windows a pre-made dll can be obtained by installing version 2.55.1 of the full RealSense SDK using the Intel.RealSense.SDK-WIN10 installer file first.

https://github.com/IntelRealSense/librealsense/releases/tag/v2.55.1

Afterwards, go to the computer location below and copy the realsense2.dll file from this folder into the LabVIEW folder.

C: > Program Files (x86) > Intel RealSense SDK 2.0 > bin > x64

[Fateluck]

Hi @MartyG-RealSense Thank you!

I tried what you indicated earlier. My camera was detected, but the error "Capture error" appeared and the image did not appear in the demo example.

I tried to downgrade the firmware version to 5.12.09 and now........... my camera is not detected in the device manager :(

Windows 10 writes "USB device not recognized" What could it be? The device is not detected in Viewer either.

[Fateluck]

I downloaded the firmware Signed_Image_UVC_5_16_0_1. I tried to detect the device via rs-fw-update -l and update the firmware via rs-fw-update -r -f Signed_Image_UVC_5_16_0_1.bin and it did not help. The device is not detected

[MartyG-RealSense]

The minimum supported firmware version for D455 type cameras is 5.13.0.50. Installing an older firmware than that can make the camera unusable and unable to be recovered by the user due to non-detection.

This problem will likely require the camera to be sent by parcel post to Intel in California, US to have its firmware corrected by an Intel RealSense engineer and then have the restored camera mailed back to you afterwards, unfortunately.

If that is what you wish to do, may I ask which country you are located in please?

[Fateluck]

Hi @MartyG-RealSense, was guided by this post - #10064. I'm from Germany. I think that sending to America is more expensive than buying a new camera. Is it possible to repeat the solution from "dorodnic" with the my D455f camera as stated in this post with the 435 camera - #5052

[MartyG-RealSense]

The only option for self-repair would be to purchase a circuit board called the Vision Processor D4 V3 Board, open up your camera and swap the existing D4 circuit board for the new one. The average price for a D4 board from Intel authorized suppliers is around 45 Euro.

[Fateluck]

Got it, I'll look for it.

[MartyG-RealSense]

Thanks very much for highlighting the Dorodnic suggested solution at #5052 (comment)

It has been 5 years since that suggestion and the structure of the librealsense SDK changes over time. The two .cpp files mentioned do not exist any more, unfortunately.

I believe that the PID list of ds5-private.cpp is now at d400-private.h

librealsense/src/ds/d400/d400-private.h

Lines 14 to 39 in e1688cc

	namespace ds
	{
	const uint16_t RS400_PID = 0x0ad1; // PSR
	const uint16_t RS410_PID = 0x0ad2; // ASR
	const uint16_t RS415_PID = 0x0ad3; // ASRC
	const uint16_t RS430_PID = 0x0ad4; // AWG
	const uint16_t RS430_MM_PID = 0x0ad5; // AWGT
	const uint16_t RS_USB2_PID = 0x0ad6; // USB2
	const uint16_t RS_D400_RECOVERY_PID = 0x0adb;
	const uint16_t RS_D400_USB2_RECOVERY_PID = 0x0adc;
	const uint16_t RS400_IMU_PID = 0x0af2; // IMU
	const uint16_t RS420_PID = 0x0af6; // PWG
	const uint16_t RS420_MM_PID = 0x0afe; // PWGT
	const uint16_t RS410_MM_PID = 0x0aff; // ASRT
	const uint16_t RS400_MM_PID = 0x0b00; // PSR
	const uint16_t RS430_MM_RGB_PID = 0x0b01; // AWGCT
	const uint16_t RS460_PID = 0x0b03; // DS5U
	const uint16_t RS435_RGB_PID = 0x0b07; // AWGC
	const uint16_t RS405U_PID = 0x0b0c; // DS5U
	const uint16_t RS435I_PID = 0x0b3a; // D435i
	const uint16_t RS416_PID = 0x0b49; // F416
	const uint16_t RS430I_PID = 0x0b4b; // D430i
	const uint16_t RS416_RGB_PID = 0x0B52; // F416 RGB
	const uint16_t RS405_PID = 0x0B5B; // D405
	const uint16_t RS455_PID = 0x0B5C; // D455
	const uint16_t RS457_PID = 0xabcd; // D457

If you want to purchase a D4 V3 board from Germany then the closest Intel-authorized supplier will likely be Rutronik24 Gmbh.

https://www.rutronik24.co.uk/product/intel/82635dsasicbdif/14278151.html