orko

QUOTE (Red @ Mar 22 2008, 08:16 AM)

It took all of the 4 hours to complete.

That was my experience as well, though my approach was different. I documented as I went, and was *minutes* away from having a broken arrow when the 4 hours was over.

Good job, it looks like you are well on your way to becoming a CLD. Let us know how it turned out! :thumbup:

QUOTE (BrokenArrow @ Mar 21 2008, 12:17 PM)

If you can convert the analog signal to digital (and that may not even be necessary depending on the level), you can wire the signal to the handshake line (CTS) and use VISA Enable Event and VISA Wait on Event to monitor the CTS line.

Hey, that's a good idea! I'll be sure to http://forums.lavag.org/www.jott.com' target="_blank">Jott it down so I can remember to use this next time. Thanks!

Welcome, not-so-new member

QUOTE (njg @ Mar 21 2008, 09:02 AM)

I couldn't agree more - simplicity! Also, be sure you're comfortable using the latest version of LabVIEW starting with a default configuration. It's ok to spend a minute changing several options, but you'll certainly want to know exactly what to change and how to change it ahead of time. Finally, be sure to read the entire set of instructions before beginning.

It's definitely worth the time before-hand to install a fresh LabVIEW somewhere and get familiar with the way it "handles". I remember that I hadn't seen a fresh LabVIEW install for a while before my CLD exam, so it kind of jarred me for a bit when I started dropping big ole icons on the block diagram and my undo history only went back 9 events... then there is the pallete itself that I didn't realize how much I had customized on my work PC.

The above posts are correct. TIME is the biggest factor on this exam. Simple, simple, simple. Simple Descriptions and icons, simple use of subVIs and typedefs (if needed), simple front panel. There is no point in making a fancy app that doesn't pass.

I like it! No to remember to look it up when I get back to the office...

And in some Australian courtroom, there is a scared little misunderstood robot screaming, "he made me do it! Do not disassemble!!"

Johnny v.22?

QUOTE (gosor @ Mar 21 2008, 03:20 AM)

It IS exactly the point. I can't believe i am the only one to think it is some of most tedious things to do with LV.

Nope, not the only one. This has been discussed a fair amount already in the forums. Oh, and yes... I'm excited that there is a "rustling in the wind" that may indicate we could see something like this coming soon.

QUOTE (crelf @ Mar 20 2008, 01:38 PM)

I'd like to nominate http://forums.lavag.org/Jim-Kring-m17.html' target="_blank">Jim Kring for a (IMHO long overdue) TALM award.

What?!? He hasn't been nominated for this yet?? For shame!

Jim has been a considerable help to many people (like me) and deserves to be recognized for his tireless efforts. And he now owes me two beers...

QUOTE(crelf @ Feb 22 2008, 09:48 AM)

http://www.cyberguys.com/templates/SearchDetail.asp?productID=18458' target="_blank">Prevent screen savers using hardware - even if your IT dept won't let you disable the screen saver...

One of the original hardware approaches was "let your mouse dangle from the side of the table and aim a fan at it"

I suppose you could duct-tape a real mouse to it...you would just have to search for it when you returned to your desk.

I'm used to seeing cheap ones like This for $12-$13 USD

As a side note, I never thought of the word origin of "rack" possibly being from the German "rake" (or vice versa). If that's the case, the shape of a typical cable rack does look like an upturned leaf rake...

QUOTE(rolfk @ Feb 22 2008, 02:03 AM)

Cool down orko

Initiating cool down.... hmm... its not working, she keeps staring at me

QUOTE(rolfk @ Feb 22 2008, 02:03 AM)

And we all appreciate it! Mad Props, Irene! :thumbup:

QUOTE(rolfk @ Feb 22 2008, 03:23 AM)

NI Spy in fact simply intercepts all VISA API calls and monitors them.

Oops. Thanks for the correction, Rolf. This isn't the first time I've slipped up and equated VISA with LabVIEW. Bad orko...

QUOTE(DarkAcMe @ Feb 21 2008, 09:53 AM)

LabView: An exception occurred within the externel code called by a Call Library Fuction Node. This might have

corrupted LabView's memory.

I think my memory is corrupted too! Look at those eyes!

A very exceptional looking woman.

PS. Irene_he is most likely on the right track, so I have nothing to add. I just couldn't help myself...

I'm still trying to figure out why anyone would ever want to revert back to buggy ole LV8.0 hehe...

I've commented in the past about the weird autosizing behavior of typedef cluster constants when their data structure changes.

In a typedef cluster, when adding/deleting an element, I guess I would be happy with something like this:

If I have autosizing turned off, then the content changes, but the border remains unchanged. IOW, the cluster border remains static and the changed elements inside retain whatever I set them to be before adding/deleting (this includes their properties such as labels and size/position)

If I have autosizing turned on, then the typedef border resizes to accomodate the change, but the content remains unchanged except for the new additions/deletions.

If we're adding a new element to a typedef then it really doesn't matter to me what it looks like initially, it can just be the default size with no label as it is now. As long as the other elements that were set all pretty-like before remain unchanged.

(BTW, I'm not crazy about hiding the constant data with an icon, but that's just my :2cents: )

QUOTE(chrisdavis @ Aug 20 2006, 05:53 PM)

Why reinvent the wheel, in this kind of case, I usually use http://www.sysinternals.com/utilities/portmon.html' target="_blank">Portmon, from sysinternals.com.

Or use that forgotten little icon in your National Instruments start menu: NI Spy (only works if your COMM port programs are written in LV)

I like portmon when I have it available, but there are times on the test floor where I don't have internet and forgot my USB stick in my other super-hero outfit.

QUOTE(crelf @ Feb 15 2008, 11:26 AM)

My opinion is that it should be one of the most comfortable seats in the house...

That's hilarious...I actually used this exact picture on a magazine project for college. I believe the main caption read, "Working too hard? -- Employees speak out about lack of breaks" or something to that effect.

Thanks for making me smile again, Crelf It's nice to come up for air once and a while.

QUOTE(Justin Goeres @ Dec 17 2007, 04:13 PM)

Side Note: I wish the Pick Line function would take negative line numbers, where e.g. -1 would give you the last line of the input string, -2 would give the second-to-last, etc.

This functionality would be very benificial. Other scripting languages (Perl) handle substrings in this manner, where a negative number in the index switches to start at the end of the string. Of course, you can get the same by reversing the string, then reversing again after the substring is extracted, but a negative number would be oh so nice to use again...

QUOTE(BrokenArrow @ Dec 4 2007, 12:56 PM)

Both of those are good ideas for firing an event based on a tab being present, but one thing persists, you still can't type a Tab into a string control (set to show '\' Codes Display) and see the Tab (\t) it in the control - LabVIEW will pop out of the control when Tab is hit.

Richard

This is odd...

I understood (I thought) what Yen was talking about in his post, and went to work putting together a small example. When it was done however, it doesn't work all the time.

http://lavag.org/old_files/post-3266-1196805366.vi'>Download File:post-3266-1196805366.vi (LV8.5)

Notice that it *kind of* works if you play with it, but then it stops working. Not sure what is causing this behavior yet.

QUOTE(BrokenArrow @ Dec 4 2007, 12:56 PM)

Both of those are good ideas for firing an event based on a tab being present, but one thing persists, you still can't type a Tab into a string control (set to show '\' Codes Display) and see the Tab (\t) it in the control - LabVIEW will pop out of the control when Tab is hit.

Richard

This is odd...

I understood (I thought) what Yen was talking about in his post, and went to work putting together a small example. When it was done however, it doesn't work all the time.

http://lavag.org/old_files/post-3266-1196805366.vi'>Download File:post-3266-1196805366.vi (LV8.5)

Notice that it *kind of* works if you play with it, but then it stops working. Not sure what is causing this behavior yet.

QUOTE(TG @ Dec 3 2007, 08:06 PM)

This circuit is contained within a Queues state machine loop. The loop keeps the file reference between iterations.

Herin lies the problem. The loop is not keeping the file reference between iterations. You just don't know yet where it is being lost

Probe your file reference on the inside of your QSM, and put a breakpoint at the probe. You should be able to step through each iteration and see which one the file reference is going away at.

Without seeing your QSM code, it is just guessing on my part, but my guess is an unwired shift register in one of your cases (timeout case? default case?) on the wire that holds the fileref. Let us know what you find.

QUOTE(Tomi Maila @ Nov 20 2007, 03:46 AM)

When wiring error into a loop, the most common use case is to have a shift register to pass the error from iteration to iteration. Hence shift registers should be the default terminal type for error clusters when wired to a loop.

EDIT: The same should apply for all reference types.

I can't count how many times I've pointed out a tunneled error cluster in a co-worker's code and each time it's the same response -- "Ack! I forgot about that..."

The majority of times, a shift register is definitely the right choice, so I agree totally it should be the default.

PS. Sometimes I am the co-worker :laugh:

Talking with the client, it looks like they are more comfortable with a remote application that is controlling the cRIO VI via TCP. There goes that idea (for now) until I get more time to test this out fully that is.

Thanks again for the help. I'm sure I'll be referring back to this thread in the future!

-:No tabs

Hmm... there aren't any events in the existing app currently, but I was planning on bringing them in to the picture later...QUOTE(sachsm @ Oct 18 2007, 04:55 AM)

That is definitely something to consider. So basically build an app for the PC that sends values to the cRIO shared variables, kind of like a dummy front panel?

Hi there,

I know I've been gone for a while, but now I'm settling into the new projects here and should be more available

I had a question about deplying cRIO applications on the network using the built-in web publishing tool. I have an application that currently runs on a cRIO (9102) that I would like to start controling with PCs on the network. One idea is to scrap the UI and develop a new one for a Windows target that uses TCP communications to pass commands to/from the cRIO. But if I'm particularly fond of the UI I have already, what would be the harm in just publishing the front panel to the network and accessing it via a browser?

Does anyone have any advice as to what some of the caveats/concerns would be in doing this (or perhaps there are no significant caveats to using the existing web publishing tool?)

Thanks!