Jump to content

Minh Pham

Members
  • Posts

    171
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Minh Pham

  1. Interesting to see you implemented the actor framwork to this example. Looks great, i have a very quick try and go through the code. Only found 1 issue:

     

    -Error handling for the user input, when deposit if user input a text instead of number, an error 85 is generated. The problem is that you wired theerror to the input of the "Error cluster from Error Code" vi in the UI.lvclass:Enter Pressed.vi within the Deposit Amount case, so this vi can not execute as you wanted.

  2. Is this device from MicroEpsilon? there is an instrument driver for it in LabVIEW i think:

     

    The scanCONTROL LabVIEW instrument driver

    supports the rapid integration of the profile sensors

    in the National Instruments’ LabVIEW®

    programming environment. Access to scan-

    CONTROL sensors and their basic settings is

    depicted in individual modules that can be directly

    integrated in your own VIs using the software

    functions. Example VIs also form part of

    the integration process.

    The integration of scanCONTROL sensors

    in the LabVIEW programming environment

    is based on the C/C++ library “LLT.dll” from

    Micro-Epsilon. The extensive documentation

    explains how its additional special sensor parameters

    can be set up.

    - Meets the National Instruments guidelines

    for LabVIEW instrument drivers

    - Supports LabVIEW 8.6 and higher

    - Easy access to a range of functions via

    function palette

    - Support for the FireWire and Ethernet

    interface

    - Example VIs, inc. single profile transfer and

    container mode

    Software for scanner integration

    The examples contained in the SDK also

    demonstrate how the different interfaces (serial,

    FireWire, and Ethernet) can be effectively

    configured

     

    http://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=5&cad=rja&ved=0CEsQFjAE&url=http%3A%2F%2Fwww.micro-epsilon.com%2Fdownload%2Fproducts%2Fdat--scanCONTROL-software-integration--en.pdf&ei=Nno2UZazHuHvmAX11YHAAg&usg=AFQjCNGUXc10h4p2I7VsFP19CPCNXHuyoQ&sig2=RVnVDNb0hRZW09yJ6h7UFw

  3. Sorry, i dont look at NI developer zone. The solution there is ok but doesnt work for clone vis as mentioned.

    I prefer a native LabVIEW function for this purpose. Im very surprise that this is still not available after 5 years of playing with LabVIEW :(

    I will vote to push this feature forward. Thanks Yair 

  4. Have you ever being frustrated by getting your project stuck after you running it and realized that you forgot to close one (or few) of your model style subvi(s) (which show front panel when called) ?

     

    You can not do anything on your main front panel as the model vi is in front of everything and you can not stop it either! All you can do is to kill LabVIEW and re-open the project. 

     

    I believe that LabVIEW should has an option to stop anything, anywhere,anytime when you are in the development environment. This has always been an issue since I started using LabVIEW. Please add a method to the next version of LabVIEW such that developers can stop thing like this from happening.    

    • Like 1
  5. I would like to integrate a tool bar in my application, but can't find any to download or to buy. Is there any XControl like the tool bar in VIPM and other tools from JKI?

     

    Putting buttons in a part of a splitted panel is not the solution.. Building own XControl would take too much time to make it properly.

    Do you really need to create an XControl for this purpose.

    Even if you have to it shouldnt take you much time i think :)

  6. Darren,

     

    The API will work for all the icons that created by the API only. But it is a pretty good starting point for many people I guess.

    Within the LabVIEW Icon API, there is an useful function: Read Icon Data from VI, this will return a cluster of the Icon Data which has stuff like: Body Text (line 1 text, line 2 text ....) font size, font alignment and such.

     

    Attached is an example I made to show this.

     

    However, this will not work if the icon created by a different API/software eg. MikaelH's GOOP tool or paint or photoshop...If this is the case, we have to use an OCR method to get the texts from the icon.

     

    It would be nice if MikaelH'sGoop uses the same type def (or just the Body Text part of the LabVIEW Icon API's Icon typedef) when generating the text field on the Icon, that way MikaelH's GOOP Tool can have access to the Text fields hence modifying/getting/setting of the texts can be unified between his tool and LabVIEW native Icon editor.

     

    Might be in the next release of GOOP? any thought Mikael? 

     

    post-11757-0-30240200-1360192281_thumb.p

    IconStuff.vi

  7. Sounds great, how do i get access to the VI's meta-data to get the right tag(s) for all the text within the icon. This is the proper way to modify the text :)

     

    OCR should be just fine (required vision dev module)

    or you can also use a 3rd party or open source  OCR tool which accepts image (icon) as an input and spit out all the characters it finds (normally in a *.dll format - eg. ActiveX or .Net component)

×
×
  • Create New...

Important Information

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