CFE_ES_GetTaskInfo: Task ID Not Valid: 0 about cfs HOT 4 CLOSED

This is correct/expected behavior. A timer callback is a different task context. Therefore when the CFE_SB_SendMsg call determines the calling context, it isn't from a thread/application that CFE ES knows about, and therefore you get this warning.

There are two alternative approaches:

• Create a semaphore and a child task. Timer callback posts the semaphore. Child task pends on the semaphore, then does any remaining work and sends the message.
• Use SCH to schedule your wakeup events rather than creating an OSAL timer directly. This is basically the same idea as above but uses the message pipe instead of a semaphore to perform wakeup.

from cfs.

This may be worth a quick discussion - maybe we should consider implementing a more descriptive error/event message than "Task ID Not Valid: 0"? This error string is not very helpful or informative and probably could be better.

from cfs.

I definitely support a more descriptive response.

from cfs.

Is it necessary for SB to know which calling context it is inside? (e.g. is GetTaskInfo(), CFE_ES_GetTaskInfo() a must?)

from cfs.