03-03-2006 05:39 PM
03-06-2006 07:48 PM
Hi Khalid,
I just attempted and ran the Slave demon VI with LabVIEW RT 7.1 and a FP-2010 without generating the VI not executable error. What compact FieldPoint device are you using and version of LabVIEW Real Time?
Regards,
Steve
03-07-2006 02:19 AM
Thanks for looking into this Steve.
I am on LabVIEW 7.1.1 and have tried on cFP 2120 and 2020 -- I don't think this really matters.
In your test, did you try launching the Ethernet Slave Demon VI dynamically (from a VI not in the NI Modbus.llb)?
-Khalid
03-07-2006 10:43 AM
Kahlid,
I did not try dynamically launching the Slave Demon Vi dynamically yet but will try this and let you know the results. The key issue, that causes the 1003 error, is that LabVIEW on your host computer is a development system and the LabVIEW in the FieldPoint controller is a run-time version.
The primary behavior difference in this instance is that a run-time engine can not re-link VIs. If the dynamically launched VI has any sub-VIs, it needs to know where to find them. The run-time engine can not search for VIs (including vi.lib VIs) because they are not resident in the FieldPoint controller, and searching/relinking is a Development Environment capability, not a run-time capability.
I found a good forum post that has some good questions and answers that might answer some of your questions. I have linked this post below. The last several post have some good general tips
http://forums.ni.com/ni/board/message?board.id=170&message.id=118121&requireLogin=False
Hope this helps.
Regards,
Steve
03-13-2006 11:30 AM
Thanks Steve. Your response was very helpful.
Just wanted to add that the Timed-loop, in its internal implementation, calls lvalarms.vi (you won't see this as a sub VI on the diagram; but will see it under "This VI's sub VIs" menu item). And since this VI is not on the RT target we receive the error.
The solution is what you mentioned.
-Khalid
03-14-2006 06:40 PM
Thanks for the update Kahlid. You are correct about the lvalarms.vi and the cause of the error. I received the same error on my first attempt at Dynamically calling. After accounting for this, the error is corrected.
I'm glad the post helped out and good luck with the rest of your application.
Steve B.
09-17-2007 02:46 PM - edited 09-17-2007 02:46 PM
Message Edited by THANG NGUYEN on 09-17-2007 03:07 PM
09-17-2007 03:49 PM
09-18-2007 03:31 PM
09-19-2007 12:16 PM