LCD Display

[mark]

Thanks John

Now all is clear.
1. The SP5 patch solved the watchog loss.
2. It is not possible to use (0.01*SEC) since this rounds down to zero. Then the task doesn't get a timer queue and so can not do delays in the initialisation sequence, wher it subsequently gets stuck in this first phase.

I made a mistake to say that delays of zero are rounded up to 1. This only happens when commanding a monostable timer and not in the task configuration table... settings a value of 1 will also set the smallest possible delay of one TICK. The rule is obviously not to use a start up delay less that the TICK period since it will result in no timer being allocated...

Regards

Mark