Reuse of .lvbitx file in different PCs

[arun004]

Hello,

I have a doubt regarding PXI 7841R. Can I reuse a .lvbitx file which was generated for a 7841R from the first PC to second PC which is having the same 7841R PXI card. I am currently using a dll to access this lvbitx file in the first PC. I want to use the same dll file and the .lvbitx file in the second PC.

Please let me know if it is possible.

Thanks in Advance!!

[crossrulz]

I don't see why not.  I've worked with similar boards, built the lit file on a development computer and used on several test systems.

Are you having issues?

[santo_13]

The .lvbitx file is for the instrument/card and not linked to the PC. You can use it on as many 7841R as possible, this is like the firmware for a microcontroller.

[arun004]

Hi 

Thanks for the response.

I have two 7841R cards which is connected to two different PCs . I want to use the .lvbitx file from the first PC in the second PC. When I tried accessing the .lvbitx using the dll generated in the first PC by copying it to second PC, I get error number 63101 saying bit file issue. I tried keeping the .lvbitx in the same path as the previous PC.

PS: I am not accessing the dll directly using labview. I am using vector CANoe to access the dll. 

[arun004]

Hi

I got 63101 error (NI error bit file loading issue). I kept the .lvbitx fiile in same path as the development pc. 

PS: I am not using Labview to access the dll. I am using vector CANoe to access the dll.

[crossrulz]

---

@arun004 wrote:

Hi

I got 63101 error (NI error bit file loading issue). I kept the .lvbitx fiile in same path as the development pc. 

PS: I am not using Labview to access the dll. I am using vector CANoe to access the dll.

---

Do you have the NI R Series Multifunction RIO Driver installed on the second computer?  If so, is it the same version you have installed on the development computer?

[arun004]

Hi

I had installed Version 17.0.1 in the development PC and Version 21.5 in the second computer. I tried changing the Second computer back to 17.0.1. But still the issue persists.

Let me know if I have to change anything else..