time get input port for custom BlockDriver/TimeManager component

[Jmb5501]

I am currently building a custom block driver/time setter component that drives rate groups based on a clock from an external simulation. This component also needs to read in time from that simulation and set the FSW's clock accordingly. I have the first part figured out, but am struggling to hook up this component to the time connections in my topology. The error I am getting says instance <myCompnent> has no time get input port. I am defining a time get port in the fpp, and I have directly copied the function defintion of timeGetPort_handler from the LinuxTimeImpl.cpp file into my component. What else am I missing here to be able to use this component as my time source?

[LeStarch]

Does the definition of the time get port on myComponent's model look exactly like the following?

sync input port timeGetPort: Fw.Time

[LeStarch]

My guess is that the thread dispatching inside a container is too slow to keep up with 2500Hz. This may be compounded if the containerization is also emulating (e.g. QEMU).

I might suggest this: clock your simulation at 1x and then ramp up the speed-multiplier? That will show you where it starts to break down. You can also try to reduce the overhead of the container/emulation if possible....but knowing what multiplier starts to break will tell you "how much" overhead must be dealt with.

[timcanham]

The other thing you can do is to add a component to the end of the rate group to start the next cycle. That way the simulation can auto-scale depending on the speed of the container.

[Jmb5501]

@LeStarch I should maybe clarify: both the sim and the FSW are running in a container on a Linux VM.

[LeStarch]

My point is that containers often have overhead and as such can be slower than traditional systems. Hence looking at specifically at how fast things can be clocked.

[Jmb5501]

This works beautifully, thanks a ton. Able to run sims at 100x realtime with FSW in the loop.