v1.5.0

• Significant improvements to GUI.
• Consolidation of some API component. default package removed and all modules moved to config package
• Colored logs using colorama and colorlog , updated setup.cfg accordingly
• Service and communication interface keys are now all strings by default. Some keys are still stored as enum.Enum values to have a programatic way of determining available options
• A lot of obsolete code removed
• File log output improved

v1.4.4

• A lot of refactoring was done
• Most of it is form / documentation related, but some are also bugfixes

v1.4.3

• Refactored Object ID manager
• Added more tests
• Project part of (personal) organization now, READMEs updated accordingly
• Configurability increased: JSON config path is passed now instead of being hardcoded
• Cleaned up GUI a bit, some additions still necessary for usability

v1.4.2

• Some deprecation warnings fixed
• Package now available on PyPI
• README update
• Generic Parameter Service (Service 20) components added

v1.4.1

• Added first tests and codecov workflow

v1.4.0

• This adds an example demo. The example currently can only be used for the single command mode and uses the dummy communication interface internally. The demo can be run by simply running the tmtc_cli.py scipt. The ExampleHookClass provides an example of how a hook object implementation might look like
• A lot of form improvements
• New common pus folder for subservice definitions
• Capability to parse PUS A and PUS C packets added
• Communication Interface Base: poll_interface removed because it was not used anyway and is not required because receive_telemetry performs the same task
• Adds GitHub actions workflow YAML file

v1.3.0

• Major improvements to argument parsing. It is now possible to specify modes and communication interface as strings. Help text was updated as well
• Refactored PUS stack components. This includes decoupling it from the rest of the library to keep the option of moving it into a separate library. This means the PUS stack is now located inside the ecss package while the generic space packet components are located inside the ccsds package
• Decoupled generic Space Packet components, which could also be used by the CCSDS File Delivery Protocol (CFDP)
• Introduced ANSI colors
• Added more documentation. Long way to go, but it's a start

v1.2.0

• This release improves handling of JSON files

v1.1.0

A lot of bugfixes, consistency fixes and improvements but also API changes.

• All enums now with capital letters
• Globals configuration improved, safer
• JSON handling improved as well as safer
• Updated logos
• Naming fixes

v1.0.0

First release. Still in beta-state, documentation missing, but code is already used across multiple satellite projects.