From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 115aec,47cd14062de43094 X-Google-Thread: 103376,47cd14062de43094 X-Google-Attributes: gid115aec,gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.realtime,comp.lang.ada Subject: Re: next_period = start + n*period; versus next_period = next_period+period; Date: Wed, 27 Oct 2004 16:41:09 +0200 Message-ID: References: <87sm81o0vt.fsf@deneb.enyo.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de +c0fmIZtcaI/eFIo08YSsw0Sv83VTC4MqbwKkW+W4zIXBLc04= User-Agent: 40tude_Dialog/2.0.12.1 Xref: g2news1.google.com comp.realtime:524 comp.lang.ada:5771 Date: 2004-10-27T16:41:09+02:00 List-Id: On Wed, 27 Oct 2004 08:46:29 -0500, Mark H Johnson wrote: > Dmitry A. Kazakov wrote: > >> [snip] >> >> Right. However there could be other issues to consider: >> [snip] >> >> 2. What happens when the task misses a deadline? Usually it should skip one >> "tick" and go to the next one. >> > Maybe yes, maybe no. I have built several system where if you run long > in one frame, you try to catch up the next one. For example, I may have > an 80 Hz task running. It is connected to a 1553 bus where at 1 Hz, I > get more messages than any other 80 Hz frame. If I overrun that one > frame (out of 80), I don't mind running the next frame a little late. > > It all depends on the application being designed and the safety (or > accuracy) considerations of that design. Yes, if you change the requirements. (:-)) However, surely, it is questionable whether jitter and even more so, a small absolute time lag is a real issue in say 80-100% cases. In my ignorance I always had an impression that guys developing controllers are just too lazy. They are pushing the problems with their bad models to us, pure programmers! (:-)) -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de