01-14-2015 11:25 AM
I am using LV2013 SP1 and working to replace existing FTP functionality with WebDAV.
For this task, I need to get a listing of files (*.tdms) on the RT (cRIO) and allow the user to select those for transfer.
My current FTP method displays name, date & size in a listbox for sorting and selection.
Regardless of whether I use WebDAV Synchronous or Asynchronous VIs to retreive a directory list, the file info's cluster type and last modification elements are empty. The RT has WebDAV Server 13.5.0 installed.
I did notice that the type is populated for text files (text/plain), but last modified is still empty.
I'm guessing the MIME type of TDMS files doesn't exist? I don't require that information for sorting.
However, the last modified information is very important for my applications & users for sorting the file list.
Could this possible be an issue with any RT settings or missing software?
Thanks for any suggestions/assistance.
James
Solved! Go to Solution.
01-15-2015 03:42 PM
Hi James,
That is certainly a strange issue. Can you post up your code so that I can try to replicate the behavior?
01-15-2015 04:07 PM
Hi Thomas,
Thanks for the response.
You can use the NI Example Finder and enter "WebDAV" to locate the WebDAV Data Acquisition.lvproj and simply run the Windows WebDAV Sync.vi to see the problem with WebDAV Asynchronous VIs.
I decided to use WebDAV Synchronous VIs in my application, but see the same problem.
Here's the WebDAV section of my code.
Thanks for any suggestions.
James
01-16-2015 02:20 PM
Hey James,
While I was researching this issue I found that you are currently working with another Applications Engineeer on a Service Request. From here it would be best to consolidate all of our effort on that Service Request. We will update this posting once we reach a resolution.
01-16-2015 02:46 PM
Yes, I agree.
When the root cause is identified and a solution or CAR created I can update this thread.
James
01-20-2015 01:35 PM
The issue has been assigned to CAR 513004
The problem details...
James
01-17-2017 10:45 AM
I hadn't thought about this thread in a long time, but this bug (CAR 513004) was corrected with the release of LabVIEW 2015; Release Notes.