Search the web
Sign In
New User? Sign Up
lecis-post · The ASTM E1989-98 (LECIS) standard defines a uniform remote control interface for laboratory instruments.
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Hear how Yahoo! Groups has changed the lives of others. Take me there.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
STATE_CHANGED ?   Message List  
Reply | Forward Message #68 of 131 |
RE: [lecis-post] STATE_CHANGED ?

Dorothe,

Did you get any responses one way or the other? Were they helpful? Did you
get an answer to your question?

I would be interested to know. You probablky know by now the OMG have given
the green light on the LECIS spec (attached)

Regards,

Tony



-----Original Message-----
From: dorothe_steidinger@...
[mailto:dorothe_steidinger@...]
Sent: 17 July 2001 10:03
To: lecis-post@yahoogroups.com
Subject: [lecis-post] STATE_CHANGED ?


PFIZER GLOBAL RESEARCH AND DEVELOPMENT
----------------------------------------------------------------
This message and any attachment has been virus checked by the
PGRD Sandwich Data Centre.
----------------------------------------------------------------

Hello,

I would appreciate if someone could help me with the interpretation of the
ASTM standard regarding the STATE_CHANGED message, in particular for the
POWERED UP state.

According to 7.4.1.1 the SLM connects to the TSC, then changes to POWERED
UP, and needs to announce this with a STATE_CHANGED message.
On the other side, POWERED UP is the very default state (that of Control
Flow, which is the entry state of Operating, which is the entry state of the
top level state), from where connection to the TSC is started (6.1.1) and
from where state changes must be due to commands or event reports (7.3.1).

I think there is a contradiction between 7.4.1.1 and the other sections
dealing with POWERED UP and the state changed message, and I'm not convinced
that the state changed message should be sent (in the same way as the entry
in LOCAL CONTROL doesn't need to be announced) as at that point the SLM
hasn't really changed a state in a current interaction (7.5.1). The TSC can
always query the status of the Control Flow interaction if it wants to know
what state the SLM is in.

Does anyone agree/disagree?

Best regards,

Dorothe Steidinger

LEGAL NOTICE

Unless expressly stated otherwise, this message is confidential and
may be privileged. It is intended for the addressee(s) only. Access to
this e-mail by anyone else is unauthorised. If you are not an
addressee, any disclosure or copying of the contents of this e-mail or
any action taken (or not taken) in reliance on it is unauthorised and
may be unlawful. If you are not an addressee, please inform the sender
immediately.

Pfizer Limited is registered in England under No. 526209 with its
registered office at Ramsgate Road, Sandwich, Kent CT13 9NJ



PFIZER GLOBAL RESEARCH AND DEVELOPMENT
----------------------------------------------------------------
This message and any attachment has been virus checked by the
PGRD Sandwich Data Centre.
----------------------------------------------------------------


To view archived messages, go to:
http://groups.yahoo.com/group/lecis-post/messages


Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



PFIZER GLOBAL RESEARCH AND DEVELOPMENT
----------------------------------------------------------------
This message and any attachment has been virus checked by the
PGRD Sandwich Data Centre.
----------------------------------------------------------------


Fri Jul 20, 2001 8:25 am

tony_parsons@...
Send Email Send Email

[lecis-post] LECIS recommended for adoption by OMG


The OMG LECIS specification has been accepted by the OMG.

In detail:
The LSR (lifescience) taskforce has voted in favour of LECIS and the OMG
Architectural Board (AB) recommended LECIS for "adoption" .
In the next few weeks, the OMG will send all members a ballot to vote for
the LECIS adoption. This is normally not a problem, since the AB has already
recommended it.
Nonetheless,the AB requires us to make some changes to the specification.
This includes things like the IDL naming conventions, and other minor
things, which will not change the overall concept of the specification.
These changes can (officially) be made in a OMG Finalization Task Force
(FTF). An FTF will be created at the next meeting.
In the next 18 Month, we must provide an implementation for OMG LECIS.
Otherwise the OMG will dismiss the specification. The FTF will resolve all
problems in the spec that will be found during the implementation. After
the FTF is done, the LECIS specification will become a "formal" OMG
specification.

Everybody, who is interested in implementing the specification should
contact me (thorsten.richter@...) to get information about
the latest version of the specification.

Currently the AB voted on the document lifesci/01-06-01 with the errata
document lifesci/01-07-08.
In the next few days I will provide the convienience document including the
changes. It has the OMG document number lifesci/01-07-09.
The documents can be found soon at:
http://www.omg.org/techprocess/meetings/schedule/LECIS_RFP.html

In the next weeks we are going to include most of the requested changes of
the AB. This document will provide a basis for a consistent implementation,
that will already include many changes that will (officially) be made during
the FTF process.

Regards,
Thorsten




Thorsten Richter,
Product Innovation, Project Manager
--------------------------------------------------------------
CREON·LAB·CONTROL AG
Postfach 4526,
D-65035 Wiesbaden, Germany
Tel. +49 611 5050 260 Fax. +49 611 5050576
http://www.creonlabcontrol.com
--------------------------------------------------------------
To view archived messages, go to:
http://groups.yahoo.com/group/lecis-post/messages
<http://groups.yahoo.com/group/lecis-post/messages>


Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .


Tue Jul 17, 2001 10:25 am

thorsten.richter@...
Send Email Send Email
Forward
Message #68 of 131 |
Expand Messages Author Sort by Date

Hello, I would appreciate if someone could help me with the interpretation of the ASTM standard regarding the STATE_CHANGED message, in particular for the ...
dorothe_steidinger@...
Send Email
Jul 17, 2001
1:57 pm

Dorothe, Did you get any responses one way or the other? Were they helpful? Did you get an answer to your question? I would be interested to know. You...
tony_parsons@...
Send Email
Jul 20, 2001
1:55 pm

Hi Dorothe ... Yes. The ASTM standard does contain quite a few "ambiguities" that require clarification before it can be successfully (or at least...
Jon Wallis
jon.wallis@...
Send Email
Jul 20, 2001
6:26 pm

Except that, since the SLM never returns to the "POWERED UP" state, the TSC needs to ask on each new connection whether it has just turned on or has been on...
Jim Redman
jim@...
Send Email
Jul 20, 2001
10:15 pm

... I'm not quite sure why it should need to do this. Why should it matter? The TSC only needs to know if the SLM is there, and is in the POWERED UP state. ...
Jon Wallis
jon.wallis@...
Send Email
Jul 21, 2001
4:54 pm

... The problem is that on loss of communication the SLM returns to IDLE, not POWERED UP. This means that everytime a connection is made from the SLM to the...
Jim Redman
jim@...
Send Email
Jul 21, 2001
6:01 pm

... Yes, I agree such a scenario is possible. If this did happen, and connection failures occurred (which I agree is very likely) TCP would (or should) handle...
Jon Wallis
jon.wallis@...
Send Email
Jul 22, 2001
3:29 am

... How do we change it, or at least make it a mandatory option. I can argue technology all day, but the most convincing argument for me is that in ...
Jim Redman
jim@...
Send Email
Jul 22, 2001
3:22 pm

Hello, ... Never say never. Power-cycling the SLM is not the only way of sending it to POWERED UP; the transition from ESTOPPED to CONTROL FLOW is another one....
dorothe_steidinger@...
Send Email
Jul 23, 2001
1:22 pm

Hello Jon, ... That would create another inconsistency: the change from 'nothing' to 'LOCAL CONTROL' then should have been listed in 4.6.5 as state change that...
dorothe_steidinger@...
Send Email
Jul 23, 2001
1:22 pm

... That's not quite true, it stays where it is or it pauses. ... INIT should only be accepted if the SLM is in POWERED UP, from NORMAL OPERATION you'd need...
dorothe_steidinger@...
Send Email
Jul 23, 2001
1:27 pm

... You're right, that opens up a whole new can of worms. The spec says that the SLM can drop information when the connection doesn't exist. If the ...
Jim Redman
jim@...
Send Email
Jul 23, 2001
6:19 pm

Dorothe, ... True, but that's why we suggested you don't think of STATE_CHANGED (POWERED UP) as a state change, but as an "I'm here" message. ... There is no...
Colin Read
Colin.A.Read@...
Send Email
Jul 24, 2001
4:26 pm

Colin, Jon, ... The standard only says that manual intervention is required. The way I interpreted it is as follows: - the 'one-way transition' means that the...
dorothe_steidinger@...
Send Email
Jul 25, 2001
5:08 pm

Dorothe, ... Correct. ... back ... cell' ... Please do not confuse the standards requirements with individual SLM implementations. What you have described...
Colin Read
Colin.A.Read@...
Send Email
Jul 26, 2001
3:07 pm

Hello, ... True, and as such it has to cater for both. I imagine though that a hardware reset entails dropping/re-establishing the connection whereas a...
dorothe_steidinger@...
Send Email
Jul 27, 2001
1:16 pm

Hi Dorothe ... The definition of a *hard reset* is when the SLM's power is switched off and then on again (what is also sometimes called *power cycling*). A...
Jon Wallis
jon.wallis@...
Send Email
Jul 30, 2001
1:29 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help