Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About Goure

  • Rank
    LAVA groupie
  • Birthday June 23

Profile Information

  • Gender
  • Location
    Minneapolis, MN

LabVIEW Information

  • Version
    LabVIEW 2013
  • Since
  1. I am trying to resurrect some old hardware and am running into some unknown errors. I will try to fully describe my setup and steps I've tried and would appreciate if anyone has any ideas on how to fix my situation. The old hardware: Hauppauge WinTV PVR-500 MCE PCI Dual Tuner card PULNiX TM-7CN Monochrome CCD camera An important note is that I know that the card and camera work because I can run them on my ~10 year old home-built PVR and watch a live image using my old BeyondTV software. I am not using this old computer with LabVIEW, however, so I moved the PCI card to a new comput
  2. Hi all, I use LabView 8.6 on Windows PC's to run instruments in my lab. The .vi's I've written all use DAQmx (version 9.0 I think) to access the hardware. What I would like to be able to do is edit these .vi's on my Mac, then upload the edited versions to the Windows computers to execute. Has anyone ever done this or know if its possible? All I've tried to do so far is open my .vi's on the Mac, and of course I get DAQmx errors and missing files (.dll's mostly). I've installed DAQmx Base on the Mac, but I can't convert all my software to use DAQmx Base on the Windows side because there ar
  3. I don't have any problems with svnX (http://code.google.com/p/svnx/). As that site you linked says, it does have separate windows for the working copies and repositories, but I view this as a plus rather than a detriment. For LabView, I've used Perforce (http://www.perforce.com/) for a couple years now. Its free as long as you don't exceed 2 users on 5 computers. I started with this for LabView because LabView didn't originally support subversion. Since what version does LabView now support it?
  • Create New...

Important Information

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