Coding Motor Connection Check

[1060B_JazzyJumpers]

I’m only really knowledge able on how to use block code but am willing to use text if someone would be willing to help me out. I’m trying to code a full system connection check display screen, where the user can check and see what motors or sensors are connected and display their output and change a label color to red if their disconnected and green if connected. Does anyone know how you could accomplish this via block code, could help me with a place to start for switch blocks, or give me some pointers on how best to go about this. Thank you.

[technik3k]

Default VEX V5 C++ API has, at the very least, motor.installed() function to check if motor is connected. I am not sure if there are any accessible undocumented functions which could give you more information regarding port status.

Then, this may a bit to steep of a climb from the block code, but an alternative to the default V5 development environment is Pros, which provides extended API and has more functionality to test for connected device status (see VEX Generic Device C API (For Advanced Users) module | PROS for V5)

How to Detect Device in Port

I am working on a piece of code that alerts the program if a device is missing. For example, the program knows that there is a motor in port 1 and detects if there is a device plugged in. I have been looking through the pros include files on GitHub and have found the command: v5_device_e_t registry_get_plugged_type(uint8_t port); It is in the pros/include/vdml/registry.h, unfortunately, that file doesn’t exist in my pros project. Is there another function that can detect if a motor or vision …

A Simple V5 Motor Test Utility

If you’re running a decently large program, you probably have a bin of questionable motors. If your program is anything like ours, that bin is probably partially full of motors that students are blaming for their own issues, cables, or overheating. This quick test software (written in PROS) helps you resolve which motors are actually bad and which can go back in the good motors drawer. It runs the motor through a forward/reverse test for a few seconds and decides if they perform well enough. No…

Over the years people have developed a number of V5 Motor Testers based on that API with source code available on GitHub: example 1, example 2, example 3

[jpearman]

For V5 Python you could do something like this.

brain.screen.set_font(FontType.MONO15)

for port in range(Ports.PORT1, Ports.PORT22):
    if Motor(port).installed():
        brain.screen.print("Motor %2d found"%(port+1))
        brain.screen.new_line();

I would avoid putting that in a loop or calling too often