Jump to content

Born2Wire

Members
  • Posts

    11
  • Joined

  • Last visited

    Never

Born2Wire's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. QUOTE(karthik @ Sep 18 2007, 03:34 AM) I am afraid if you want to have a meter that looks exactly like the one in your image that you are going to have to do a lot of low level coding. Either that or buy an ActiveX control of the kind you want. In other words, you are going to have to write code that turns on and off the individual pixels you want.
  2. QUOTE(tharrenos @ Sep 17 2007, 02:04 PM) The student edition is pretty stripped down. And even the developer edition will not necesarrily have the add ons. This link takes you to the price list for Remote Panels which would allow embedding LabVIEW in a web page. http://sine.ni.com/nips/cds/view/p/lang/en/nid/11017 Here is the link for the PDA add on prices. http://sine.ni.com/nips/cds/view/p/lang/en/nid/12222
  3. QUOTE(tharrenos @ Sep 17 2007, 04:59 AM) Ahh. If money is going to be an issue, then you are going to have problems. The add-ons to develop on an embedded target, or a hand held device, or a web application all cost extra. NI is very proud of their product, and most of their customers are used to paying a lot for tools.
  4. QUOTE(tharrenos @ Sep 16 2007, 11:18 AM) Presumably you are going to have one embedded system. Specifically the remote. You should decide if the HW that will control the heating will also be an embedded system or if you can leave a PC to do it. NI has an embedded toolkit addon for embedded platforms. You should research these and decide which target you want to use. A pointer is to find one that has a Wi-Fi solution already. Alternatly, it may be acceptable to allow a Palm Pilot or PocketPC device control the heating via a web page or similar. You can get an add-on for LabVIEW that allows you to embed Labview in a webpage. You could get an add on to allow you to write labview for the handheld device as well. So there are three aproaches as I see it. 1. Custom remote control HW running an embedded system supported by LabVIEW with a supported Wi-Fi interface and driver. (Don't do this one.) 2. Embed LabVIEW in a webpage, then use Wi-Fi enabled hand helds to view that page. (Should allow you to develop code just for the PC running the heating system. This way probably has the least development on your part.) 3. Develop TCP/IP application for hand held devices to talk to your PC.
  5. Maybe this is a silly suggestion that you have already thought of and checked. Could it be that there is some corrupt memory on the machine that you are developing on?
  6. I finally tried the Alliance Vision Twain driver for LabVIEW. It worked out of the box. If the rest of it as slick as the demo, then it is truly a nice piece of work. A bit steep for personal projects, but that's life I suppose.
  7. Well for your application, none. However in my last project it was decided to add fancy background graphics (stills) to make the product look more attractive to the customer. Since this was 7.1, the solution was a bit painful and we all had to learn not to touch the various panels for fear of getting everythng misaligned.
  8. Hi, I was wondering if anyone had used LabVIEW and/or the NI Vision tools to get pictures from a flatbed scanner? If so, what tools did you use, and what did you think of them? Thanks!
  9. Hi Suneel, I had this same problem with IMAQ picture controls. I think the problem is that the IMAQ control is itself a reference. So when you try to make a reference to it, you are trying to make a reference to a reference. This apparently makes LabVIEW unhappy. When I got that far in my thinking I just re-wrote my code to pass the IMAQ wire everywhere I needed it. I suppose if you really really wanted to make a reference to it, you could try a generic control reference instead of a specific IMAQ control reference. WHat is it that you are trying to do by makeing the reference?
  10. Hi Ton, I tried various re-installs. I did both the IMAQ and Vision packages. I think I even tried the Vision 8.2 upgrade that is suggested on here, although I confessed that all the install uninstall madness may have thrashed my system enough that it would not have worked anyway. I did a wipe of all NI stuff from the machine and re-installed LabVIEW, the drivers, IMAQ and the 8.01 patch complete with re-compile. I still need to re-install Vision to complete.
  11. I suggest you go carefully when upgrading from 8.1 to 8.20. I had a large application that was using IMAQ and Vision, and after the upgrade many of the VIs for these packages were 'missing'. Still trying to recover.
×
×
  • Create New...

Important Information

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