10-01-2013 09:41 AM
Hello,
In my application i have communicated controller with the labview via serial communication with USB Serial cable (using VISA tool). My application works perfectly fine in development mode and in.exe(without installer)
Problem starts when I create the installer the communication starts malfunctioning. The communication behaviour is unpredictable. I have included different additional installer associated with VISA while creating my installer, the attached image shows it. Tell me if I am missing any additional installer. Some of the thread says that I should be having NI-Serial which is actually not listed in my case in the additional installer list.
The problem is that my application on target device (which is not having labview) is not taking certain commands. Guide me with this please. Thank you
10-01-2013 10:47 PM
Guys.... I would really appreciate help on this ..
10-02-2013 01:30 AM - edited 10-02-2013 01:33 AM
hi
can you connect to application in debug mode and check whats going on inside? you dont need labview on target pc.
http://forums.ni.com/t5/LabVIEW/how-to-run-labview-in-debug-mode/td-p/74636
On your exe projcet you need to enable debug mode and wait for debuger to start, then you have to open labview on your pc and Operate>Debug Application>put ip and connect
best regards
10-02-2013 01:44 AM
I am not sure but i think if you are using a controller ... Don't you think you need to generate C code from LabVIEW code ..... when you go to File<<VI Properties ... you have option there for generating code for ARM andother controllers..
10-02-2013 01:45 AM
what?
10-02-2013 07:17 AM
Well....a littel doubt in my mind. I developed all the VIs on labview 2011, but by mistake I opened it in labview 2012 and made installer and everything on labview 2012 only. Does it have to do anything with this?
10-02-2013 11:20 AM
@Saumil wrote:
Well....a littel doubt in my mind. I developed all the VIs on labview 2011, but by mistake I opened it in labview 2012 and made installer and everything on labview 2012 only. Does it have to do anything with this?
In my experience, there is little risk in updating your VIs to a newer version; it's when you go backwards that you begin to have issues. That being said, maybe There are some options that are different between the two LabVIEW versions?
I know it's too late for this project, but have several versions of LabVIEW on the same (Windows 7) PC, and I've opened up projects in the wrong version even though I selected the project from the --> menu from the correct LabVIEW version on the Start Menu. It seems that the shortcut will open in the last version of LabVIEW that you had open, even if you did what I did above. Now I explicitly open the correct LabVIEW version and select the project from inside LabVIEW instead.
10-02-2013 11:17 PM
In my experience, there is little risk in updating your VIs to a newer version;
How do i convert my VIs back into 2011 version from 2012?
10-02-2013 11:27 PM
File>>Save for Previous Version
Also refer to:
KnowledgeBase 203EDCXC: Can I Save VIs in My Current LabVIEW Version for Use in a Previous Version?
http://digital.ni.com/public.nsf/allkb/DA470EB199497F4086256931007050C0
A quick search on NI.com or Google will often save you time.
Regards,
10-03-2013 12:32 AM
Put one error indicator and see what is going on.