Vertiq has launched a new firmware update, version 0.1.1, for its G2 production modules and the 81-08 G1 modules.
This update addresses a minor issue from version 0.1.0,where the Report Telemetry as Speed setting inadvertently influenced the FC 2D/3D Mode setting,and vice versa.
For the majority of users, this issue has a negligible effect, as the FC 2D/3D Mode setting typically only matters when utilizing a 3D Motor Direction (for instance, when attempting to apply negative throttle).
All modules that were updated to version 0.1.0 are impacted, including:
- 40-06 370Kv, 770Kv (M34.1, M34.2, M34.3, M41.1, M41.2)
- 40-14 400Kv (M35.1, M35.2)
- 60-08 150Kv, 300Kv, 660Kv (M40.2, M47.1, M48.0, M48.1)
- 81-08 G1 85Kv, 150Kv, 240Kv (M16.0, M28.0, M39.0)
- 81-08 G2 85Kv, 140Kv, 240Kv (M16.2, M28.2, M39.2)
- 81-17 G2 110Kv (M42.0,M42.1)
Summary of Modifications
This firmware version mirrors the functionality of v0.1.0, with the sole distinction being the resolution of the bug that linked the Report Telemetry as Speed and FC 2D/3D Mode parameters. No additional modifications have been made.
issue Details & Consequences
The bug rectified in this update caused the saved values of Report Telemetry as Speed and FC 2D/3D Mode to become interconnected. When one parameter was adjusted and saved, both would revert to the same value after the module was powered off and on again.
For instance, if Report Telemetry as Speed was activated and saved, upon rebooting, FC 2D/3D Mode would default to 3D, even if it had been previously set to 2D. Conversely, if FC 2D/3D Mode was saved as 2D, then after rebooting, Report Telemetry as Speed would be turned off, despite being enabled before.saving either parameter would unintentionally alter the othre upon the next reboot.
The FC 2D/3D Mode setting is relevant only for modules configured in specialized and rare vehicle setups. It is important primarily when the Motor Direction is set to 3D, allowing the motor to rotate both clockwise and counterclockwise using positive and negative throttle inputs.
The standard and recommended practice with PX4 and Ardupilot flight controllers is to utilize a 2D direction, where the motor responds to throttle input by spinning in a single direction. In this setup, the FC 2D/3D Mode has no bearing. Thus, most users will not experience any issues related to this parameter, even if they enable Report Telemetry as Speed.
However, users who activated Report Telemetry as Speed might have encountered issues if they subsequently tried to set FC 2D/3D Mode to 2D. This could have inadvertently disabled Report Telemetry as speed due to the bug.
When to Transition to v0.1.1
For the majority of users, this bug will not influence motor performance. Unless you are utilizing a 3D motor Direction, the FC 2D/3D Mode setting is irrelevant. If you were affected, the issue would manifest as a noticeable difference in the module’s throttle mapping.
If you are using Report Telemetry as Speed and noticed unexpected changes in the parameter, your module may have been impacted. This specifically pertains to those who adjusted both Report Telemetry as Speed and FC 2D/3D Mode.
If neither scenario applies, upgrading to v0.1.1 is unlikely to yield significant changes in module performance compared to v0.1.0.
Vertiq encourages users to upgrade to v0.1.1 when feasible to avoid encountering this bug in the future. However, the company acknowledges that some users may choose to delay firmware updates for operational reasons. Version 0.1.0 will remain accessible for those who prefer to continue using it.
