Component initialization that allows logging

[keck-in-space]

Hello,

I would like to be able to initialize a database connection as part of my component starting up. I can do this fine in the constructor, but due to how F-Prime starts up, the logging ability is not enabled at the constructor phase, so I have limited options for alerting via GDS that the connection attempt failed or if any issues were encountered.

I am fine with moving this to another function and having it called by F-Prime elsewhere, but I do not know how to do this.

I've tried creating a public initialize call in the component class and calling that at the end of setupTopology, but that does not appear to work. At least, I can't get any logging to occur there.

My basic question is: Is there some way to ask F-Prime to run an initialize call for a specific component after the system has been brought up and it is possible to log events and telemetry?

[timcanham]

@keck-in-space You should be able to do your initialize() call in your setup in a place equivalent to here:

https://github.com/nasa/fprime/blob/devel/Ref/Top/RefTopology.cpp#L174

At that point, all the ports are connected, so you should see messages.

[keck-in-space]

Thanks Tim.

I added the call to my initializer at the end of the setupTopology function, but I am still not seeing any event logs.

That function does create a file, which I verified is being created. So, the function runs, but no logs are output, not even in the event.log file inside the logs folder.

The last step I tried is to wire up the initialize call to a command, which does run and generate event logs, so I know that function does create events correctly.

Any other ideas as to why I can't get logs through even when calling the initializer at the end of the setupTopology function?

[keck-in-space]

I am really referring to the ability to send Events. For example, I'd like to send a log_DIAGNOSTIC_CompName as part of an initialize function call for a component. I placed the call at the line specified by @timcanham, but I did not get any events.

[LeStarch]

Ah! DIAGNOSTIC events are filtered out by default by the ActiveLogger. You could make them active high or active low.

[LeStarch]

You may also set the base configuration for active logger:

 FILTER_DIAGNOSTIC_DEFAULT = false, //!< DIAGNOSTIC events are filtered at input

[keck-in-space]

Oh, I should have mentioned this. I have already changed the config to allow diagnostic messages. I can see the diagnostic messages in GDS when running normally (outside of the initialize function). But, even when I call initialize here: https://github.com/nasa/fprime/blob/devel/Ref/Top/RefTopology.cpp#L174, I get no Events.

[keck-in-space]

It might be relevant to also know we are running F Prime version 3.4.3.

[keck-in-space]

Does anyone have any possible fixes for this? I am still experiencing this issue in F Prime 4.0.0. I cannot find a way to run an initializer for a component that has the ability to update telemetry channels or log an event at start up of the F Prime executable. I have tried adding the initializer to the DeploymentTopology.cpp right after the startTasks(state); call, but no telemetry channels are updated and nothing is logged via the event.