thank you very much for your quick response.
Well, of course there are ways to obtain the monitor data at least nearly at run time - it is just a matter of time and effort I have to spend on the subject. Retrieving the data via a named pipe would have been a very convenient way, and on the monitor side it would have required only little effort to support named pipes, too. I think the only thing that had to be done is to do without random file access - and to process a continuous data flow I do not need the number of fieldbus messages in the file header, for what reason the random file access is obviously required.
So I'd like to pose another question: Is it possible to obtain a version of the NI-FBUS Monitor that supports named pipes within a few weeks, and if so, at what price? I believe strongly that I am not the only one who would appreciate such extended features ...
I am afraid that we are not able to provide such a NI-FBUS Monitor within a few weeks. According to NI's product development criterion, every software which is released to customers must through well scheduled development phase and strictly testing process. This criterion aims to ensure the quality and reliability of NI software. I am sorry that a few weeks time is not enough for a new release.
Currently, we are correcting feedbacks on NI-FBUS Monitor software for the next release. Thank you very much for informing us this requirement. I will forward it to our R&D department.
Any suggestion and requirement on NI-FBUS products is mostly welcomed. You can also email to email@example.com for any NI-FBUS related requests.