Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GV not evaluated properly for a>b or a<b #3411

Closed
filago opened this issue Apr 10, 2016 · 2 comments
Closed

GV not evaluated properly for a>b or a<b #3411

filago opened this issue Apr 10, 2016 · 2 comments

Comments

@filago
Copy link

filago commented Apr 10, 2016

It appears that the GV value used to determine a Logical Switch with a>b or a<b is ~1/10 the actual GV value. This is with 2.1.7; I didn't check other versions.

Example:
SF1: ON Adjust GV1 Source S1
L1: a>b, Thr, S1
L2: a>b, Thr, GV1
L3: a<b, GV1, Thr

I believe L1-L3 are logically equivalent so they should go ON/OFF together, but they don't. L1 behaves as expected, going ON when Thr exceeds S1 value. But L2 and L3 go ON when Thr exceeds ~1/10 the S1 value.

@kilrah
Copy link
Member

kilrah commented Apr 11, 2016

See here for an explanation:
#1361

@kilrah kilrah closed this as completed Apr 11, 2016
@filago
Copy link
Author

filago commented Apr 11, 2016

OK, thanks. My apologies for not researching to find that this is intended behavior for now.

#3185 indicates that it may be resolved at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants