M2M2 is currently in Alpha, and is being reviewed by certain collaborators and customers. We are awaiting feedback from them, after which we will be able to provide a time line for other releases.
Technically yes. But all three are intended for different purposes, and have subtle differences. E.g. number 2 could be used for database serialization, but not in its current form because it is XID-based (not a deal breaker, really, but not ideal). Also, the current object serialization assumes data integrity. If it were text-base and therefore human editable, the code should no longer assume this.
From what i read DDE is meant for communication between Windows applications running on Windows platforms. And JDDE includes a DDL as the JNI component, which naturally is for Windows.
The problem with the library is it doesn't support 4 byte types. The writer of the library says that the canonical (and old) rtu specification doesn't support 4 byte types.
We're going to make this a pluggable feature of Mango V2 (aka M2M2). The thinking is that a template module could be written that would allow users to customize to their exact needs. Not sure how this will work exactly at the moment though.
Yes, we know of Jamod. It is a working implementation, but we decided to write our own for a number of reasons. We believe, as you have noted, that the Modbus4J library is now more advanced.
The Modbus4J library has a number of test classes that others have successfully used to set up their own integration.
Just a note: Java and Javascript are similar in syntax, but that's about it. I don't know if you've used the term interchangeably by mistake, but just so you know they are quite different.
what ever happened with this issue?
did we ever come up with a way to auto-ack alarms when they go inactive?
along those lines....
is there a way to turn off the ack requirement altogether?
i want to get emails but i don;t want to have to go to the web to ack alarms.
emails are enough.
Well, you could always just export the points and import then into the new data source. There's a bit of manual effort in there, but not as much as re-entering everything.