Hardware Developers Community - NI sbRIO & SOM

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW Error Code -63040 on sbRIO-9651

Hello,

 

I'm trying to download VI to sbRIO-9651 on LabVIEW 2020 Version 20.0f1 (32-bit). After the compilation of the fpga VI completed successfully, it's giving me the "Warning: Connection to the target (NI-sbRIO-9651-01f836bbb) has been lost." and "LabVIEW FPGA called another software component, and that component returned the following error: Error Code: -63040" as you can see from the image.

 

NI Error codeNI Error code

 

I have already tried the steps that are explained in that pages:

Error -63040: Connection Not Established Using LabVIEW FPGA - NI

 

Solved: LabVIEW Error Code -63040 on sbRIO 9632 - NI Community

 

Also I have tried on 3 different computers and with LabVIEW 2014 and NI RIO software 17.6 installed on the 9651. Nothing solved the problem.

 

Details of the software and firmware installed on the sbRIO-9651 and network settings:

System settings and installed software of the sbRIO-9651System settings and installed software of the sbRIO-9651Details of the network settings of the sbRIO-9651Details of the network settings of the sbRIO-9651

 

Here is the ethernet adapter settings of the computer:

Ethernet adapter settings of the computerEthernet adapter settings of the computer

0 Kudos
Message 1 of 8
(1,717 Views)

Additional information:

NI-RIO settings at MAX:

NI-RIO settings at MAXNI-RIO settings at MAX

 

Also I have created several different CLIP files and predefined DevKit CLIP but do not solve the problem. Blow is the CLIP file which aims to enable eth2 and other listed peripherals:

CLIP deneme2.jpg

0 Kudos
Message 2 of 8
(1,711 Views)

Did you check the NI-RIO Settings on the sbrio. Your screen shot is showing that any other device can access RIO devices hosted by your windows system but you deploying a fpga image from the windows system to the sbRIO. If you've removed the * from the list (on the sbrio)it may present this error. 


Under remote systems 

Expand software under the sbrio

select NIRIO switch to the NI RIO settings tab.

Kyle Hartley
Senior Embedded Software Engineer

0 Kudos
Message 3 of 8
(1,693 Views)

Hi Kyle Hartley,

 

Thanks for your reply.

If I follow the path Remote Systems => NO-sbRIO-9651 => Software => NI-RIO 21.8.0 that is the screen I see is the below:

NI-RIO Software pageNI-RIO Software page

 

At this page I can not see any value or setting that I can change.

After that I follow Tools => NI-RIO Settings menu and under the Remote Device Access section there is * and sbRIO-9651 device name already on the list as you can see at the below image.

 

NI-RIO SettingsNI-RIO Settings

 

Best regards,

 

Emre Dincol

0 Kudos
Message 4 of 8
(1,683 Views)

What does the page look like for NI RIO Server under the sbRIO? Sorry I'm on LabVIEW 2016 with NI RIO 17.5 and the packages are slightly different.

 

Kyle Hartley
Senior Embedded Software Engineer

0 Kudos
Message 5 of 8
(1,674 Views)

Below is the sbRIO 9651 NI-RIO Server page:

NI-RIO ServerNI-RIO Server

0 Kudos
Message 6 of 8
(1,662 Views)

If you have a support contract then I suggest talking to NI. Unfortunately I was expecting you to find a another page that allows access. Double check the ip address of your target is all I can suggest further.

Kyle Hartley
Senior Embedded Software Engineer

0 Kudos
Message 7 of 8
(1,640 Views)

Hi there,

 

I am colleague of edincol. I want to inform you that we have solved the issue. The problem was hardware related. As summary, we developed a daughterboard for sbRIO 9651 SoM for first time and started testing all the I/Os of board. When we were testing the ethernet ports we encounter a problem which we first thought that it is a CLIP issue. After testing all the suggestions you and ni forum made on software side, we went deep to investigate the hardware layout of board. Second ethernet port which is our issue, hardware is implemented on our daughterboard which is based on KSZ9031MNXIA. This IC's reset and physical address pins connections were faulty on our board. After we fixed that connections, second ethernet port showed up on MAX and we are now able to communicate via this port to SoM. Also we managed to work the EtherCAT connection on this port to EtherCAT slave drives. 

 

Hardware Note: We also made work EtherCAT connection by using KSZ9021RL which is nearly pin-to-pin compatible with KSZ9031MNXIA hardware.

 

Thank you

0 Kudos
Message 8 of 8
(1,562 Views)