07-09-2013 10:00 PM
I used the .net api to create a definition file for the pxi target, but error 15550 appeared when i deploy the DEF. After compare with the correct DEF generated from VerStand, i found the RTDestination property in Model section is different, but i do not know how to change it. Any one knows?
Solved! Go to Solution.
07-09-2013 11:00 PM
Hello Nico,
- What version of the NI VeriStand .NET API are you using to create your System Definition file?
- Could you also post the two RTDestination strings so I may evaluate the issue.
- If deploying using the NI VeriStand environment, could you also post the Deployment Log. This should have the error message you are receiving.
07-10-2013 04:16 AM - edited 07-10-2013 04:23 AM
07-10-2013 05:54 PM
Hi Nico,
This is indeed in an issue in our .NET API. I've documented this as Corrective Action Request #416291. Attached below is a workaround to the problem.
07-11-2013 02:36 AM
Thanks, but i am not good at labview and do not know how to use the vi file, can you give me some steps to make it usefull ?
07-11-2013 04:44 PM
Hi Nico,
This workaround is using the same .NET API you are; therefore, you can recreate these calls in whatever environment you are using to programmatically create your system definition.
To explain the image from left-to-right:
- First block is calling the Model constructor and initializing it with the shown values.
- Next block, is down-casting the newly created Model object into a BaseNodeType. This is done by calling into a property of the Model object called BaseNodeType (ie. Model.BaseNodeType). This is simply the Model's base type. We need to do this to get access to low-level methods.
- The next two blocks are getting and setting the DLL Path XML-element in your system definition file.