"I am looking for LabVIEW instrument drivers for a PTS 160 Frequency Synthesizer

looking for instrument driver for PTS 160 Frequency Synthesizer

"Unfortunately I was unable to find a driver for this instrument at http://ni.com/idnet. This leaves you with one of a couple options. It may be possible to modify an existing driver to work with this instrument. Otherwise, http://www.ni.com/devzone/idnet/other. htm states a few options to obtaining a driver. NI only writes drivers for standalone instruments in the eight IVI classes(DMMs, Scopes, Function Generators, Switches, Power Supplies, Power Meters, RF Signal Generators, and Spectral analyzers) that communicate via GPIB, Serial, or TCP/IP, so a driver cannot be written for your instrument. It would also be beneficial to notify the instrument manufacturer, they often have drivers for multiple programming languages. If they do not, you may want to hire an
Alliance Member to write an driver for you.
Alliance Member Directory
http://www.ni.com/alliance/ alliance_member.htm"

Similar Messages

I am looking for LabVIEW instrument drivers for Audioprecision test equipment. It looks like you do not support any Audioprecision intruments?

I also do not see any support for Keithley 2420 Sourcemeters.

Hi Kristen,
If you search www.Keithley.com you will find an instrument driver for the 2420 device. Go to the "downloads" section and search for 2400.
I am not sure what you mean by Audioprecision instruments. If you had a specific driver in mind, I would check with the instrument manufacturer. Often times they develop and support the drivers since they know the instruments far better.
If you do not see the driver on their website, please submit a request at http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/ and with the instrument manufacturer.
We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
If you would like to try developing your own instrument driv
er (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at:
http://www.ni.com/devzone/idnet/development.htm
Hope this helps out!
Best Regards,
Aaron K.
Application Engineer
National Instruments

Same error cluster for different instrument drivers?

Hi All...
mz question is regarding error cluster wiring for different instrument drivers. As u can see from attached file, i have 3 different devices with drivers. At the beginning i initialize and configure each one by wiring adresses and error clusters individually. After that i want use measruement vi's with an order. That s why I would like to use same error cluster for those 3 different measurment drivers as illustrated in the picture. is it possible?
second question is that at the beginning in the initializing process, i do not set any order of those 3 devices. VI would try to initialize all of them at the same time which is not possible due to serial GPIB? Do i need to determine any sequences of initializing of devices?
thanks
Attachments:
vi scheme.JPG ‏19 KB

Your sceme is fine. The error cluster is a generic container to pass any error that can occur from one function to the next. Normally, if a function has it's Error In terminal connected and an error is passed in from a previous function, that function will not do naything except pass the error through so it can be handeled in you code.
Since your running on serial, just "serialize" your initialization functions using the error cluster to set the order. This way only one will be running at a time. It doesn't matter what order.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Best way to distribute LabVIEW Instruments Drivers.

Hello,
I'm trying to stick to the standards described just there:
Developing LabVIEW Plug and Play Instrument Drivers
Instrument Driver Development Tools and Resources
Instrument Driver Guidelines
However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
Here is a couple of questions I'm not really sure about their answers:
Is it okay to use a .NET dll and to make some calls?
Is it fine to hide the Block Diagram? With passwords in the Drivers
Can we put prevent the modification
In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
Solved!
Go to Solution.

Ehouarn wrote:
Hello,
I'm trying to stick to the standards described just there:
Developing LabVIEW Plug and Play Instrument Drivers
Instrument Driver Development Tools and Resources
Instrument Driver Guidelines
However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
Here is a couple of questions I'm not really sure about their answers:
Is it okay to use a .NET dll and to make some calls?
Is it fine to hide the Block Diagram? With passwords in the Drivers
Can we put prevent the modification
In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
Not sure about 1) but 2) and 3) are definitely a no go if you want your library to be distributable through the ID network. The standard only allows for DLLs in that are really developed in C but would require you to also distribute the C code as far as I understand.
OOP may not be a problem.
Packed Library is definitely not something you want to do. They only work in the LabVIEW version in which they were created. You will hate the moment you decided to go with packed libraries as requests come in for other LabVIEW versions and your drivers are bashed on all discussion forums as being a pain in the ass to use.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Need help in converting old LabVIEW instrument drivers to new version.

Hello,
I just rented a Tektronix DG2020A data generator. I did not find any instrument drivers for the DG2020A on the Instrument Driver Network, although there are drivers for DG2040 that could be used to some extent. With the instrument, I also received a floppy with example programs. This does include LabVIEW drivers for the DG2020A. However, when I tried to load the VIs, I received an error message that the VI version 3.1 is too old to be converted to 7.1. Can someone at NI help with the conversion? It would be very useful.
Thanks.

There is a driver available for the DG2020 on NI's site. Models supported are the DG2020, DG2030, and DG2040. Available in both 7.x and 8.x.

Looking for Keyence Instrument driver for LV.

Looking for instrument driver for LV developed for the Keyence LS-7500 series micrometer. Has anything seen any or done this already? Any help would be greatly appreciated. BTW I have already checked NI's listing of instrument drivers to no success.

Hello-
There are no drivers listed for this instrument at http://ni.com/idnet. You may want to contact Programmed Test Sources to see if they have a LabVIEW driver for their instrument. If they don't, you can easily create a low-level driver by configuring an I/O assistant VI for each function in the manual. Once you have this low level driver you can just combine functions to make higher level VIs. Alternatively, you can hire an Alliance Member to write an driver for you.
Alliance Member Directory
http://www.ni.com/alliance/alliance_member.htm

Looking for DOS based drivers for model ct4

i am looking for dos based dri'ves for model ct4730 for a DOS gaming machine that i am building.
any help would be great thanks.
emiual me direct at [email][email protected]][email protected][/url] thanks in advance.. i cant wait to play rise of the triad and the original c+c

I looked for a driver at http://zone.ni.com/idnet97.nsf/browse/ but was unable to find one for the Denver Instruments' Balance. National Instruments develops Instrument drivers based on demand and popularity. If it is a commercially available instrument, you can officially request one at:
http://zone.ni.com/idnet/other.htm
We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one in the future.
If you would like to try developing your own instrument driver, we have documentation, model instrument drivers, and driver templates to help at :
http://zone.ni.com/idnet/development.htm).
We also have a syndicate of third party vendors that specialize in National Instruments' produc
ts and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance"
Ryan Mosley
National Instruments, Applications Engineer
http://www.ni.com/exchange

Need documentation for writing GPIB drivers for RTOS-32 using Borland C 5.51

Greetings,
I need to develop GPIB drivers (using the NI GPIB card) for the RTOS-32 operating system (by On-Time). I am using Borland C 5.51 as the compiler. I am looking for info/examples on writing/porting low level drivers for the GPIB. The examples I have found come with the low levels drivers in an object file which you link in, but nothing on how to write the low level drivers.
Any pointers on what documentation/examples that I should look at would be greatly appreciated.
Thank you for your time,
Fred A. Ennerson
Electro-Optical/Sonatech

Fred,
National Instruments offers a DDK for customers to develop NI-488 drivers for operating systems that we do not support directly. Refer to the following product data sheet on using the NI-488DDK. http://www.ni.com/pdf/products/us/4gpib664.pdf
Craig A
National Instruments Engineer

What labview package do I need to develop third party labview instrument drivers?

We have been asked develop labview 6.1 drivers for a third party data acquisition card. What Labview package do we need to buy, basic, pro etc?

The only way to really program for a third party data acquisition card in LabVIEW would be through a "call library function node". You would have to call the dll that third party card developer provided. As far as I know all LabVIEW packages contain a "call library function node". I would recomend buying at least the full development environment because of some of the additional features in that package.

Help needed by Good Samaritans for info on Drivers for RS232 / USB ports.

Dear all,
I would first like to thank you for taking the time to read my message.
I would like to ask all you proffesional LV developer how difficult it
might be to write the drivers for a bluetooth-RS232(or for a Wireless
LAN ethernet/USB access point) device using LV. Would it be better to
write the drivers in C++?
I have finished the LV Basics 1&2, though we did not learn something helpfull for my case.
Are there any usefull examples i should look at?
The signal transmitted would have a data rate of about 0.5MBbs and the LV program would just display and store the data.
Thanks for your help

Bogiasac
Couple of quick points then I will allow the LV Community to reply to the specifics. From NI's point of view we would recommend that you use the development language that you feel most confident in, so if you are a C++ guru then use C++. Another point, you mention that you attended the LV Basic training classes. I conclude from your comments that you were looking for specific training (while attending did you raise this with instructor at the time?), these training classes are an introduction to the LV environment and set out the ground rules how to best develop a LV application. Our intermediate courses go into greater detail into advanced LV features - though for some this is still not deep enough (future developments in that for LV 8.0 users soon). If you are looking for specific training please contact our Training Co-ordinator in the UK and she will be happy to advice.
On the Bluetooth question, LV has Bluetooth tools built in. These can be found in the Communication palate under Bluetooth (this depends on which version of LV you have, Base or FDS). Please use these VIs to develop you Bluetooth application. There are 9 Bluetooth examples shipped with LV, these can be found by using the “find examples” in the help menu.
Kind regards
Joe
NIUK

Deploy teststand system Labview instrument drivers

I'm trying to deploy a teststand application but I have an error with some Labview VI's.
I'm using some VI's to control an Agilent 34401A, so Labview instruments library that
is in the default package was used. The error says that Labiew Could no open the following VIs...
I don't want to install the Labview development system on the target machine, so I don't know
how to fix this problem.
I tried to copy the library to a different location an removing the VIs that are not wired (VI Tree.vi),
but I have the same error. (On the sequence was changed the path to the new VI location).
Thanks
Marcos

Marcos,
You can execute VIs using the LabVIEW Runtime Engine, but all of the source VIs must be processed to collect their required dependencies and insure they are compiled in the current version of LabVIEW. The Deployment Utility process VIs from your sequences automatically. The TestStand Reference Manual has a chapter on deploying TestStand systems that should help you get started.
-Rick Francis

Looking for Labview instrument programmers in/near Michigan

We are looking to hire a programmer familiar with Labview for high speed instrument control and data analysis applications

pico wrote in message news:<[email protected]>...
> We are looking to hire a programmer familiar with Labview for high
> speed instrument control and data analysis applications
Hi, I am exactly what you want! Here is (part of) my cover letter.
Please email me where I can send the resume.
In addition to my broad educational background including two Masters
Degrees in Electrical Engineering and Physics, numerous Computer
Science courses taken, and twelve years of diverse experience in
programming, system administration, and support, I am a National
Instruments Certified LabVIEW Developer. As you can see on the
National Instruments website, there are only 167 people worldwide and
4 including me in the State of Illinois who were granted this title. I
have a history of numerous successful projects in the areas of
industrial automation, control and data acquisition. In particular, I
have implemented several LabVIEW test systems projects including the
following:
- Real-Time Electron Beam Doses Monitoring, Beam Parameters
Measurement, and Ion Charge Measurement Systems for Steris
Corporation;
- Control and Data Acquisition Program for an Electron Spectrometer
System in the Western Michigan University Accelerator Laboratory;
- LIMS II (Temperature Test),Surge Test Automation, Locked Rotor Test,
Variable Ambient Chamber Control and Data Acquisition for Underwriters
Laboratories (UL);
- Abrasion Wear Test for Caterpillar;
- Distributed Data Acquisition and Reporting System for Hydraulic
Spray Nozzles Testing for Spraying Systems Co.
Descriptions and code examples of projects I have done are available
upon request.
The latest projects utilize my own architecture which allows creating
complex applications as a collection of components that have uniform
structure, but different purposes. Each component runs independently
providing services to other components and exchanging data via
standardized queued messages. The resulting code looks similar
regardless of specific functionality. It is easily readable and
modifiable by developers other than the author.
I also have done several projects involving HMI, digital I/O, motion
control, communication between a PC and PLC's, using Visual Basic,
Think & Do, Steeplechase and other software tools.
My experience and background enable me to master any software
development tool quickly, making me a perfect candidate who can always
keep up with the ever-changing world of computer technologies.
I am looking forward to discussing this opportunity with you.
Sincerely,
Stanislav Rumega
(847) 437-0794(home)
(312) 255-8757(office), (312) 925-0780(cell)
[email protected]

LabVIEW serial drivers for CAL Controls 9500.

Anyone already created a LabVIEW Modbus serial driver for the Cal Controls 9500 process controller. Please let me know if you have.
Best Regards
Dunc

Same question, has anyone made a serial driver for this yet?

MNC looking for LabVIEW & teststand developers for Bangalore division

Location: Bangalore
Qualifications:
Degree in Electronics/Electrical/Instrumentation Engineering.
Experience Profile:
   6+ years prior automating software development experience including coding, test and integration.
  Proficient in LabVIEW; NI certified as LabVIEW developer(CLAD/ CLD) is added advantage.
Proficient in Test Stand.(CTD is added advantage)
  Experience in Vector canoe is added advantage.
Sound knowledge of Data acquisition,VISA,Serial communication,CAN Protocal other NI hardware.
Automotive domain knowledge and infotainment knowledge is added advantage.
Email your resumes to: [email protected]
Please do not post your resumes as reply to this message in this forum.
Please shoot a mail if you have any questions\queries. I will forward the resumes to the HR and I don't have any authority in hiring.

Can you let us know the company name & the position.

Looking for 2 signed drivers for Probook 470 G1

Ok, thanks, I'll try that. For now I tested the Ralink version 11.0.759.0 available at HP. Manually it installed well with command-line setup.exe /s /v"/qn LOGPATH=\"C:\BT_470G1.log\" REBOOT=Suppress /l*v \"C:\BluesoleilMsiInstall.log\" Now I'll see if it installs with SCCM. I'll post my findings

Hi: The only suggestion I can offer is to try each of the ones listed on the revision histor tab starting with the newest one. http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5405417&swItemId=ob_147890_1&swEnvOid=4059#tab-history

"I am looking for LabVIEW instrument drivers for a PTS 160 Frequency Synthesizer

Similar Messages

Maybe you are looking for