Software:

* Toolchain:

  * VS Code C/C++ extension does now support an intellisense mode setting for

    gcc to ARM (``windows-gcc-arm``). This is set as the new default value for

    the ``IntelliSenseMode`` key. (``c_cpp_properties.json``)

* Bugfixes:

  * Automatic retransmission mode for CAN messages was DISABLED instead of

    ENABLED. The logic in HAL configuration struct has been inverted with HAL

    update performed in ``v1.6.0``. Now automatic retransmission is ENABLED

    again. (``can_cfg.c``)

  * Fixed compile error if ``BUILD_MODULE_ENABLE_CONTACTOR`` was set to 0. If

    contactor module is disabled, current limits are now always checked against

    configured current limits of power line 0. (``bms.c``)

  * Corrected the function LTC_I2CCheckACK() that did not check the acknowledge

    signal of multiplexer over I2C communication. (``ltc.c``)

  * Corrected the function LTC_SetMUXChCommand() because message content for

    I2C communication with multiplexers was wrong. (``ltc.c``)

* Enhancements:

  * none

Hardware:

* none

Documentation:

* Following difference is now made between warning and error flags: warning flags

  are for information purpose only whereas error flags will trigger a reaction of

  the bms. (``monitored_parameters.rst``)

* Added the ``.vscode`` directory to the list of ignored directories for git.

  (``.gitignore``)

------------------------------------------------------------------------------

Author: foxBMS

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+# Please read this before creating a Pull Request
+
+The foxBMS project is an open source project to empower everybody to build
+beyond state of the art battery management systems (BMS) based on software and
+hardware that:
+
+- **does not** compromise their outcomes with restricted licenses and
+- **does not** create a vendor lock-in.
+
+We therefore release foxBMS with permissive licenses:
+
+- Hardware (layout, schematics) and documentation:
+  **Creative Commons Attribution 4.0 International License**
+- Software: **BSD 3-Clause License**
+
+For details see the [LICENSE](../LICENSE) file and the
+[license documentation](https://iisb-foxbms.iisb.fraunhofer.de/foxbms/docs/latest/general_information/licenses/licenses.html).
+
+However foxBMS is not openly developed on GitHub (or any other platform). The
+main development on this project is done by members of the Fraunhofer IISB and
+organized in a non-public repository at the Fraunhofer IISB. This repository is
+the output of the release branch of this internal repository.
+
+This workflow allows us to release these development outputs under these
+permissive licenses. We do not have a Contributors License Agreement (CLA)
+system or similar that would allow us to integrate input from GitHub Pull
+Requests, therefore GitHub Pull Requests are currently not accepted.
+
+We would be very pleased if you intend to contribute to this project. Please
+contact us first at [email protected] in order to discuss your contribution and
+how it can be applied to the project.

.gitignore

@@ -5,6 +5,9 @@
 /*eclipse*
 /qa-chain/
 
+# VS Code directory
+.vscode/
+
 # ignore complete build directory
 /build/
 

CHANGELOG.rst

@@ -2,6 +2,48 @@
 Changelog
 =========
 
+**Release 1.6.6**
+
+Software:
+
+* Toolchain:
+
+  * VS Code C/C++ extension does now support an intellisense mode setting for
+    gcc to ARM (``windows-gcc-arm``). This is set as the new default value for
+    the ``IntelliSenseMode`` key. (``c_cpp_properties.json``)
+
+* Bugfixes:
+
+  * Automatic retransmission mode for CAN messages was DISABLED instead of
+    ENABLED. The logic in HAL configuration struct has been inverted with HAL
+    update performed in ``v1.6.0``. Now automatic retransmission is ENABLED
+    again. (``can_cfg.c``)
+  * Fixed compile error if ``BUILD_MODULE_ENABLE_CONTACTOR`` was set to 0. If
+    contactor module is disabled, current limits are now always checked against
+    configured current limits of power line 0. (``bms.c``)
+  * Corrected the function LTC_I2CCheckACK() that did not check the acknowledge
+    signal of multiplexer over I2C communication. (``ltc.c``)
+  * Corrected the function LTC_SetMUXChCommand() because message content for
+    I2C communication with multiplexers was wrong. (``ltc.c``)
+
+* Enhancements:
+
+  * none
+
+Hardware:
+
+* none
+
+Documentation:
+
+* Following difference is now made between warning and error flags: warning flags
+  are for information purpose only whereas error flags will trigger a reaction of
+  the bms. (``monitored_parameters.rst``)
+* Added the ``.vscode`` directory to the list of ignored directories for git.
+  (``.gitignore``)
+
+------------------------------------------------------------------------------
+
 **Release 1.6.5**
 
 Software:

documentation/doxygen/doxygen-primary.conf

@@ -38,7 +38,7 @@ PROJECT_NAME           = ""
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 1.6.5
+PROJECT_NUMBER         = 1.6.6
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

documentation/doxygen/doxygen-primary_bare.conf

@@ -38,7 +38,7 @@ PROJECT_NAME           = ""
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 1.6.5
+PROJECT_NUMBER         = 1.6.6
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

documentation/doxygen/doxygen-secondary.conf

@@ -38,7 +38,7 @@ PROJECT_NAME           = ""
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 1.6.5
+PROJECT_NUMBER         = 1.6.6
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

documentation/doxygen/doxygen-secondary_bare.conf

@@ -38,7 +38,7 @@ PROJECT_NAME           = ""
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 1.6.5
+PROJECT_NUMBER         = 1.6.6
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

documentation/sphinx/general_information/releases/releases.rst

@@ -42,6 +42,8 @@ released. The first line is the most recent one, the last one the oldest one.
 +--------+----------+--------------+
 | foxbms | foxconda | Release date |
 +========+==========+==============+
+| v1.6.6 | 3.0.3    | 2021-02-05   |
++--------+----------+--------------+
 | v1.6.5 | 3.0.3    | 2021-01-15   |
 +--------+----------+--------------+
 | v1.6.4 | 3.0.3    | 2020-03-04   |

documentation/sphinx/getting_started/eclipse_workspace/eclipse_workspace.rst

@@ -425,7 +425,7 @@ Testing the Project Setup
 
     If problems occur while using the Eclipse workspace, it is possible to use
     a VS Code setup. For details on |foxbms| and VS Code see
-    `here <https://github.com/foxBMS/foxbms/tree/v1.6.5/tools/vscode>`_.
+    `here <https://github.com/foxBMS/foxbms/tree/v1.6.6/tools/vscode>`_.
 
     **However, VS Code is not actively supported and should only be used in**
     **cases where the Eclipse setup does not work.**

documentation/sphinx/macros.rst

@@ -3,7 +3,7 @@
 .. -----------------------------------------------
 .. General Documentation Macros
 .. -----------------------------------------------
-.. |version| replace:: ``1.6.5``
+.. |version| replace:: ``1.6.6``
 .. |version-hal| replace:: ``V1.7.4``
 .. |version-cmsis| replace:: ``V2.6.2``
 .. |version-freertos| replace:: ``V10.1.1``