Experimental Physics and Industrial Control System
|
Hi Scott
That looks like a severe bug. I will have a look on Monday.
Am 14.02.2025 um 19:10 schrieb Baily, Scott A via Tech-talk <tech-talk at aps.anl.gov>:
I seem to be having a problem with the formatting of 16-bit checksums from StreamDevice 2.8.25. When I use a string that ends with “%+<sum16>” in the protocol file, I get the correct checksum in ascii characters as expected, but I have
an extra leading 0 (5 characters instead of 4). A checksum that should be “0389” is written as “00389” A similar problem seems to be happening when reading (seems to be expecting an extra leading zero). I can work around this because I know what will
be sent and can ignore the checksum on reads,. Has anyone else had this problem? If this is working correctly for you, what version of StreamDevice are you using?
|
- References:
- StreamDevice Checksum formatting bug Baily, Scott A via Tech-talk
- Navigate by Date:
- Prev:
StreamDevice Checksum formatting bug Baily, Scott A via Tech-talk
- Next:
Re: IOC, QServ, and AMSG / alarm.message Michael Davidsaver via Tech-talk
- 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>
- Navigate by Thread:
- Prev:
StreamDevice Checksum formatting bug Baily, Scott A via Tech-talk
- Next:
Re: StreamDevice Checksum formatting bug Baily, Scott A via Tech-talk
- 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>
|
ANJ, 16 Feb 2025 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
·
Download
·
Search
·
IRMIS
·
Talk
·
Documents
·
Links
·
Licensing
·
|