signalexpress2009 with sound and vibration suite: "vibration level" step

[bon2b]

1)The running RMS function worked before and calculted a running RMS of 1s. This function quit to work without any modifications to the application project, and now gives 0 as result all the time.

2) When viewing the RMS value in "project document", how do I set the time so only the RMS value of the latest 5min shows? 

[Dustin_D]

Hi bon2b,

Can you try this project in your system to see if outputs a proper value?

Regards,

Dustin

[JDubb007]

Hello,

     I am using the Sound and Vibration suite and ran into a problem trying to set the measurement type to "Torque".  My DAQ card is a NI--PXIe 4330 and I'm running the tool with the Stand Alone Interactive Acquisition.  The tool generates an "Error" stating that "lbs" are not supported  on the channel for the requested measurment type.  Supported units are "Nm, lb-in, lb-ft, etc".  I verifired that my selected units are "lb-In", but continue receiving this message.  I changed my measurement type to "Bridge" and was able to acquire data.  Is this a bug in the Torque measurment type or is there some additional parameter that I need to set.  I was only looking at a single channel.

Thanks

[GarPar]

Hi JDubb007-

     Are you using a custom scale?  Make sure that for the Custom Scaling parameter in your task, you have chosen No scale.  There have been no reported bugs on this issue - it seems that you have selected an incorrect parameter.

     I hope this helps.  Have a great day!

[JDubb007]

Hi Gary,

      Thanks for the response.  No, I am not using the Custom Scaling parameter.  The tool defaults to Pounds as soon as you specify the "Measurement Type" = Torque (Bridge).  The same thing happens when setting the "Measurment Type" = Pressure (Bridge).  If I manually change the "Scaled Unit" to a valid option (In-lb, Nm, oz-in, etc), it does not register that change in the "Channel View" Window. This leads me to believe this is a SW bug, because the parameter specified in the "Setup" window is not updated in the "Channel View" window and consequently, the SW believes the user has specified the incorrect units.  Attached are some slides describing the problem.  Please let me know if I have performed any steps incorrectly in this setup.

Thanks

[GarPar]

Hi JDubb007-

     I am not able to replicate your error on my end.  Everything works fine.  Does this happen every time you create a new analog input torque step?  Meaning, if you open up a new project and add an analog input torque step, do you consistently get the same behavior?  What about on simulated hardware; the same thing?

     I have not seen any documented CARs (Corrective Action Requests) or other Service Requests with this issue.  You might also try upgrading to the most recent version of NI-DAQmx, version 9.2.3.

[JDubb007]

Hey Gary,

     Yes, this error appears everytime I create a new analog torque step.  I updated to NI-DAQmx v 9.2.3 and that appears to have fixed the problem.  I don't know the previous version that was running, but perhaps there are some compatiblility issues when using older DAQmx versions?

Thanks a lot!

[GarPar]

Hi JDubb007-

     Glad to hear it worked.  I know that we introduced the torque AI task just within the last year, but am not sure about any exact bug fixes.  You can check the readme files with each release of NI-DAQmx to see what bugs are fixed.

     Have a great day!