LabVIEW TDMS Channel Update Automation
Budget: €250 – €750 EUR
I have a batch of legacy *.tdms files generated in LabVIEW. In each file there is a single channel whose data needs correction: at a predefined set of sample indexes I will supply, the existing values must be replaced with new ones. All other channels, properties and file-level metadata stay untouched.
The workflow I picture is: open the original file, patch only the targeted indices inside the specified channel, then save the result as a new file (same name plus a suffix is fine) so that my original data remains intact for traceability.
Essential requirements
• LabVIEW-based solution using the native TDMS API (no external converters).
• Reads a tdms file list of index–new-value pairs.
• Preserves channel and group properties exactly as found.
• Produces a clean set of updated TDMS files ready for direct use in DIAdem and my existing VIs.
Deliverables
1. A VI or small library that performs the update as described.
2. Short usage note or inline documentation so I can rerun it when new correction lists arrive.
3. The first set of corrected TDMS files for validation.
If anything in the TDMS schema could complicate a straight overwrite, flag it and propose the safest handling. Looking forward to working with someone who knows the quirks of the TDMS file format inside out.
The workflow I picture is: open the original file, patch only the targeted indices inside the specified channel, then save the result as a new file (same name plus a suffix is fine) so that my original data remains intact for traceability.
Essential requirements
• LabVIEW-based solution using the native TDMS API (no external converters).
• Reads a tdms file list of index–new-value pairs.
• Preserves channel and group properties exactly as found.
• Produces a clean set of updated TDMS files ready for direct use in DIAdem and my existing VIs.
Deliverables
1. A VI or small library that performs the update as described.
2. Short usage note or inline documentation so I can rerun it when new correction lists arrive.
3. The first set of corrected TDMS files for validation.
If anything in the TDMS schema could complicate a straight overwrite, flag it and propose the safest handling. Looking forward to working with someone who knows the quirks of the TDMS file format inside out.