LIBNODAVE FAQ

Q: Can you give me a documentation about MPI protocol?

A: Here's what I know

Q: That warning on LIBNODAVE home page, does it mean the software is so dangerous/unreliable?

A: No, it's just there to prevent anybody from holding me responsible for whatever he might do with it. I trust my software. But I heard, in USA a manufacturer of ladders had to put a label on them saying: "Use on firm ground only" and another one: "Do not use on frozen dung."

Q: Why doesn't LIBNODAVE work with my MPI adapter?

A: Haven't heard this for quite while. If you have difficulties, first send me the output from testMPI, once started with and once without the option -2. Also include the exact order code of the adapter. I probably can help if I can provide such an adapter. If not, you may think about giving me access to your computer or sending me the adapter.

Q: Can LIBNODAVE work with CP 5x1x?

A: No, it can't. The reason is that there is no documentation for this hardware that would allow to write drivers for it. There are commercial products that use the drivers that are installed with Step7 or other Siemens software. But they are for Windows only.
I guess a speedy USB to MPI adapter could make this hardware obsolete.

Q: How can I support the development of LIBNODAVE?

A: Give feedback. I should like to be able to put as many order codes of supported hard ware on the list as possible.
Donations in hardware or money are allways very welcome.

Q: I want to use LIBNODAVE for my project, but will it support future hardware?

A: It does what it does and it is absolutely unlikely that it could fail with future members of S7 family or compatibles. Naturally, I cannot speak about an immaginary S9...

Q: What is the largest block of bytes LIBNODAVE can read/write to a PLC?

A: This is limited by the maximum length of a PDU, which in turn depends on your CPU type.For 240 byte PDU length, you can read 222 bytes and write 218 bytes in a single transaction.

Q: The xy software can write larger blocks, or?

A: No,whichever software hides that limit from you has to split larger blocks into multiple requests.

Q: Why don't you do that automatically also in LIBNODAVE?

A: LIBNODAVE is for programmers. They will be easily available to do it themselves. On the other hand, automatic splitting would hide a limit that costs performance...