M
Michael Griffin
I didn't think your original explanation was complicated. Your reply is quite detailed, but it doesn't really answer my question. If you have an application program and a communications protocol driver, how do the two meet? How does the data get from the driver to the application?
You could simply provide a library and compile the driver into the application. However, this means re-compiling to add or change a driver. Many people would find this inconvenient or impractical (especially if they couldn't shut the program down).
The question isn't how you get the bytes out the ethernet (or serial) port, the question is how do you move the information between the application and the driver?
I would forsee you need to provide the following components:
1. Physical communications port.
2. Low level port driver (this may be provided by the O/S).
3. Protocol driver (e.g. modbus, profibus, etc.).
4. The application interface API (you suggested this as a register map).
5. The missing piece of the puzzle.
6. The application software.
The question is, what is #5? Whatever it is, it should preferrably be some existing standard rather than something new you had to invent for the purpose.
--
************************
Michael Griffin
London, Ont. Canada
************************
You could simply provide a library and compile the driver into the application. However, this means re-compiling to add or change a driver. Many people would find this inconvenient or impractical (especially if they couldn't shut the program down).
The question isn't how you get the bytes out the ethernet (or serial) port, the question is how do you move the information between the application and the driver?
I would forsee you need to provide the following components:
1. Physical communications port.
2. Low level port driver (this may be provided by the O/S).
3. Protocol driver (e.g. modbus, profibus, etc.).
4. The application interface API (you suggested this as a register map).
5. The missing piece of the puzzle.
6. The application software.
The question is, what is #5? Whatever it is, it should preferrably be some existing standard rather than something new you had to invent for the purpose.
--
************************
Michael Griffin
London, Ont. Canada
************************