Jump to content


  • Content Count

  • Joined

  • Last visited


Community Reputation


About winmac96

  • Rank
    LAVA groupie
  1. QUOTE(Matheus @ Jul 10 2007, 04:01 PM) Hi Matheus, I myself have just upgraded to LV 8.20 and can build my applications to an executable (EXE) via AppBuilder. The difference with my version and yours (seems to be) is that you have the Professional version while I have a Full Development version. Although LabView installer installs pretty much the same code into your machine (like Vista does), different functionalities are activated by what license you have purchased at the time of install. When you purchase the full development capability you won't have to reinstall LV 8.2 again. You wil
  2. I have just installed LabView 8.2 on an XP SP2 VAIO (3.3 GHz) desktop along with the Modulation Toolkit and Spectral Measurement Toolkit. When the dust settled and rebooted PC, an "Error 1605 occurred while installing NI-PAL 1.6.1f0 engine". Using MAX to verify the NI software installed and indeed lists the above NI-PAL version. After reading NI forums regarding the subject, I tried downloading NI-VISA. Installing the latest NI-VISA (version 4.1 at this stage) installs a fresh new version of NI-PAL (v. 2.0.0). After NI-VISA installation, rebooting XP SP2 no longer come up with the old error
  3. Hi M3NTH, I apologize for the late reply. Yes I did try running LV with the multi-threading feature of LV off and on. I assume you meant the multiple thread capability of LV and not the hyperthreading of the CPU which I don't know how to disable. So, my solution is to rebuild the PC back to SP1 to get back on my feet. Thanks! Winmac96
  4. Hi All, Has anyone experienced problems with NI-VISA (version 3.1) when VI is run under XP SP2? I have just updated my laptop (P4 2.8G Toshiba) running LV 7.1 to the supposedly better XP Service Pack 2. I think I just opened a can of worms... With SP1, my LV 7.1 worked flawlessly. Now, when I run my app (it is a rather large and complex and uses events extensively to communicate via GPIB and remote wireless serial). The problem I am encountering now is that LV gives me occassional (but persistent thereafter) VISA errors. A sample of one error attached. I have tried installing the NI-VISA
  5. Hi dnvalen, I assume you have used the standard RS-232 serial VIs provided with LV. As you may know, those are designed for a single-ended or point-to-point serial communications. For example, COM1 to ONLY one device (mouse, keyboard, so on). The provided VIs assumes both sides of the line have been set to the same parameters - (e.g. 9600-N-8-1). But you are using a different serial communication standard - RS-485. Signaling and topology is completely different. For one, RS-485's signaling is called 'Balanced data transmission', or 'Differential voltage transmission'. Compared to RS-232, an
  6. Hi Nan All the previous suggestions are quite helpful. Controlling the serial ports is like a never-ending trial & error experiment. Timing is everything. Since it is the most common device interface around, it is very useful to get to know how it works. I wrote a LV driver for an antenna rotator control box recently (for a project) and it came with its own set of control app. I needed to have this box controlled by LV and the distributor did not have one. But I did get the format of the commands. This is important since serial commands can in ASCII or binary format (you have to find out
  • Create New...

Important Information

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