LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

FATAL INTERNAL ERROR 'datamgr.cpp', line no. 1882

I am getting the above error when i try to create DLL for my vi. My vi transmits message from serial port to FPGA Module (ver 1.0). FPGA receives the message and stores it in the memeory, it is same as it is in the NI LVRT FPGA SERIAL READ.LLB. AS i create the dll and build it i am getting this error. Please help me out in fixing the error.
I am using LabVIEW version 7.0
Regards
Subramania Bharathi
0 Kudos
Message 1 of 6
(3,905 Views)
Hi,

I'm afraid that I don't completely understand the explanation of the problem in your situation. It sounds as if you are using a VI in LabVIEW and you are attempting to create a DLL from this VI. So the VI that you plan to build the DLL with contains Serial VI's to do communications. Are you using VISA functions to do the communications? What were you referring to when you say that "it is the same as the NI LVRT FPGA SERIAL READ.LLB"?

Are you receiving the error when you run application builder to create the DLL? Have you attempted to remove any of the serial code in the VI and try to build the DLL again? Any more detailed information you can provide may be helpful in determining the problem. Please let us know.

Thanks,

Patrick R.
0 Kudos
Message 2 of 6
(3,905 Views)
Hi

I am facing problems in creating DLL for a LabVIEW VI.

Previously i had no problems in creating DLL for the VI that transmits a message from serial port(VISA functions) to NI - PXI 7831-R Reconfigurable I/O card (configured by FPGA MOdule). The example VI given in NI site for FPGA MOdule.

When i try the same VI with a similar customized serial port created using IVI drivers, i am not able to create the DLL. It gives me error as follows:


Fatal Internal error: "datamgr.cpp", Line No: 1882

This is the problem i am facing. You can also see the LabVIEW RealTime FPGA Serial Read.llb frrm the NI site
Follow the link below.

http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=C1074FF79B533B59E03408002
0E74861&p_node=200449&p_submitted=N&p_rank=&p_answer=&p_source=External

Regards
Subramania Bharathi
0 Kudos
Message 3 of 6
(3,905 Views)
Hi,

So are you still using the FPGA examples to build your DLL? The LabVIEW VI that you are trying to create the DLL from, does it contain any FPGA code? Is the only thing different the addition of the IVI drivers?

I am trying to determine if it is possibly the FPGA code that is causing the error or if it is the IVI or just something in general with LabVIEW and DLLs. This error code does not provide much information so it must be determined what functions are causing the error. Can you attach your VI to this thread so that we can take a look and hopefully determine the problem?

Thanks,

Patrick R.
0 Kudos
Message 4 of 6
(3,905 Views)
Hi,
Thanks for your curiosity in replying my questions. I am really sorry for replying so late. Actually the problem was with the NI SWITCH 2503 functions. Actually i was multiplexing the channels of my customized serial port using NI Switch module. This switching is done before i start my communication. My VI follows a sequence as follows.
1. Connect two channelss using Switch functions
2. configuration of both FPGA and the customized port
3. Transmit data from the port
4. Receive it in FPGA.
5. Reset the channels using Switch functions

I never expected that the error was because of NI Switch. When i removed them from my VI i was able to create the DLL and able to create sequence successfully to run in
the Testsand. And further i am using Switch Executive for swithcing the channels in TestStand.

But now i am very curious why it posted me that error when i used my NI Switch function?? I tried to create DLL for a VI that switches two channels and i was successful. But the error occurs only when i combine i with my FPGA functions!! If you could trace out the reason, please let me know

Once again thanks a lot for your support

Regards,
Subramania Bharathi
0 Kudos
Message 5 of 6
(3,905 Views)
This error can also occur if you can defined constant typedefs in your application.

If this is the case, then you should use the following procedure:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/34bb42ecbc41e22186256d5100660511?OpenDocument
0 Kudos
Message 6 of 6
(3,905 Views)