취소
다음에 대한 결과 표시 
다음에 대한 검색 
다음을 의미합니까? 

i/o not working when build executable

해결 완료!
솔루션으로 이동

I am trying to build an executable of a LabVIEW vi which communicates with a plant via a Festo EasyPort data acquisition device. The vi works fine and I have followed the steps in the NI 'Distributing Applications with the LabVIEW Application Builder' to build the executable. The executable itself opens and looks like it is running fine but it is not actually reading the inputs or sending the output signals. There are no error messages. Any ideas where i might have gone wrong? I've tried including all the i/o VIs in the 'Always Included' Source Files specification tab in application builder but it doesn't make any difference. I am using LabVIEW 2009.

I've attached the orginal VI and a zip file containing the project and application files

모두 다운로드
0 포인트
1/5 메시지
3,527 조회수

Hi,

 

can't open your example as I don't have these FESTO-Vis, but you already looked into these VIs? Perhaps, they use something like "Current VIs Path" to load any config files or so? This path differs if you use LabView or the executable...

 

christian


THINK G!! 😉
------------------------------------------------------------------------------------------------
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)
0 포인트
2/5 메시지
3,523 조회수

Thanks - good point. I had a look but they don't call any other files. I have attached the Festo vis this time if you want to have a look.

0 포인트
3/5 메시지
3,514 조회수
솔루션
주제 작성자 KiteM이(가) 승인함

As these VIs use a USB-Communication, perhaps it's something in a DLL file or so that doesn't work because of a different working path? Don't know...you tried to compile the test.vi in the Festo-Lib to look if this sample program will work?


THINK G!! 😉
------------------------------------------------------------------------------------------------
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)
0 포인트
4/5 메시지
3,508 조회수

Thanks again! I tried that and it worked fine, so I figured the problem was my original project file - I think I forgot to save the project after defining the build specification and before building. Made sure I did that this time and it seemed to work fine. Sorry for the dumb mistake but thanks for helping me work it out.

0 포인트
5/5 메시지
3,502 조회수