10-03-2025 02:25 PM
I have successfully integrated WT5000 power analyzer custom device into the existing Veristand project that is used for Dyno system integration testing and validation for automotive applications within the org that I am currently working for. The current software version that I built and deployed has the capability of capturing harmonics but the harmonics as a signal could be in order of 10, 20 or 30 different magnitudes which means 30 different data points. Currently, the Veristand does not support for arrays, it supports only scalars and waveforms. In LabVIEW I could easily capture them in an array and log the data but Veristand has a limitation and I don't want to create so many scalar channels, it is just not efficient and it is going to be a huge problem in terms of data management, scalability and complexity. Therefore, to mitigate this, I installed the NI waveform data logger and converted my arrays into waveforms and passed them through to the veristand system. Upon reading, the waveform data logger should be able to log the captured data that is showing up as a waveform but it is not working for me. I basically followed the steps for configuration and checked the file after I deploy the system definition file but the log file never gets created even though the file status is always 1 which means it is getting logged (I think). Please check and confirm if my understanding is correct. Can you please confirm following:
1. Is my approach the best way to fix the issue where I have data in an array and I am trying to get the data out via Veristand?
2. How to get the waveform data logger configured correctly? Am I missing anything (Please see the snapshots in the attachments for my settings)
3. If everything is getting configured correctly, why can't I see the TDMS file in the desired location where the folder exists.
My current environment:
LabVIEW 2021 64 bit
Veristand 2021 R3 64-bit
Does Veristand 2024 fix this issue automatically?
Please let me know.
10-05-2025 11:42 PM
First to answer "Does Veristand 2024 fix this issue automatically?"
No, the custom device is independent of VeriStand version. It is essentially some LabVIEW code called by VeriStand Engine. The latest release is at https://github.com/NIVeriStandAdd-Ons/Waveform-Data-Logger-Custom-Device/releases
I would recommend you to test with DAQmx Waveform to isolate if it is your WT5000 power analyzer custom device issue.
When you said you couldn't find the file, did you try to find it on your host PC or on the remote target via FTP or SFTP?
10-06-2025 12:52 PM
Thank you for your answer.
1. How to test with DAQmx Waveform? Can you please outline the steps? Do I need any additional hardware, if so, most likely that is not possible for me. Please suggest any alternate debug techniques.
2. The path that is shown on the snapshot is supposed to be the path on the host pc and not RT I believe unless I am missing something. Please check and let me know if the waveform data logger by default logs the data to the RT target or the host windows PC in this case. I haven't checked RT target that I am using to see if the data is there.
Thank you very much. I look forward to hearing from you soon.
Best Regards,
Vinod
10-06-2025 07:41 PM
1. How to test with DAQmx Waveform? Can you please outline the steps? Do I need any additional hardware, if so, most likely that is not possible for me. Please suggest any alternate debug techniques.
You can create a simulated DAQmx hardware then configure DAQmx AI waveform.
2. The path that is shown on the snapshot is supposed to be the path on the host pc and not RT I believe unless I am missing something. Please check and let me know if the waveform data logger by default logs the data to the RT target or the host windows PC in this case. I haven't checked RT target that I am using to see if the data is there.
The path shown in the snapshot is in fact on the RT target. The logging happens on the RT target. VeriStand does not upload the files to host PC automatically.
10-22-2025 06:18 PM
So, I checked the path on the RT target and I couldn't find the file which means it is not logging there, I checked the path construction on the waveform data logger and it definitely looks to be host PC.