Messages posted by: mlohbihler

If you can provide I/O logs of the traffic, the episodes can be simulated and we can check if there are changes to the software that may make the behaviour better. If you can create such logs with different timeouts, that would be ideal. See ModbusMaster.setIoLog.

You misinterpreted what they said. You had said you didn't know what hashes might be good for, and i provided an answer. You were using them inappropriately: as a unique key, rather than an indexing key, which are two different things. Since a hash is not guaranteed to be unique, you obviously should not use it for such a purpose.

That said, you need to reconsider what you can use as a unique key, if that is what you need. This is a question for you to decide. I don't know your application, and so can't really help.

Search for "why are hashes useful": http://stackoverflow.com/questions/506029/whats-the-purpose-in-hashing-information

Check out the DGLux module.

I would create a virtual binary that alternates every second, and then use a point link to have it control the modbus point.

Yes, it is certainly something that is possible. There must be something wrong in your setup.

Hmm, i can only assume that somewhere in my ant classpath is the RXTX lib, perhaps in the JVM that it references. So, it's a fluke that it works for me. You can always add the lib/RXTX jar into the build script. That should clear things up.

It's certainly not a small job. You would want to route acks from wherever they occur (MiscDwr and EventDwr come to mind) to the event manager, so that it can look up the instances. This would be a bit of work because events can RTN without being ack'ed, and so would not necessarily be in memory. The EventHandler will need to have a new notification method, which the event manager would call. Then all of the event handler implementations would need to be enhanced. Finally, the UI for each event handler would need to include the new notification.

Hi Michael,

I personally would not generate a new event upon an event acknowledgement. That feels a bit much like the snake eating its own tail. Instead, i would be inclined to add a new notification to the event itself.

Currently, an event is raised and in many cases returns to normal (or goes inactive). I would add to this a notification for when the event is acknowledged. The event handlers would need to be enhanced to handle this notification, but i believe it's the better way to go.

It was more a question out of curiosity. To make this work the data source would need to be changed to queue up set point requests, and then include them in the next response. Then there's the issue of whether confirmation is required from the remote device. This is not work that is on the development roadmap at the moment, especially since it also sounds very custom.

Dave, do you want the set points to be returned in the HTTP response? If so, in what format would they be returned?

Try the ASCII data source

Ah, ok. There are differences in the var names between M2M and MA, and also between MA 1.x and MA 2.x.

Note that you can return the stats object from your script and click the test icon if you want to see all of the attributes that it has. No need to guess about the attribute names.

The maximumTime attribute may be 0 if there were no values during the interval. What is the value of the "count" attribute?

Try maximumTime.

return pxxxx.past(DAY, 30).maximumTime