It would be great if you could post images of key parts of the code too, for those of us who do not access to an install of labview (me!)
Generally you can do a few things to reduce the number of LUTs that your design uses. Check out page 59 of the user guide to see some hints:
Reduce the bit depth you use where possible
Be aware of FXP bit depth increasing as a result of some operations
Avoid arrays
Use SCTLs
Good point Pedro!
Bob_Schor wrote:Bert,
I'm "on the same page" with the other responders, except I haven't (yet) gotten around to incorporating my "re-use" libraries into VIPM (though it's high on my list of "things to do".
I'm not on that page per sé. I want my code to be in my project, not in user.lib or vi.lib. I haven't looked into VIPM for a while, but I think I'll only keep using it for external packages. For internal libraries, I'm more leaning towards external repo's. The difference is that when everything is under my project, everything is under one directory that I can copy (and commit) without worrying about missing parts. I'm not sure if VIPM has a way around this or not, but this would be a deal breaker for me. I might be very wrong (feel free to enlighten me)...
Please explain how your question is related to LabVIEW. Thanks.
Hi All,
I am trying load .net DLL, I have dropped .net constractor on the block diagram and tried to load a DLL it is giving me an error "an error occurred trying to load the assembly", I am using LV 2014 64bit.
Same DLL is working in other computers which has LV 2013 and LV 2016 32 bit.
I am suspecting these issues let me know if any one has clear idea on this:
1. LV 64bit is a problem.
2. OS 64 bit is a problem
3. I missed out any LabVIEW configuration.
Hello: I created a vi that consists of an LED that is greyed out or is not greyed out, using a property node. This works fine.
I create a sub-vi from this vi and it no longer works. I guess that my property nodes are not referencing the Boolean indicator of the calling VI.
How should this be done correctly?
The indicator vi that works is "indewenable.vi" and the calling program is "tester.vi".
Thanks for your help
Cliff
For those interested in this, I have made some progress.
Using the code below in the DLL, I have been able to get a printf(s) within the DLL to output text that is readable from a pipe within LabVIEW, which I can then put into a text window. Just using a slightly modified version of the Example Output.vi provided previously in the STDIO.zip.
It's a little bit clumsy right now having to use the extra code in the DLL. I'd prefer to be able to get all of that done outside of the DLL so that it doesn't need to be modified for LabVIEW purposes.
extern "C" __declspec(dllexport)int testReadParams(VOID )
{
HANDLE hStdout;
int fStdout;
int a;
hStdout = GetStdHandle(STD_OUTPUT_HANDLE);
fStdout = _open_osfhandle((intptr_t)hStdout, 0);
FILE* f = _fdopen(fStdout, "w");
_dup2(_fileno(f), _fileno(stdout));
a = 50 + 100;
printf("I wonder if this will work.\n ");
printf(" The answer is %d....", a);
fflush(stdout);
return(10);
}
That's precisely what l'm doing now. Each project has its own repository, and I have copies of my common routines within the project.
Bob Schor
I think it was the Input Cluster of the Bundle by Name that was the problem.
Despite your good advice, I haven't added the variant data to my queue yet - but I have managed to change the states to a TypeDef. As far as I can see, my data will always be passed from front-panel controls. I have learnt a lot from what you suggested - much easier in context. I shall have to see if I can go on a training course.
I've attached my VI, which I hope looks in better shape than before!
gregoryj and Minions, thank you very much for your inputs.
I tried more and realized the Enable Burst.vi did act as an immediate trigger. There were confusions earlier when I placed the vi at the beginning of my sequence, and it triggered periodically.
Hi Indula,
Since this is such an old version of LabVIEW the resources for being able to support this issue are going to be very scarce. I was however able to find the following link provides information regarding the correct plug-in setup procedure for each OS as well as some information regarding browser compatibility. See if the recommendations with within this doc help resolve your issue. The second link also provides some good information on how to properly set up a web server from within LabVIEW.
Why Do I Get a Plugin Error When Loading a Remote Front Panel?
Viewing and Controlling Front Panels Remotely with the Web Server
Hi Emil,
Can't seem to find any EOL to mess with..
Search for "\r\n" (string constant in \-code)…
Thank you GerdW!! Your expertise has been extraordinary!!
ATE-EGNE wrote:Here's what I have implemented:
It does not work correctly because you have connected to the lower "IQ" output instead of the upper "R" output of Q&R. Be careful there! Image may be NSFW.
Clik here to view.
(compare with my VI above)
Yes it' somenething like that, but the time of siulation has to e the same of the graf simukation. If you look at how it works, te grf it full in 1 segond, and I don't wanna do that!
Merci!
Please start a new thread, and provide all the necessary information, and see a doctor if you are having a medical issue.
Ace,
That template looks interesting.
Do you have an example of the TLB architecture showing some complexity? The base template makes some features a little difficult to follow (like registering events for the Event structure within an Event structure).
Came across this post looking for best practices for TDMS files. This is not really that discussion but was wondering if there is such a page or doc online?
This would probably be answered better on the LabVIEW Makerhub LINX forum .