Some of this information may be better places in a separate message. For instance, a separate message may contain more detailed information about errors encountered so that they periodic status can be smaller. In the same vein, many fields do not change over time and may make more sense as a 1 time only type message at startup (HW/SW version, configuration version, etc.). I think a single status message either needs to be much more verbose, or multiple other interfaces can be created to better manage network traffic and compartmentalize data.
Some of this information may be better places in a separate message. For instance, a separate message may contain more detailed information about errors encountered so that they periodic status can be smaller. In the same vein, many fields do not change over time and may make more sense as a 1 time only type message at startup (HW/SW version, configuration version, etc.). I think a single status message either needs to be much more verbose, or multiple other interfaces can be created to better manage network traffic and compartmentalize data.