Deadlock when using CIN

[Josv]

Hi

I have trouble when I’m reading data into Labview using the CIN, code interface node. The problem “memory could not read” which occurs at the second or third reading and forces the Labview to restart. Se attachments…

I’m receiving data from an USB chip and will further manipulate the data in Labview…

 

Best regards

Jonny

[Jimmie_A.]

Hello Jonny!

Check out the following information regarding the Code Interface Node (CIN) and LabVIEW that contains information that hopefully is useful for you.

Code Interface Node:
Why does my CIN run once, but gets a memory error the second time?
http://forums.ni.com/ni/board/message?board.id=231&message.id=364&requireLogin=False

When a program included a CIN is executed,it always indicate that some memory can not be read or written,please why?
http://forums.ni.com/ni/board/message?board.id=170&message.id=25374&requireLogin=False

Multiple References to the Same CIN in Different VIs
http://zone.ni.com/reference/en-XX/help/371361A-01/lvexcodeconcepts/mult_refs_same_cin_diffvis/

Q:how to allocate memory in CINs?
http://forums.ni.com/ni/board/message?board.id=170&message.id=4409

Would also like to suggest that you try to use Call Library Node instead (call DLLs). Some things to consider when it comes to Call Library Node functions can be found below:

LabVIEW Application Error: The instruction at "[address x]" referenced memory at "[address y]". The memory could not be "read".
http://digital.ni.com/public.nsf/websearch/E8C5C452F04EF7BE86256EF50068CAAF?OpenDocument

LabVIEW Crashes after a VI That Calls a DLL Exits
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/91d4656b15b0dc7a86256ace0073ca90?O...

When Using the Call Library Function Node, LabVIEW Crashes after the Function Executes
http://digital.ni.com/public.nsf/websearch/58596F5D41CE8EFB862562AF0074E04C?OpenDocument

 Regards,

Jimmie A.

Applications Engineer, National Instruments

[Josv]

Many great links...

By initiate the arrays correctly the problem were almost solved, sometimes deadlocks do occur but not so often...

"In the correct method, the array is initialized to the desired size, which allocates space in memory, before passing the array to the function."

From: http://digital.ni.com/public.nsf/websearch/58596f5d41ce8efb862562af0074e04c?OpenDocument

There could be better to look into Call Library Node instead as you suggested, any great links to get started?

Thanks

Jonny

[Jimmie_A.]

Hello!

I had some time off therefore the delay but here is some useful information for you:

http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/building_a_shared_library_dll_/

Regards,

Jimmie A.

Applications Engineer, National Instruments