08-20-2005 03:37 AM
08-22-2005 08:45 AM
Hi DF,
Glad to read that the examples were useful. 😄
Yes, I do have lots of experience parsing files. If you explain what you are trying to do, I can help.
I do not have that much experience with databases... But if you post your question, I will try to point you in the right direction.
Regards,
JLV
08-22-2005 03:00 PM
08-22-2005 04:38 PM
08-22-2005 10:52 PM - edited 08-22-2005 10:52 PM
Hi DF,
Attached is a little cleaner vi.
Sorry I didn't get a chance to go through it thoroughly.
I think I understand most of what you want to do. I simplified some stuff and created one sub-vi as an example for you. You should make use of sub-vi's. They keep the code tidy.
I asked some questions within example 3. I purposely wired wrong the box where you change the filename. A simpler way is to use a loop and use the counter to create the addtiotional extention to the filename. However, I did not understand why you are incrementing it. Can you describe the logic behind it?
I must call it a night. If you look at some of the logic change, you can adapt some of it in your vi. Try it and [post your resulting vi.
Have fun,
JLV
😄
Message Edited by Support on 09-15-2005 10:47 AM
08-23-2005 02:28 AM - edited 08-23-2005 02:28 AM
Hi, JLV
#1 in the file paths_read.txt there is info like station number in the start ST No; and you forget to take the destination path(Output path).
#2 i write to you some info in the vi.
regards,
eyal.
note: i hope that I'm not making for you trouble with your wife ![]()
i know this problem my wife also want to kill me because I'm working to late.![]()
Message Edited by Support on 09-15-2005 10:48 AM
08-23-2005 08:44 AM
Hi DF,
Not too much trouble with the wife 😉
So how are the station names defined? Do the stations write the data to a single server? And how is the text file prepared?
Basically, I am wondering if the front-end info can be automated.
Are you creating the text file? If so, there are tricks you can use to simplify the parsing of the file. Try to describe the naming convention of the files and how they are created. I can propose something like an "ini" file which is easy to parse. Also, we can identify what is static and what is dynamic within the file and / or folder. Planning ahead will help you to simplify the vi. Architecturing (planning) the work will save you lots of time and lots of headaches. It is a simple task, and well worth the effort.
Then we can walk through the process, this way, you can use the same method for other parts of the project.
I can only look at LabVIEW at home (at night).
Remember to have fun. You did okay so far, now you need to simplify it and start using sub-vi's (which can be used in other vi's later on). Sub-vi resemble sub-routines. They are usually task specific vi's. And easy to implement.