Ted Kosan wrote:
> Just send your application challenges to the list and I
> will attempt to wire an application together using the
> (above referenced) wiring tool mockup. Of course, I am
> free to come up with Embedlets and Proxies to help me solve
> these problems but this is one of the reasons for doing
> this exercise.
We have started to work on an interface to the TRI-PLC device at
www.triplc.com. This device can be accessed directly, or via TCP/IP (by
connecting to a PC whose serial port is connected to the device, and it
is running the 'server').
We are creating a polling engine for access to the PLC to do data
gathering off of it. It will continue to run as a PLC and manage
whatever it is programmed to. What we want to do is allow a collection
of features of the PLC to be specified as the 'enterprise data', and
then a sub-collection of that collection to be specified as 'triggers'.
So, when one of trigger conditions are met, the current values are read
(except for the trigger) and the appointed collection of data is
published to the enterprise system.
This is a pretty sophisticated interface, but it is where I think that
this group needs to be able to go.
Gregg
|
