| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: hex stream processing with StreamDevice? |
| From: | Eric Norum <[email protected]> |
| To: | "Barker, Alan M." <[email protected]> |
| Cc: | EPICS tech-talk <[email protected]> |
| Date: | Fri, 20 Aug 2010 08:45:54 -0700 |
Adding an interpose layer like this is how I handled the case of reading some arbitrary-length binary data using streamDevice. Contact me if you'd like to have a look at this. It's not 100% tested so I don't want to post it everywhere yet. On Aug 20, 2010, at 3:14 AM, Dirk Zimoch wrote: > Alan, > > Maybe you should try to write an interpose layer for asyn that handles all the "outer" protocol issues and leaves only the user data to stream or other device support. See the asyn documentation and some example interpose layers in asyn. -- Eric Norum [email protected]