Timer as input function calculates wrong

ahahn
Topic Author
Offline
Elite Member
Posts: 303
Thank you received: 143

TPL_KUNENA_MESSAGE_CREATED Timer as input function calculates wrong

13 Sep 2025 19:07 - 13 Sep 2025 19:08

#1

DC-24-II, version 6.03.1832

Since version 6.03.1832 a timer can be used as input function.
The calculated values of the actual implementation do not match the description in the manual. The result is likely to be incorrect.

Statement in manual

Attachment 2025-09-13_20h37_09.png not found

Timer T1 settings

Attachment Screen004_2025-09-13.png not found

Code:

Timer used as input function
                     +------------------------+------------- ----------+
                     |      wrong output      |   correct output       |
                     |   version 6.03.1832    |                        |
+--------------------+------------------------+------------------------+
| Timer (Flugzeit)   | -100..+100% | 0..100%  | -100..+100% | 0..100%  |
| 01:00 downto 00:00 |   (Mitte)   |          |   (Mitte)   |          |
+--------------------+-------------+----------+-------------+----------+
|      01:00 (start) |   +100%     |  +100%   |   +100%     |  +100%   |
|      00:45         |    +75%     |    ..    |    +50%     |   +75%   |
|      00:30         |    +50%     |   +75%   |      0%     |   +50%   |
|      00:15         |    +25%     |    ..    |    -50%     |   +25%   |
|      00:00 (end)   |     0%      |   +50%   |   -100%     |     0%   |
|     -00:15         |    -25%     |    ..    |   -100%     |     0%   |
|     -00:30         |    -50%     |   +25%   |   -100%     |     0%   |
|     -00:45         |    -75%     |    ..    |   -100%     |     0%   |
|     -01:00         |   -100%     |    0%    |   -100%     |     0%   |
|     -01:15         |   -100%     |    0%    |   -100%     |     0%   |
+--------------------+-------------+----------+-------------+----------+

Use standard input function, e.g. P4
+--------------------+-------------+----------+
|     input P4       | -100..+100% | 0..100%  |
|                    |   (Mitte)   |          |
+--------------------+-------------+----------+
|  max (upper pos)   |   +100%     |  +100%   |
|      ...           |    +50%     |   +75%   |
|     center         |     0%      |   +50%   |
|      ...           |    -50%     |   +25%   |
|  min (lower pos)   |   -100%     |    0%    |
+--------------------+-------------+----------+

Any thoughts?
Am I correct or is it a feature?

regards
Alois

Last edit: 13 Sep 2025 19:08 by ahahn.

Please Log in or Create an account to join the conversation.

sunbeam
Offline
Platinum Member
Posts: 2843
Thank you received: 896

TPL_KUNENA_MESSAGE_REPLIED_NEW Timer as input function calculates wrong

14 Sep 2025 15:49

#2

I did not know this feature before (or I forgot it), but at timer = 0:00 I would expect the output to be 0 like Jeti does (see your two left collums). So I guess it is not a bug, but a feature

Regards, Kai

Please Log in or Create an account to join the conversation.

ahahn
Topic Author
Offline
Elite Member
Posts: 303
Thank you received: 143

TPL_KUNENA_MESSAGE_REPLIED_NEW Timer as input function calculates wrong

14 Sep 2025 18:46

#3

Hi Kai,

I still think it's not implemented correct. The timer range, e.g. from 01:00 to 00:00, should represent the full input range. Just like P7, turning from full left to full right.

In your case, you would switch off "center/Mitte" and the output will run from +100 to 0.
If you "reverse" it, it will run from 0 to 100.

In the current implementation, the output continues changing, even the timer is outside its start and end
range. In the example you see output changes when the timer runs from 00:00 to -01:00. IMO this is a bug, clearly.

Alois

Please Log in or Create an account to join the conversation.

ahahn
Topic Author
Offline
Elite Member
Posts: 303
Thank you received: 143

TPL_KUNENA_MESSAGE_REPLIED_NEW Timer as input function calculates wrong

15 Sep 2025 05:57

#4

Ingmar, please foward. Thank you, Alois

Please Log in or Create an account to join the conversation.

IG-Modellbau
Offline
Moderator
Posts: 3781
Thank you received: 2809

TPL_KUNENA_MESSAGE_REPLIED_NEW Timer as input function calculates wrong

15 Sep 2025 08:41

#5

Hallo an Alle,
ist weitergeleitet!

Ingmar

www.ig-modellbau.de
Mein YouTube Kanal

The following user(s) said Thank You: ahahn

Please Log in or Create an account to join the conversation.

sierra_uniform
Offline
Elite Member
Posts: 306
Thank you received: 149

TPL_KUNENA_MESSAGE_REPLIED_NEW Timer as input function calculates wrong

15 Sep 2025 12:10

#6

Hallo zusammen,

ich habe damit vor einiger Zeit auch herumexperimentiert und mir dann folgendes aufgeschrieben:

Ab V5.3 können auch Timer als Geber verwendet werden. Sinnvoll ist das aber nur bei Timern mit Zielwert. Egal, ob der Timer aufwärts oder abwärts läuft. Der Signalverlauf erfolgt immer von +100 % bis -100% bezogen auf den Zielwert. Der Zielwert ist bei 0% erreicht. Danach geht’s in die negativen Werte bis -100%. Weiter nach unten geht das Signal aber nicht.
Verwendet man den Timer für eine eigene Sprachausgabe, muss die Wirkrichtung bei der Zuweisung als Schalter auf invers gestellt werden.
Beispiele für Count-Down-Timer beginnend ab 5 Minuten (300 Sek):

a) Sprachausgabe „Landung einleiten“ bei 30 Sekunden vor Ablauf des Timers
Timer Schaltwert = 100/300*30 = 10 %
oder allgemein: 100%/Timerzeit[sek]*Vorwarnzeit[sek] = x %

b) Sprachausgabe „Zeitüberschreitung“ 30 Sekunden nach Ablauf des Timers
Timer Schaltwert = -100%/300*30) = -10 %
oder allgemein: -100/Timerzeit[sek]*Nachwarnzeit[sek]) = -x%

Verwendet man den Timer als normalen Geber, lässt er sich natürlich über Servoeinstellungen und Funktionskurven wie gehabt beeinflussen. Die Einstellungen für die Sprachausgabe bleiben dabei unberührt.

The following user(s) said Thank You: sunbeam, ahahn

Please Log in or Create an account to join the conversation.