Using Custom Workcell Configurations – VEX Library

VEXcode V5 allows for the custom configuration of the Arm in the Devices menu for use with the V5 Brain. This is done for a multitude of reasons, which includes the allowance of further customization with your Workcell, such as moving your Arm without having to recreate cables and switch ports. The purpose of this article is to guide you through performing this operation in VEXcode.

Note: be sure to view the Example Projects and Past Projects section at the end of this article as it contains vital information when changing configurations with your Workcell.

Configuring the Arm

VEXcode V5 download page with download options for platforms including Chrome Web Store, Windows, Mac, Apple App Store, Google Play, and the Amazon appstore.

First, ensure that your version of VEXcode V5 is 2.4.0 or later. To update a downloaded version of VEXcode, upon opening the application when a new version is available, you will be prompted to update to the most current version. The web application found at codev5.vex.com is always up to date with the most recent version.

Select here to download the latest version of VEXcode V5.

VEXcode V5 with the Devices icon highlighted on the Toolbar in between the Code Viewer and Monitor icons.

Open VEXcode V5 and select the 'Devices' menu.

Arm device option is highlighted in the Select a Device menu.

Select 'Add a device' and select 'Arm' if it is not already added.

For more information on adding, renaming, and deleting an 'Arm,' view this article from the VEX Library.

Select Configuration menu is shown with two options that read Standard Config and Custom Config.

Once you have selected 'Arm', the screen to the left will appear.

Using Standard Config

Arm Configuration menu after the Standard Config option has been selected, the four Joints are assigned to the first four Smart Ports.

Selecting 'Standard Config' will use the same port configurations used in the Workcell STEM Labs (Smart Ports 1-4 and Three Wire Ports A-D). You are not able to change these port configurations in this Config. If you wish to use this selection, select 'Done', else select 'Change Configuration' and see next step.

Using Custom Config

Arm Configuration menu after the Custom Config option has been selected, the four Joints have menus where they can be assigned to a custom port configuration.

Selecting 'Custom Config' will prompt the screen to the left. You are now able to change which port each Joint will use.

Arm Configuration menu after the Custom Config option has been selected. Port 1 has been selected in the Select a Port menu.

In the image on the left, port 1 was selected and the 'Select a port' menu appears. You are able to select any numbered ports not currently in use as determined by the devices menu.

Arm Configuration menu after the Custom Config option has been selected. Port A has been selected in the Select a Port menu.

Selecting a port from this menu will assign it to the selection you have made (note how Joint 1 is now using Smart Port 5). The same process is done to change which port is used by the Three Wires.

Arm Configuration menu with the Done button highlighted below.

Repeat the Custom Config steps to complete your configuration, with whatever ports you want. After your selections have been made, select 'Done' to add your Arm into VEXcode. Note that you are able to go back and change any ports if needed.

Example Projects and Past Projects

VEXcode V5 with an example project opened and the blocks code shown in the workspace. The Devices menu is open to show that the example project also added an Arm device.

It is vital to know that when downloading Example Projects or opening Past Projects, the 'Standard Config' is the default.

VEXcode V5 with an example project opened and the Devices menu open to show that the added Arm is in Standard Config.

If you would like to change the configuration from the default 'Standard Config' you can do so using the steps above.

It is important to keep in mind that the Robot Configuration in VEXcode V5 must match the physical build of the Workcell, or the code will not run properly.