Hello bro,
sorry for (my easy) english. Im from Czech
I manage a gas heater like a thermostat with this device. It works properly.
I have two questions:
Why Events have smaller priority than Scheduler? Scheduler run heater (before coming home) and the Events doesnt stop when is the temperature above hysteresis.
Second question:
I try to connect by mobile phone (galaxy Ace) with opera (ver. 12.00.ADR-1207201819) and it doesnt work Instead it lag the Controler :o
Is the true, the Opera is too simple?
raptor napisał(a):I have two questions:
Why Events have smaller priority than Scheduler? Scheduler run heater (before coming home) and the Events doesnt stop when is the temperature above hysteresis.
Events has identical priorytet that scheduler.
State of the outputs is dependent on the last event of an config events, scheduler or watchdog
raptor napisał(a):Second question:
Is the true, the Opera is too simple?
We testet opera only PC computer and it works fine.
Maybe change the font size or resolution
Nothing happend because config events switches outs when the signal exceeds the setpoint + hysteresis and next setpoint- hysteresis.
In this case you have set point 17+ 0,6 hysteresis, if temp was below 17-0,6 (=17,6, then out0 OFF.
But if temp was above 16,4 (eg. 16,8) and next go to >=17,6, nothing hapend because temp never was below 16,4.
See picture
wilkxt napisał(a):Nothing happend because config events switches outs when the signal exceeds the setpoint + hysteresis and next setpoint- hysteresis.
In this case you have set point 17+ 0,6 hysteresis, if temp was below 17-0,6 (=17,6, then out0 OFF.
But if temp was above 16,4 (eg. 16,8) and next go to >=17,6, nothing hapend because temp never was below 16,4.
See picture
[ATTACHMENT NOT FOUND]
ok, when I push on by scheduler, I must stop by scheduler (for sure), I understand
It works well for other purposes.
New question:
Are you thinking about trigger which stop(start) the output depending on actual temperature, not hysteresis?
Thank you a lot for your time.
raptor napisał(a):ok, when I push on by scheduler, I must stop by scheduler (for sure), I understand
No, scheduler set out ON and events can OFF this out
raptor napisał(a):New question:
Are you thinking about trigger which stop(start) the output depending on actual temperature, not hysteresis?
You may set hysteresis to 0, but if inp8 wil be below 17 then out0 set ON, but you don't that? You want to set out0 ON only by scheduler(not event), and event have it OFF only when temp wil be above 17,6?
raptor napisał(a):ok, when I push on by scheduler, I must stop by scheduler (for sure), I understand
No, scheduler set out ON and events can OFF this out
wilkxt napisał(a):But if temp was above 16,4 (eg. 16,8) and next go to >=17,6, nothing hapend because temp never was below 16,4.
I don't know, how is the temperature when scheduler START out0, I must stop by scheduler (for sure).
wilkxt napisał(a):You may set hysteresis to 0, but if inp8 wil be below 17 then out0 set ON, but you don't that? You want to set out0 ON only by scheduler(not event), and event have it OFF only when temp wil be above 17,6?
Tel me what is lowest temperatur on INP8?
I would like to maintain the temperature in the house was close to 17-18 ° C (0.5 ° C hysteresis) - heater always slightly overheated. It works wonderfully
But.
When I come home, and when I get up, I'd like to have more heat.
Then I manually switch to a different event (20 ° C + -0.5 ° C)
The overheating must be fully automatically, because, I may have work responsibilities and do not have to be at home. perhaps
if there was a trigger at 22 ° C which would say STOP, it would be pretty easy.
Instead it lag the Controler :o