Example VIs for winsock with LabVIEW 7.0

Are there any example VIs for TCP communications with winsock using LabVIEW 7.0?

I would like to join the request - I would like to know how to use WinSock from within LabVIEW to use a modem to dial a number and connect to another PC with a modem. An extra complicaiton is the fact that I need to be able to vary the number (to access numerous data acquisition stations).
Message Edited by alysko on 03-08-2006 03:57 PM
Message Edited by alysko on 03-08-2006 03:58 PM

Similar Messages

SpaceX is looking for engineers with LabVIEW experience in Hawthorne CA (LA area)

SpaceX is looking for engineers with LabVIEW programming experience for our Launch group. Our responsibilities include:
Controlling launch pad equipment via PXI/LabVIEW
Commanding and monitoring our Falcon 1 and Falcon 9 rockets via a LabVIEW-based Vehicle control system
Commanding and monitoring our Dragon capsules via a LabVIEW-based Mission Operation system
Ocean recovery of Falcon 1 and Falcon 9 stages after liftoff and Dragon capsules after splashdown
Cargo configuration of Dragon capsules going to resupply the International Space Station
Maintenance of Mission Control Centers with the help of our IT department
With the exception of the launch pad equipment program, most of our LabVIEW programs do not interact with DAQ hardware (unusual, I know). The Vehicle control and Mission Operations software get their data via Ethernet from 'black boxes' that connect to NASA & Commercial RF ground stations. We also create several utility programs in LabVIEW that also don't interact with hardware. So, this is mostly a software gig, not a hardware/software gig.
Ideal candidates will have the following qualities:
CLD-level LabVIEW experience
A good understanding of basic computer networking (TCP/IP, UPD, firewalls, VPN)
Must be enthusiastic about space (What year did we land on the moon? How many men walked on the moon? How many Space Shuttles do we currently have? etc.)
Must be willing to travel. Common destinations include Houston (NASA Johnson Space Center), McGregor TX (test site), Cape Canaveral FL (launch site), Kwajalein Marshall Islands (launch site)
Must be able to work without supervision. We have a very flat management structure, no one will be telling you what you need to do. If you don’t know, ask. If you do know, get it done.
About the job:
Job is located in Hawthorne, CA in the Los Angeles area.
This is not a 9-5 job. There will be some late nights.
You won't be LabVIEW only. Everyone chips in as needed. Our group has done Javascript, C++, MATLAB, configuring of TELEX comm systems, cutting of metal with bandsaws, welding, Unigraphics CAD, etc. If we need it and you don't know it, grab a book and learn.
We are only hiring full time employees. Contractors need not apply.
To conform to U.S. Government space technology export regulations, SpaceX hires only U.S. citizens and U.S. Permanent Residents.
Apply at SpaceX.com. Click the Careers button and fill out the general application. Mention this posting in the cover letter field. Don’t reply to this forum. You need to go to SpaceX.com to get your information into our system.
Message Edited by Lavezza on 03-31-2010 03:59 PM

There is a job posting up now at SpaceX.com. Go to the careers tab and search for LabVIEW.
Look for the position called: Mission Control Software Engineers (LabVIEW).

Are there any DAQmx examples available for use with pci 6229 M series card?

I have been searching around for examples which work with the pci 6229 M series DAQ card. Most examples do not list this card as applicable and the one I have found gives an error. Is there anywhere specifically available, what I am particularly interested in is seeing an analogue channel being triggered by another analogue channel reaching a certain value.
Thanks
Kevin

Hi Kejoglo,
You are right in the fact that the M-Series card is newer than LabVIEW (and therefore the examples that are shipped with it) and therefore the example finder doesn't list the M-Series cards in the list of available hardware.
Basically though, the M-Series cards work with DAQmx and not Traditional DAQ so if you just go into the example finder and search under Hardware Input and Output>>DAQmx and choose an example from that folder to run on your M-Series card. As long as you don't try to do anything outside of the specifications of your card (which I doubt you will do) then you shouldn't have any trouble running any of the DAQmx examples on an M-Series card.
Hope this helps, if you still have problems then please feel free to write back.
Best regards,
Peter H
Applications Engineer
National Instruments UK

Suggested in-process database for use with LabVIEW?

I've been researching databases for a few days looking for something lightweight that I can use when developing applications. I saw the post by Anthony Lukindo on Expressionflow (http://expressionflow.com/2007/07/05/labview-based-utility-to-package-deploy-ms-sql-server-2005-expr...), but I'm not really looking to use an enterprise level db and it sure seems complicated. I looked at both MS SQL Server Compact 3.5 and SQLite, and they both look to be about what I'm looking for, but I haven't found any LV interfaces to these things. There appeared to be an aborted effort to get a SQLite interface made as an OpenG toolkit (SQLite database toolkit (Windows)), but it seems to have inexplicably vanished. I like the idea of SQLite better than the MS product because it seems to only include the things I'm looking for, and it's cross platform (and public domain) and I am thinking about starting to write an interface myself. I'd appreciate any comments on the topic.
I do have the LV DB toolkit, but I would rather not have all the overhead associated with speaking to an out-of-process db through external components (plus the headeaches associated with deploying the thing). I am pretty much a nubie in this area though, so maybe I can be convinced otherwise.
Thanks,
Chris

SQLite is propably the best performing free open source disk based database for a "single-threaded" applications or for reasonably sized multi-threaded applications that do not require row-level or table-level locking. So do not consider SQLite only as a development time alternative... it is a good alternative for many purposes.
You can connect to SQLite with a ODBC driver, I think, and do not need a native LabVIEW support for SQLite. Just google SQLite ODBC.I have not tested this, but if so, you can use any of the ODBC database toolkits for LabVIEW, even the National Instruments one
A different thing is that if you need a database for development purposes, should you actually set up one? I'm a friend of a software-as-a-service and currently use hosted mysql databases at Mosso. I use them for web development project but I see no reason to use them with LabVIEW as well, as long as your development computer is online. The good thing about hosted services is that they really are zero-configuration and zero-maintenance. When ever I've a problem or don't know something, I simply chat with the support person online Another good thing is that my hosted databases come with online administrative interface, phpMyAdmin, which simplyfies the database management, especially during the development phase when everything is not working as expected. Furthermore I can use MySQ Workbench to visualize the structure of my database for documentation purposes.
p.s. Mosso pricing starts from $100/month which may be over your budget, but the support is simply superb. For the price you get practically unlimited number of databases of you choice such as MySQL and MS SQL 2005, and practically unlimited number of hosted web sites running in a load balanced cloud with either Linux or Windows or mixed. The downside is you cannot install new programs such as LabVIEW and you have to do with the services they provide. When your computational needs exceed certain limit of processor cycles a month, you need to pay more. This limit is something like a single processor server.If you decide to go for mosso, use the following referral code "REF-EXPRESSIONFLOW" to get the second month free. The promotion is valid until the end of September and after that you get $50 off from the first month price.
Tomi Maila

Ask for help with LabView Daq and Tek VX4244 VX4101

I use NI VIO-MXI-64XE-10, Tek VX4101 and Tek VX4244 to acquire data in one
Tek 1410A VXI mainframe connected a PII 350/64M computer with MXI2
cable.these modules are used for three independent applications,the datum
are acquired and through preliminary computation, then sent to three TCP/IP
ports the computer served in real time. the burden of the system will be
very heavy because the 64XE-10 need to use up the 100K sample rate
continuously dealed by 50 channels,and the VX4244 need about 30Hz for all 16
channels.
64XE-10 is easily detected by NI software, and I can use LabView Daq
intermediate analog input VIs to acquire data in background, read 50 samples
and compute the mean for each channel,then packa
ge the 50 mean and send to
client end with 40 times a second. I found the speed is satisfactory.
As for VX4244 and VX4101,I can't use LabView Daq VIs,and the driving
functions for LabView with the product are difficult to understand, I want
to know how I can get data and send out efficiently,how to get data in
background,and how to use FDC ?
And for 64XE-10, although the speed is satisfactory, but it use much more
CPU resource, I want to use advanced analog input VIs to build the code,I
want to know where I can find examples using the advanced analog input VIs ?
Best Regards

I use NI VIO-MXI-64XE-10, Tek VX4101 and Tek VX4244 to acquire data in one
Tek 1410A VXI mainframe connected a PII 350/64M computer with MXI2
cable.these modules are used for three independent applications,the datum
are acquired and through preliminary computation, then sent to three TCP/IP
ports the computer served in real time. the burden of the system will be
very heavy because the 64XE-10 need to use up the 100K sample rate
continuously dealed by 50 channels,and the VX4244 need about 30Hz for all 16
channels.
64XE-10 is easily detected by NI software, and I can use LabView Daq
intermediate analog input VIs to acquire data in background, read 50 samples
and compute the mean for each channel,then packa
ge the 50 mean and send to
client end with 40 times a second. I found the speed is satisfactory.
As for VX4244 and VX4101,I can't use LabView Daq VIs,and the driving
functions for LabView with the product are difficult to understand, I want
to know how I can get data and send out efficiently,how to get data in
background,and how to use FDC ?
And for 64XE-10, although the speed is satisfactory, but it use much more
CPU resource, I want to use advanced analog input VIs to build the code,I
want to know where I can find examples using the advanced analog input VIs ?
Best Regards

Why does visa write hang with Labview 2009 instrument drivers.

I'm having an issue with a code package that I'm running. The pacakge is very complex and was written by someone other than me. It runs fine while using the labview 8.5 drivers, however, when the 2009 instrument drivers are install there is a visa write call to an instrument where the software will hang up at the VISA write VI. I tried setting the timeout attribute but that makes no difference. I would expect that if the visa write did not work, that it would time out with an error instead of hanging up.
Some additional information. The instrument is an EPM which is on a GPIB bus with other instruments. When I place the EPM2000 on a serparate bus this problem goes away, but I want to be able to operate on the same GPIB bus.
Has anyone experienced a similar problem? What can I try to help troubleshoot the problem. I tried opening NI Spy but that shows no activity going on.

Hi Steve,
My apologies, when you said instrument drivers I assumed you were refering to the individual drivers for your instrument. Were you refering to the VISA drivers? If so, the latest version of these is 5.1.1 which can be downloaded here: http://joule.ni.com/nidu/cds/view/p/id/2659/lang/en.
Also are you able to communicate with this device using the test panels in Measurement & Automation Explorer? There is also a tool called NI IO Trace (or it may still be called NI-SPY in 2009) that can be opened from MAX that monitors all GPIB commands sent and received on the machine. Getting a log of the commands when the hang occurs may help to diagnose it.
It is possible this issue could be caused by opening and closing the VISA reference frequently in the code such as in a loop iteration. Is this is case in your code?
Justin D
Applications Engineer
National Instruments
http://www.ni.com/support/

Warning while loading example VIs for XPS motion controller

Hi,
I'm new to Labview. I want to control the XPS motion controller using Labview and I wanted to get started with the examples provided by XPS along with the drivers. But I get a warning while loading the example. I have attached a screenshot of it. Please help.
Also, opening the example opens just the front panel. How do I open the bloack diagram of the example VI?
Thank you.
Attachments:
warning.png ‏40 KB

That warning is nothing to be worried about -- it just means that things were found in a new location, which is normal when you move code around. Once you save the project it should go away.
To look at the block diagram, use Window - Show Block Diagram, or simply Ctrl+E.
Good luck!
Edwin

Looking for istructions/examples for using winsock in Labview

I'm looking for instructions or examples of using winsock in Labview. Looking in the NI examples I found an example using winsock UDP with Labwindows but nothing for Labview. Is the same function named different in Labview?

Thanks for the links. Unfortunately, I am specifically looking for the ways to use WinSock (I want to collect data from a number of remote locations and the WinSock would provide me with an effective way to
a) control the telephone number to be dialed (different for different remote stations)
b) provide me with TCP/IP, so I could use the full power of LabVIEW seeing a remote computer as an IP address (and being able to use shared variables, web server, data socket etc. instead of me having to program all that myself)
The other acceptable way would be to utilise a driver for a virtual network card (so I can programmically access it as TCP/IP on one side, and as a flow of bytes on the other, "virtual network cable", side). Any suggestions in this direction? By the way, it would be the best if the National Instuments would do such a virtualisation themselves. It would allow to utilise a number of solutions painlessly.

Labview basic vis for controlling Newport ESP6000 controller and 3 axis stages

I have looked in Ni.com's development zone and cannot find anybody who
has created or developed Labview code for controlling a ESP6000
Newport controller. Newport provides the basic level dll for use with
Labview. Has anybody developed a good basic LabView VI implementing
these dlls?
Any advice and suggestions on how to proceed would be greatly
appreciated.
K Patel

This is a library I just quickly put together from what I remember when I used to used the ESP6000 and Unidrive systems - All you need to do is call "Open and Initialise Axes" (note the Australian/UK spelling!) and then home each axis individually, and then call any of the other commands (Move Relative, Move Absolute, Stop, etc) - note: sue to an hardware limitation, you can only home one axis at a time, and that could take a while!
*** The DeveloperZone is not letting me upload the library - email me (address below), and I'll email it directly to you.
Like my answer? Give it a rating!
Christopher G. Relf
Certified LabVIEW Developer
[email protected]
Int'l Voicemail & Fax: +61 2 8080 8132
Aust Voicemail & Fax: (02) 8080 8132
E
ULA
1) This is a private email, and although the views expressed within it may not be purely my own, unless specifically referenced I do not suggest they are necessarily associated with anyone else including, but not limited to, my employer(s).
2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

MSMQ with Labview

I want to use the Microsoft Message Queue to communicate between applications on different machines. Does anybody have experience in using the MSMQ with Labview (in the .NET framework)? How do I send messages? The MessageQueue.Send method requires an object, and I don't know how to create this object format.

Jim,
please find attached an MSMQ send/receive example I've created with LabVIEW 8.2.1
To get it working, you need to do the following:
1. Make sure MSMQ is installed on all involved machines, senders and receivers. The attached ZIP archive contains batch files to install MSMQ on Windowx XP and Vista in the so-called workgroup mode (does not involve active directory integration).
2. Manually create a private queue named "labQueue" or whatever you like on the receiving(!) MSMQ target machine.
See http://technet2.microsoft.com/windowsserver/en/library/53f029d6-8824-4b1b-a312-167b03f5fca51033.mspx... for instructions to do so.
Important note: people often misunterstand the term "private" in a way that such queues would only work locally, within one machine. This is not the case, in fact there is no kind of local-only receive queue like there is no local-only TCP port binding and private queues are open to get messages from anywhere. They are just not public to the active directory queue management services so any sender needs to know the correct target address itself.
3. Adapt the "FormatName" string of the SampleSender.vi that it points to the queue on the MSMQ receiver, that is: Insert the queue name you've chosen and replace the IP with the address of the target machine.
Run both VIs, SampleSender.vi and SampleReceiver.vi and send single messages typed into the "myMessage" string control by pressing the "Send" button or create looped bulk messages with the corresponding boolean switch control.
To experience the coolness of MSMQ, send some messages from the running sender VI before the receiver was started, then start the receiver VI. Or run both VIs on 2 different machines, unplug the LAN connection of one while still sending messages and then plug it in again. MSMQ does all the caching for you in case one of the peers is temporarily unavailable. This rocks!
The VIs demonstrate a very straight forward use of the .NET System.Messaging namespace for synchronous MSMQ messaging. A more elaborate (and better) way included the automatic creation of non-exisiting receive queues and asynchronous message receiving with .NET events.
Greetings + have fun,
Hans
Attachments:
MessageQueue (MSMQ).zip ‏31 KB

CAN with LabVIEW

I am working on a project involving CAN and LabVIEW. Are there any decent tutorials out there on some of the basic functions and VIs for working with CAN in LabVIEW?

I assume you are using a National Instruments NI-CAN interface. If that's the case, your best bet is the "NI-CAN Programmer Reference Manual" (installed as a PDF in your NI-CAN folder). This manual documents all of the NI-CAN functions available in LabVIEW and shows the wiring diagrams for how to use each of them. You may also open the VIs from the NI-CAN function palette in LabVIEW and get context-sensitive help by toggling +H.
Another option is to examine the LabVIEW examples that come with NI-CAN. These demonstrate a wide variety of functionality, so you should be able to find something close to what you're trying to do. You can use the examples to get an idea of good NI-CAN programming techniques with LabVIEW, and possibly make minor modificati
ons to suit your specific application.

Deploy teststand with labview ui

Hi,
I'm using teststand now since 9 months and now I have to distribute my application to a testing machine. I have some questions about this process. But first I discribe my application:
I have a labview ui, which has 3 main tasks:
1.) Start selected teststand sequences for automatic testing.
2.) Give operator the possibility to manually control the testing environment (purely written in labview)
3.) Run continous data aquisition, which provides data for teststand and manual testing.
Sharing data between labview and teststand is done mainly via global variables (e.g. reference to tdms file). Because of 1.) and 2.) above teststand and labview share a lot of VIs for communicating with the testing environment.
OK, now my questions:
I'm searching for the best way to deploy this application via an installer. I know, that there is a teststand deployment tool (which I havn't used, yet) and I know how to build installers with the labview project manager.
1.) What about sharing of VIs and global variables between my teststand sequences and my generated labview exe? When I place my sequences in the workspace file for the teststand deployment tool, all referenced VIs are included in teststand. But Some of these VIs are also included in my generated labview ui. Will this generate a conflict?
2.) I was thinking about to create a teststand deployment without a workspace file. The sequences and all required VIs would be placed in the generated labview ui instead. Will the teststand sequences find the VIs inside of the ui exe?
3.) What about required drivers (e.g. daq-mx)? Should I create a labview installer of my ui with the required drives and install this, then create a teststand installer (perhaps including the ui, too) and install this, too?
Thanks for any help in advance.
Marc
CLD

Hi,
I would recommend the Deployment Tool for your TestStand and OI. I would also keep your Test Sequence files seperate from your TestStand Engine amd UI deployment.
[1.) What about sharing of VIs and global variables between my teststand sequences and my generated labview exe? When I place my sequences in the workspace file for the teststand deployment tool, all referenced VIs are included in teststand. But Some of these VIs are also included in my generated labview ui. Will this generate a conflict?}
This is going to cause you a problem because LabVIEW doesn't like / will not load the same VI into memory from two different locations.
The Deployment Tool will probably object as well therefore you will not beable to create a deployment package.
The Deployment Tool will place all the VIs that are called directly from TestStand Sequence Files as seperate VI's (not in a LLB) into the target folder. It will then create a support LLB containing all the subVI's used by the directly called VI's. If you have VI's that are called directly from TestStand and are also used as subVI's you will again have problems because the same VI can be loaded from two different locations.
2.) I was thinking about to create a teststand deployment without a workspace file. The sequences and all required VIs would be placed in the generated labview ui instead. Will the teststand sequences find the VIs inside of the ui exe?
No Teststand will not beable to find your VI's in the EXE. If you need to use the same VI's in both your OI and TestStand sequence file then create a DLL.
But I would recommend you keep the OI code seperate from your Test Code.
3.) What about required drivers (e.g. daq-mx)? Should I create a labview installer of my ui with the required drives and install this, then create a teststand installer (perhaps including the ui, too) and install this, too?
Install your drivers first. The IO should be installed as part of the TestStand deployment as this will register the various components correctly.
Regards
Ray Farmer
Message Edited by Ray Farmer on 08-06-2008 01:02 PM
Regards
Ray Farmer

Error -18004 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

Hi to all,
I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
The Problem is that I get the following error, saying that my VIs cannot be executed:
-18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
All my VIs were masscompiled with LabVIEW 7.1.1
How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
Thanks for you help,
- Caribe -
PS: I configured the adapter to use the LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

Hi Caribe,
Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
Thank you,
Sasi

Can't install niDAQ 6.9.3 with Labview 8.0?

I'm trying to install the legacy drivers for my new/used DAQCard-1200 for use with Labview 8.0. For reference, I've also installed Labview 8.2 evaluation. I've downloaded both niDAQ and Labview 6.1 eng support and ran setup with it all in one directory. The problem is that the Labview 6.1 Support option has a green checkmark next to it and the description says it "won't be installed", that it is already installed and that the installed version is higher than what I'm trying to install. Any suggestions?

At this point I would recommend attempting to:
1) Make sure that National Instruments Software is not listed under Add/Remove Programs (and if it is, uninstall MAX and go from there). Should look something like this:
I don't mean to harp on this point, however it is very odd that the folder is not there at all...
2) Possibly use System Restore to revert back to a point before you 'manually uninstalled'
3) You could also try to use the Driver CD. That should detect the software on the system and you may be able to remove/modify the software that way.
If this does not work, then we may have to work on this "offline" and have me contact you directly. If you give me permission, I can get your contact information from our web team and we can go from there.
Message Edited by Neal M on 10-23-2007 04:24 PM
Neal M.Applications Engineering National Instruments www.ni.com/support
Attachments:
AddRemovePrograms.JPG ‏115 KB

Where can I find example LabVIEW VIs for the NI-USRP?

There are several sources of example LabVIEW VIs for the NI USRP:
We have established a NI Community "NI USRP Example LabVIEW VIs" where you can find example VIs from us (NI) and the community.
The NI-USRP driver installs a variety of example VIs to the to the following folder on your PC:
<LabVIEW Installation path>\examples\instr\niUSRP
where you should replace <LabVIEW Installation path> with the root folder of your local LabVIEW installation. For instance, my Windows 7 32-bit PC here has LabVIEW 2011 installed and the examples can be found here: C:\Program Files\National Instruments\LabVIEW 2011\examples\instr\niUSRP
I've installed the NI-USRP driver, but I can't seem to find the new examples in the LabVIEW Example Finder. Where are the example LabVIEW VIs installed by the NI-USRP driver?
Although the NI-USRP driver does indeed install examples, the current NI-USRP 1.1 release does not update the LabVIEW Example Finder with entries for these examples. To find the examples, you can navigate the Windows Start Menu to the following location:
Start Menu\Programs\National Instruments\NI-USRP\Examples
This Start Menu entry includes several Shortcuts that point to folders that are the home to example VIs.
Sam Shearman

Hello,
It looks like Agilent/HP makes the 8990A, but I was not able to find a driver for it that we or Agilent has written for this device.
Since I am not familiar with the 8990A, I cannot recommend which drivers might be similar, but you are pointed in the right direction. Agilent themselves might know more about which models use similar command sets so that you can modify a driver easily.
Hope this helps.
Scott B.
Applications Engineer
National Instruments

Example VIs for winsock with LabVIEW 7.0

Similar Messages

Maybe you are looking for