Using tcp/ip as an I/O interface

StateWORKS RTDB is a tcp/ip server. All attributes of each object in RTDB can be accessed by tcp/ip clients. A client connects to the RTDB server using two sockets: Request and Event. The Request (R) socket is used for queering of object attributes. The Event (E) socket delivers object attributes that are registered as "advise" in RTDB.

The primary goal of the server/client model of the RTDB has been communication with a User Interface. When the tcp/ip communication began to be used for input/output purposes we could extend the StateWORKS server/client model very easily by completing attributes of corresponding object by a concept of RawData. The completion of Raw data are required for objects: DI, DO, NI, NO, the objects CMD, XDA, PAR and DAT possessing per se the raw data values.

We have add another technical note to our web site describing the tcp/ip communication in RTDB. You may download the note http://www.stateworks.com/active/download/TN24-Using-tcpip-as-io.pdf to study the details.

...continue reading "Using tcp/ip as an I/O interface"

Search tags: StateWORKS

Posted by Ferdinand Wagner on Friday 18 July 2008 at 12:09
Permalink | Comments (0)

Getting started

I received an email from John M. who is evaluating StateWORKS. He started with a fairly complex example that has confronted him with several issues that must be understood to use effectively our tools and the run-time system. Because of a general nature of his questions I put (with his acceptance) my answers into that blog.

...continue reading "Getting started"

Search tags: StateWORKS ,  finite state machine,  StateWORKS,  state transition,  input action,  entry action

Posted by Ferdinand Wagner on Monday 07 July 2008 at 12:38
Permalink | Comments (1)

Book critics

Our book "Modeling software with Finite State Machines" has received quite good reviews. Recently, I read in Amazon two controversial reviews on which I commented to my friends in an email as follows:

...continue reading "Book critics"

Search tags: General ,  modeling software,  finite state machine

Posted by Ferdinand Wagner on Tuesday 11 March 2008 at 10:08
Permalink | Comments (0)

What is a state machine?

Our web site contains several technical notes and papers that discuss some aspects of software engineering associated with the concept of a finite state machine. On introducing our blog we have decided to present you a few topics covered by a group of our documents. We started with the Mealy and Moore models of a finite state machine, honoring the fact that it is a favorite topic according to visitors' statistics. The topic that we would like to present you today is "What is a state machine".

...continue reading "What is a state machine?"

Search tags: Finite state machine ,  state machine,  state,  automata,  stateworks

Posted by Ferdinand Wagner on Monday 03 March 2008 at 08:00
Permalink | Comments (0)

Moore or Mealy model

Moore and Mealy models are the basic two models of state machines as defined in the literature. To understand the differences between them the actions (outputs) must be defined and bound to state changes. The technical note "Moore or Mealy model?" discusses both models and shows that the optimal solution is achieved when features of both models are used in a mixed model. Although the concepts of these two models are useful when performing certain theoretical studies, they are also interesting for software developers, and StateWORKS makes the use of a mixed model easy and effective.

...continue reading "Moore or Mealy model"

Search tags: Finite state machine ,  state machine,  stateworks,  Moore,  Mealy

Posted by Ferdinand Wagner on Friday 22 February 2008 at 17:58
Permalink | Comments (0)