Reserved for additional advanced building technique 1
Reserved for additional advanced building technique 2
Reserved for additional advanced building technique 3
Reserved for discussion of Pneumatic components 1
Reserved for discussion of lubrication of mechanical components
What do you find is the best type of grease for vex gears. Is it graphite powder, white lithium grease, WD - 40 etc.
1 Like
Reserved for discussion of mechanical maintenance of V5 smart motors
DO NOT use industrial lubricants like WD-40 or white lithium grease on internal plastic gears inside V5 motors or cartridges.
You may use light synthetic oil or synthetic grease like SW-92SA that is used for fine/plastic mechanical internals of cameras, printers, keyboards, dvd players, etc…
Broken Motor Inserts
V5 motor Cap and Threaded Insert replacement parts are sold separately
May need to be moved into V5 Motor electric/programming entry:
vexos 1.0.9 uses a different algorithm than versions 1.0.8 and earlier.
8 or less motors are still capped at 2.5A.
9 or more are capped as follow, remember this is current at the motor not current from the battery,
9 2.39A
10 2.29A
11 2.20A
12 2.12A
13 2.04A
14 1.98A
15 1.91A
16 1.85A
17 1.80A
18 1.74A
19 1.69A
20 1.65A
However, those values are only valid if user code has not set current limit lower on one or more motors. If that has happened we take the user specified lower motor curren…
1 Like
Reserved for V5 components overview
3-wire:
The issue is that the build system will not guarantee the order in which instances are created across different source files.
The instance of Brain is defined I’m assuming somewhere else such as robot-config.cpp. That means it may not have been created, and therefore the Brain.ThreeWirePort also not created, when you try to access it in your main.cpp source file. The solution is to either move
bumper LiftBumper = bumper(Brain.ThreeWirePort.A);
into the same file (and placed after) as the Br…
Specific 3-wire port numbers for dual wire sensors:
Pretty sure all programming solutions either enforce this or have documentation explaining it. For example, PROS has
Encoders must be plugged into the ADI such that the top wire
is in an odd numbered port (1, 3, 5, 7 or ‘A’, ‘C’, ‘E’, or ‘G’), and then
the bottom wire must be in the next highest port number.
Possible problem due to order of initialization of 3-wire port accessor instances:
Memory Permission Error
Temporary workaround for 8 legacy 3-wire port limit:Connect multiple sensors to a single port to overcome the limit of 8 legacy ports
Legacy, non competition legal components:Using Flashlight in VCS
1 Like
Reserved for Bumper and Limit Switch wiki entry
Reserved for VEX Potentiometer wiki entry
Reserved for Quad Encoder wiki entry
Reserved for IMU / Gyroscope wiki entry
Description
The Inertial Sensor is a combination of a 3-axis (X, Y, and Z) accelerometer and a 3-axis gyroscope. The accelerometer will detect a change in motion (acceleration) in any direction and...
V5 Inertial Sensor
This procedure calibrates the accelerometers in the Inertial sensor and saves the result in non volatile memory.
This procedure needs vexos 1.0.10 or later.
Only perform this calibration if your VEX inertial sensor is showing angles for roll and/or pitch that are larger than perhaps 1 or 2 degrees when the inertial sensor is on a flat surface that is known to be level in both axis.
Some inertial sensors can show significant error for roll and pitch when placed on a level surface. To check a…
When you run a program, the inertial sensor starts a calibration sequence, the first second of that sequence does not look at gyro values, it just waits for everything to stabilize, so any movement from touching the V5 should have stopped. It won’t hurt if you restart the calibration at the beginning of your program, I’m just saying that it’s not strictly necessary. You can also choose to manually recalibrate the inertial sensor at any time by going to the dashboard and selecting calibrate, yo…
3 Likes
Reserved for Light Sensor wiki entry
Reserved for Ultrasonic / sonar / rangefinder sensor wiki entry
Correct.
Yes, the ROBOTC executive and interrupts handle the ultrasonic sensors.
You can stop the ultrasonic by setting the sensor type to “sensorNone”, I don’t see why you would want to though, the overhead is minimal. Some demo code to show how to do that.
#pragma config(Sensor, dgtl1, sonar1, sensorSONAR_cm)
//*!!Code automatically generated by 'ROBOTC' configuration wizard !!*//
task main()
{
while(1)
{
// Turn off sonar
if( vexRT Bt…
No official way and the unofficial way is unreliable.
The Ultrasonic sensor is polled approximately 20 times per second but varies depending on the distance.
The ping is initiated, the receiver will wait up to about 36mS for a reply, there is a delay of 50mS before the next ping.
Here is the sonar detecting an object about 130cm away. The blue trace is the output ping, the yellow trace goes low when the reply is received.
[sonar_130.jpg]
Here is the sonar failing to detect a reply.
[son…
1 Like
Reserved for V5 Vision sensor wiki entry
have a look at these knowledge base articles.
https://help.vex.com/category/205-vision-sensor
There are two different ways to configure the sensor depending on whether you want to use the robot config panel or just create vision header files.
https://api.vexcode.cloud/v5/html/classvex_1_1vision.html
Vision Sensor
USD: $79.99
This is a demonstration of how to write code using the V5 Vision Sensor to find a vision target object, and then orient your robot to “face” directly towards the target. You will need to configure the vision sensor before trying the program. We include a link to how to configure the Vision Sensor here .
Sample Projects
Blockly Python C++
[image]
There still seems to be some issues setting up the vision sensor. Although we do know that VCS 1.0/vision sensor utility has a few bugs in this area, it is still pretty simple, I’m not sure why the theories about needing to freeze the image are running around. Anyway, here’s a quick demo showing how easy it is.
The configuration that is hidden inside robot-config.h looks like this and is what is used in your program to setup the vision sensor when it runs.
vex::vision::signature SIG_1 (1, -…
I had a play around today with the vision sensor on one of my old demo robots. The goal was just to test some simple targeting code that could be used as a basis for a more complex program. The robot setup looks like this.
[P1050576]
I obviously have a large target, but the concept would be the same no matter what size although the code would need to filter out more noise (meaning removing small intermittent objects) with something less well defined. I have the vision sensor mounted sideway…
I’ve been asked a few times about the vision sensor field of view.
I wrote in this thread that is was 67 deg, that was based on quick measurements with a target pretty close to the sensor, that number is close but not correct.
@Windows10010 posted earlier today here that they thought it was 30 deg, that seemed way too narrow from what I remembered.
I used to do this type of measurement often as I worked in the film industry for a camera manufacturer. It’s pretty easy to do, harder with this …
Get more with VEXcode We recommend you transition to our new software. VEXcode has both block-based and text-based options, that work on Chromebooks, iPads, And
If you look at the V5 dashboard when you are running your code, do you see the detected objects ?
When your code is not running, you can test the vision sensor with our preset values for red, green, blue and yellow, but these settings are not related to anything in your program, they are just for testing if it is working.
Meaning of Vision Sensor parameters? Vision Sensor config - objectCount inconsistent V5 Vision Sensor "The Camera detected must be unlocked" Vision Sensor Wifi Vision Sensor Having Issues Seeing Objects V5 Vision Sensor Color Code Coordinate Tracking
Vision Sensor Math:
EDIT: DODGY AND/OR INCORRECT MATH
CASE WITH GROUND OBJECT
I am not that confident in my math, but here is what I came up with.
SETUP
Your sensor is mounted on a tower. Your sensor is always a certain distance from the ground, if your robot stays level.
[image]
The sensor can see objects, and it gives them X and Y coordinates. (x is between 0 and 640, y is between 0 and 400.) I am not sure if the coordinates will work exactly as shown, but it wil…
Object Tracking:
We’ve been experimenting with the V5 vision sensor to better understand how it works and what its limitations are. Theo, our programmer, has so far been able to make it track and follow a ball using just a P loop for now. We used an old NBN ball because our game objects hadn’t arrived yet.
4 Likes
Reserved for V5 Optical Sensor
Vex Knowlege base article
1 Like
Reserved for V5 Distance SensorVex Knowlege base article
1 Like
Reserved for V5 3-Wire Expander
(I’m not so sure this needs it own entry but I will put it for now - Floub)
https://kb.vex.com/hc/en-us/articles/360047144991-Using-the-3-Wire-Expander-Sensors-for-VEX-V5
1 Like
