Khalid

NI's Application Note # 168 on LabVIEW Performance and Memory Management is a good one too:

http://zone.ni.com/devzone/conceptd.nsf/we...6256A37005541D3

-Khalid

What kind of a security system are we talking about here? A building security system? an airport security system? a prison??

Please provide as many details as you can... without breaching the secuirty

-Khalid

See if the attached VI works for you.

-Khalid

Download File:post-311-1134022089.vi

Hi Michael,

With LabVIEW 8.0 supporting the mouse wheel for such controls, I guess there's not much point in us developing any tools for this anymore.

Regards,

-Khalid

Hi Regis,

Have you tried IID3.UINSTx? Where x is the Attribute - 1. Also, "UNIST" may have to be replaced with whatever datatype that particular Attribute happens to be.

I haven't tried the above -- it's just what I gathered from the documentation; maybe worth a try.

This is not my final answer

-Khalid

3) The shape is significant.

Is it the physical size of the Array Size function? Not sure how this is ironic, but hey, it's better than Jim's spelling

-Khalid

I am assuming you're using DataSocket Read VIs. So, to write to the OPC Server, you will use the DataSocket Write function (or VI if using the legacy version).

-Khalid

PS: You attached a VI; doesn't seem to do much. What was the purpose?

Sorry about that: just realized that you're using front-panel datasocket. So to write this way, you will want to make a "Publish" data-connection from your Control. Or if it's an Indicator then "Publish and Subscribe."

Unless it's a real simple project, you will have more flexibility using the DataSocket VIs as opposed (or, in addition to) to front-panel datasocket only.

-Khalid

You may find the following useful:

http://zone.ni.com/devzone/devzoneweb.nsf/...62568FF00696FBE

http://zone.ni.com/devzone/devzoneweb.nsf/...62569060074F0CB

Regards,

-Khalid

PS: I apologize for redirecting you to these tutorials rather than helping you directly -- I feel these give good background info' to what you're trying to do.

See the following KnowledgeBase article:

http://digital.ni.com/public.nsf/allkb/709...6256DD4004F3DE6

If the above link doesn't work, search NI's website for "3337DOV4"

Regards,

-Khalid

As you probably know, there's a Fuzzy Logic Toolkit for LabVIEW. And there are examples for implementing Neural Networks in LabVIEW (on NI's website). But nothing for Neuro-Fuzzy.. as far as I can tell.

What exactly is the theory behind Neuro-Fuzzy? Are the Fuzzy rules modified (dynamically?) using a Neural Net?? My understanding of this theory is a little fuzzy . If you can point to a good, authoritative, resource on this, may be we can come up with ideas to implement it in LabVIEW.

Regards,

-Khalid

Hmm, I wonder how many NI LabVIEW developers are "Certified".

As of last year at least, NI developers were not allowed to take the NI Certification exams. Not sure what the rationale behind it was/is.

-Khalid

The file has gone. :headbang: Any other ftp resources available?

Otherwise I'll have to wait for my SSP update in November (yes, that late in Germany..). What a pity.

Thomas

There's a readme in there which says the following:

LabVIEW 8 is no longer available at this location.

To obtain the file please visit:

http://digital.ni.com/demo.nsf/websearch/1...&node=157200_US

-Khalid

This is a minor annoyance but I'm reminded of it every time I use the context help to look at a connector pane that has optional terminals.

I do wish their name showed up in some manner rather than being entirely hidden.

I may be missing something, but doesn't the first button at the bottom-left corner of the context-help window show optional terminals?

-Khalid

Hi Neville, and Lavezza,

Thank you for sharing the little utilities. They'll definitely come in handy.

I quickly modified Lavezza's VI to either clear breakpoints from all VIs in memory or from just the one it was invoked from. NOTE that it doesn't save the VI(s) so the breakpoints will come back when the VI(s) are reloaded.

Thank you,

-Khalid

Download File:post-311-1129734474.vi

... Also, if you're in a multi-developer team then you could be clearing breakpoints put in by other coders that you're not even aware of. ...

I agree we have to be careful. However, I am not sure checking-in code with breakpoints is a good practice -- especially on multi-developer projects. IMHO, the scope of debugging should be local to each developer, and thus only the individual's VIs should have the breakpoints she wants (clearing them before checking-in). Imagine hitting breakpoints in places we least expect (and care!). It's like when people check-in broken VIs on a multi-developer project -- well not as bad, but still intrusive. But I guess that's a topic for another discussion

Regards,

-Khalid

National Instruments recommends that you save VIs as individual files,

organized in directories, especially if multiple developers are working on

the same project.

LabVIEW 7.x User Manual, Page 7-12.

If you're stuck with LLBs in an ongoing project, here's a trick you can use: in your file structure, create a folder (directory) to represent the LLB -- name it exactly the same as the LLB, for instance, "myLibrary.llb" including the 'dot llb' part. And then put the VIs from the original LLB under this folder. (You may use the Library Manager to do this... )

This way, you are now working with individual VIs (great for source-code control, etc.), and at the same time your rest of the system isn't broken because the paths to these VIs are still the same as before.

-Khalid

It will be nice to have a "Clear All Breakpoints" feature (from the menu + shortcut). Just like MS Visual Studio, for instance:

http://msdn.microsoft.com/library/default....breakpoints.asp

As of now (7.1.1), we have to do a "Find" on Breakpoints and manually clear them one-by-one.

-Khalid

I don't think I'd use a "Clear All Breakpoints" function - I use breakpoints for a reason (debugging code), and I'd like all my co-developers to have to clear them manually after they've assesed that the code has been properly debugged...

I beg to differ. Case in point: we're happily debugging and adding breakpoints left-n-right as we go. We finally find and fix the problem. At this stage, I shouldn't have to go to each breakpoint -- some of which I don't even remember where I put them (may be in a false case which doesn't get exercised under normal operation, for instance) and clear them manually.

-Khalid

It will be nice to have a "Clear All Breakpoints" feature (from the menu). Just like MS Visual Studio, for instance.

-Khalid

It's Friday.. so here's something to kill those afternoon hours..

http://news.bbc.co.uk/1/shared/spl/hi/pop_...fest/html/1.stm

-Khalid

Yes you can [merge]. Take a look at lvdiff, which allows side by side comparisons of VI differences.

Hi Jim,

I use LVDiff -- it only facilitates in comparing the two VIs by highlighting the differences. We cannot merge changes from one VI into another, like we can with text files (C/C++, for instance). Merging VIs automatically would be quite involved.

I like the check-in/check-out paradigm because my team mate then knows I am working on it. And he can either wait for me, or come talk to me. In update/commit, I am guessing we would end up manually merging changes from one into another.

I guess it all boils down to personal preference.. and/or company policy.

Regards,

-Khalid

... Also, since CVS and Subversion use a concurrent access model (update/commit) rather than a synchronous access model (check-out/check-in), I am not sure that I would like limiting myself to the latter by going through the SCC API.

How, in your opinion, is "update/commit" better than "check-in/check-out"? We can't merge VI diagrams..

Just trying to understand as I have always used the latter (with Perforce).

Thank you,

-Khalid

Lookup Shift Registers in Online Help. You will need these to remember values from one iteration to the next.

-Khalid

PS: Sorry Michael, I know talk is cheap.. but time is not

On the Expres pallette, under Signal Manipulation, you will find an Express block called 'Convert from Dynamic Data.' That should convert the LVM Signals (output from the 'Read LVM File' block) into an array of doubles.

A shortcut is to create an array of DBL indicators, wire the Signals output form the 'Read LVM File' to this. LabVIEW will then auto-insert the above conversion block for you.

Hope this helps,

-Khalid

The LabVIEW-DSC module has "HMI Wizards" which generates diagrams (using scripting) based on what the user wants to accomplish. Obviously the VIs are protected, but you may get some ideas by looking at the HMI Wizards' interfaces.

-Khalid