Order analysis, executable and LabVIEW 8.0 RT

Hi,
I'm facing a peculiar problem. I have a LV RT code which uses VIs from
order analysis toolkit. The program as source code works perfectly. But
when I create an RT startup application and deploy it with debugging
enabled, the application gives a broken arrow. I was able to track down
to some four VIs. All these four VIs use functions from order.dll
(like OAT Single Stage Interpolation with IC). There are no description
for the errors. I tried to build the application after installing OAT
runtime in the host PC. But that also didn'thelp. I am using OAT 2.1,
with LV RT 8.0. Hope someone knows whats going on...
Thanks in Advance
Kallis
Have a nice day!!!
LabVIEW | LabWindows/CVI | TestStand
Certified LabVIEW Architect

Hi,
Even after I changed the dll to the RT-dll, the executable is still not
running. Now when I try to connect to the remote application
(using the 'debug aplication or shared library' utility), I get a
'failed to connect to remote appliction' message. So not able to realy
know what's happening there inside RT. After this I tried to build an
application which has only one vi which calls the 'OAT convert to even
Angle Signal (1 channel) as a subVI. With this, the remote debugging
works, but again the VI will show a broken arrow. The error is with the
same old VI (OAT single stage Interpolation with IC.vi). Now I'm really running short of ideas....
Bye
Kallis
Have a nice day!!!
LabVIEW | LabWindows/CVI | TestStand
Certified LabVIEW Architect

Similar Messages

I am using the Order Analysis Toolkit and want to get more information about the compensation for "Reference Signal Processing", which is scarce in the manuals, the website and the examples installed with the toolkit.

I am using the Order Analysis Toolkit and want to get more information about the compensation for "Reference Signal Processing", which is scarce in the manuals, the website and the examples installed with the toolkit.
In particular, I am analyzing the example "Even Angle Reference Signal Processing (Digital Tacho, DAQmx).vi", whose documentation I am reproducing in the following:
DESCRIPTIONS:
This VI demonstrates how to extract even angle reference signals and remove the slow-roll errors. It uses DAQmx VIs to acquire sound or vibration signals and a digital tachometer signal. This VI includes a two-step process: acquire data at low rotational speed to extract even angle reference; use the even angle reference to remove the errors in the vibration signal acquired at normal operation.
INSTRUCTIONS:
1. Run the VI.
2. On the DAQ Configurations tab, specify the sample rate, samples per channel, device and channel configurations, and tachometer channel information.
NOTE: You need to use DSA PXI-447x/PXI-446x and PXI TIO device in a PXI chassis to run this example. The DSA device must be in slot 2 of the PXI chassis.
3. Switch to Extract Even Angle Reference tab. Specify the number of samples to acquire and the # of revs in reference which determines the number of samples in even angle reference. Click Start to take a one-shot data acquisition of the vibration and tachometer signals. After the acquisition, you can see the extracted even angle references in Even Angle Reference.
4. Switch to the Remove Slow-roll Errors tab. Click Start to acquire data continuously and view the compensate results. Click Stop in this tab to stop the acquisition.
ORDER ANALYSIS VIs USED IN THIS EXAMPLE:
1. SVL Scale Voltage to EU.vi
2. OAT Digital Tacho Process.vi
3. OAT Get Even Angle Reference.vi
4. OAT Convert to Even Angle Signal.vi
5. OAT Compensate Even Angle Signal.vi
My question is: How is the synchronization produced at the time of the compensation ? How is it possible to eliminate the errors in a synchronized fashion with respect to the surface of the shaft bearing in mind that I am acquired data at a low rotation speed in order to get the "even angle reference" and then I use it to remove the errors in the vibration signal acquired at normal operation. In this application both operations are made in different acquisitions, therefore the reference of the correction signal is lost. Is it simply compensated without synchronizing ?
Our application is based on FPGA and we need to clarity those aspects before implementing the procedure.
Solved!
Go to Solution.

Hi CracKatoA.
Take a look at the link bellow:
http://forums.ni.com/ni/board/message?board.id=170&message.id=255126&requireLogin=False
Regards,
Filipe Silva

Noise, Vibration & Order Analysis

Dear all,
I am currently looking for a program that can perform a noise, vibration and order analysis. I was just made aware that LabVIEW (Developer Suite, if I'm not mistaken) comes with Noise and Vibration and Order toolkits. I've read through the data sheets for both toolkits. Now, I'm wondering whether the two mentioned toolkits can perform the analysis below:
1. Vold-Kalman Order Tracking Filter
2. Modal and Structural Analysis
3. Noise Source Identification
4. Modal Test Consultant
5. Acoustic Test Consultant
6. Real time CPB Analysis
7. Rigid Balancing and Two-Plane Balancing Consultant
8. Baseband FFT Analysis
9. Signal Enhancement
10. Auxiliary Parameter Logging
11. Cepstrum Analysis, and
12. Envelope Analysis
These analysis modules can be performed by Bruel & Kjaer product. I'm trying to influence my superior that National Instrument can also achieve the same objectives. So, maybe the users out there, or NI technical experts can help me with this. If the two toolkits are insufficient to perform such tasks, but NI has other toolkits that can supplement, can you guys please mention it in your reply.
Many thanks!
Shazlan

The order analysis tools and the sound and vibration tools provide the fundamental signal analysis for most all machinery vibration functions. However, the application level such as hammer blow test (modal), balancing, and so forth are not complete solutions.
I recommend looking at the following solution, which is based on these tools and comes with a turn-key application solution....
www.vibdaq.com
Let us know what further questions you have.
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

Is there any Way to find Which case is Executing in LabVIEW VI programmatically and Display it..

Is there any Way to find Which case is Executing in LabVIEW VI programmatically and Display it..
Solved!
Go to Solution.

I wrote this a few years ago: http://lavag.org/files/file/199-state-machine-follower/
This JKI RCF Plugin sets the Visible Frame property of a Case Structure while the owning VI is running. Use it to follow the execution through the cases in your string-based State Machine/Sequencer when Execution Highlighting isn't fast enough (and, it's never fast enough).
The use-case I wrote this to improve is setting a Breakpoint on the Error wire coming out of the main Case Structure and probing the Case Selector terminal so I can float-probe wires during execution. The problem with this is that I had to manually select the current frame every time. This is boring, so I developed this plugin to automatically set the Visible Frame to the case most recently executed.
You might be able to adapt it to your needs. The basic idea is that a custom probe on the wire to the Case structure's selection terminal sends a notification to a VI that displays the appropriate case.
We might be able to help you develop something easier if you'll give us more information. Is it OK if the code to display the case is in the same VI?
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice

Labview executable and Webserver

I'm having a little difficulty getting the webserver to run with a labview executable. (Labview 8.5)
The problem appears to be that the webserver does not think that the vi is running (probably because it is an exectuable).
The message is "Requested VI is not loaded into memory on the server computer".
Here is part of the HTML code:
<PARAM name="LVFPPVINAME" value="Adjustable Wing.lvproj/My Computer/Adjustable Wing.vi">
<PARAM name="REQCTRL" value=true>
<EMBED src=".LV_FrontPanelProtocol.rpvi85" LVFPPVINAME="Adjustable Wing.lvproj/My Computer/Adjustable Wing.vi" REQCTRL=true TYPE="application/x-labviewrpvi85"
The part ="Adjustable Wing.lvproj/My Computer/Adjustable Wing.vi" does not seem right to me - surely this should point at the .exe?
Thanks
Smiler

Hi Smiler,
To use an executable as the source for the LV web server you need to make sure the Adjustable Wing.vi is your main VI (Startup VI). If it is then once you have built the application move the .exe .alias and .ini file to the web server root directory by default <LabVIEW install dir>\www
Once the VI is in this directory open the .ini file and the first line under the [<App name>] should be:
postScriptLevel2=False
WebServer.Enabled=True
If the web server is not a the default location update the entry WebServer.RootPath= in the .ini file
At this point open LabVIEW go to Tools >> Options >> Web Server: Configuration and turn OFF the web server.
Now run the exe from the web server root directory and then open the html page you created before.
Regards
JamesC
NIUK and Ireland
It only takes a second to rate an answer

Create an API to Launch an LabVIEW Built Executable and Pass it Input Parameters

Hello,
I'm looking for a way to create an API to Launch/Close an executable, created with LabVIEW, which in additional to Launching/Closing tht executable, will also allow me to pass input parameters.
To give you some background, I'm working on a logging utility, basically a background dameon, which I currently have implemented as a LabVIEW packed library and my API is a few VIs to launch that daemon and pass it a filename and a logging rate. Functionally it works just fine however is executes within LabVIEW not as an independent process. So instead of using a packed library, I would like to compile my logging daemon down to an executable but I still need a way to launch it and pass it parameters from an external application (such as Teststand).
I know you can launch executables and pass parameters using windows command lines, but I'm wondering if there is a more direct method such as a DLL that I could call in Teststand? Thanks.
Post CLD and when I'm a CLA when someone asks who I am, I can spin around in my chair and say "I am... the architect."

When Teststand Launches the Logger, it does so by opening a reference to the logger daemon using the "Open VI Reference" primitive and then it launches an instance of the dameon using the "Start Asynchronous Call" node.
This currently, launches the logger within labview not teststand. If I were to directly call the logger daemon VI itself as a step in TestStand, then it could run in a new teststand thread. At that point I would need a way to stop that logger which I should be able to do by storing a reference to its control queue within the teststand thread that it is running in. Since teststand let's you specify VI execution in the runtime engine instead of LabVIEW that might do the job.
The one catch is once the sequence completes, the logger does some cleanup, post processing, etc that depending on the amount of data captured can take some time so if a set of sequences needs to be executed, this could hang up teststand until that post processing is completed. That is one reason why I wanted it to execute outside of testtand so that additonal sequences could continue to run while the daemon finishes up in the background.
But, it's something I'll have to look into.
Post CLD and when I'm a CLA when someone asks who I am, I can spin around in my chair and say "I am... the architect."

Rshd and LabVIEW executable

Hello,
I have a LabVIEW executable built from LabVIEW Pro 2012. The executable executes without error normally. I now need to remote-execute it from a Windows 2000 networked computer. The labVIEW executable resides on a Windows 7 Pro (32-bit) computer peer-to-peer networked to a Windows 2000 computer. I have the latest rshd binary in the "system32" subdirectory on the Windows 7 computer and am using the native rsh client that comes with Windows 2000 on the Windows 2000 computer. The executable and it's front panel come up OK on the Windows 7 computer but the executable asks for the location of several DLLs. If I take the time to navigate to the DLLs the executable proceeds OK. I have added the path of the DLLs to the Windows 7 environment path but the executable still asks for their location. Is there any way to "add" the external DLLs to the LabVIEW executable build so they will be found at remote execution startup? The daemon on the Windows 7 computer is started at login via batch file that contains rshd -d -r.
Thanks in advance
Tim
Solved!
Go to Solution.

My apologies for this post. It’s been so long since I worked with things like the system variables and system path. I "thought" I had added the subdirectories of the required DLLs but I had set environment variables to each of them and then used the environment variables to append the system path. When I finally opened another CMD window and did an echo of the path I saw that the path had the literal variable names appended not their contents. I added the actual paths and nor the LabVIEW executable finds everything OK.

Query for Sales Order Analysis

Dear Experts
I have written a Query for Sales Order Analysis and would like to have help on this.
The query is used for generating daily report for Sales Order on number of documents (Sales Order), total amount of sales orders and total GP of Sales Order. The query is written as below:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum] ORDER BY T0.[DocNum]
where U_Total_GP is a UDF for storing the GP of each order.
After executing the query, a selection criteria of date appears and after a date is selected, the report shown information required. However, the query does not calculate column total for total amount and total GP. Although I know the total for each column can be displayed by pressing "Ctrl" + Click on the column title, it would have to be done from time to time.
Therefore, I would like to modify my query in order to calculate the column totals when executed. Are there any suggestions for this?
Thank you
Regards
Elton

Hi Elton,
Try this:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT '', SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]
ORDER BY T0.[DocNum]
Thanks,
Gordon

Query on Sales Order Analysis

Dear Experts
I have written a Query for Sales Order Analysis and would like to have help on this.
The query is used for generating daily report for Sales Order on number of documents (Sales Order), total amount of sales orders and total GP of Sales Order. The query is written as below:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT '', SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]
After executing the query, a selection criteria of date appears and after a date is selected, the report shown information required. Everything is fine with this query except I would also like to incdude the total number of Sales Order (per day) right below the column "DocNum".
Is it possible to achieve this?
Thank You
Regards
Elton

Try this:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT count(DocDate), SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]

Difference between diadem and LabVIEW Report Generation Toolkit

I want to expand LabVIEW's reporting capabilities. Can someone tell me what the difference is between DIAdem and the LabVIEW Report Generation Toolkit for Microsoft Office.

Hello Mr Bean,
There are several major differences between the two solutions. I'll try and outline them as good as I can ...
The biggest different is that LabVIEW and its toolkits are programming tools and DIAdem is a ready to run application.
The LabVIEW Report Generation Toolkit basically provides an extensive library of VIs that allow you to connect LabVIEW to the MS Office library and create and edit reports in Word and Excel.
DIAdem is a stand alone application that was designed to post-process data from various sources. The tools included in DIAdem are:
1. NAVIGATOR: Allows you to import data from files (ASCII, binary, Excel, etc.) as well as DataBases (SQL/ODBC, Citadel, ASAM, etc.). The unique DataPlugin technology available within DIAdem allows you to import vitually and data file by creating a DataPlugin that describes the data format and gets linked to DIAdem. More information at: http://www.ni.com/diadem/dataplugins.htm
2. VIEW: Graphical and Numerical data inspection tool. Use cursors to zoom and scroll through your data, edit your data graphically and numerically and compare different tests.
3. ANALYSIS: DIAdem has a wide range of analysis functions, ranging from simple functions like integration and differentiation to FFTs, Order analysis and 3D data analysis.
4. REPORT: The DIAdem REPORT tool allows you to create reusable report layouts that can contain multiple axis systems (2D, 3D and polar plots) as well as tables (2D and 3D) and variables. The REPORT tool generates templates that can be usedwith multiple data sets due to the inclusion of automatic (or manula if required) scaling as well as extensive use of variables for annotations. Finished reports can be exported to printers, graphics files, the Windows Clipboard, HTML pages and PDF files (PDF writing is build into DIAdem, no extra software required). Using Scripts, it is also possible to create Word, Excel or Powerpoint reports from DIAdem automatically.
5. SCRIPT: The DIAdem scripting tools allows users to record macros or write scripts that automate complete sequences, for the import of data, via extensive analysis, to creating a publication ready report. Scripts can make reports "intelligent" by modifying the appearance of a report based on the data or calculation results that are going to be displayed in the report.
I recommend you check out the following link for more information: http://www.ni.com/diadem/
DIAdem is an extremly powerful tool for report generation. I am leaving to go on a business trip to Asia, but I would be more than happy to give you an Web presentation on DIAdem after I have returned. We could use your data and create a DIAdem report Script together online. My Email address is [email protected] and I will be back the week of Thanksgiving.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

Font Size Difference between Exe and Labview IDE

I'm stumped on the following issue and surprizinglycan't find any references that are similar on this forum.
I've developed an application which, when built to an Exe, has different font sizes than when executed on the same computer in the Labview Integrated Development Environment. In each instance the screen resolution is the same. I've used the "Application Font". I'm having trouble figuring why the font would render differently in each case. Of possible signifigance is that I'm running the Exe by simply browsing to the folder where the build procedure drops it instead of building an installation.
I've attached one of the most glaring examples that shows the rendering in each case.
I'm hoping that someone can point me in the right direction to resolve this issue.
Attachments:
Font Differences1.zip ‏1704 KB

Hi Doctor,
two notes:
for the font size differences: I would try to change the font settings
to a more 'specific' font like Arial 14pt. The application font is set
somewhere in an ini-file and the setting may change with the
environment (IDE vs. exe-rt).
for your attachment: please convert pictures to jpg or png. This will
reduce size by orders of magnitude :-) And please crop them, unless you
have a very (VERY) beautiful desktop background picture!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Installation problems with Order Analysis Toolset

I am trying to install Order Analysis Toolset version 2.0 on my computer, but it is not allowing me. Whenever I prompt the installation, an error message appears which says "You must install LavVIEW 6.1 or higher version before running Order Analysis Toolset 2.0 Setup." I have LabVIEW 2010 already installed. Why is it giving me this message?

Hi,
Version 2.0 of the Order Analysis Toolset was released in 2003. NI does its best to maintain compatibility, but over the years compatibility with version 2.0 was likely dropped in favor of newer tools. In this case, the order analysis functions were incorporated into Sound and Vibration Measurement Suite starting with Version 5.0. If you'd like to use these functions, I'd recommend using the appropriate version of the suite for your version of LabVIEW.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/203624
Regards,
Luke B.

Order Analysis when there is a significant DC offset in signal

Thanks for reading this. I am using the NI LabVIEW Order Analysis Toolkit to do order analysis of strain gage signals of a part attached to an auto engine. My goal is acquire data from a strain gaged part attached to an engine during its rampup and identify the signifcant orders in the strain signal. I am not able to understand an issue I see with my results in the Order Power Spectrum.
I measure the strain gage signals during the engine run-up using the cDAQ 9235 module (1000 to 6000 rpm in 15 seconds). I also acquire the Tachometer using NI-9402 module (counter). I then converted the strain signals to even angle signals, and did the Order Power Spectrum.
Please the resulting Order Power Spectrum shown in Fig1. What I am finding is that the DC offset in the strain signal shows up as a high amplitude peaks (red or green) in the Order Power Spectrum (Please see Fig 1) around order of 0. Because of these huge peaks around order 0, the order peaks of real interest around 2 or 3 order (blue or purple) are hard to discern in the graph.
The DC offset shows clearly in the graph of Strain vs RPM (RPM is a linear function of time), so essential this is same as Strain vs Time. The white line in Fig 2 is the DC offset. In this example, the DC offset is constant during the RPM rampup, but more often, the strain gaged part experiences both changing static strain and cyclic strain as shown in Fig 3. Here the part is undergoing increasing tensile strain, with cyclic strain overlaid on top of that.
My questions are:
Am I missing some key step here in preprocessing?
-- do I need a high pass filter to remove DC offset?
-- do I need to subtract the mean value of the signal from the time based signal before sending to Order Processing?
How does one handle signals that have a varying static strain in addition to a cyclic signal overlaid on top of the static signal? This appears to me a common scenario in strain measurements because the DUT is undergoing both varying static and dynamic stresses during an engine ramp.
Thanks for any comments or tips!

Other fun facts:
--- The Encoder solution has absolutely no connection to speed. It is all connected to crank angle.
For what we were doing that was perfect. We were looking at cylinder pressure and valve position vs. crank angle. But you have to measure speed some other way (use the encoder's INDEX output into a COUNTER channel, for example).
--- Measuring speed on a (combustion) engine is an illusion anyway. You can come up with an average speed, but the crankshaft literally slows down (that gas does not want to be compressed) and speeds up (exploding gas REALLY wants to get out). If you analyze the 512/rev signal vs. time, you can see the cylinders firing. A flywheel mitigates this, but everything is an average.
--- You're better off (speed wise) if the number of points you choose is a power of 2. You can use a FAST fourier if so.
--- The basic assumption behind Fourier analysis is that the signal you are analysing is synchronous to the block (the chunk you are analyzing), and repetitive: the next sample after the tail (element N-1) would be the head (element 0).
--- Order analysis involving windows (Hanning, Hamming, etc.) is simply an attempt to correct for the fact that you're measuring it wrong. If you take an arbitrary time-chunk of data, then your head may not match up to your tail. As far as Fourier is concerned, that is a sudden transition in the signal and will show up as energy spread through the 1st order, 2nd order, etc. It's polluting the data. Worse, it's not consistent: if the head and tail meet at 750 RPM, you have little pollution. If the head and tail are 180 out at 760 RPM, you have a large pollution. Hanning, etc. basically reduce that transition by bending the signal toward zero at the head and the tail. You then multiply the results by a fudge factor, because the window distorts the data.
--- If you record an arbitrary time-chunk of data, you don't have any phase information. You don't know if this particular order's artifact is related to the valve opening at 270 degrees, or the suction valve closing, or what. It's just not there. You can get a phase result, but it's a phase relative to the start of your block, and if that's arbitrary, then phase is useless.
--- All those issues are avoided if you take the data synchronously. Don't window it. Don't filter it, unless you have a known interfering signal way above the highest order you want.
I mentioned above that you can record as many channels as you like as long as the total scan time is < RPS / 512.
Obviously, that should be < 1 / RPS / 512 : the TIME it takes to turn the encoder one 512th of a rev. You shouldn't get too close to that limit, because the speed varies during a revolution.

How does Order Analysis measure phase lag, particularly super-sync amplitudes?

In recent testing of a high speed gear box, an 8X amplitude was observed (on the radial displacement probes) as the gear passed through a certain speed range. An NI4472 pci card and vi's written in 7 Express, w/ Order Analysis tool kit were configured with radial displacement probes and keyphasor as input signals. The behavior of the phase lag measurement is significant. If the phase lag of the 8X amplitude rolled as the gear passed through a particular speed range then this could suggest one particular problem, but if the phase lag remained constant then this could indicate a different problem. So, someone asked: How does the system measure phase lag of supersynchronous amplitudes?

See attached file for figure 1,2,3
The Phase measurement in the LabVIEW Order Analysis Toolkit uses the phase lag convention. Phase is defined as the angle difference measured from the peak of a vibration signal backward in time to the reference trigger point. This means the directions of numerically increasing angles are always set against the shaft rotation. The trigger point here is the tachometer pulses.
Figure 1 shows the relationship of the vibration signal and reference signal to zero degree phase. The shaft has a heavy spot and a keyway slot. When the keyway slot passes the tachometer, the tachometer detects a trigger pulse. The heavy spot causes the shaft to vibrate as the shaft rotates. When the heavy spot passes the proximity probe, the vibration reaches a peak. When the heavy spot passes the proximity probe and the keyway slot passes the tachometer simultaneously, the peak of the vibration does not lag or lead the reference trigger point. At this point the phase is zero degrees.
The other part of the convention dictates that 90 degrees means that the peak of vibration lags 90 degrees behind the trigger point. Figure 2 1illustrates the 90 degree phase. When the vibration signal reaches the peak, rotate the shaft backward (counter the rotation direction) until the keyway slot passes the tachometer. The number of degrees you rotate is the phase lag, or the phase value in machinery vibration measurement. Figure 2 shows the relationship of the vibration signal and reference signal to the 90 degrees phase convention.
For the 8x phase, the measurement is conducted in the similar way. The difference is that the 8x order component go 8 times faster than the trigger pulses. Figure 3 shows the 90 degree phases ( tacho pulse in rising edge) of the 8x order components. The phase measurement is still conducted through calculating the delay between the peak in the 8x vibration components and the trigger pulses and comparing the delay to one cycle of the 8x components. In figure 3, the signals between the two green grid lines are used to output one phase results.

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

Order analysis, executable and LabVIEW 8.0 RT

Similar Messages

Maybe you are looking for