control design & simulation

[esplu88]

Thanks for your help so far! Just to specify: I have changed my RT system from cRIO to a PC with LabVIEW RT OS.

So this is where I'm at at the moment:

PICTURE 1

This is where I select the model path. I understand that it has to be locally located on the RIO, but what I don't understand is how to select the path on the RIO.

PICTURE 2
The dll is listed under dependencies, but it's path is naturally an absolute Windows path (C:\etcetc).

PICTURE 3
I have placed the dll in the startup folder. dbohls told me that if the relative paths between the VI and the dll are the same on each platform, it would work. The problem is that if I 1) try to FTP the VI into the same folder as the dll - how do I run the FTP'd VI? and 2) LabVIEW won't let me set a relative path as shown in picture 1.

I've also attached the actual VIs. I wanna take dbohls tip about not using feedback nodes in consideration, but for now I just wanna get this thing running! 🙂

[esplu88]

These are the VI's for the post above.

[esplu88]

Use these VI's instead. 

[dbohls]

---

@esplu88 wrote:

Just to specify: I have changed my RT system from cRIO to a PC with LabVIEW RT OS.

---

So is this basically just a PC running Pharlap?

Please note, I never said anything about FTPing the VI over to the target. When you run the VI from the LabVIEW project, LabVIEW takes care of placing the VI on the target and running it for you. I do not know offhand where the VI will be placed, but you should be able to find it by looking around. I believe it may be in the system folder. My directions were to FTP your shared library to the target so that it is in the same relative location to the VI that calls it. The easiest thing to do is have the VI and the DLL in the same folder.

On your host, have things in the following location:

C:\Documents and Settings\Daniel\My Documents\Dropbox\MAS302\LabVIEW\Jada\Target.vi

C:\Documents and Settings\Daniel\My Documents\Dropbox\MAS302\LabVIEW\Jada\DFMA_tilt_test.dll

Find out where Target.vi gets placed when deployed on the target and place DFMA_tilt_test.dll in the same folder. This strategy worked for me in the past with both Phalap and VxWorks targets.