Jump to content

LAVA 1.0 Content

Members
 View Profile  See their activity

  • Posts

    2,739

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by LAVA 1.0 Content

  9. fp1000, omega tempscan 1000 and labview

    in Hardware

    Posted

    QUOTE(kunal227 @ May 22 2007, 03:14 AM)

    Welcome to LAVA. I don't have experience with the Omega Tempscan, but I did a quick search of the Omega and NI web sites for drivers, and found nothing.

    Your profile indicates you are somewhat recent to LabVIEW. If you ever need drivers for an instrument, the first place to look is at NI's web site at http://www.ni.com/idnet . The next place is here or the NI forums.

    I used to work for an equipment manufacturer that OEM'd equipment for Omega. Omega stuff is spotty, some is really good and other stuff is cr@p. Omega probably sources the Tempscan from somebody that has LabVIEW drivers; the Omega data sheet for it indicates they are available. You need to contact Omega support to get the driver. My experience is that these types of drivers are written in a poor style and long ago (LabVIEW 5.x). Just getting a driver doesn't mean that you can install and go.

    If you look carefully at the instrument (worst case: take off the cover and look inside) you might be able to figure out who makes the instrument and get the driver directly. I suggest this only if the Omega support is unable to help. This may void your warranty, so don't call me if you have problems :laugh:

  11. LabVIEW and DSL (Damn Small Linux)

    in Linux

    Posted

    QUOTE(hooovahh @ May 17 2007, 03:46 PM)

    If you're still confused send Bart an email, in my experience he's very friendly, and has even helped my company with random questions we had about DOS boot ables a while back.

    Basically, you agknowledge excactly what I was thinking. It would be illegal in my case.

    With the article, I ment the article Bart wrote a few years ago in a Dutch magazine.

    Btw. This thread hasn't been about "LabVIEW and DSL" for a while now, so we might as well talk about BartPE...

    Thanks,

    Wiebe.

  13. Queue are no longer working accross different context (App Instances)

    in Development Environment (IDE)

    Posted

    QUOTE(jpdrolet @ May 17 2007, 08:41 PM) 

      server.tcp.paranoid=False

    :D I love that one !

    QUOTE(jpdrolet @ May 17 2007, 08:41 PM)

    I usually set
    server.vi.access="+Server*"
    so only VIs with names beginnig with
    Server
    are accessible from the VI Server interface. Maybe the "+" is missing in arg3, so sorry my mistake...

    That sounds like a good trick !

    Thanks a lot for your help ! :worship: I was about to :throwpc:

  14. Annual LAVA/OpenG BBQ

    in NIWeek

    Posted

    QUOTE(crelf @ May 17 2007, 07:08 PM)

    I'll be sending out an invitation to all LAVA and OpenG folks - we do need to know numbers so we can make sure we fit in the resturant, but there'll be room for everyone!

    Great, I can't wait ! :thumbup:

  15. Queue are no longer working accross different context (App Instances)

    in Development Environment (IDE)

  17. CLD....1,2,3?

    in Certification and Training

    Posted

    QUOTE(Thang Nguyen @ May 17 2007, 12:56 AM)

    Could you tell me more detailed about documentation? Is it the comments in the block diagram?

    Yes but not only, it is also:

    - the VI documentation press ctrl + i to open the "VI properies", then go to "documentation", there you can describe what the VI does (this will be what you'll see in the context help)

    - the VI icon, double click on the icon to edit it

    - the tip strips on front panel controls and indicators, right clic on the control and go to "documentation"

    If you do this for all you VIs, put a label for any constant, and place text all over the place to describe you code, then you'll easily get a very good mark for the documentation part.

  18. Value of CLAD / CLD / CLA?

    in Certification and Training

    Posted

    QUOTE(Wolfram @ May 17 2007, 12:43 AM)

    My opinion:

    This is an additional way for NI to make money. Last year, we were force by NI to make

    at least the CLD certification. Otherwise we would loose the status to be a NI selected

    alliance partner. So we made it.

    Not so fast... setting up a required "LabVIEW skills certification program" is also a way to increase the value the Alliance partnership for NI and for the partners.

    NI makes sure that the alliance member have a certain number of developper with a minimum level.

    Being a partners doesn't mean only selling NI hardware and software licences, it show you can bring expertise.

    And... well... Can you tell me one and only company that makes huge profits and that is not tight @$ ? :P

  19. Queue are no longer working accross different context (App Instances)

    in Development Environment (IDE)

    Posted

    QUOTE(Aristos Queue @ Feb 2 2007, 09:44 PM)

    Basic principle: An app instance should always be treated as a separate machine. If the code works in separate app instances, then it should work on separate machines. Behind the scenes, LV might cheat for two app instances on the same computer, but the same VIs must still work if the app instances aren't co-machine.

    Hi,

    I know that thread is starting to be "old", but it let me doubtfull.

    Is there really a way to pass data between 2 EXEs (built with LV 7.1.1) running on the same computer through VI server ?

    I ask this because I've been transfering data between 2 EXEs for for a long time, but one EXE was on a Windows PC and the other EXE was running on an RT PXI... so I though it was going to be as easy as the example "VI server Manager application" (example that comes with LV 7.1.1), but apparently it works only betwwen a WinEXE and a RT EXE. Am I wrong ?

    A small example or a screenshot would be very highly appriciated (a diagram is worth a thousand word ;) )

  20. Value of CLAD / CLD / CLA?

    in Certification and Training

    Posted

    QUOTE(eaolson @ May 16 2007, 02:23 PM)

    ... I'm just trying to decide if the trouble and expense is worth a bullet point on the resume or not.

    I went to the NI Developer Day here in Boston, and by attending I received a voucher for $200 off of a training class or test. An associate of mine was told he could use this voucher to take the CLAD test (cost $125 or FREE!)

    During the presentations, it was mentioned again and again that NI is working hard to get LabVIEW more widely used in educational institutions. If more and more grads start showing up with "formal" LabVIEW training, A CLD certificate might be worth having...

  21. LabVIEW and DSL (Damn Small Linux)

    in Linux

    Posted

    QUOTE(hooovahh @ May 10 2007, 04:03 PM)

    BartPE is Free and Legal when used properly (you would be using it properly) BartPE is not owned by Microsoft. I think you are getting WinPE and BartPE mixed up. If you're interested here's the BartPE home page.

    http://www.nu2.nu/pebuilder/''>http://www.nu2.nu/pebuilder/' target="_blank">http://www.nu2.nu/pebuilder/

    But as I mentioned earlier BartPE probably wouldn't work because of the ethernet drivers issue. BartPE would need the drivers for the specific ethernet card. Usually this is done by running a small utility from within Windows, and extracting the driver that way. But since these machines don't have windows install it would make it more difficult to get the right drivers.

    You mean I can use PartPE to put a Windows XP compatible OS on 500 PC's? (The 500 PC's do not have windows XP installed on it.) Because that is how I want to use it...

    The website, will all respect, doesn't explain to me what what free and legal use is. I haven't read every word of it, but regarding licensing, all I can find is in step 7 in the getting started.

    I'll see if I can find your article in CT from a while ago. I'm sure I have it somewhere.

    Regards,

    Wiebe.

  22. CLD....1,2,3?

    in Certification and Training

    Posted

    I'm going in on Monday the 21st for my first try at the CLD. I've been reviewing my Intermediate I & II course books along with the downloadable examples. I'm also looking over The LabVIEW Style Book when I get a chance.

    :unsure: Where's the nail-biting emoticon?

  23. CLD....1,2,3?

    in Certification and Training

    Posted

    QUOTE(skof @ May 15 2007, 05:27 PM)

    To don't create a new topic... I'm going to take my CLAD test next Wednesday. What is your experience with CLAD (if you still remember that :) )? I've passed NI LabView Fundamentals online exam, does it about the same as CLAD test or CLAD is more difficult?

    When I took the CLAD the exam was quite similar to the blank exam on the web, maybe the real exams cover more different subjects that the online exam, but there isn't a huge gap between the two.

    Good luck !

  24. CLD....1,2,3?

    in Certification and Training

    Posted

    I failed my first CLD last year because :

    #1 Lack of experience

    #2 I was not appropriately prepared

    #3 I was much too slow (because of my lack of experience and also because I was not appropriately prepare for this type of exam)

    oups... I'm going round :rolleyes:

    I took the exam again last friday and now expect the result quietly. I had time to prepare myself, to train to do a small state machine with enum in a short time, to, first do a template vi with error handling + empty text for documentation + specific icon + documentation filled with "date, author, project".

  25. Instrument Driver for a product family!

    in Application Design & Architecture

    Posted

    QUOTE(mesmith @ May 14 2007, 10:52 AM)

    I agree with Tomi that in principle, OO code is the way to go.

    I don't disagree that OOP is useful, but I don't see it as "the way to go" in this case.

    My argument is that a driver developed for distribution to users needs to be:

    1. multi-revision compatible (7.x, 8.x)
    2. functional with different LabVIEW levels(base, full, prof)
    3. modification friendly to the end user

    There are still lots of 7.x users out there (even a few 6.x) An base OOP driver would put the instrument(s) at a competitive disadvantage

    Not all users have full or pro licenses, so a LVOOP driver could limit use ( and limit to 8.2x )

    making a modification to a driver based on classes would be above the skill level of > 75% of LabVIEW users at this point.

    When developing something like this, identifying the least common denominator is as important as selecting the sharpest tool in the shed.

    Just my :2cents: ...

×
×
  • Create New...

Important Information

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

  I accept