Serial Compatibility VI's not working in Labview 7.0

I recently upgraded from Labview 6.02 to Labview 7.0 and found that my application could no longer open or communicate via a serial port.
My application uses and I prefer the old serial compatibility VI's because I had trouble with the VISA serial VI's. And the new, Labview 7.0 turned the old serial compatibility VI's into VISA serial VI's.
For anyone interested in using the old serial compatibility VI's, here is one way to get them back, and working properly.
1) Find a computer with an older version of Labview, probably 6.02 or older.
2) Replace the following v 7.0 *.llb files: "_sersup.llb" and "serial.llb" with these v 6.* or earlier files: "_sersup.llb" and "Serial.llb".
3) Also copy this file "serp
drv" from your root v 6.* or earlier folder into your root v 7.0 folder.
That worked for me.
I sincerely hope that Labview will consider replacing the serial compatibility vi's in any future versions or patches with the original ones.
Tom

The only advantage of serial compatibility is cross-platform, and you
get this with visa too. If you are creating an exe then you have to
install the visa runtime engine. If you want to stick with Windows
programs I have found that the MSComm control called with activex is
much more flexible. Also, in order to get write access to the MS Comm
control (writing a LabVIEW program) you have to install some trivial
microsoft enviroment like visual basic, this licenses the control for
both writing and using. When you distribute the application the control
is automatically licensed for use.
Anyway, thanks for the app note on serpdrv.
Tom at Onset wrote:
> I recently upgraded from Labview 6.02 to Labview 7.0 and found that my
> application could no longer open or commu
nicate via a serial port.
>
> My application uses and I prefer the old serial compatibility VI's
> because I had trouble with the VISA serial VI's. And the new, Labview
> 7.0 turned the old serial compatibility VI's into VISA serial VI's.
>
> For anyone interested in using the old serial compatibility VI's, here
> is one way to get them back, and working properly.
>
> 1) Find a computer with an older version of Labview, probably 6.02 or
> older.
>
> 2) Replace the following v 7.0 *.llb files: "_sersup.llb" and
> "serial.llb" with these v 6.* or earlier files: "_sersup.llb" and
> "Serial.llb".
>
> 3) Also copy this file "serpdrv" from your root v 6.* or earlier
> folder into your root v 7.0 folder.
>
> That worked for me.
>
> I sincerely hope that Labview will consider replacing the serial
> compatibility vi's in any future versions or patches with the original
> ones.
>
> Tom

Similar Messages

[LAVA Cross Post] CTRL+SHIFT+ Shortcuts sometimes not working in LabVIEW

Cross-post from LAVA: http://lavag.org/topic/15619-ctrlshift-shortcuts-sometimes-not-working-in-labview/
See the above post for more information - here's a synopsis:
CTRL+SHIFT modifiers are not working while running LabVIEW in a Parallels 7 virtual machine. This problem affects both LV2011 and LV2012. I'm not certain that this is a LabVIEW bug - could be an issue with my virtual machine environment or it's configuration - except that CTRL+SHIFT modifiers work in other applications on the affected VMs. It's just LabVIEW that appears to ignore shortcuts with the CTRL+SHIFT modifiers.
Any ideas?
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

X. wrote:
Still well and alive in Parallels 9 and LabVIEW 2013 SP1. Of course I could upgrade to the latest versions to check whether things have gotten any better.
Any news on that?
@mellroth figured out the solution :-)
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

I purchased PSE 13 but have a Vista OS. It was suggested in this chat room that I download PSE 12. I did that & installed. The serial # for 13 does not work. Any thoughts on how I can get a number for PSE 12?

I purchased PSE 13 but have a Vista OS. It was suggested in this chat room that I download PSE 12. I did that & installed 12.
The serial # for 13 does not work. Any thoughts on how I can get a serial number for PSE 12?

Hi
There is a newer version of Resolution+ Plug-in released for an Qosmio X series
[Resolution+ Plug-in v 1.1.2004|http://eu.computers.toshiba-europe.com/innovation/download_driver_details.jsp?service=EU&selCategory =2&selFamily=381&selSeries=231&selProduct=7506&sel ShortMod=null&language=13&selOS=all&selType=400&ye arupload=&monthupload=&dayupload=&useDate=null&mod e=allMachines&search=&action=search&macId=&country =all&selectedLanguage=13&type=400&page=1&ID=82406& OSID=30&driverLanguage=42]
try it out...
If it has not been installed properly, try rebooting your computer and reverify.

Serial communication does not work in an executable.

I have created a vi that communicates with a serial device. It works fine on the computer that it was creatd on. I then created an application and then built an installer to put it on another machine. The second machine does not have LV 2009 on it. Once installed on the machine the vi does not work. When it runs on the computer with LV 2009 the the com port control is a pull down, and it lists all comports on the computer and then you select the one you want to connect with. The computer that the vi is installed on does not list the available com ports. This leads me to believe that there is no serial comms support in the installable version. What do I do now?? I noticed that you can add "Additional Installers" when you build the installer and one of them is NI-Serial 3.4. I try to add this and a message said that it had to get, so I didn't use it thinking it was more than I needed and that standard com port driver would be included. Am I wrong here or am I missing something else?? All help is greatly appreciated.
[email protected]
Solved!
Go to Solution.

claudio.rossi wrote:
Hi at all!!
I'm new in NI forum.
I have one similar problem. My VI communicate with external device on serial port. The VI work very well, but when I create executable (.exe) file with Labview application builder (on Labview 2010) the .exe don't use serial port!!! The executable run perfectly (nothing error or warning by the application builder), but the serial data on selected COM port isn't send!!! Also on the PC where I developed the VI!!!
What do you mean by your last sentence? Are you trying to say that you can't run your executable even on the same computer on which you developed the application? If so, was LabVIEW open when you tried to run it? Try quitting LabVIEW; if you had previously run your VI and didn't close the serial port, LabVIEW might have kept it open, which would prevent the executable from accessing it. If the executable won't run on the development machine it's unlikely to be resolved by installing VISA since you need that installed for the VI to work properly in the development environment. Do you have any error handling in your code that would indicate if an error occurred after trying to write to the serial port (an indicator on the front panel, or a call to Simple Error Handler)?

ActiveX not working with LabView 6.0i Evaluation Version

I am trying to run some ActiveX container samples in LabView 6.0i Evaluation Version.But it is not working and no error message is displayed. Is ActiveX supported in LabView 6.0i Evaluation Version.

[email protected] (pl) wrote in <506500000008000000CD610000-1031838699000
@exchange.ni.com>:
>I am trying to run some ActiveX container samples in LabView 6.0i
>Evaluation Version.But it is not working and no error message is
>displayed. Is ActiveX supported in LabView 6.0i Evaluation Version.
>
Don't know for sure, but with the Student editions this is certainly the
case so it is possible.
The student editions do not allow:
1.AxtiveX
2.External Code (DLL's, CINS)
3. and somethjing else that escapes me at the moment.
Try simple examples such as the MSBrowser and the Adobe PDF reader AX
controls - these always work if Ax is going to work at all.
Not a solution, sorry ;-)
cheers, Alex.
Alexander C. Le Dain, PhD
ICON Technologies Pty Ltd
http://www.icon-tech.com
.au
* The LabVIEW FAQ http://www.icon-tech.com.au/thelabviewfaq.html *

Sf compatibility plug-in not working

When I download microsoft attachments and attempt to open them in either pages or numbers, I get a message that says my sf compatibility plug-in is not working and it errors out the application. I just had a repair done - worked before I brought it in to apple. Does anyone know the download to fix this problem???

Go to: Mac HD/library/Internet Plug Ins
Trash the Flash Player.plugin file from there
Go to: Mac HD/Library/Application Support/Adobe
Trash the Flash Player folder from there
Empty the trash
Download the Offline Installer: http://fpdownload.macromedia.com/get/flashplayer/current/licensing/mac/install_flash_playe r_11_osx.dmg
(Right click and "Save as")
Mount the DMG and run the installer
Relaunch Safari
Got to: Safari>Preferences
Under the Security tab, make sure "Alow all other plugins" is checked.
Go to a page with Flash Content.
It should now work.

Charger with serial number A1300 is not working for iPhone 5, is it?

I have an issue charging my new iPhone 5. I bought an extra cable - and they seem to both work when pluggin it into any computer. But one of my chargers will not work with it - but it works if I plugin my iPhone 4. How come? I noticed that the serial number is A1300. I borrowed one from a friend with serial number A1400 - and that worked (with the same cable).
can I conclude that chargers with serial numbers A1300 don't work for iPhone 5?

Any iPhone or iPad charger should work with the iPhone 5. There is something wrong with your charger. If it is the one that came with the phone it is covered by the phone's warrantee.

NI Goop Wizard not working with LabVIEW 2009

I have added the NI Goop Wizard using VIPM (VI Package Manager) into my LabVIEW 2009 SP1 installation however it is not working. Whenever I select Create New Class from the drop down (same applies to menu selection) nothing happens and the drop down returns to it's default selection. I have tried this on 2 PC's both with 2009 SP1 installed, both exhibit the same unwanted behaviour. One of the PC's also has LabVIEW 8.2.1 installed also with NI GOOP Wizard and this installation works fine.
Anybody using GOOP Wizard with 2009 ?
Cheers
Chris
Don't forget to give Kudo's for a good answer !
LabVIEW Champion
Certified LabVIEW Architect
Certified TestStand Architect

Hi there Chris,
Off the top of my head it's my understanding that NI GOOP wizard is legacy software that was made redundant by the native GOOP tools in LabVIEW 8.2.0 and later.
In light of this it's a bit confusing that everything is working fine with 8.2.1 for you. Is there a version to the NI GOOP Wizard that you are using?
I had a search across the website but I'm afraid I haven't found any other examples or poeple using the GOOP Wizard in LabVIEW 2009 or 2010.
Kind Regards.
Rhys
Applications Engineer
National Instruments

VIs worked in LabVIEW 2009 but do not work in LabVIEW 2010

The VIs were originally written in LV 7.1 but then compiled in LV 2009 and saved. These VIs worked fine on Windows XP machine.
Unfortunately, the XP machine was crashed and I am trying to run these VIs in LV 2010, with windows 7, 32 bit.
I have installed traditional DAQ drivers (latest version, 7.5) alongwith DAQmx (version 9.8).
We use these VI to control the vacuum valves, using PCI 6503.
To initiate we first use a VI that reset the valves and the PCI card. The name of the first vi is: portconfig.vi This vi uses port config and port write VIs. I see the error 10401 from port config vi, when I run step by step (i.e., sequence 1). However, the VI runs but not doing any actual work.
The second VI that depends on first VI, and therefore the second VI is also not working. on this VI we have buttons (representing valve) and when we click on them, the valves should shut off or open, but nothing happens in LV2010. the same VIs worked in LV2009!
PCI 6503 card is defined under devices and interfaces in MAX. It is not defined under legacy DAQ devices. When I test PCI 6503, it works.
I am attaching both the VIs (there are in QuadMain.llb). I dont know how to get the actual VI from the harddisk...
first open portconfig.vi
then open Control Panel.vi
there are global variables used in Control Panel.vi, there are listed in Valve Global.VI, which is in globals.LLB (second attachement).
I really appreciate if someone can convert these VIs for LV 2010.

Jpdas06 wrote:
Yes, I am doing that. But this is holding up the experiments. So I thought an easy fix for now and then once the work load goes down i can concentrate on changing the port config.vi using DAQmx.
I would really appreciate if you or someone can provide me steps for listing PCI 6503 as both types in MAX.
Thanks again.
You should be able to see the DAQ card in both driver interfaces DAQmx and Traditional DAQ. I just checked on one of out test fixtures. We have MAX 5.6, DAQmx 9.8 and Traditional DAQ 7.5 on Windows 7 32-bit. We use LabVIEW 2013 executables on this PC, but this really doesn't matter.
I believe the only exception, when you don't see cards in both drivers, is when the card is supported in DAQmx only. But in your case this card (PCI 6503) is supported by DAQmx and TDAQ.
I had some issues before renaming devices in Traditional DAQ. If you have more than one card, the device names not always match in both drivers. You could have one card for example as Device 2 in TDAQ and then as Dev 4 in DAQmx.
I would uninstall and install again the Traditional DAQ driver. I never added cards manually to the drivers. This should happen automatically.

Sound and Vibration Spectral map not working in LabVIEW 2011

I recently installed the latest development suite with LabVIEW 2011 and sound and vibration toolkit.
Previously I have successfully used the express function "spectral map" without a speed profile for plot type "frequency-time". With the installation of LV2011 I get an error saying "OA Speed Profile attribute not found" when using the function.
The setup is pretty straight forward with express functions "Simulate Signals", "Spectral Map" and "Color Map" in series.
Is there a bug fix or workaround for this problem?
Attachments:
Spectral Map Error.png ‏30 KB
Spectral Map VI.png ‏36 KB

No, I haven't been able to make the Sound and Vibration Spectral Map express node work in LabVIEW 2011.
A workaround is to not use the express function for a spectral map. You can find the spectral map node under "Sound and Vibration"-"Order Analysis"-"Spectral Map".
I guess the speed profile should be the same for both the express and ordinary function. If so you need to input a cluster of 2 1D arrays, not a waveform. Array1 contains the time in seconds and Array2 the associated speed.

Serial command not working in Labview, but it works in docklight

I am trying to run a RGA via labview.
I can control the RGA via docklight (see attachment), but when I try to give the same command to labview, I do not get a responce. What is going wrong?
What do I mis in the VI?
Best regards,
Rens
Solved!
Go to Solution.
Attachments:
docklight.jpg ‏85 KB
Read EV voltage.vi ‏17 KB

Your code is sending a string which represents the decimal values. You need to convert to Hex string first. See code snippet below.
(I'm sure there is a better way of doing this, but I did it quickly - might be a Rube Goldberg candidate )
(wow. lot's of people posted while I was busy with work rleated stuff.. )
Here goes anyway.. You could have added the code below to convert to Hex equivalent string, or simply write the Hex values in the string directly (probably better).
Message Edited by Ray.R on 04-15-2010 09:01 AM
Attachments:
convertHexDecimal.png ‏18 KB

I am trying to reset a serial device through serial port ,MAX is able to do it but the same command is not working in labview

max can do it but labview cant

- Run NI Spy Tutorial
- Reset the serial device in MAX
- Run the LabVIEW code
- Post the *.spy file.
The spy capture will show any difference in function calls to the driver.

TCP Listen vi does not work in Labview RT 7.0

I'm trying to use a TCP Listener to accept connections from another PC on the local network.
When running the program with Labview 7.0 all works fine and I'm able to receive IP packets from the remote PC.
However, when I run it in Labview RT 7.0, the TCP listener does not listen on the specified port.
Another issue - after running the program in Labview 7.0, and then trying to run it again with Labview RT 7.0, if the specified port
is the same, I get error 60: "The specified network address is currently in use."
I'd appreciate your help,
Alik

Hi alikm,
I am a little confused on what your set up is. When you say that you are running LabVIEW Real-Time, do you mean that you are running the program on a Real-Time target? How are you establishing that the project you are setting up is a Real-Time project?
Also, if you are trying to access one port at the same time using two systems, you will get an error that you are not able to do this, since you can only write to a single port once at a time.
Regards,
Stephen S.
National Instruments
Applications Engineering

Why does the Browse to OPC item.vi example not work in Labview 6.0?

I was trying to update my application from Labview 5.1.1 to Labview 6.0, I could not be able to use the DataSocket Vis. Then I opened the example "Browse to OPC item.vi" in Communication examples in Labview 6.0, the Vi was not able to browse the OPC servers on the network. Does anyboy have experienced this and what could be the problem?
Thanks.
Attachments:
Browse_To_OPC_Item.llb ‏13 KB

Yurong,
In the documentation for the Browse To OPC Item.vi, it is stated that it uses DataSsocket VIs shipped with versions of LabVIEW prior to version 6i. These VIs are provided with LabVIEW 6i for compatibility. The DataSocket primitives shipped with LabVIEW 6i are not currently fully compatible with OPC. When using DataSocket to connect to OPC Servers, use the older compatibility DataSocket VIs.
I was able to run this VI and browse to opc://localhost/National Instruments.OPCDemo/SINE:0.0..8.0:2.0
and didn't have any errors accessing NI OPC Demo server.
Zvezdana S.
National Instruments
Attachments:
Doc1.doc ‏30 KB

MC-4 Controller Not Working with LabView

I have a Klinger MC-4 Motor Controller and am trying to control it with LabView. I have thus far not been able to get the motor to move with the driver that I downloaded from this website. If anybody has written anything for this same purpose, I would greatly appreciate your insight. Any help with this problem in either LabView 5.1 or 6.0 would be great. Thanks.

Hello-
It may be possible to modify the existing driver to work with this instrument. Otherwise, drivers are developed and modified based on demand and popularity so the more requests, the greater the possibility that one will be modified. Please send an email to [email protected] about this issue. It would also be beneficial to notify the instrument manufacturer.
Randy Solomonson
Application Engineer
National Instruments

Serial Compatibility VI's not working in Labview 7.0

Similar Messages

Maybe you are looking for