change path for every 24 hours

[karthickkece]

Use format date and string to get the current date in a format u want.

[Perarasi]

Thank you so much for your reply.

I have a problem while changing the date format (i.e) I would like to have year in four digit,date and month in one or two digit.

I f i give %d_%m_%y it give 18_09_15 i need 18_9_2015.Please help me to solve it

[karthickkece · Accepted solution]

Hope it will useful.

[Perarasi]

Thank you so much.It works.Thank you all for the help.

[Perarasi]

Hi,I have a problem with path selection.The actual path it has to be select is \\coimachp.mach.corp\Data\EHS\multihub v2\17_ 9_2015.log.When i use the build path the appended path gives the same location as i mentioned above.but the read from measurement file gives the error as not a path.Can anyone help me to solve this?

Thank you in advance for your reply.

 

[RavensFan]

Are you sure those directories and that file exists?

Your path includes a reference to another machine.  Are you sure you have access to that other PC from the one you are running this VI on?

[Perarasi]

Thank you for the reply.

Yes i am sure that i have access to that machine from my PC.What will be the possible reason that it says it's not a path?

[dkfire]

What function is giving you that error?

You have TWO functions that tries to read the same file.

What is the purpose of reading the same file two times and not using the data from the first read?

When something is not working you need to do some debugging.

Place some probes or indicators on the wires going into the different functions to see if the data match your expectation

[dkfire]

And one more thing, how is the "Read from Measurement File" configured?

Take a picture of the option dialog for that function.

[James.M]

---

@Perarasi wrote:

Yes i am sure that i have access to that machine from my PC.What will be the possible reason that it says it's not a path?

---

Like dkfire mentioned above, you need to probe the path to see what it's saying is not a path. The error itself is telling you exactly where to look for the issue. There are many debugging tools supplied for you in LabVIEW, but if you don't use them then we won't be able to even tell you what's going wrong.