Is this setup capable of Labview controlled analog or digital output to 5V?

DAQCard AI-16XE-50 to a CB-68LP using Labview 6.1 and NI-DAQ 7. Win2k pro

chazimusmaximus,
For your specific DAQCard AI-16XE-50, the only output you can perform is digital output since there are no analog output lines on this board. Digital ouptut with NI-DAQ 7.0 will work with LabVIEW 6.1, but you can only use the Traditional DAQ VIs. Windows 2000 and the CB-68LP are both fine in this combination.
For example programs, simply launch LabVIEW 6.1 and go to Help >> Find Examples. Then follow the path Hardware Input and Output >> DAQ >> Digital Input and Output >> E-series to choose the example that works best for you.
Have a great day.

Similar Messages

PID Control - analog input, digital outputs

Hello everyone,
I am trying to use the PID toolkit to convert my existing feedback control system to one using PID or just PI whatever works best. Problem is that the tutorials out there discuss in detail about obtaining Analog inputs and using the PID output to control an analog output. Are there any tutorials that show how I can control my process variable which is an analog input by using the PID output to generate digital outputs?
Basically, what I am doing is controlling the incline of my device with two digital outputs that control two solenoid valves. The angle is calculated from a calibration curve that plots distance sensor voltage with Angle. Any help would be immensely apprecitated. I want to try this out on my own before I post some vi's. Thanks!
V
I may not be perfect, but I'm all I got!

That is exactly what I am doing currently. I have error bands specified around the target to make sure that it doesn't oscillate. But, under load conditions such as pulsed load conditions, the device goes out of bounds and the values trigger to correct for it. But, what I need is seemless or atleast seemless correction. Currently what I see is sudden adjustments to the incline. Please find attached what I am currently using. I am trying to get a more finer solution if at all possible.
Note: Within 5% of the target = NO action
Between 5% and 15% = Pulsed ACtion ( DO On for Pulse width time)
Greater than 15% = continuous action until it reaches Pulse band
I may not be perfect, but I'm all I got!
Attachments:
TDML_subElevationControl.vi ‏41 KB
TDML_subPulsedValveFuntion.vi ‏16 KB

Airtunes - Analog and Digital output at the same time?

Howdy,
This may seem strange to ask, but can the Airport Express output audio in digital and analog formats at the same time? Is there a strange splitter cable that could do this for me?
I recently learned that most AV receivers with digital inputs cannot output digital sources to their analog zone 2 outputs. The usual work-around is to connect their digital sources to the receiver by both analog and digital cables.
Mikael

I just learned the same thing. Does connecting the digital and analog connections to your reciever work ? Did you connect them to the same source or assign different sources for each? Thanks,

Creating a control sequence of digital outputs with timing

I'm trying to create a controls system for a cleaning process. I am controlling a pump, heater, and several solenoid valves using relays that I am opening and closing with the +5V from my USB 6008 and each relay goes to one of the digital I/O lines, where I provide a sink to switch the relay.
I am using the front panel as the user interface for the machine, so the user can specify three different processes, so I'm using an event structure to call each process. An example of the steps in the process are as follows:
1. Open relay #1 (solenoid valve)
2. Open relay #4 (heater)
3. Wait 30 seconds (while relays #1 and #4 are still open)
4. Close relay #4
5. Close relay #1
6. Open relay #2 (solenoid valve)
7. Wait 5 seconds (while relay #2 is still open)
8. Close relay #2
I am trying to use a framed sequence structure within the event cases, with the DAQ Assistant saying which lines are sinks and which are also outputting +5V (no delta, keeps relays closed), but I don't think this is working and will bog down the system if it did. I think inverting the lines will make it so the lines nominally output the +5V so I just need to send it a sink when I want to close the relays, and make sure it keeps doing that while it waits so the process can be completed.
What is the best way to do this? I've used Labview before, but I'm hardly a pro, so any help would be greatly appreciated.

As nijams mentioned a state machine architecture is a good place to start. In case you are unfamiliar in how to implement this in LabVIEW there is a blank state machine template available in LabVIEW. When you create a new VI select From Template->Frameworks->state machine. In addition I've included a link to a simple example posted on our NI Community.
State Machine Example.zip: https://decibel.ni.com/content/docs/DOC-15515
Regards
Regards,
Isaac S.
Applications Engineer
National Instruments

Macbook Pro 4,1 (early 2008) is the DVI port analog or digital?

I have been tasked with a slide show presentation on a family member's HD TV using my MacBook Pro 4,1. The TV is a slightly older big screen TV without HDMI inputs. I would lke to use the component (YPbPr) inputs on the TV rather than VGA. VGA degrades the image appearance too much.
I purchased a "ViewHD" HDMI input (Digital) to YPbPr (analog component) Output Switch Converter with the thought of using my 2nd Gen Apple TV (ATV) to connect the ATV via HDMI into the Converter and output the component YPbPr to the TV set. I am looking for a simple, elegant solution as I know this question will rear it's ugly head again.
First, I could find no resources that discusses the output of the DVI port on the MBP. Is it DVI-D, DVI-A, or DVI-I?
Is there an adaptor out there that I can use to change the DVI out on the MBP (if it is digital) to HDMI so I don't have to use the Apple TV?
Any help or solutions would be greatly appreciated.
TIA

The DVI connector on a MacBook Pro supports both Analog and Digital output.

Is Digital Output worse than analog output in 5.1 set

Hi, I've read in this forum (I don't remember where) that Digital Output doesn't sends 00% of sound, instead it reduces its quality by something (encode / decode) so I would like to know your opinions and if this is true or false?
I have plans for using 5. sound.

The sound card, as I said before, will send out DolbyDigital or DTS recorded on a DVD-Video. This is because the encoding process happend in the studio, at the making of the disc.
Any other surround sound, created in your computer (like the games) will not be encoded surround on the digital out. That goes for X-Fi also.
And Yes, the DD and DTS are compressed formats, but are waaay batter that any other compressed format. DTS in my opinion is the best, but occupies more space on disc (higher bitrate).
The only uncompressed surround is the one on the SACD discs or the one on DVD-Audio (actually this is compressed but without loosing information, kinda like the zip files).
There are sound chipsets capable of Dolby Digital encoding: one is the nVidia's nForce2 motherboards with SoundStorm (not in production anymore). This is the same chip used in XBOX (that has DD out).
The others are some chips made by C-Media: CMI8768+ (only the PLUS variant) and CMI8788 (this has DTS encodin also). But the encoding is done software, and occupies some 0% of the processor time. Not really good...
Message Edited by SoNic2367 on 04-2-2006 08:2 PM

Senior LabVIEW Controls Engineer--GOLDEN, CO

JOB DESCRIPTION
Vehicle Projects Inc is seeking a full-time, senior controls engineer for the development and demonstration of high-power hydrogen-fuelcell rail vehicles. For background on our rail-vehicle program, please google the keywords: (“fuel cell locomotive” “vehicle projects”). Responsibilities of the position include:
Overall fuelcell powerplant control system design, including integration with the vehicle control system
Computer modeling and simulation of hybrid powerplant operation
Design and development of complex LabVIEW control system applications
Preparation of electrical drawings, specifications, and test plans
Participation in laboratory and field testing of subsystems and vehicles
Data analyses
Part-sourcing and ordering of hardware
Support of hardware-build activities
Occasional technical support to other staff members’ projects, including research
Travel to build-facilities, test sites, and demonstration sites (based on the past 12 months as a sample, this position requires 17 % of work-days on travel)
QUALIFICATIONS
The successful candidate must demonstrate the following qualifications:
Self-motivation and ability to learn quickly
Self-confidence to thrive in the high-risk, high-reward R&D environment
8-10 years of experience with LabVIEW, including 4 years each with Realtime and FPGA Modules
Experience with the National Instruments cRIO platform
Experience with CAN communications
Familiarity with Ethernet networking
Ability to work closely with skilled trades people and understand the practical side of system design
Excellent communication skills, including the ability to interface with multiple international design teams
Excellent hands-on and troubleshooting skills
MS degree in Electrical Engineering, Computer Science, or Controls Engineering is preferred
Interest in scientific disciplines and having a scientific mindset are a plus
While the ability to learn fuelcell and hydrogen technology is essential, in-depth knowledge of fuel cells and hydrogen is not a prerequisite for the appointment.
COMPANY
Vehicle Projects Inc (since 1998), based in Denver/Golden, Colorado, serves the transportation industry by developing and demonstrating prototype hydrogen-fuelcell vehicles that address worldwide societal problems such as energy efficiency, energy security, and global climate change. Once a fuelcell prototype vehicle is built and tested, we provide it to industry for demonstration under working conditions.
The company has two independent associated nonprofit research organizations: Fuelcell Propulsion Institute (since 1996) and Supersonic Institute. The Fuelcell Propulsion Institute laid the foundations for the current development of railway locomotives. Supersonic Institute conducts research and educates the public on supersonic vehicles fueled by hydrogen.
Industrial clients and co-funders of our projects have included Placer Dome Mining Company, Newmont Mining Corporation, Caterpillar, Mitsui & Co (Japan), and BNSF Railway Co. Government funders have included the US Department of Energy, US Department of Defense, National Institute of Occupational Safety and Health (NIOSH), Government of Canada, and Government of Japan.
Our state-of-the-art facility, constructed in 2007, is part of the burgeoning west-Denver (Golden) corridor of renewable-energy companies, including the nearby National Renewable Energy Laboratory (NREL). Metro Denver (www.metrodenver.org), with a population of three million, is a well-managed city located at the base of the Rocky Mountains. With an average annual temperature of 50 F, low humidity, and 300 days of sun, its moderate climate is one of many attractive features of the city. Its citizens are in the top national percentiles for fitness, health, and formal education.
We believe our company’s most important asset is its people. New employees are selected with care, and successful employees are nurtured and encouraged to remain with the company through empowerment, highly competitive compensation, a generous benefits package, job-related training, profit-sharing, and a pleasant work environment.
COMPENSATION
A person of the caliber we are seeking will receive an above-average salary, employment contract, and a generous benefits package, including profit sharing.
APPLICATION
Apply by 4 April 2011 by sending an email-attached MS-Word letter of application, resume, salary history, and the names and contact information of three references. A portfolio in support of the application is desirable. The letter of application, addressed personally to the president of the company and using proper style for a business letter, should specifically address your qualifications and experience to undertake the stated responsibilities. Only applicants who write such a letter will be considered. The selection process includes more than one interview, a LabVIEW proficiency test, and a writing-skills evaluation. Please send application materials to [email protected].

I am a control systems engineer with 16 years of experience designing and building large systems using LabVIEW in Albuquerque NM and working currently for TEAM Technologies Inc. almost 15 years.
I hold a Master Degree in Space Power Systems graduated from Moscow Aerospace University.
I invented and implemented a message-driven and scripting controlled LabVIEW architecture which I presented couple times at NIWeeks, published in LTR, and local NI and ALVIN seminars. This architecture I was successfully used to develop projects for SNL (National Lab), WSTF (NASA), EMCORE, and etc. firms and organizations.
My expertise areas are: 1) Mechanical Engineering; 2) High Temperature Energy Converters; 3) Thermodynamics 4) Digital and Analog Electronics; 5) Programming: LabVIEW, C, embedded microprocessors (ARM, Cortex); Distributed hard real-time control with PXI and Compact RIO instrumentation.
I have published 45 scientific papers and have six patents.
I am NOT a certified NI LabVIEW programmer, because I believe that scientists and engineers has to have Degree Diploma only.
LabVIEW is just a programming tool nothing more.
Regards,
Youri Djachiachvili
Aerospace Engineer.
email: [email protected]

Labview controll using Multisim feedback

Hello,
I would like to control a circuit in Multisim with a few simple analog and digital signals from a Labview VI. The circuit running in the Multisim simulation would generate analog and digital signals to be fed back to the Labview VI which would intern modify its control signals being sent to the circuit.
I have Labview 2011 and Multisim 11 but not NI's Control Design and Simulation Module. Is there a way to do simple circuit simulation with feedback without added software (modules)?

Hi,
In V11, you can import a LabVIEW signal into Multisim by using the LVM source which is located in the Source group, and you can also export simulation data to LabVIEW through the grapher. The feature you are looking to use is called LabVIEW Multisim co-simulation and this feature allows Multisim and LabVIEW to pass data back and forth as you run the simulation in both products at the same time. This feature was introduced when Multisim 12 was released, you cannot do this in V11.
Tien P.
National Instruments

Control analog output based on analog input

Dear forumers,
I am pretty new to the labview programming so excuse me if this was posted before.
I use: Labview 8.5 + PCI 6229
I want to create a real time feedback: to control analog output based on analog input. The task is very simple - if the ai1 (analog input 1) voltage is larger than a constant, then decrease the voltage of the ao1 (analog output 1) by a constant. Otherwise increase the voltage of ao1 by the same constant.
All should work for 10 seconds.
I have tried to implement this using 2 daq asistants and various methods. The problem is that I get the whole signal recorded from the ai1 ( 10 seconds) and then modified and released to the output (another 10 seconds). The execution takes 20 seconds instead of 10 and it is not realtime at all.
Is it a must to make vi in "run continuous" mode to make it work ?
Please help :}.
I am attaching 2 examples.
1. Main idea what I am trying to accomplish
2. Very simple example that still does not work in real time simultaneously.
Attachments:
example-main.vi ‏180 KB
example-simple.vi ‏147 KB

nooto wrote:
Thank you for your suggestion.
I understand the simple arithmetic you are talking about. However I do not understand why it takes 20 seconds instead of 10 to complete the task. In other way to say - why it reads the whole input first (10 seconds) then write the output ( 10 seconds).
Why doesn't ir read and write simultaneously?
If I use Elapsed Time function - what feedback response time can I expect ? Is it good to use Elapsed Time if i need fast response time? In my application i would I need about 1 milisecond response time. Currently in the example the rate is 50 Hz, later I would like to change the rate to 1000.
You simply don't understand the underlying paradigm of LabVIEW -
dataflow. You have a dependency between the first DAQ Assistant and the
second. The second simply will not start until the first finishes. There
is no way around that given your condition that the output depends on
what you read.
If you want 1 millisecond response time then you will have to swithc to a real-time OS. Windows does not have that kind of resolution and there is way to much jitter.

Using usb to serial adaptor , how do I select this port from within labview

Hi
I am using a usb to rs232 adaptor , how can I select this port within labview as all I can see is the com 0, com 1, lpt ports .
Any help appreciated
Brett
Snr Mining Engineering Technician
Western Australian School of Mines
Curtin University of Technology,
Locked Bag 22, Kalgoorlie Western Australia 6430
Ph: 08 90886159 Fax: 08 9088 6151 Mobile: 0407441251
Web http://research.wasm.curtin.edu.au/

vicky wrote:
Hi Brett,
yeah its easier tohandle and i think cheaper also,i found it easier to install also,so better go in for the USB stuff.
cheers
vicky
While the many USB adapters seem to be easier to handle, we have had some bad experiences. Their stability is not always up to the task for industrial applications. This might not be an issue when you only use them to control your RS-232 lab equipment for manual experiments, but in our case we have fully automated lab systems running, where LabVIEW controls sometimes up to 8 serial devices and those applications are supposed to run day and night, if possible for many days in a row without interruption. With many of those noname USB-RS232 adapters we noticed various kind of problems. It could range from intermittent communication errors (which could be handled by additional code in our software to retry communication on such errors) to complete failure of the RS-232 port after some time, which could only got back online by unplugging and replugging the USB adapter.
For our purpose this was completely unacceptable and we ended up using ENET-RS232 devices instead which are working fine for months in a row.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Is this roughly how the labVIEW Execution Systems work?

I've not taken a class in OS design, so I don't know the strategies used to implement multitasking, preemptive or cooperative. The description below is a rough guess.
LabVIEW compiles Vis to execute within its own multitasking execution environment. This execution environment is composed of 6 execution systems. Each execution system has 5 priority queues (say priorities 0->4). Vis are compiled to one or more tasks which are posted for execution in these queues.
An execution system may either have multiple threads assigned to execute tasks from each priority queue, or may have a single thread executing all tasks from all priority queues. The thread priorities associated with a multithreaded execution system are assigned according to the queue that they service. There are therefore 5 available thread priority levels, one for each of the 5 priority level queues.
In addition to the execution queues, there are additional queues that are associated with tasks suspended in various wait states. (I don't know whether there are also threads associated with these queues. It seems there is.)
According to app. note 114, the default execution environment provides 1 execution system with 1 thread having a priority level of 1, and 5 execution systems with 10 prioritized threads, 2 threads per priority queue. NI has titled the single threaded execution system "user interface" and also given names to the other 5. Here they will be called either "user interface" or "other".
The "user interface" system is responsible for all GUI actions. It monitors the keyboard and mouse, as well as drawing the controls. It is also used to execute non-thread-safe tasks; tasks whose shared objects are not thread mutex protected.
Vis are composed of a front panel and diagram. The front panel provides an interface between the vi diagram, the user, and the calling vi. The diagram provides programmatic data flow between various nodes and is compiled into one or more machine coded tasks. In addition to it own tasks, a diagram may also call other vis. A vi that calls another vi does not actually programmatically branch to that vi. Rather, in most cases the call to another vi posts the tasks associated with the subvi to the back of one of the labVIEW execution system�s queues.
If a vi is non-reentrant, its tasks cannot run simultaneously on multiple threads. This implies a mutex like construction around the vi call to insure only one execution system is executing the vi. It doesn�t really matter where or how this happens, but somehow labVIEW has to protect an asynchronous vi from simultaneous execution, somehow that has to be performed without blocking an execution queue, and somehow a mutex suspended vi has to be returned to the execution queue when the mutex is freed. I assume this to be a strictly labVIEW mutex and does not involve the OS. If a vi is reentrant, it can be posted/ran multiple times simultaneously. If a vi is a subroutine, its task (I think there is always only one) will be posted to the front of the caller's queue rather than at the back of the queue (It actually probably never gets posted but is simply mutex tested at the call.) A reentrant-subroutine vi may be directly linked to its caller since it has no restrictions. (Whether in fact labVIEW does this, I don�t know. In any event, it would seem in general vis that can be identified as reentrant should be specified as such to avoid the overhead of mutexing. This would include vis that wrap reentrant dll calls.)
The execution queue to which a vi's tasks are posted depends upon the vi execution settings and the caller's execution priority. If the caller's execution priority is less than or equal the callee's execution settings, then the callee's tasks are posted to the back of the callee's specified execution queue. If the caller's execution priority is greater than the callee's specifications, then the callee's tasks are posted to the back of the caller's queue. Under most conditions, the vi execution setting is set to "same as caller" in which case the callee�s tasks are always posted to the back of the caller's execution queue. This applies to cases where two vis are set to run either in the other execution systems or two vis are set to run in the user interface execution system. (It�s not clear what happens when one vi is in the �user interface� system and the other is not. If the rule is followed by thread priority, any background tasks in the �other� systems will be moved to the user interface system. Normal task in the �other� systems called by a vi in the �user interface� system will execute in their own systems and vice versa. And �user interface� vis will execute in the caller�s �other� system if the caller has a priority greater than normal.)
Additionally, certain nodes must execute in the "user interface" execution system because their operations are not thread-safe. While the above generally specifies where a task will begin and end execution, a non-thread safe node can move a task to the �user interface� system. The task will continue to execute there until some unspecified event moves it back to its original execution system. Note, other task associated to the vi will be unaffected and will continue to execute in the original system.
Normally, tasks associated with a diagram run in one of the �other� execution systems. The tasks associated with drawing the front panel and monitoring user input always execute in the user interface execution system. Changes made by a diagram to it own front panel are buffered (the diagram has its own copy of the data, the front panel has its own copy of the data, and there seems to be some kind of exchange buffer that is mutexed), and the front panel update is posted as a task to the user interface execution system. Front panel objects also have the advanced option of being updated sequentially; presumably this means the diagram task that modifies the front panel will be moved to the user interface execution system as well. What this does to the data exchanged configuration between the front panel and diagram is unclear as presumably both the front panel and diagram are executing in the same thread and the mutex and buffer would seem to be redundant. While the above is true for a control value it is not clear whether this is also true for the control properties. Since a referenced property node can only occur on the local diagram, it is not clear it forces the local diagram to execute in the user interface system or whether they too are buffered and mutexed with the front panel.
If I were to hazard a guess, I would say that only the control values are buffered and mutexed. The control properties belong exclusively to the front panel and any changes made to them require execution in the �user interface� system. If diagram merely reads them, it probably doesn�t suffer a context switch.
Other vis can also modify the data structure defining the control appearance and values remotely using un-reference property nodes. These nodes are required to run in the user interface system because the operation is not thread-safe and apparently the diagram-front-panel mutex is specifically between the user interface execution system and the local diagram thread. Relative to the local diagram, remote changes by other vis would appear to be user entries.
It is not clear how front panels work with reentrant vis. Apparently every instance gets its own copy of the front panel values. If all front panel data structures were unique to an instance, and if I could get a vi reference to an instance of a reentrant vi, I could open multiple front panels, each displaying its own unique data. It might be handy, sort of like opening multiple Word documents, but I don�t think that it�s available.
A note: It is said that the front panel data is not loaded unless the front panel is opened. Obviously the attributes required to draw an object are not required, nor the buffer that interfaces with the user. This rule doesn�t apply though that if property references are made to front panel objects, and/or local variables are used. In those cases at least part of the front panel data has to be present. Furthermore, since all data is available via a control reference, if used, the control�s entire data structure must be present.
I use the vi server but haven�t really explored it yet, nor vi reference nodes, but obviously they too make modifications to unique data structures and hence are not thread-safe. And in general, any node that accesses a shared object is required to run in the user interface thread to protect the data associated with the object. LabVIEW, does not generally create OS level thread mutexes to protect objects probably because it becomes to cumbersome... Only a guess...
Considering the extra overhead of dealing with preemptive threading, I�m wondering if my well-tuned single threaded application in LV4.1 won�t out perform my well-tuned multithreaded application in LV6.0, given a single processor environment�
Please modify those parts that require it.
Thanks�
Kind Regards,
Eric

Ben,
There are two types of memory which would be of concern. There is temporary and persistent. Generally, if a reentrant vi has persistent memory requirements, then it is being used specifically to retain those values at every instance. More generally, reentrant code requires no persistent memory. It is passed all the information it needs to perform its function, and nothing is retained. For this type of reentrant vi, memory concern to which you refer could become important if the vis are using several MBytes of temporary storage for intermediate results. In that case, as you could have several copies executing at once, your temporary storage requirements have multiplied by the number of simultaneous copies executing. Your max memory use is going to rise, and as labview allocates memory rather independently and freely, the memory use of making them reentrant might be a bit of a surprise.
On the other hand, the whole idea of preemtive threading is to give those tasks which require execution in a timely fashion the ability to do so regardless of what other tasks might be doing. We are, after all, suffering the computational overhead of multithreading to accomplish this. If memory requirements are going to defeat the original objective, then we really are traversing a circle.
Anyway, as Greg has advised, threads are supposed to be used judiciously. It isn't as though your going to have all 51 threads up at the same time. In general I think, overall coding stategy should be to minimize the number of threads while protecting those tasks that absolutely require timely execution.
In that sense, it would have been nice if NI had retained two single threaded systems, one for the GUI and one for the GUI interface diagrams. I've noticed that control drawing is somewhat slower under LV6.0 than LV4.1. I cannot, for example, make a spreadsheet scroll smoothly anymore, even using buffered graphics. This makes me wonder how many of my open front panel diagrams are actually running on the GUI thread.
And, I wonder if threads go to sleep when not in use, for example, on a wait, or wait multiple node. My high priority thread doesn't do a lot of work, but the work that it does is critical. I don't know what it's doing the rest of the time. From some of Greg's comments, my impression is it in some kind of idle mode: waking up and sleeping, waking up and sleeping,..., waking up, doing something and sleeping... etc. I suppose I should try to test this.
Anyway that's all an aside...
With regard to memory, your right, there are no free lunches... Thanks for reminding me. If I try this, I might be dismayed by the additional memory use, but I won't be shocked.
Kind Regards,
Eric

I want to use labview controls in VB ? how do i do it

i want to use labview controls in VB ? how do i do it?

The easiest way to do this is to create a LabVIEW DLL and call it from vb. So write a vi in labview with the front panel you want and then compile it into a dll. The only problem with this is that when vb calls the dll nothing else can happen in vb. Hope this helps.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

How to use Expression Edit in the LabVIEW control (teststand category)?

Hi All,
I am developing the teststand specify module using LabVIEW. I found that is Expression Edit control in the Labview Controls pallete. does anyone have any example?
I have enabled the expression browser button but I dont know how to link it to the teststand. Pls advise.
Thanks
- toko -

Hey Toko,
You basically need to refer the button to the sequence context. For a great description of this and an example, please refer to this previous discussion forum:
http://forums.ni.com/ni/board/message?board.id=330&message.id=10609&requireLogin=False
Thanks,
Andy McRorie
NI R&D

Setup of invoice match control

Hi,
Our auditor wants a screendump from the IMG of the setup of invoice match control. With this I mean the setup of how incoming invoices is matched against the PO and how mismatch is handled.
Where in the IMG is this set up?
Best regards,
Thor-Egil

Hi,
You can do with two steps:
Step-1:
Use t.code:OBA7 and double click RE doc. type and select the check box of Reference Number in Required during document entry segment and save.
Step-2:
With above you need to set message in M8(Invoice Verification/Valuation)
Set Error for message no 108, 462 in OMRM t.code
Now when you do invoice verification with a invoice, you need to enter Reference Number wrt PO & with same Reference Number, you can not do further invoice verification again with same PO.
Regards,
Biju K

Changing language of LabView controls?

I just need confirmation. If LabView controls, like a graph, have a context menu then this context menu will be first in the language of the LabView IDE it was used with. If I build an application, then the builder includes the LabView RTE. This will also be the same language version as the IDE.
Now , if I wanted to change the context menu language let's say to french, would it be sufficient for the user just to install a french version of the RTE? Is this correct?
Solved!
Go to Solution.

You could you Import/Export strings from the menu bar to import other language text to the control on the FP.
A programatic code for this is possible.
-FraggerFox!
Certified LabVIEW Architect, Certified TestStand Developer
"What you think today is what you live tomorrow"

Is this setup capable of Labview controlled analog or digital output to 5V?

Similar Messages

Maybe you are looking for