Jump to content

crelf

Members
  • Posts

    5,759
  • Joined

  • Last visited

  • Days Won

    55

Everything posted by crelf

  1. Re-test?!? There is no re-test for the CLA (yet) - you just get a new certificate and a "nothing significant has changed since you took the test" letter. :question: Does that suggest that ExpressVI development is insignificant?
  2. :question: John - why is it password protected? Is it something anyone will ever use purely privately (ie: never use it in relation to thier work, only for play)? I don't see any reason for the password protection at all...
  3. G'Day Peter and welcome to LAVA - it's great to have you here! For those who don't know Peter, he is the founder and president of Bloomy Controls and is a published LabVIEW author - a great resource for us here at LAVA I very very rarely use them - usually when I'm trying to tech someone else a technique and need to fill in the blanks quickly. I never use them in production code. I tired to once (a long time ago, and maybe things have improved since then, but I haven't had a need to go back since), but needed to modify one of them a little, so I opened one of them up and was spooked by the horribly inefficient and amaturish code inside - it was quicker (and safer) to code what I was doing from scratch.
  4. Glad to hear that you've got it working, but there's nothing obvious in your code that calls networked files - unless it's hiding in a hidden frame or a subVI. If you'd like us to look into the problem further, feel free to post your code here.
  5. Here here! :thumbup: Maybe 180 degrees out of phase from NI-Week, but somewhere warm so us Northeners can have some winter respite... Whilst I share your musings, it doesn't apply to my project - I've got a very small window to get this system installed in, so every half a day counts (I've also got an unmovable task to complete in the first couple of weeks of September). I work in a great environment where the decision to cancel of my NI-Week trip actually came down to me - and as much as it hurt, I know I made the right decision.
  6. excuse the spelling: sawardee korp! (spent a month in Thailand in 2001 - some of the best food I've had in my life!)
  7. Harsh! (...but fair )
  8. Gee - who's been looking up Aussie terms on the internet?!? Indeed, I am deadset. In fact, I'm also fair dinkum, and not telling Furphys...
  9. Contrary to popular belief, I have not sold my soul to NI... ...yet
  10. You beat me to it
  11. Just thought I'd let you gents know: I've had some horrific project issues that, whilst a pain-in-the-arse on their own, mean that I'm not going to be able to make it to NI-Week. As you can probably imagine, I'm not happy about it, but it's something that just has to be done.
  12. They are voices from the future... (neither 8.20 nor native GOOP have been announced yet)
  13. Good on ya Crystal - you're more than welcome!
  14. Oops
  15. Welcome xtaldaz - it's great to see NI staff joining in so they can come along to the LAVA / OpenG BBQ during NI-week :thumbup:
  16. Because your timer is in a whiloe loop, I assume that it's looping on whether a target time has been reached? Put a button on the front panel and "OR" it with the timer. It'd be a lot easier to help if you post either your code or a screenshot...
  17. Don't be sorry for asking this question - it's very common for people starting out using LabVIEW. The concept you need to understand is "dataflow". Each node on your block diagram will begin executing once there is data at all its inputs - for example, if you have wires connected from the output of one subVI to the input of another subVI, the second one cannot run until the first one has completed and put its output data on the wire. To solve your problem: you have two operations (subVIs) in on frame and want to force some sort of timing control over them: put a "wait" function between them. I don't usually recommend express VIs, but in your case I think they're appropriate: look for the wait express VI, and then wire the "error out" output from your first subVI into the "error in" input of the wait, then wire the "error out" from the wait into the "error in" of the second subVI - this will force dataflow and ensure that they each execute in turn.
  18. :question: Do you want to generate the signal in the PC, spit it out a DAQ card and then acquire it again? Or is the signal generation not part of the system (ie: generated externally)?
  19. It depends on what you mean by "profiling" - if you're after a metric that measures code complexity, check this thread out. We also have a statement coverage tool that does exactly what you're after for measuring the percentage of code executed - contact us to find out more information.
  20. Looks like you're getting the "You have broken the temporal continium" error - it's standard when you're using something from the future. The easiest way to fix it is to stop and wait for time to catch up
  21. Sounds more like you've got a Nokia conflict That said - you get the idea: you can easily create a background for your cell - experiement and enjoy!
  22. crelf

    UML tools?

    Sure can - fill this out and the most appropriate person will get back to you ASAP.
  23. Looking for a new way to show the world that you're a true G-eek and LAVA-lover? Download this wallpaper for your cell phone! * tested with Nokia phones - the string constants line up with your network provider name and current profile, the time constant lines up with your clock, and there's room in the bottom corners for button labels. The image may not look great on you PC, but looks just fine once it's on your phone! * No, I do NOT have too much time on my hands!
  24. You're welcome - that's what I'm here for :laugh:
  25. :arrow: The article you're looking for was written by Jeff Kodosky, and is archived here.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.