jcarmody

LabVIEW is so not self-documenting. I know I had a reason for using the time and IP address in my VI.

I've taken to using Globals wherever I need something in multiple processes. When the values need to be configurable (which tests to run, test limits), In my JKI State Machine I read an ini file to get the values then write them to the Globals (and to the test data, to keep folks honest). If the value doesn't need to be flexible I set the default value of the Global. There's a good illustration here.

My only comment is that the Regex doesn't need the pipe. I don't understand why Match Pattern doesn't work, but it definitely doesn't.

A Regex would be slower, I would ignore the error (if using Match Regular Expression) and the \w will include non-hex characters.

I've needed one and have seen requests before. I've done some crazy things in my quest... The .txt file is the VB Script (was .vbs) called in the VI (hidden in Diagram Disable structure). Generate GUID.vi guid3.txt

I often use Search and Replace String to get null characters out of strings before applying a Regular Expression.

This brings back memories of a project I worked on 10-15 years ago. We bought a vision system solution that was to characterize the performance of an analog pressure gauge and calculate a custom non-linear dial. It appeared that their curve-fit forced the path to go through each measured point and the dials looked horrible - graduation marks bunched together in some points, spread way out in others. There was some inaccuracy in the measurements so the gauges weren't accurate. I changed to a polynomial fit and Bob was my uncle.

Phew... Wait. I still can't duplicate the bug.

I knew this sounded familiar - http://forums.ni.com/t5/LabVIEW/String-constants-resized-Bug/td-p/1100741 Now, finding the solution...

Thank you for the kind word and bug report. I've noticed the String constant behavior but have blamed it on 2011. I didn't experience before 2011 so it's definitely associated with the new version. CaseSelect examines every String constant when renaming cases; perhaps something is amiss in that operation. I'll have to try working on a VI without using it to see if it's in my plugin. I can't duplicate this with your attachment. Can you list the steps required to cause this issue?

I'm out.

Here's a note I kept from Zen and the Art of Motorcycle Maintenance (I've added some of my own ideas to it). The Hypothesis (1) and Expirement (1) sections are to be repeated as required. I've had this in my Emacs folder forever, and it has helped a few times. zen experimenting . begin - . Statement of the problem . Early observations . Hypothesis (1) - . Experiment (1) designed to test this hypothesis . Equipment . Procedure . Predicted result of the experiment . Observed result of the experiment . Conclusion . Recommendations . Conclusion [/CODE] Jim

Here's one that I wrote with a different approach. What about the project are you trying to read? What have you tried so far?

I'm working on an ESS ATE that will address and monitor 30 CAN devices and control an environmental chamber. I'm beginning to implement LVOOP to abstract the CAN and oven communications.

[edit] Are you running the version from the post above yours, or did you download it from the download page?[/edit] I can't tell what's happening yet. I thought it might be a required something that I have in my development environment and you don't, but I can't find anything that isn't called from the plugin's directory. Would you try running my Abort.vi when you get stuck in the endless loop and let me know which VIs it says are running? The Abort.vi is often useful to stop this kind of loop without ditching your entire process. You may be the only one to try the Event Structure feature or you may have a unique situation.

I love that book. I was young enough when I first read it that I was half-way through before I realized it was a philosophical treatise. What about it made you consider dropping out of college?

Your experience sounds like something I read earlier this week.

I'm at the point where I'm ready to begin trying it. I'm finishing an application where I know I could have used a better messaging architecture. My application has five CAN channels, each of which is monitored by a re-entrant VI. This VI communicates the messages I'm interested in back to the main VI via User Events.I read all of these wonderful threads and realize the neither of the "A"s in LAVA apply to me...

It's amusing, albeit a bit sad, when a teen-ager acts this way. Wait 'till he grows and...

You need to do all the SQL yourself with SAPHIR's kit. ShaunR's kit has high-level VIs that work like the NI DB kit and low-level stuff for, well, low-level stuff.

I've been happy using http://www.xp-dev.com/ for the past few years for my private projects.

There's a recent conversation on NI's forum, here. I passed mine last year, but it had a bunch of questions on topics I've only read about in the forums so I'd say it will take a lot of preparation. It's got the same format as the CLAD. Good luck. Jim

You still may be. All we've determined is that this issue is not a symptom.

You're not alone; I've seen it.

1. Do you use LabVIEW Snippets? Yes, for posting to this (and NIs) forum 2. How often do you create new snippets? A few times a week 3. How do you organize your snippets? I don't - the Code Capture Tool puts them in a folder and puts the path onto my clipboard. I never browse to them so I never think about them after posting them. Some things you didn't ask: I don't use the native LabVIEW tool I use a quick-drop plugin to open snippets from better browsers than IE The Code Capture Tool will back-save a snippet, so I wrote a RCF plugin to extract a snippet in LV 8.2 and up