#10 DRVH limit not working for float records

None
wont-fix
None
5
2015-01-05
2013-08-19
No

Tag: 3.0-pre1
OS: linux, 64-bit

In those cases where db record definition does not allow it, users should not be allowed to set values higher or lower than operating range. For ints and doubles this behavior works, but for floats it does not.

Steps to reproduce:

1) run test IOC using st.cmd from pvaSrv/testApp/iocBoot/testDbPv

2) invoke pvput commands as in the examples below (in all cases DRVH and HOPR are set to <= 10). Note that pvput for floats actually works, while for ints and doubles it sets record value to DRVH):

bash-4.1$ pvput float01 1112
Old : float01 5.6
New : float01 1112

bash-4.1$ pvput int01 1112
Old : int01 1
New : int01 9

bash-4.1$ pvput double01 1112
Old : double01 5
New : double01 9.9

Discussion

  • Matej Sekoranja

    Matej Sekoranja - 2013-09-19

    pvaSrv (the implementation) should disallow such puts. This is not responsibility of pvAccess - pvAccess only provides means to report this.

     
  • Matej Sekoranja

    Matej Sekoranja - 2013-09-19
    • assigned_to: Matej Sekoranja --> Ralph Lange
    • Group: -->
     
  • Matej Sekoranja

    Matej Sekoranja - 2013-09-19

    Reassigning.

     
  • Ralph Lange

    Ralph Lange - 2014-10-13
    • status: open --> wont-fix
    • Group: --> 4.4
     
  • Ralph Lange

    Ralph Lange - 2014-10-13

    Won't fix.

    This is a non-issue. Float and double records in the testTop example are basically inputs: ai is used for double, test's own float record for float.

    pvaSrv tests should cover hitting limits, but that's actually a different BUG [#27]

     

    Related

    BUGS: #27

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks