This error appears when a path has been incorrectly specified, which is most often caused by improper formatting of the path.
The preferred method of specifying file paths is to use a file path constant of c:\
and then use the Build Path.vi
to add your string constant to the path. Further details about this implementation can be found in Tutorial: Working With File Paths on Real-Time Targets
If for some reason you have to cast a string to path and cannot use the path control or constant, this error can occur if the string that you build into a path uses c:\
as the root directory. This might happen if you need to communicate a path over a string-only protocol like TCP. If you are building the file path from a string, you should use /c/
as a base path. Designate any subfolders using forward slashes instead of the backslashes used in a Windows path. Make sure to build the whole string before casting to a path. The VxWorks OS uses Unix-style file paths which follow this convention. The following snippet demonstrates the syntax for a file on a cRIO controller.
The path controls, indicators and VIs convert Windows style paths to the Unix format automatically. If you use a path constant or control and are not casting a string into a path, do not use the Unix style path. Entering a path in the Unix format will cause Error 1430