Subject: |
Re: Dev Asyn and Cygwin/Win IOCs , Modbus and scheduling. |
From: |
Bill Nolan <[email protected]> |
To: |
Tech-Talk <[email protected]> |
Date: |
Fri, 18 Aug 2006 14:27:10 -0500 |
What I am actually looking to do is well suited to SNL,
I am scheduling the path a product will take through a production
line, starting with input bins and ending in output bins.
Each step in the production functions independataly and is
controlled by some form of low level controller, in some cases that is
an EPICS iOC, but in most cases it it a vendor supplied software package
with high level hooks, typically a stringout and two Bi/Bo records.
If the process was static or semi static I could schedule it using
SNL and have no issues at all, But the process is VERY dynamic, changing
as much as 3 time in an 8hr day. So I need a way to control the sequence
of events that is easy and rapid to program.
I have looked at using SEQ or SSEQ records, but the any way i have
been able to think of to model the process has be requiring a new
instance of the seq record for each piece going through the system. And
well, until we get a dynamic database loader that is out.
I was considering possibly writing a GUI State editor and doing some
sort of compile on the fly state programs, but that seems like, well, a
lot of work.
The real killer is that the only thing that is fixed in the entire
system are the records in my database, how they connect and in what
order is entirely dynamic.
--Bill
Tim Mooney wrote:
> Bill Nolan wrote:
>
>> Hi all,
>> Has anyone had experience with using DevAsyn on a win/cygwin based
>> IOC's ? was it good, bad ?
>> Second, Has anyone worked with Modbus-TCP and the Phoenix contact
>> controllers ?
>> And lastly has anyone done any work at all with dynamic sequences or
>> runtime editable sequences or event scheduling.
>
>
> I'm not sure what you mean by the last item. I gather you're talking
> about something beyond the capability of the seq and sseq records.
> (sseq is seq extended to handle strings or numbers, and, optionally, to
> wait for processing completion between sequence steps.)
>
> The synApps std module also has something called the 4step database,
> which performs up to four user-programmable control actions, each
> followed by a completion wait, and by user-programmable read and
> calculate actions.
>
- Replies:
- Re: Dev Asyn and Cygwin/Win IOCs , Modbus and scheduling. Tim Mooney
- References:
- Dev Asyn and Cygwin/Win IOCs , Modbus and scheduling. Bill Nolan
- Re: Dev Asyn and Cygwin/Win IOCs , Modbus and scheduling. Tim Mooney
- Navigate by Date:
- Prev:
Re: VCCT and CA sniffer Ernest L. Williams Jr.
- Next:
Re: Dev Asyn and Cygwin/Win IOCs , Modbus and scheduling. Tim Mooney
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Dev Asyn and Cygwin/Win IOCs , Modbus and scheduling. Tim Mooney
- Next:
Re: Dev Asyn and Cygwin/Win IOCs , Modbus and scheduling. Tim Mooney
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|