Jump to content

Minh Pham

Members
  • Content Count

    171
  • Joined

  • Last visited

  • Days Won

    2

Minh Pham last won the day on February 5 2013

Minh Pham had the most liked content!

Community Reputation

9

About Minh Pham

  • Rank
    Very Active

Profile Information

  • Gender
    Male
  • Location
    Sydney
  • Interests
    Cars, automation, robots, biomedical, photography, Wavelength Selective Switches.

    Soccer, Tennis, Table Tennis

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since
    2006

Recent Profile Visitors

1,773 profile views
  1. Cant win the 'smart' computer, damn
  2. Please go through the properties of this Waveform Graph (object), you will find many other stuff that you can customize as well.
  3. 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.
  4. you can start with the Vision assistant, and please playing with the OCR stuff through there. When you are familiar with the all the features, you can start exporting/building LabVIEW code from the Vision Assistant
  5. What do you want to obtain from that image? Please describe your requirements
  6. Hi, just wonder if there is anyone here has work with *.tps file before. Can we convert the file to be used within LabVIEW. Attached is the PARTS.txt file --> Please rename the file to PARTS.tps as i could not upload tps file so I changed the extension to *.txt for uploading purpose. PARTS.txt
  7. 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
  8. I saved this as 2010 as attached This is nothing special Stobber MouseClick.vi
  9. 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
  10. There is an interesting thread here: http://forums.whirlpool.net.au/archive/811621
  11. 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.
×
×
  • Create New...

Important Information

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