02-09-2026 06:17 PM
Hi, I have something I want to create, and I would appreciate your help if possible. I want to read these 10 files one by one, and if any value is outside a certain predefined range, I want to write an error message indicating which file and which line it occurred on, as well as the command name associated at that point. I want to specify the files with names like 01, 02, etc., so it's clear which file is which. Also, if a file is empty, it should continue without an error, but if a file does not exist, it should display an error saying that this file does not exist. If anything is unclear, I can answer immediately, so thank you very much for your help.
02-09-2026 07:33 PM
Hi, I have something I want to create, and I would appreciate your help if possible. I want to read these 10 files one by one, and if any value is outside a certain predefined range, I want to write an error message indicating which file and which line it occurred on, as well as the command name associated at that point. I want to specify the files with names like 01, 02, etc., so it's clear which file is which. Also, if a file is empty, it should continue without an error, but if a file does not exist, it should display an error saying that this file does not exist. If anything is unclear, I can answer immediately, so thank you very much for your help.
02-10-2026 12:48 AM - edited 02-10-2026 12:52 AM
Hi nana,
@nananass wrote:
- I want to read these 10 files one by one,
- and if any value is outside a certain predefined range, I want to write an error message indicating which file and which line it occurred on, as well as the command name associated at that point.
- I want to specify the files with names like 01, 02, etc., so it's clear which file is which.
- Also, if a file is empty, it should continue without an error,
- but if a file does not exist, it should display an error saying that this file does not exist.
Instead of some block text now there are some (more or less) clear sub steps you need to work on.
What is your actual question?
Where do you need help?
You didn't learn to provide files without Unicode chars until now, so you still make it harder for us to help than it should.
All we get from you is an image showing some LabVIEW block diagram with lots of Japanese text and some unknown subVIs...
Btw. why did you post the very same question in two different boards?
02-10-2026 01:17 AM
1. Inputting scenario files and converting to arrays
Up to 10 file paths can be received in a cluster, converted into an array, and then processed in a loop.
2. File reading and CSV parsing
For each file path, the CSV data is read using csv read.vi.
The delimiter is basically a comma (,).
The read CSV data is stored as a two-dimensional string array.
3. Command determination (case structure)
Extract the command name from each row and branch the processing for each command using a case structure.
For example, for MFC-related commands, check if the value is within the range of 0–100.
For the TIME command, check if the value is within 0–3600 and in increments of 10.
Comment lines (starting with #) are skipped.
4. Error aggregation
If a row does not meet the conditions, add it to the error text in the format "file number: line number: command name".
Aggregate all errors from all files and all rows. This is the kind of functionality I want to create.
The parts I’m struggling with are, first, how to display messages.
I’m also unsure how to specify this for each row and how exactly to write it.
02-10-2026 01:25 AM
Hi sheep,
@nananass wrote:
The parts I’m struggling with are, first, how to display messages.
I don't see anything about "displaying messages" in your requirements list...
You may use a simple string indicator to display a string. A OneButtonDialog may work, too.
@nananass wrote:
I’m also unsure how to specify this for each row and how exactly to write it.
"Rows in the file" will be "rows in your 2D arrays".
As you process the rows using an autoindexing FOR loop you can VERY EASILY determine the row number frm the loop iteration terminal!
@nananass wrote:
1. Inputting scenario files and converting to arrays
2. File reading and CSV parsing
3. Command determination (case structure)
4. Error aggregation