Commandline connection improvements #418
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add commands --about and --version to print some about/version info respectively.
Fix autoconnection issue with connected CAN devices: If VESC Tool is run with a command that connects to a CAN-connected VESC over USB (for example 'vesc_tool_6.06 --vescPort /dev/ttyUSB1 --canFwd 13 ...'), and then the next time VESC Tool is run with a command for only the USB-connected VESC ('vesc_tool_6.06 --vescPort /dev/ttyUSB1 ...'), the previously connected CAN VESC will be communicated with instead. Now, behaviour is changed so that if --canFwd is not specified, connection will either proceed directly with the USB VESC (if --vescPort is specified), or autoconnect will be used to connect to the last USB/CAN VESC (if --vescPort and --canFwd are both not specified).
On Windows, support specifying arguments to --VescPort by a partial name such as '--VescPort COM4' in addition to the full explicit path '--VescPort \.\COM4'.
Reduce printouts (of test version and fw update available) when running VESC Tool with commandline arguments, to aid parsing/logging program output.