0.2.6

This version update the FW Updater sketch. This sketch now waits until the Serial is open, ensuring the fact that the user see the update message and acknowledge the FW update.

What's Changed

• Improve the FW updater script by @maidnl in #28

Full Changelog: 0.2.5...0.2.6

Opta Blueprint release 0.2.5

The version 0.2.5 introduces:

• timeout and default values for Opta Analog
  using functions setTimeoutForDefaultValues(), setDefaultPwm(), setDefaultDac() on Analog Expansion the user can set a timeout (defined as the time the Analog Expansion is not receiving any message from the Opta Controller) and default values for the outputs (PWM and DAC). As soon as the timeout elapses (the expansion is not receiving msg for more than the timeout set) the expansion autonomously sets the outputs to the default values. As soon as the communication comes back the values are set to the values they have before the timeout.
  By default the timeout is disabled and default values are all OFF.
  To disable timeout once enabled, set the timeout to 0xFFFF.
  Timeout is expressed in ms.

• actual activation channel status for Opta Analog
  This introduces the possibility to ask the Analog Expansion if a channel has actually set up the requested function for a certain channel.
  This function has been introduced by adding a parameter (default is false) to the functions isCh.
  Before this change, these functions accepted only the channel as parameter, the returned value was the status memorized by the Controller (i.e. the last command sent by the controller to the expansions), this could not reflect the actual status of the hardware since the expansion could take sometimes (a few milliseconds) to set up the channel function.
  Now these functions have an additional parameter (by default false and so you get old behavior), when this second parameter is set to true, the controller asks the expansion if the channel has actually set up the requested function and returns true only when the expansion has actually set up the channel.
  Be aware of the fact that the expansion sets up the requested function as soon as it can and usually it is not necessary ask for the "actual" status, this function is intended to be used in particular cases when some output is set once in a while and so it is necessary to be absolutely sure that the channel is able to receive the command. It is suggested to use this only when strictly necessary, because this function requires an I2C transaction that might slow down other operations.

• revision of I2C message functions (BREAKING CHANGE for custom expansion development!)
  In order to simplify the code the functions "prepare" and "check" I2C message function (see OptaMsgCommon.h file) do not have the fourth parameter anymore (that was useless, a leftover of on old implementation).
  This change has no impact for users of the Opta Blueprint library since it is transparent, however this is a breaking change for users that relied on those functions to develop their own custom expansion library that have now to switch to this new simpler implementation.

• fix in the I2C protocol: expansions answered with the last sent answer if an i2c message they were not
  intended to handle was erroneulsy dispatched. This behavior was observable only by sending raw I2C messages
  to the expansion. From this version if an expansion receive a message which is not able handle the first 2 bytes
  of the answer will be 0xFA, 0xFE (sort of NACK)

• further semplification in the Opta Analog FW related to the possibility to change the function assigned
  to the channel runtime

What's Changed

• Opta Analog: added timeout and default values by @maidnl in #19
• Opta Analog: added channel activation status function by @maidnl in #20
• Opta Controller and Expansions: clean up of I2C messages functions by @maidnl in #21
• Opta blue print: revision of some examples and test sketches by @maidnl in #22
• Opta Analog and Digital: new FW version Analog 0.1.10 and digital 0.1.4 by @maidnl in #23
• Opta Blue Print Protocol by @maidnl in #24
• Opta Analog: default PWM set to 0 after timeout by @maidnl in #25
• Opta Analog: simplify change function by @maidnl in #26
• Opta BluePrint: new FW version for expansions by @maidnl in #27

Full Changelog: 0.2.4...0.2.5

Opta Blue Print release 0.2.4

This release:

1. fixes some problems related to PWMs (pwm get functions now uses channel from OA_PWM_CH_0 to OA_PWM_CH_3 instead of 0..3. Using indexes 0..3 in these functions is DEPRECATED but kept for compatibility reasons.)
2. revises the I2C address assignment (in relation to start up and custom type assignment, see below)
3. revises the expansion start up by controller (expansions now are no more "reset" during the hot-plug of a new expansions but they keep their current state)
4. simplifies the custom type assignment for custom expansions

What's Changed

• Opta Controller: Revision of custom type assignment by @maidnl in #10
• Opta Controller: Get pwm functions used wrong index by @maidnl in #11
• Opta Analog: Pwm channel 0 not working plc ide fix by @maidnl in #12
• Opta Analog: Pwm pulse and period changed together fix by @maidnl in #13
• Opta Analog: Reworking register definition by @maidnl in #14
• Opta controller and expansions: assign address enhancement by @maidnl in #15
• Opta Controller: Revision start up processes by @maidnl in #16
• Opta Controller / Analog Expansion: fixing problems on additional ADC configuration by @maidnl in #17
• Opta Analog and Opta Digital: New FW release (Analog 0.1.9, Digital 0.1.3) by @maidnl in #18

Full Changelog: 0.2.3...0.2.4

Release 0.2.3

What's Changed

• Analog expansion Example fix by @marqdevx in #6
• Compilation fix when compiling with DEBUG_SERIAL and DEBUG_EXPANSION_PRINT_ADDRESS by @Delph in #8
• Opta Analog Expansion: fix for updateAnalogOutputs() function by @maidnl in #9

New Contributors

• @marqdevx made their first contribution in #6
• @Delph made their first contribution in #8

Full Changelog: 0.2.2...0.2.3

Release 0.2.2

What's Changed

• Change I2C speed to 400KHz by @maidnl in #4

Full Changelog: 0.2.1...0.2.2

Release 0.1.1

Release 0.1.1

0.1.0

Update library.properties