Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update oscc to v1.2.4, add validation modifications #31

Open
wants to merge 24 commits into
base: master
Choose a base branch
from

Conversation

cotos
Copy link
Contributor

@cotos cotos commented Jul 10, 2019

Before this PR the oscc submodule was v1.2.3

This PR will make the following changes:

oscc default submodule is now: v1.2.4

Changed the steering range percentage to the value used for validation.

#define STEERING_RANGE_PERCENTAGE (0.36)

Changed commander update interval so JC will work with the safety gateway

#define COMMANDER_UPDATE_INTERVAL_MICRO (5000)

I updated the README to follow the the DriveKit README currently on the
feature/dfu-bootloader branch.

I updated the MIT copyright to 2019 in the license and readme files.

vertexmachina and others added 23 commits November 9, 2017 10:34
Prior to this commit, the exponential filter of the inputs
(triggers and joystick) were filtered so the modules received a smooth
series of commands, but the filters were not cleared after a disable,
causing the modules to actuate on old command values when re-enabling.
This commit clears the filters when control is not enabled.
Prior to this commit, steering range wasn't being limited from the application firmware whatsoever, i.e. it would iterate through the full allowable range of spoofs. This commit limits it to be 20% of the full range, allowing for better steering control and a better out-of-box user experience.
Prior to this commit, OSCC Joystick Commander didn't have any CI pipeline. This commit adds one.
Prior to this commit, there was an unneeded catch block in the Jenkinsfile. This commit removes it.
Prior to this commit the initialization of the static global variable `joystick_data` was initialized ambiguously and what looked like erroneously.

This commit represents a revision explicit initialization instead.

Motivation for this change was a support ticket raised with an email to `help@polysync.io`

Note to reviewers: I validated that after this change the joystick commander still behaved as _I_ expected on the car but would HIGHLY recommened that reviewers do the same.

Thanks!
…into devel

* snewt/bug/explicit-joystick-data-init:
  Make initialization of `joystick_data` explicit
Prior to this commit joystick commander required an ifdef block to support
different platforms. This commit updates joystick commander so that the oscc
configuration can be referenced instead keeping platform support in the oscc repo.
Prior to this commit joystick commander required the user to clone oscc into
the joystick commander directory and did not keep track of oscc versions. This
commit fxes that by adding oscc as a submodule so that updates to oscc api and
joystick commander can be kept in lockstep.
Before this PR the oscc module was v1.2.3

This PR will make the following changes.

oscc default module is now:  v1.2.4

Changed the steering range percentage to the value used for validation.

`#define STEERING_RANGE_PERCENTAGE (0.36)`

Changed commander updat interval so JC will work with the safety gateway

`#define COMMANDER_UPDATE_INTERVAL_MICRO (5000)`
I updated the README to follow the the DriveKit README on the
`feature/dfu-bootloader` branch.

I updated the MIT copyright to 2019 in the license and readme files.
Copy link

@twaddington twaddington left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks alright to me!

Added note for debug flag
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants