Suggestion to change okFilePipe documentation

[mwayne]

Hello,

We ran into some confusion when trying to get a simple okFilePipe working, and have some suggestions for the documentation page and maybe even the error messages.

Firstly, we copied the XML example for okFilePipe given on the webpage into our code, and were getting the error message “UnsupportedFeature”. It turns out that the example given has a length parameter of 5000, an invalid length for USB which needs particular powers of 2. A small header on the webpage stating what sizes are applicable would be nice, as well as changing the error message to something more informative.

It turns out other users have voiced this exact suggestion in a thread six years old.

Minimum BTPipeIn length

Thank you! What I’ve decided to do is use one pipeIn for the main bulk of data. A second pipeIn is used for the remaining data. The first 4 bytes define the number of valid bytes to follow. The first 4 bytes also hold flags to be written along with the last valid data. The data buses from of the two pipIns are then multiplexed into a FIFO. I am assuming that the first pipeIn will be complete before the second starts!

Secondly, there’s no example for the filename field. It may seem obvious that one should write the full path name without single or double quotes, but it’s a text field and the syntax is not well defined on the page. Adding that in the XML example would be nice.

Thank you!

[tom_mcleod]

Hello,

We have added additional language in our documentation to clarify these points.

Note that while 5000 is an invalid length for a USB3 device, this example was likely written with a USB2 device in mind where this is a valid length. We have updated the value to one that works for both devices.

Thank you for pointing this out.