FP-2000 Error 8

[daniele]

My application, written in LabVIEW 6.1 RT, and running on a FP-2000, stops with error 8 (status LED flashing 8 times), and the error log shows:

*** REGISTER DUMP FROM EXCEPTION HANDLER (code 😎 ***

EAX = 0x00000000 EBX = 0x00000002
ECX = 0x0000001D EDX = 0x00137604
ESI = 0x007E6398 EDI = 0x0000CA00

EBP = 0x007E6258 ESP = 0x007e5fc8
CS = 0x0018 DS = 0x0020 ES = 0x0020
EIP = 0x003834fc

Thread name:
Thread stack base: 0x007C7004 stack size: 131072

Call Stack:
Level 1 : Code pointer: 0x003C2AF7 Stack Base: 0x007E65C0
Level 2 : Code pointer: 0x0038CEB3 Stack Base: 0x00000002
Level 3 : Code pointer: 0x005E1E97 Stack Base: 0x00000000

Error Message =Not enough memory to complete this operation.


LabVIE
W RT engine is Shutting down due to internal error: Error Message =Failure : "setstate.cpp" line 1608



For assistance in resolving this problem, please record the preceding information and navigate to www.ni.com/failure, or contact National Instruments.

----------------------

Thank you in advance for the help.

NB. My application is 0,7 MB and it does not log any data. BTW, is there a way to monitor the D-RAM of the FP-2000?

[JeffBoettcher]

This definitely sounds like an issue with running out of RAM.

Keep in mind that while your VIs might only total 700 KB, that is not all that gets downloaded to the FP-2000. All LabVIEW built-in VIs and DLLs used within also need to get downloaded to the FP-2000. If you are using a lot of LabVIEW functionality, while the VIs you have written might only total 700 KB, your whole application might be much larger. In particular if you are using any polymorphic VIs (the FieldPoint Read / Write VIs themselves are an example of this) all versions of the polymorphic VI are downloaded, and this takes more memory at download time.

In addition to these issues, your program could be dynamically allocating memory. If you have a Create Tag VI inside a loop, this consumes me
mory very quickly. The Publish Data.vi is also fairly memory intensive, especially when many data points are being used. In general, the use of build array, string concatenate, and other functions that dynamically allocate memory inside a loop are a bad idea and can cause this sort of behavior.

[daniele]

Thank you for the suggestions.

I tried to eliminate the problem using different functions and data structures and finally found out that the problem was most probably related to queues.

Apparently, just subsituting the queues with different structures (i.e. simple VIs using shift registers) the problem disappeared. Our application was using queues intesively for communication between different tasks, but I am afraid that the queue implementation in LabVIEW RT on FP-2000 has some problems in memory allocation.