Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About Stormshadow

  • Rank
    More Active

LabVIEW Information

  • Version
    LabVIEW 2009
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I ended up with issues after using this one for over a year because it ignores spaces before the number: http://rosettacode.org/mw/images/f/fb/LabVIEW_Determine_if_a_string_is_numeric.png This is my version that allows NaN, Inf, -Inf to work and spaces are considered as a string. .1 doesn't work, but a condition can be easily added. Sorry for digging up an old thread, but this is the first link on Google and another thread would just get lost. This gives another alternative to the suggestions offered in this thread.
  2. As a suggestion, you may try to work as a group to create a "UML" based strategy on your needs for most aspects of the Tests in order to separate the work and know what is required for each developer. For the first project of the company I'm working for, I created a set of VIs that will be universal (libraries, drivers, HW calls, etc.) and used for all future projects and will be independent. They are in a separate folder. Currently running in some deployment annoyance because my VIs aren't all within the Workspace folder, but I'm working around it. As the main LV developer, I create
  3. This is a post as a reference to others on how I resolved my ghosting issues. Well mostly resolved, I still have a 1mV per 1V adjustment. Works fine with my hardware in between. You may want to tweak the values around to get none at all. Feel free to post your values and how you fixed ghosting issues. I only added Crosstalk as a reference in subject for those that are unaware of ghosting. Same Topic on NI Forums: http://forums.ni.com/t5/Multifunction-DAQ/Ghosting-Resolved-Crosstalk/td-p/3196396 My Offline Setup: Direct connection of a NI PXI-6723 to a NI PXI-6255. I tweaked around wi
  4. I need to measure the RMS of the generated sine wave with a 0.2% precision. There will be a transformer between the output of the 6723 card and the input of the 6225 that cleans up the signal a little. So I guess I won't have the harmonics issues once I go live. Still strange to see those issues wince 3KHz is not a very high frequency and with the number of samples from the AI.
  5. Actually the RMS is much better with 1 signal at 450KS/s and 45KS/channel. It varies between 0.459 and 0.464. I did add the low pass filter in parallel and it stabilizes the signal when Read with a single channel. It stops floating on water and the most of the noise is gone. Difference between running with 1 channel at 450KS/s @ 45KS/channel and 8 channels @ 15KS/channel: 1 Channel RMS varies between 0.4615 and 0.4617 8 Channel RMS varies between 0.4659 and 0.4660 A jump of 4mV is added to the RMS when running with 8 channels. The other channels do not have the filter instal
  6. So I did some extra monitoring and found that the generated sine wave sometimes gives an 200015 Error. I changed the monitoring to 1 channel and increased the sampling to 450KS/s and 45KS/channel and I get a bouncing Sine Wave with glitches all over. It gradually goes from nice to bad looking and back to nice in a loop. This is the sine waves I was getting when I scoped it a few weeks ago (shown 4 of the 8): The spikes at the 0V are known as Glitch Energy, an effect known to happen with any DAQs when all the relays switch at once. Difficult to remove, must add hardware filte
  7. I have a Mean of ~0.013 for the 0.65V sine wave. Not enough to offset it. However my sine waves are not always nice. It captures the Glitch Energy and seems to be offset to the positive by much more. It can reach the 1V at times. Not sure how it can get those kinds of values... Both the 6723 and the 6225 are in the same PXIe-1073 chassis.
  8. I'm reading a sine wave generated by a AO DAQ and reading this same signal with another AI DAQ and a DMM at the same time. AO is set at 0.65V AI RMS reads 0.5V±0.0056 DMM reads 0.46053V ± 0.00001 0.65/1.414=0.46 so the DMM read is accurate. What makes the RMS LabVIEW function not reporting the accurate information? Could it be the Glitch Energy affecting the read? On a side note, I also need an accuracy of 0.2%. AO generates a 3KHz signal at 0.65V (450KS/s @ 150S/Buffer). AI reads at 90KS/s at 15KS/channel. DMM a 34401A is set VAC. Thanks
  9. Is there a Property Node that detects change of a button, similar to an Event? Context: I inherited a 5x7 square monitors code without any Sub-VIs and the detection of buttons is the following: Note that the Loop is often Late. I need to do an operation when the buttons change state (from ON to OFF) and adding an event case or a Producer-Consumer would be too big of a change (wouldn't be accepted). Is there a better way other than plugging the array into a shift-register and detecting a change in the array, such as an event equivalent property node? Thanks
  10. Added the question on NI Forums: http://forums.ni.com/t5/Multifunction-DAQ/How-to-calculate-the-optimal-Sinewave/td-p/3164565
  11. Not entirely sure what you are suggesting. Not sure this would be the best option, sometimes loops are late in this massive application. There's even a LED on the front panel indication the user when the loop is late... So if some loops are late, this will distort the sine wave generated in that small loop. The system is not running on RT LabVIEW. This is what I get when I search for your suggestion: http://www.edn.com/design/analog/4320590/Shift-registers-and-resistors-deliver-multiphase-sine-waves
  12. How do we calculate the optimal Sine wave waveform on a NI-6723? What is the best settings to generate a clean sine wave with the NI-6723? According to the specs it can do 800KS/s (45KSamplings/second per channel). I'm using 8 AO channels. What would be the best settings for the Waveform Buffer Generation and for the DAQmx Timing (Sample Clock)? Do I need to add a Regen? Other information: When I set the Resulting Sample Clock Rate to 450000, the card gives no issues and generates a somewhat clean sine wave, with the exception of spikes when the sine wave crosses 0 (Glitch Energ
  13. With the flexibility of the JKI State Machine and the fact that it already has the Event Case integrated into the main loop, the extra loop for User Events (Producer-Consumer implementation) can be somewhat avoided if the code runs without much of a delay. I would like to see some way that the JKI State Machine's Event Case could be activated to behave as a Producer-Consumer without having an additional loop with a queuing system.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.