LabVIEW Embedded

cancel
Showing results for 
Search instead for 
Did you mean: 

Microprocessor VIs and TCP Debugging

I am trying to use the
LEP_Utilities_GetProjectInfo.vi  (included when you install microSDK) and
getting an error every time I call it. There are no inputs except an error
wire. Am I in the wrong scope? Do I need some type of reference to be established?
 Is there documentation regarding how to use this and the other  SDK
VI’s? The help sections are not much help.

 

The underlying reason that I am
trying to use this VI is to implement the instrumented TCP/IP debugging, if
there is a better reference than the porting guide for the debug
implementation, could you also point me that way.


 
0 Kudos
Message 1 of 4
(6,529 Views)

Hi Bill,

 

I have a couple questions from R&D:

1. What Version of LV are you using?

2. Microcontroller are you using ?
2. What exact errors are you getting ?
3. What compiler are you using ?
4. Do you get the same errors with the other utility VI's?

Regards,
Claire Reid
National Instruments
0 Kudos
Message 2 of 4
(6,508 Views)

Claire,

 

1. LabVIEW 8.6.1

2. I am porting to VxWorks 6.6 using a target xml file that I developed

2.  "Error 1055 occurred at Invoke Node in LEP_Utilities_GetProjectInfo.vi->Untitled 5"

       Possible Reason:  LabVIEW:  Object reference is invalid

3. WindRiver Workbench using GCC (the VI which produces this error is not being compiled)

4. Yes

 

Is there any sort of guide out there for setting up instrumented debugging? 

0 Kudos
Message 3 of 4
(6,464 Views)

The problem here is that LEP_Utilities_GetProjectInfo.vi is running in the wrong context. The missing context manifests itself in the form of error:

 

Error 1055 occurred at Invoke Node in LEP_Utilities_GetProjectInfo.vi

Possible reason(s):

LabVIEW:  Object reference is invalid. 

 

LEP_Utilities_GetProjectInfo.vi is meant to be a Plug-In VI, which means that it runs on the desktop in the context of the Embedded Project. So even if this VI is executable on the desktop, running it by itself outside a project will throw error 1055. Merely including in an embedded project under the My Computer as shown below will not make it work either.

 

Embedded Context.png

 

So where does this VI get its context from?

As a Plug-In VI, this VI should get invoked directly or indirectly by right-clicking the embedded target in your Project Explorer and choosing one of the Target actions (like Build, Run, Deploy etc). This invocation provides the VI with the right context. Please look at the Plug-In VIs for any of the example targets included with the LabVIEW Microprocessor SDK to see proper usage.

 

Hope this helps,

Jaidev Amrite 

Senior Product Manager
National Instruments
0 Kudos
Message 4 of 4
(6,442 Views)