Execution ends with a detected error and result indicates FilePathInvalid.

oThe specified file or the directory is not available.

oThe given file path has invalid syntax.

oVerify that the file exists under the specified directory. In case the file path targets extended memory (such as an SD memory card), verify that it is available.

oVerify that the syntax used is supported by your particular controller.

For example, your controller may support '\' as a separator, while another controller supports '/' instead.

Execution ends with a detected error and result indicates FileInvalid.

oThe file contains characters outside the ASCII range.

oDuring parsing, an unexpected closing tag has been detected.

oVerify that the file contains only ASCII characters.

oVerify that the XML file is valid: Make sure that each open tag is closed and that the elements are properly nested.

NOTE: Element names are case-sensitive.

Execution ends with a detected error and result indicates XPathExpressionInvalid.

oThe entered XPath expression is invalid or not supported.

oVerify the correct syntax of the XPath expression.

oVerify that the expression is supported by the function block.

Execution ends with a detected error and result indicates NumOfParentsExceeded.

oThe nesting depth of elements in the XML file to read is larger than specified.

oIncrease the value for the parameter Gc_udiXmlMaxNumOfParents in the GPL.

oAvoid the use of files with deeply nested XML structures.

Execution ends with a detected error and result indicates BufferFull.

oThe number of items in the XML file to read is greater than the size of the buffer provided by the application.

oIncrease the buffer size by the parameter Gc_XmlMaxNumOfItems in the GPL.

oSplit the read operation in several blocks. Use an appropriate XPath expression to limit the number of elements to read per block.

Execution ends with a detected error and result indicates ElementNotFound.

oThe element specified in the XPath expression does not exist in the file.

oThe path declaration in the XPath expression does not match the structure in the XML file.

oThere is a typing error in the XPath expression.

oVerify that the specified element is typed correctly.

oVerify that the path declaration meets the expected structure in the XML file.

oVerify that the correct XML file is specified with the parameter i_sFilePath.

Execution ends with a detected error and result indicates FileInconsistent.

oThe end of file has been reached but at least one tag has not been closed.

oVerify that the XML file is valid: Make sure that each open tag is closed and that the elements are properly nested.