BrokenArrow

QUOTE (crelf @ Jul 15 2008, 05:52 PM) Isn't "crelf" short for Carriage Return Line Feed?

QUOTE (crelf @ Jul 14 2008, 08:42 PM) The LAVA carriage return? have at it! :laugh:

In the process of trying out the custom listbox symbols Invoke Node, I worked up the attached "File Lister". I recalled a similar tangent on this thread. Some nice additions would be a working drag-n-drop, an indicator (and a note on the file) showing the total KB of the selected files, an Insert Comment, and run file or view file utility, etc. Not rocket science, but no time now... any takers? You'll need the two jpg's to make the app look decent - the stock listbox symbols are too plain looking.

QUOTE (crelf @ Jun 13 2008, 03:41 PM) Yeah exactly, a guy with a Simpsons avatar claims to inadvertently bring up the Simpsons. :laugh: BrokenArrow sayz... Lets talk about Golden Retrievers! ... BTW crelf, whose that guy in your avatar?.... it cracks me up!

QUOTE (hooovahh @ Jun 13 2008, 11:37 AM) Hey... it's the Lounge! Anything goes. The Simpsons are always welcome!

QUOTE (PaulG. @ Jun 12 2008, 04:38 PM) "Everybody's stupid but me" - Homer Simpson (after deciding that going to church is a waste of time)

QUOTE (Siconi @ Jun 12 2008, 04:07 AM) You won't find the driver "in LV" - the driver is not an NI product. You'll find the driver on the Advantech site or on the CD-ROM that shipped with your module(s). You will install the drivers in the user pallete and then they'll show up in LV. I still say you're better off just writing commands to VISA.... Edit: ned is correct, they don't have a seamless driver for ADAM products. All the more reason to learn to fish.

Enough LAVA to be Dangerous

QUOTE (ned @ Jun 10 2008, 09:43 AM) That is, by a wide margin, the easiest and most highly recommended way to go about using your ADAM-4000 device. Are you able to communicate with your device in Hyperterminal? A manual is http://www.bb-elec.com/bb-elec/literature/manuals/Advantech/ADAM-4000.pdf' rel='nofollow' target="_blank">here. Richard

QUOTE (neB @ Jun 9 2008, 05:57 PM) Homework Hawkers don't want to do things the FIRST time. I will bet $5 he doesn't check back in. Richard

QUOTE (georgekm @ Jun 6 2008, 11:05 AM) I'm not sure what you mean by "...in the same VI". Do you mean, in one VI? For example (and to jgcode's point), using DAQmx, you can make one Multi-Function VI that does ALL of your Digital & Analog reads and writes. Of course, this one VI will contain several polymorphic sub VI's, but these ship with LabVIEW, your one VI (i.e. same VI) just makes calls to the other VI's. Do you need an example? We also need to know what interface (driver) you are using: DAQmx, NI-DAQ (i.e. Traditional DAQ), or third party. Richard

QUOTE (jdunham @ Jun 5 2008, 12:54 PM) I wondered where that was. I submitted my long time request to have Wire Labels that snap to wires! :thumbup:

QUOTE (aa9310 @ Jun 3 2008, 03:18 AM) You can't do much better than LabVIEW For Everyone, which is a classic. Maybe the author himself will chime in on that one. Books can only go so far. To take it to the next level, you'll need training, which can be done on the internet. The following website is administered by yet another proven LabVIEW community hero. You can even look at a few things for free... http://www.labviewmastery.com/ You say you want to study advanced labVIEW technology, but, do you have the basics down first? It is very important to build a solid foundation first. Best of luck to you. Richard

QUOTE (jdunham @ Jun 2 2008, 10:53 PM) That's good info, I didn't know that, thanks. I know about that INI font deal, in fact it's all over the NI forums and I was on one of those threads years ago. However, my issue back then had to do with the fact that the EXE did not differentiate between a size 13 and size 14 Application Font, and would make them all 13, and we're talking about being on the same computer, same OPS. On a side note, I recently built an application in 8.5 which had 13 and 14 size fonts, and it did not exhibit this problem, and I didn't change the INI, so maybe it's gotten smarter. I'll try the INI deal on our one Vista computer and see it fixes my array in Dev mode. What is odd is how it (Vista) chose a different font for the Integer and String arrays, even though they were both Application 14. Richard

QUOTE (jdunham @ Jun 2 2008, 05:50 PM) Your point is in relation to EXE's. I don't think in Dev mode, we're talking about the same thing. NI has stated specifically "you might notice cosmetic issues, such as overlapping or truncated text strings". This is documented in the KnowledgeBase article. See.. http://forums.ni.com/ni/board/message?boar...d=33221#M257736

QUOTE (rolfk @ May 27 2008, 07:32 PM) OK thanks Rolf... I didn't get an email notification that this thread had a response (.. ? ..) I have a friend (no really) that will be using Advantech on a product and they were wondering about configuration. I've never used non-NI PCI cards but I've used non-NI eveything else. Richard

QUOTE (crelf @ May 31 2008, 05:15 PM) Exactly! But to their credit (NI), and your point, an XP "system" is not a Vista "system" so this kind of thing is bound to happen when transporting system fonts. I've just never seen anything quite as bad as I encountered as shown in the attached picture, where the numeric array no longer lines up with the integer array, causing me to think I was missing the bottom element. -Richard

QUOTE (Amelia @ May 5 2008, 12:52 PM) I found this on NI in regards to an issue I was having when switching between XP and Vista computers... Because the default fonts on Windows Vista are different than the default fonts on previous versions of Windows, you might notice cosmetic issues, such as overlapping or truncated text strings, in VIs and LabVIEW dialog boxes. To correct this problem, change the theme of the operating system to Windows Classic in the Theme Settings dialog box and then restart LabVIEW. Select Start»Control Panel»Appearance and Personalization and click Change the theme to display the Theme Settings dialog box. -Richard

Has anyone used Advantech PCI cards with success? (not talking about the popular ADAM series, rather, the PCI cards, which appear to be a good value). If anyone has used these, how much use can you get from MAX, or does it all have to be configured off-line or inside a VI? Thanks, Richard

Just a note that if you use your own code and normal VISA to talk to some Agilent devices, as I do, you have to pay close attention to the com setup. The results are worth it because I've found the Agilent drivers to be clunky. -Richard

QUOTE (george seifert @ May 19 2008, 04:27 PM) But with some strange timing requirement built in. If you select a cell then click too fast the second time, it'll think it's a double-click and not let you in. You have to click and wait about one second. This isn't very intuitive IMO, and I can see your lament, George.

QUOTE (george seifert @ May 19 2008, 12:40 PM) Triple-Clicking is a known LabVIEW practice, such as when you want to select an entire string (or a a string with a space in it), or to select an entire wire plus all of its branches. However, in your scenario, I'm not sure why Triple-Clicking is necessary. Maybe the first click is simply shifting the focus and the other two clicks are selecting it. If you can use a 2-D array rather than a list box, you'd have a lot more control over each "cell", such as, you'd be able to show the increment/decrement, and there's more property nodes to play with. Richard

QUOTE (george seifert @ May 19 2008, 10:09 AM) For me, it is reliably letting me change values upon a Triple-Click. It never allowed me to edit upon one click. Richard

Not sure if this is the category to put this in, but here's some Nixie Tube controls/indicators. Click on the bottom control with left or right mouse button. The top two are self-explanotory. Saved as version 8.0. Richard

QUOTE (rolfk @ May 16 2008, 02:54 AM) A company (who will remain nameless), has been in contact with me (more than once) to write some "drivers" for them, but in actuality, the job entailes working on the phone putting out fires for people who are struggling with interfacing LabVIEW to their products. They continually run a job ad that reads something like: provide customer solutions for (blah blah blah) must have excellent communication skills, Help Desk experience is desired, LabVIEW is a plus." This company's president told me personally that he doesn't "like" LabVIEW. When I probed further, I found his opinion was formed from bad example code from the mid 90's and a few of his engineers downloading the eval version and giving up in a few hours. Now THERE is your example of bad SDK's, or turd balls. Richard