Submit ideas for Improving F´ Code Consistency

[thomas-bc]

Call for Comments

Dear Community,

As part of the improvements we are targeting to introduce with the v4.0.0 Release, we would like to solidify the consistency of our code base (naming scheme, code style, etc.).

If you have suggestions for improvements, please respond to this Discussion with your own!

Here are a few examples:

Title	Notes	Proposal (optional)
log vs event	F´ speaks of events, but for historical reasons, a lot of event-related concepts are using the term log (e.g. log_**() function to emit an event, LogPackets/LogBuffer types, etc.)	Rename everything to "Event" ?
Serialization naming scheme	There are two naming schemes for the serialize() call. Sometimes it's <element>.serialize(<buffer>), while sometimes it's <buffer>.serialize(<element>)	Rename functions serializeTo() deserializeFrom() where applicable for clarity
autocoded function names	For an FPP struct with a field fieldA, the autocoded getters/setters are setfieldA/getfieldA	use set_*/get_* instead
port/event/etc. name style and case	Some ports use PascalCase, others camelCase. Some events use THIS_CASE, others use ThatOne. For RateGroup ports, there are 3 different names run/schedIn/Run.	Consolidate and provide an F´-core-enforced style guide

As you may have noticed, this kind of changes will cause a lot of (somewhat simple to fix, but still tedious) breaking changes. The rationale is that we aim for v4.0 to introduce as many breaking improvements as possible, to have a stable and consistent product going forward. If you have comments with regards to that, please do comment.

[SterlingPeet]

I am in favor of all of these adjustments.

For log/events, I like the idea of allowing a separate but FPP supported mechanism for local textLog output. The use case is primarily for debugging: it would be nice to be able to print true log-like statements that leverage the same time source and component to emit the text logs that don't need to be EVRs.

Bringing the conventions for parameters and commands in-line with each other would also be nice.

[LeStarch]

From @timcanham: "Modify component command/channel/etc names to remove component names that used to be part of the command and are now instances."

[kevin-f-ortega]

Run code formatter on all F Prime core code.

[celskeggs]

I'd like for us to eliminate the ComponentImpl files that don't seem to add anything except extra indirection:

I would also like for us to avoid mixing different naming styles: it should either be snake_case or camelCase, not both! I'm really not a fan of names like bufferDeallocate_out. In my opinion, it should either be buffer_deallocate_out or bufferDeallocateOut.

[kevin-f-ortega]

Location of port and type definitions is inconsistent. A solution: move port definitions to a Port directory and types definitions to a Types directory. Perhaps defined these directories in Drv and a separate one in Svc?

[kevin-f-ortega]

Replace PlatformIntType with just int

[kevin-f-ortega]

We have PRI_* definitions for printf, should have similar ones for scanf

[kevin-f-ortega]

Regarding parameters, it autogenerates a SAVE command but it's misleading. The SAVE command just sends the new parameter to PrmDb. The SAVE command should be something like SEND

[celskeggs]

We use the term "Deployment" both to refer to a build of a specific topology into a specific binary, AND as a generic term for the support needed for a platform. I would like the term "Deployment" to only have ONE meaning.

[thomas-bc]

AND as a generic term for the support needed for a platform

Could this be a confusion with a platform's Reference deployment ?

e.g. VxWorks has a platform package, and that platform package is used in the VxWorks Reference Deployment which showcases how to use the platform package.
The reference deployment might be lazily shortened in spoken form as the "VxWorks deployment" but that's indeed a misnomer, and I agree that our documentation should not use that terminology (I don't think it does).

[thomas-bc]

cc @kevin-f-ortega

[bocchino]

This issue gets trickier when we think about FSW installations that use multiple binary executables. For example, suppose there are two binary builds of F Prime running on two computers (or two partitions within the same computer) and that use the same dictionary. In the current terminology, there are two "deployments" here; but in fact there is one FSW installation and one dictionary, so in a naive or common-sense way there is one "deployment" of F Prime to the system. This terminology could become more confusing as we move to space-partitioned FSW systems consisting of many "deployments."

[bocchino]

Eventually we would like to model this multi-deployment system (in the current terminology) as a single FPP model with subtopologies for the separate executables. The current terminology seems geared towards the case in which each topology-binary pair is its own separate thing, not part of a larger whole that is modeled as one thing.

[bocchino]

Here is my wish list:

1. The Active Logger component does not log anything; it just filters events. Maybe call it EventFilter?

2. The PRM_SAVE command does not save anything; it just sends the parameter value on an output port. Usually the output port is connected to a PrmDb component, but it doesn't have to be. This is confusing because in the ordinary use case, actually saving the parameter requires sending this "save" command followed by a separate command to PrmDb to save the parameter file. Maybe rename this command to PRM_SEND?

3. The Command Dispatcher component is called CommandDispatcher in the FPP model, but it lives in the directory CmdDispatcher.

4. I have never understood why the Block Driver component is called Block Driver, or why it is an active component, or why it has so many ports. Shouldn't it just be a passive component with a cycleOut port, to drive the Ref system? Also, Block Driver seems to be a demo component and/or a toy component for driving a reference deployment in an unrealistic way. Should it be called System Driver Stub or something like that, to make clear it is a stub component? And should the SDD explain that it is a stub component for initial development that is designed to be replaced, like the Com Stub?

5. The code in Assert.cpp is written as if to "assert" means to handle or report an assertion failure. I have always found this confusing. The assertion is the check of what is supposed to be true. For example, when you write FW_ASSERT(x > 0), the assertion is that x is greater than zero. If the assertion is true, then nothing happens. If the assertion is false, then an assertion failure occurs and must be handled. Only in this case should functions like doAssert and reportAssert be called. So ideally those functions would be named handleAssertionFailure and reportAssertionFailure or something like that. Names like doAssert suggest that an assertion is being checked, rather than that an assertion failure is being handled.

6. Constant names like FW_STRING_MAX_SIZE are confusing. In FPP, the size of a string type is equal to the max string length. So ideally these constants would be renamed to ..._STRING_SIZE (as is already the case for FW_FIXED_LENGTH_STRING_SIZE) or ..._MAX_LENGTH.

[bocchino]

I forgot this one: Can we fix up the cases where the framework API uses a Boolean argument to specify a behavior mode? Can we enumerate the modes instead? The most confusing example is here:

fprime/Fw/Types/Serializable.hpp

Line 86 in 23d259a

SerializeStatus serialize(const U8* buff, FwSizeType length, bool noLength);

To avoid serializing the length, you have to set noLength to true.

There is an improved version of this function here:

fprime/Fw/Types/Serializable.hpp

Line 99 in 23d259a

SerializeStatus serialize(const U8* buff, FwSizeType length, Serialization::t mode);

Can we deprecate or remove the old function, and make the same improvement throughout the framework?

[LeStarch]

Yes!!!!! BlockDriver is a Red/demo component. Why is it in Drv? So many projects try to use it. Can we just put in a proper Unix or Posix driver?

[timcanham]

BlockDriver was meant to demonstrate a notional driver that passed buffers around, but without any actual hardware dependencies. I didn't want to make it a "real" driver so people could run the Ref demo on plain old Linux.

[zimri-leisher]

Most obvious win in my opinion is making Fw.Time and Fw.TimeInterval FPP structs instead of abstract types.

Second one would be to switch all unit tests to using GTest fixtures.

Big pain point is the "buffer circus":
ComPacket (parent of CmdPacket, TlmPacket, LogPacket but not FilePacket)
LogPacket (instead of EventPacket)
CmdPacket
ComBuffer
CmdArgBuf
Buffer
SerialBuffer
SerializeBufferBase (could we get a DeserializeBufferBase?)
ExternalSerializeBuffer
ExternalSerializeBufferWithDataCopy :(
ExternalSerializeBufferWithMemberCopy :(((
SmSignalBuffer

Second biggest pain point is the "string circus". Not going to enumerate them all but there are like 10 different string types, and they all just seem to have different max sizes.

This should not be necessary:

My suggestion is using type aliases to make EventString an alias for StringSizeXYZ, etc

[celskeggs]

💯 especially regarding the buffer circus issues!

[bocchino]

I think the string circus exists because we have been unwilling to use C++ templates to manage these sizes. There is a string template here:

https://github.com/nasa/fprime/blob/devel/Fw/Types/StringTemplate.hpp

If we used that, the string circus would go away. Overuse of templates can cause problems in C++, but underuse can cause problems too. We have to find the sweet spot here. I think right now we are on the underuse side of the sweet spot.

[zimri-leisher]

Agreed, templates should be used, but sparingly as they spread like a virus. Too much potential for "clever" ideas.

Perhaps the various Log/Cmd/TlmStrings could just be cpp type aliases for the string template. Likewise with the buffers.

[bocchino]

Yes, that is a strong use case. Then the string definition becomes a one-liner, e.g.,

using FooStringType = Fw::StringTemplate<FOO_STRING_SIZE>;

[kubiak-jpl]

There are inconsistencies in the naming of standard port types throughout components in Svc. Standardize these names across F Prime components

Buffer Manager

    @ Port for emitting events
    event port eventOut

CmdDispatcher

    @ Event port
    event port Log

This also extends to Sched ports, which are sometimes called schedIn and othertimes called run

[LeStarch]

FPrime code files are not namespaced. i.e. one includes Svc/.... instead of FPrime/Svc/.... However, we insist that libraries and projects use namespacing folders. This pollutes the default "namespace" of include paths, infects the build system, and really should be corrected.

[bocchino]

I agree! And if we're doing this rigorously, the entire F Prime FPP model should be in an FPrime module, e.g.,

module FPrime {

  module Svc {

    active component CmdDispatcher { ... }

  }

}

This would also fix a problem we have seen in client projects of F Prime, where if a project defines its own Svc module, e.g.,

module MyProject { module Svc { ... } }

then MyProject.Svc hides Svc, and this hiding is disallowed by our coding standards. If Svc were FPrime.Svc, this hiding would not occur.

[bocchino]

The current workaround for avoiding hiding is to use module MyProjectSvc { ... } instead of module MyProject { module Svc { ... } }. This works, but it is ungainly.

[celskeggs]

It might also be nice to specify the module for the whole file in a single statement, like this:

module Fprime.Svc

active component CmdDispatcher { ... }

instead of:

module Fprime {
    module Svc {
        active component CmdDispatcher { ... }
    }
}

[zimri-leisher]

Understood on this but wouldn't it be a huge pain to add FPrime::Svc or Fprime.Svc instead of just Svc? If you're going to fix this then maybe you should also consider adding a "using module" statement like "using namespace"

[bocchino]

I agree that would be a big change, but I think FPrime.Svc is ideally what we want for client uses of F Prime symbols. If you open up the namespace, then you reintroduce all the problems of not having the namespace at all, so you might as well keep the status quo.

[kevin-f-ortega]

Consistent use of private vs PRIVATE -- do we still want PRIVATE?
Same with STATIC -- do we still want STATIC?

[thomas-bc]

We want to move away from PRIVATE and use friend class instead
#3446

[LeStarch]

This one has already been approved and assigned. STATIC will go away too.

[celskeggs]

I still would like us to look at potentially eliminating the rate group context argument. I haven't seen any practical use for Svc.Sched having a U32 argument.

[timcanham]

We have used it frequently to call the same component multiple times at different phases in the rate group. It's very good for that, so I wouldn't want to eliminate it.

[LeStarch]

Should we replace it with a context FPP struct? That way we could have project defined fields that are more illustrative than 32bits.

[celskeggs]

@timcanham I don't see why you can't just have multiple Sched input ports on such components. That makes the multiple invocations much clearer at the FPP level.

[timcanham]

I see what you are saying, and it certainly is an alternate pattern, but we've used enumerations to overlay the context variables so you get another kind of clarity like GNC_PROCESS_SENSORS or GNC_COMPUTE_ACTUATION. I don't see eliminating the context as that much of a payoff.

[celskeggs]

Right, the thing is that with context variables:

1. If you are using them, you have to cross-reference two different files to understand the code flow, because the configuration for the context values is provided in a .cpp file separate from the .fpp file where the rest of the rategroup information is specified. If you need to adjust the rategroup later, for example inserting a non-context-variable step at the start of the rategroup, you have to remember that an adjustment to another file is required: otherwise it will result in mysterious misbehavior of the steps that depend on context variable values.
2. If you are not using them, you have to include a useless boilerplate call in your .cpp file to pass contexts for all of your rategroup clients, even though this is just an array of zeros. This dead code serves no function.
3. In either case, since this is the only place in F Prime (to my knowledge) where this concept of "context variables" is used, it is an additional concept for users to understand. Using the existing topology mechanisms would not require any special knowledge not already needed to understand F Prime.

[Kronos3]

I'd like to suppress the wall of text coming from dictionary generation:

[9/20] Generating RefTopologyAppDictionary.xml
WARNING: XML file RefTopologyAppAi.xml is not valid according to schematron /Users/tumbar/git/fprime/Autocoders/Python/src/fprime_ac/parsers/../../../../../Autocoders/Python/schema/default/top_uniqueness_schematron.rng.

Searching for component XML files
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Drv/BlockDriver/BlockDriverComponentAi.xml
Parsing Component BlockDriver
Populating instance blockDrv of type BlockDriver with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Drv/TcpClient/TcpClientComponentAi.xml
Parsing Component TcpClient
Populating instance comDriver of type TcpClient with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/Ref/PingReceiver/PingReceiverComponentAi.xml
Parsing Component PingReceiver
Populating instance pingRcvr of type PingReceiver with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/Ref/RecvBuffApp/RecvBuffComponentAi.xml
Parsing Component RecvBuff
Populating instance recvBuffComp of type RecvBuff with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/Ref/SendBuffApp/SendBuffComponentAi.xml
Parsing Component SendBuff
Populating instance sendBuffComp of type SendBuff with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/Ref/SignalGen/SignalGenComponentAi.xml
Parsing Component SignalGen
Populating instance SG1 of type SignalGen with parser tree
Populating instance SG2 of type SignalGen with parser tree
Populating instance SG3 of type SignalGen with parser tree
Populating instance SG4 of type SignalGen with parser tree
Populating instance SG5 of type SignalGen with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/Ref/TypeDemo/TypeDemoComponentAi.xml
Parsing Component TypeDemo
Populating instance typeDemo of type TypeDemo with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/ActiveLogger/ActiveLoggerComponentAi.xml
Parsing Component ActiveLogger
Populating instance eventLogger of type ActiveLogger with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/ActiveRateGroup/ActiveRateGroupComponentAi.xml
Parsing Component ActiveRateGroup
Populating instance rateGroup1Comp of type ActiveRateGroup with parser tree
Populating instance rateGroup2Comp of type ActiveRateGroup with parser tree
Populating instance rateGroup3Comp of type ActiveRateGroup with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/AssertFatalAdapter/AssertFatalAdapterComponentAi.xml
Parsing Component AssertFatalAdapter
Populating instance fatalAdapter of type AssertFatalAdapter with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/BufferManager/BufferManagerComponentAi.xml
Parsing Component BufferManager
Populating instance commsBufferManager of type BufferManager with parser tree
Populating instance dpBufferManager of type BufferManager with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/CmdDispatcher/CommandDispatcherComponentAi.xml
Parsing Component CommandDispatcher
Populating instance cmdDisp of type CommandDispatcher with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/CmdSequencer/CmdSequencerComponentAi.xml
Parsing Component CmdSequencer
Populating instance cmdSeq of type CmdSequencer with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/ComQueue/ComQueueComponentAi.xml
Parsing Component ComQueue
Populating instance comQueue of type ComQueue with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/ComStub/ComStubComponentAi.xml
Parsing Component ComStub
Populating instance comStub of type ComStub with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/DpCatalog/DpCatalogComponentAi.xml
Parsing Component DpCatalog
Populating instance dpCat of type DpCatalog with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/DpManager/DpManagerComponentAi.xml
Parsing Component DpManager
Populating instance dpMgr of type DpManager with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/DpWriter/DpWriterComponentAi.xml
Parsing Component DpWriter
Populating instance dpWriter of type DpWriter with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FatalHandler/FatalHandlerComponentAi.xml
Parsing Component FatalHandler
Populating instance fatalHandler of type FatalHandler with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FileDownlink/FileDownlinkComponentAi.xml
Parsing Component FileDownlink
Populating instance fileDownlink of type FileDownlink with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FileManager/FileManagerComponentAi.xml
Parsing Component FileManager
Populating instance fileManager of type FileManager with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FileUplink/FileUplinkComponentAi.xml
Parsing Component FileUplink
Populating instance fileUplink of type FileUplink with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FprimeDeframer/FprimeDeframerComponentAi.xml
Parsing Component FprimeDeframer
Populating instance deframer of type FprimeDeframer with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FprimeFramer/FprimeFramerComponentAi.xml
Parsing Component FprimeFramer
Populating instance fprimeFramer of type FprimeFramer with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FprimeRouter/FprimeRouterComponentAi.xml
Parsing Component FprimeRouter
Populating instance fprimeRouter of type FprimeRouter with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/FrameAccumulator/FrameAccumulatorComponentAi.xml
Parsing Component FrameAccumulator
Populating instance frameAccumulator of type FrameAccumulator with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/Health/HealthComponentAi.xml
Parsing Component Health
Populating instance health of type Health with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/PassiveConsoleTextLogger/PassiveTextLoggerComponentAi.xml
Parsing Component PassiveTextLogger
Populating instance textLogger of type PassiveTextLogger with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/PosixTime/PosixTimeComponentAi.xml
Parsing Component PosixTime
Populating instance posixTime of type PosixTime with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/PrmDb/PrmDbComponentAi.xml
Parsing Component PrmDb
Populating instance prmDb of type PrmDb with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/RateGroupDriver/RateGroupDriverComponentAi.xml
Parsing Component RateGroupDriver
Populating instance rateGroupDriverComp of type RateGroupDriver with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/SystemResources/SystemResourcesComponentAi.xml
Parsing Component SystemResources
Populating instance systemResources of type SystemResources with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/TlmChan/TlmChanComponentAi.xml
Parsing Component TlmChan
Populating instance tlmSend of type TlmChan with parser tree
Found component XML file: /Users/tumbar/git/fprime/Ref/build-fprime-automatic-native/F-Prime/Svc/Version/VersionComponentAi.xml
Parsing Component Version
Populating instance version of type Version with parser tree

Determining kind of component and maximum required ID's for component instances
Found assembly or deployment named: Ref

Parsing Component BlockDriver
Parsing Component TcpClient
Parsing Component PingReceiver
Parsing Component RecvBuff
Parsing Component SendBuff
Parsing Component SignalGen
Parsing Component TypeDemo
Parsing Component ActiveLogger
Parsing Component ActiveRateGroup
Parsing Component AssertFatalAdapter
Parsing Component BufferManager
Parsing Component CommandDispatcher
Parsing Component CmdSequencer
Parsing Component ComQueue
Parsing Component ComStub
Parsing Component DpCatalog
Parsing Component DpManager
Parsing Component DpWriter
Parsing Component FatalHandler
Parsing Component FileDownlink
Parsing Component FileManager
Parsing Component FileUplink
Parsing Component FprimeDeframer
Parsing Component FprimeFramer
Parsing Component FprimeRouter
Parsing Component FrameAccumulator
Parsing Component Health
Parsing Component PassiveTextLogger
Parsing Component PosixTime
Parsing Component PrmDb
Parsing Component RateGroupDriver
Parsing Component SystemResources
Parsing Component TlmChan
Parsing Component Version
WARNING: No assembly base Id set, defaulting to 0
WARNING: No assembly base Id window size set, defaulting to 20
WARNING: blockDrv instance resetting base id to 256
blockDrv instance resetting base id window range to instance specified size (1)
WARNING: rateGroup1Comp instance resetting base id to 512
rateGroup1Comp instance resetting base id window range to instance specified size (2)
WARNING: rateGroup2Comp instance resetting base id to 768
rateGroup2Comp instance resetting base id window range to instance specified size (2)
WARNING: rateGroup3Comp instance resetting base id to 1024
rateGroup3Comp instance resetting base id window range to instance specified size (2)
WARNING: cmdDisp instance resetting base id to 1280
cmdDisp instance resetting base id window range to instance specified size (11)
WARNING: cmdSeq instance resetting base id to 1536
cmdSeq instance resetting base id window range to instance specified size (26)
WARNING: fileDownlink instance resetting base id to 1792
fileDownlink instance resetting base id window range to instance specified size (9)
WARNING: fileManager instance resetting base id to 2048
fileManager instance resetting base id window range to instance specified size (21)
WARNING: fileUplink instance resetting base id to 2304
fileUplink instance resetting base id window range to instance specified size (11)
WARNING: pingRcvr instance resetting base id to 2560
pingRcvr instance resetting base id window range to instance specified size (2)
WARNING: eventLogger instance resetting base id to 2816
eventLogger instance resetting base id window range to instance specified size (5)
WARNING: tlmSend instance resetting base id to 3072
tlmSend instance resetting base id window range to instance specified size (0)
WARNING: prmDb instance resetting base id to 3328
prmDb instance resetting base id window range to instance specified size (8)
WARNING: dpCat instance resetting base id to 3584
dpCat instance resetting base id window range to instance specified size (43)
WARNING: dpMgr instance resetting base id to 3840
dpMgr instance resetting base id window range to instance specified size (4)
WARNING: dpWriter instance resetting base id to 4096
dpWriter instance resetting base id window range to instance specified size (8)
WARNING: comQueue instance resetting base id to 4352
comQueue instance resetting base id window range to instance specified size (2)
WARNING: typeDemo instance resetting base id to 4608
typeDemo instance resetting base id window range to instance specified size (22)
WARNING: health instance resetting base id to 8192
health instance resetting base id window range to instance specified size (8)
WARNING: SG1 instance resetting base id to 8448
SG1 instance resetting base id window range to instance specified size (9)
WARNING: SG2 instance resetting base id to 8704
SG2 instance resetting base id window range to instance specified size (9)
WARNING: SG3 instance resetting base id to 8960
SG3 instance resetting base id window range to instance specified size (9)
WARNING: SG4 instance resetting base id to 9216
SG4 instance resetting base id window range to instance specified size (9)
WARNING: SG5 instance resetting base id to 9472
SG5 instance resetting base id window range to instance specified size (9)
WARNING: sendBuffComp instance resetting base id to 9728
sendBuffComp instance resetting base id window range to instance specified size (14)
WARNING: comDriver instance resetting base id to 16384
comDriver instance resetting base id window range to instance specified size (0)
WARNING: fatalAdapter instance resetting base id to 16640
fatalAdapter instance resetting base id window range to instance specified size (8)
WARNING: fatalHandler instance resetting base id to 16896
fatalHandler instance resetting base id window range to instance specified size (0)
WARNING: commsBufferManager instance resetting base id to 17152
commsBufferManager instance resetting base id window range to instance specified size (5)
WARNING: posixTime instance resetting base id to 17408
posixTime instance resetting base id window range to instance specified size (0)
WARNING: rateGroupDriverComp instance resetting base id to 17664
rateGroupDriverComp instance resetting base id window range to instance specified size (0)
WARNING: recvBuffComp instance resetting base id to 17920
recvBuffComp instance resetting base id window range to instance specified size (5)
WARNING: version instance resetting base id to 18176
version instance resetting base id window range to instance specified size (22)
WARNING: textLogger instance resetting base id to 18432
textLogger instance resetting base id window range to instance specified size (0)
WARNING: systemResources instance resetting base id to 18688
systemResources instance resetting base id window range to instance specified size (21)
WARNING: dpBufferManager instance resetting base id to 18944
dpBufferManager instance resetting base id window range to instance specified size (5)
WARNING: frameAccumulator instance resetting base id to 19200
frameAccumulator instance resetting base id window range to instance specified size (1)
WARNING: deframer instance resetting base id to 19456
deframer instance resetting base id window range to instance specified size (4)
WARNING: fprimeRouter instance resetting base id to 19712
fprimeRouter instance resetting base id window range to instance specified size (2)
WARNING: fprimeFramer instance resetting base id to 19968
fprimeFramer instance resetting base id window range to instance specified size (0)
WARNING: comStub instance resetting base id to 20224
comStub instance resetting base id window range to instance specified size (0)
     INSTANCE NAME      | BASE ID (HEX) | REQUESTED WINDOW SIZE | DIFFERENCED ID WINDOW SIZE | LARGEST COMPONENT INTERNAL ID | MAX AMOUNT OF IDS
       blockDrv         |  256 (0x100)  |           1           |            256             |               1               |         1        
    rateGroup1Comp      |  512 (0x200)  |           2           |            256             |               2               |         2        
    rateGroup2Comp      |  768 (0x300)  |           2           |            256             |               2               |         2        
    rateGroup3Comp      | 1024 (0x400)  |           2           |            256             |               2               |         2        
        cmdDisp         | 1280 (0x500)  |          11           |            256             |              11               |        11        
        cmdSeq          | 1536 (0x600)  |          26           |            256             |              26               |        26        
     fileDownlink       | 1792 (0x700)  |           9           |            256             |               9               |         9        
      fileManager       | 2048 (0x800)  |          21           |            256             |              21               |        21        
      fileUplink        | 2304 (0x900)  |          11           |            256             |              11               |        11        
       pingRcvr         | 2560 (0xa00)  |           2           |            256             |               2               |         2        
      eventLogger       | 2816 (0xb00)  |           5           |            256             |               5               |         5        
        tlmSend         | 3072 (0xc00)  |           0           |            256             |             None              |         0        
         prmDb          | 3328 (0xd00)  |           8           |            256             |               8               |         8        
         dpCat          | 3584 (0xe00)  |          43           |            256             |              43               |        33        
         dpMgr          | 3840 (0xf00)  |           4           |            256             |               4               |         4        
       dpWriter         | 4096 (0x1000) |           8           |            256             |               8               |         8        
       comQueue         | 4352 (0x1100) |           2           |            256             |               2               |         2        
       typeDemo         | 4608 (0x1200) |          22           |            3584            |              22               |        30        
        health          | 8192 (0x2000) |           8           |            256             |               8               |         8        
          SG1           | 8448 (0x2100) |           9           |            256             |               9               |         9        
          SG2           | 8704 (0x2200) |           9           |            256             |               9               |         9        
          SG3           | 8960 (0x2300) |           9           |            256             |               9               |         9        
          SG4           | 9216 (0x2400) |           9           |            256             |               9               |         9        
          SG5           | 9472 (0x2500) |           9           |            256             |               9               |         9        
     sendBuffComp       | 9728 (0x2600) |          14           |            6656            |              14               |         9        
       comDriver        | 16384 (0x4000 |           0           |            256             |             None              |         0        
                        |       )       |                       |                            |                               |                  
     fatalAdapter       | 16640 (0x4100 |           8           |            256             |               8               |         8        
                        |       )       |                       |                            |                               |                  
     fatalHandler       | 16896 (0x4200 |           0           |            256             |             None              |         0        
                        |       )       |                       |                            |                               |                  
  commsBufferManager    | 17152 (0x4300 |           5           |            256             |               5               |         5        
                        |       )       |                       |                            |                               |                  
       posixTime        | 17408 (0x4400 |           0           |            256             |             None              |         0        
                        |       )       |                       |                            |                               |                  
  rateGroupDriverComp   | 17664 (0x4500 |           0           |            256             |             None              |         0        
                        |       )       |                       |                            |                               |                  
     recvBuffComp       | 17920 (0x4600 |           5           |            256             |               5               |         9        
                        |       )       |                       |                            |                               |                  
        version         | 18176 (0x4700 |          22           |            256             |              22               |        22        
                        |       )       |                       |                            |                               |                  
      textLogger        | 18432 (0x4800 |           0           |            256             |             None              |         0        
                        |       )       |                       |                            |                               |                  
    systemResources     | 18688 (0x4900 |          21           |            256             |              21               |        21        
                        |       )       |                       |                            |                               |                  
    dpBufferManager     | 18944 (0x4a00 |           5           |            256             |               5               |         5        
                        |       )       |                       |                            |                               |                  
   frameAccumulator     | 19200 (0x4b00 |           1           |            256             |               1               |         1        
                        |       )       |                       |                            |                               |                  
       deframer         | 19456 (0x4c00 |           4           |            256             |               4               |         4        
                        |       )       |                       |                            |                               |                  
     fprimeRouter       | 19712 (0x4d00 |           2           |            256             |               2               |         2        
                        |       )       |                       |                            |                               |                  
     fprimeFramer       | 19968 (0x4e00 |           0           |            256             |             None              |         0        
                        |       )       |                       |                            |                               |                  
        comStub         | 20224 (0x4f00 |           0           |            inf.            |             None              |         0        
                        |       )       |                       |                            |                               |                  
-------------------------------------------------------------------------------------------------------------------------------------
| INSTANCE NAME                 - Name of the instance object.                                                                      |
| BASE ID (HEX)                 - Base ID set for the instance.                                                                     |
| REQUESTED WINDOW SIZE         - Specified by either the 'base_id_range' attribute in the instance tag or by finding the max of th |
|                                 e 'base_id_range' attribute in the topology tag and the largest internal ID of the instance.      |
| DIFFERENCED ID WINDOW SIZE    - Calculated by subtracting the current base ID from the next base ID.                              |
| LARGEST COMPONENT INTERNAL ID - The largest ID found in the events, channels, and commands of the instance.                       |
| MAX AMOUNT OF IDS             - The largest amount of items from either events, channels, or commands.                            |
-------------------------------------------------------------------------------------------------------------------------------------
Only port connections will be generated for Topology.
Parsing Interface DataBuffer
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Cycle
Parsing Interface Ping
Parsing Interface Sched
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Cycle
Parsing Interface Ping
Parsing Interface Sched
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Com
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Ping
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Com
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Ping
Parsing Interface Sched
Parsing Interface CmdSeqCancel
Parsing Interface CmdSeqIn
Parsing Interface BufferSend
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface SendFileComplete
Parsing Interface SendFileRequest
Parsing Interface Ping
Parsing Interface Sched
Parsing Serializable SendFileResponse
Parsing Serializable SendFileResponse
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Ping
Parsing Interface BufferSend
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Ping
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Ping
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Com
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface FatalEvent
Parsing Interface Ping
Parsing Interface Com
Parsing Interface TlmGet
Parsing Interface Tlm
Parsing Interface Ping
Parsing Interface Sched
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface PrmGet
Parsing Interface PrmSet
Parsing Interface Time
Parsing Interface Ping
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface SendFileComplete
Parsing Interface SendFileRequest
Parsing Interface Ping
Parsing Serializable SendFileResponse
Parsing Serializable SendFileResponse
Parsing Serializable DpRecord
Parsing Interface BufferGet
Parsing Interface BufferSend
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface DpGet
Parsing Interface DpRequest
Parsing Interface DpResponse
Parsing Interface DpSend
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Sched
Parsing Interface BufferSend
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface DpWritten
Parsing Interface Sched
Parsing Interface BufferSend
Parsing Interface Com
Parsing Interface Log
Parsing Interface LogText
Parsing Interface SuccessCondition
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface ComDataWithContext
Parsing Interface Sched
Parsing Serializable FrameContext
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface PrmGet
Parsing Interface PrmSet
Parsing Interface Time
Parsing Interface Tlm
Parsing Serializable ChoicePair
Parsing Serializable ChoiceSlurry
Parsing Serializable ChoicePair
Parsing Serializable ScalarStruct
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Ping
Parsing Interface Sched
Parsing Interface WatchDog
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface DpGet
Parsing Interface DpRequest
Parsing Interface DpResponse
Parsing Interface DpSend
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Sched
Parsing Serializable SignalPair
Parsing Serializable SignalInfo
Parsing Serializable SignalPair
Parsing Serializable SignalPair
Parsing Interface DataBuffer
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface PrmGet
Parsing Interface PrmSet
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Sched
Parsing Interface ByteStreamData
Parsing Interface ByteStreamReady
Parsing Interface BufferGet
Parsing Interface BufferSend
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface FatalEvent
Parsing Interface BufferGet
Parsing Interface BufferSend
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Sched
Parsing Interface Time
Parsing Interface Cycle
Parsing Interface DataBuffer
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface PrmGet
Parsing Interface PrmSet
Parsing Interface Time
Parsing Interface Tlm
Parsing Serializable PacketStat
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Version
Parsing Serializable CustomVersionDb
Parsing Interface LogText
Parsing Interface Cmd
Parsing Interface CmdReg
Parsing Interface CmdResponse
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface Tlm
Parsing Interface Sched
Parsing Interface BufferGet
Parsing Interface BufferSend
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface ComDataWithContext
Parsing Serializable FrameContext
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface ComDataWithContext
Parsing Serializable FrameContext
Parsing Interface BufferGet
Parsing Interface BufferSend
Parsing Interface CmdResponse
Parsing Interface Com
Parsing Interface Log
Parsing Interface LogText
Parsing Interface Time
Parsing Interface ComDataWithContext
Parsing Serializable FrameContext
Parsing Interface BufferGet
Parsing Interface BufferSend
Parsing Interface SuccessCondition
Parsing Interface Time
Parsing Interface ComDataWithContext
Parsing Serializable FrameContext
Parsing Interface ByteStreamData
Parsing Interface ByteStreamReady
Parsing Interface BufferSend
Parsing Interface SuccessCondition
Parsing Interface ComDataWithContext
Parsing Serializable FrameContext
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum CmdResponse
Parsing Enum DeserialStatus
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum CmdSequencer_BlockState
Parsing Enum CmdSequencer_FileReadStage
Parsing Enum CmdSequencer_SeqMode
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SendFileStatus
Parsing Enum SendFileStatus
Parsing Serializable SendFileResponse
Parsing Enum SendFileStatus
Parsing Serializable SendFileResponse
Parsing Enum SendFileStatus
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum ActiveLogger_Enabled
Parsing Enum ActiveLogger_FilterSeverity
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum TlmValid
Parsing Enum PrmDb_PrmReadError
Parsing Enum PrmDb_PrmWriteError
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum ParamValid
Parsing Enum Wait
Parsing Enum DpHdrField
Parsing Enum SendFileStatus
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SendFileStatus
Parsing Enum SendFileStatus
Parsing Enum DpState
Parsing Serializable SendFileResponse
Parsing Enum SendFileStatus
Parsing Serializable SendFileResponse
Parsing Enum SendFileStatus
Parsing Serializable DpRecord
Parsing Enum DpState
Parsing Enum CmdResponse
Parsing Enum Success
Parsing Enum Success
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum QueueType
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum Success
Parsing Serializable FrameContext
Parsing Array BuffQueueDepth
Parsing Array ComQueueDepth
Parsing Enum Choice
Parsing Enum Choice
Parsing Enum ParamValid
Parsing Enum Choice
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum ParamValid
Parsing Enum Choice
Parsing Enum Choice
Parsing Enum Choice
Parsing Enum Choice
Parsing Serializable ChoicePair
Parsing Enum Choice
Parsing Serializable ChoiceSlurry
Parsing Enum Choice
Parsing Serializable ChoicePair
Parsing Enum Choice
Parsing Serializable ScalarStruct
Parsing Array FloatSet
Parsing Array ManyChoices
Parsing Array TooManyChoices
Parsing Array ManyChoices
Parsing Array TooManyChoices
Parsing Array ManyChoices
Parsing Enum Enabled
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SignalGen_DpReqType
Parsing Enum SignalType
Parsing Enum CmdResponse
Parsing Enum Success
Parsing Enum Success
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalInfo
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalPair
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Enum SignalGen_DpReqType
Parsing Enum SignalType
Parsing Enum CmdResponse
Parsing Enum Success
Parsing Enum Success
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalInfo
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalPair
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Enum SignalGen_DpReqType
Parsing Enum SignalType
Parsing Enum CmdResponse
Parsing Enum Success
Parsing Enum Success
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalInfo
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalPair
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Enum SignalGen_DpReqType
Parsing Enum SignalType
Parsing Enum CmdResponse
Parsing Enum Success
Parsing Enum Success
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalInfo
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalPair
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Enum SignalGen_DpReqType
Parsing Enum SignalType
Parsing Enum CmdResponse
Parsing Enum Success
Parsing Enum Success
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalInfo
Parsing Enum SignalType
Parsing Serializable SignalPair
Parsing Serializable SignalPair
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Array SignalPairSet
Parsing Array SignalSet
Parsing Enum SendBuff_ActiveState
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum ParamValid
Parsing Enum ByteStreamStatus
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum ParamValid
Parsing Enum PacketRecvStatus
Parsing Serializable PacketStat
Parsing Enum PacketRecvStatus
Parsing Enum VersionEnabled
Parsing Enum VersionType
Parsing Enum VersionEnum
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum VersionStatus
Parsing Enum VersionEnum
Parsing Enum VersionStatus
Parsing Enum VersionEnum
Parsing Serializable CustomVersionDb
Parsing Enum VersionStatus
Parsing Enum VersionEnum
Parsing Enum LogSeverity
Parsing Enum SystemResourceEnabled
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Serializable FrameContext
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Serializable FrameContext
Parsing Enum CmdResponse
Parsing Enum LogSeverity
Parsing Enum LogSeverity
Parsing Serializable FrameContext
Parsing Enum Success
Parsing Serializable FrameContext
Parsing Enum ByteStreamStatus
Parsing Enum Success
Parsing Serializable FrameContext
Generating XML dictionary RefTopologyAppDictionary.xml
Generating code filename: RefTopologyAppAc.hpp topology, using default XML filename prefix...
Generating code filename: RefTopologyAppID.csv topology, using default XML filename prefix...
Completed generating HTML command tables...
Completed generating HTML channel tables...
Completed generating HTML event tables...

[thomas-bc]

XML autocoders are planned for removal by v4.0, so this should go away then

[zimri-leisher]

This problem could be fixed by simply commenting out a line right now. I have done it a few times

[LeStarch]

Can Fw.Buffer use a FwSizeType size and not a U32?

[kevin-f-ortega]

Agreed! Otherwise I need to add static_cast<FwSizeType>

[kevin-f-ortega]

Could event throttling be limit at most X Events per Y seconds?

[thomas-bc]

This likely falls under a feature request more than a code consistency issue