Component Properties in FPP

[timcanham]

FPP currently supports a general set of F Prime properties (queue depth, priority, etc) for configuring components. How about a notion of component-unique properties? They could be set in the topology to customize behavior in a more explicit and model-searchable ways. For instance:

module Svc {

  @ A component for running command sequences
  active component CmdSequencer {
  ...
  command recv port cmdIn
  ....
  property timeout: U32
  ...
 }
}

The topology FPP could have:

instance cmdSeq: Svc.CmdSequencer base id 0x0600 \
    queue size Default.QUEUE_SIZE \
    stack size Default.STACK_SIZE \
    priority 100 \
    timeout 10

The property fields could be any legal F Prime type.

The generated code could have:

class CmdSequencerComponentImpl final :
    public CmdSequencerComponentBase
  {

    public:

      void setProperty_timeout(F32 val);

where:

 void CmdSequencerComponentImpl::setProperty_timeout(F32 val) {
    this->m_property_timeout = val;
}

The generated code could call the setProperty_timeout(F32 val) function during init.

[zimri-leisher]

This is a decent idea, it removes the need for most of the "configure" functions. This is basically a compile-time parameter.
Maybe a better idea that works with the Fprime system more would be per-instance setting of default prm values?

[celskeggs]

Another approach to this sort of configuration was previously discussed here: nasa/fpp#600