marte2_python – DDB Signal Producer Fix

We've fixed an issue affecting signals with the same name in different DDBs when those signals were routed to an external DataSource.

Previously, these signals could ultimately be written into OutsideWorldDDB, resulting in two identically named signals being placed in the same DDB and triggering a multiple producer conflict.

Signal handling has now been corrected so that signals originating from separate DDBs are handled appropriately when interfacing with external DataSources, avoiding these false producer conflicts.

1.1.0

• Type setting in all GAMs, objects and datasources on init.
• lstrip applied to all configuration_names for better synchronicity on the '+' naming. (held internally, ignored if given).
• toPython functions provided for application and GAM, object and datasource levels - mainly for xmarte to write macro python files from a GUI generated MARTe2 cfg.

1.0.9

Add support for histogram and statistics GAMs

1.0.8

support for rt sync bridge

1.0.7

Fixed a bug where if MaxWait is not set in a message, cannot import with reader

1.0.6

Fix for bad upload of pypi distribution

1.0.5

Added support for:

• RealTimeSynchronisation
• Interfaces

1.0.4

Fix for onlyErrors added which allows complex types to be verified against and fixes bug introduced there with this new function.

1.0.3

New Features:

• Support for JSON, example: Create using_json.py
• Allow override of reader function for JSON support

Fixes:

• Fixed MessageGAM definition
• Fix for ExpressionGAM reading with terms including =

1.0.2

New Features:

• Able to output to JSON now
• Added SimulinkWrapperGAM to the code
• Several bug fixes in signal definitions for xMARTe
• Fixed Examples thanks to Mandarancio