Question about specs of vex brain

[spaghettoid]

I have three questions about the processing power of the vex brain.

1. In pros what is the fastest it can run a loop(I want to try to have a separate loop for odom)
2. How many threads does the brain have
3. Is there a way to tell how long a process took in pros

[turbodog]

There was a post on this not too long ago. The iq brain has a limited # of concurrent threads… not sure what it was but I think it was like 20 or so, something pretty decent. v5 was unlimited.

[sazrocks]

@turbodog

v5 was unlimited.

@jpearman is this true? I remember that VCS had a limit of 128 back in the day, not sure about modern VEXCode.

Maximum Amount of threads

A lot. With VCS I set the limit at 128, but events use some of those. I’ve tested with 80 threads running.

@spaghettoid

In pros what is the fastest it can run a loop(I want to try to have a separate loop for odom)

Very fast, however for 99% of situations you aren’t going to have any advantage to looping faster than 10ms, as that is the rate that most sensor values update.

@spaghettoid

Is there a way to tell how long a process took in pros

The easiest way is probably to use high resolution timer on the brain and compare the value of it before and after you run the function. e.g.

uint64_t startTime = pros::micros();
someFunction();
uint64_t stopTime = pros::micros();
printf("time: %llu\n", stopTime-startTime);

The result will of course be in microseconds.

[jpearman]

@turbodog

v5 was unlimited.

@sazrocks

is this true?

No it’s not true and is still limited in VEXcode to 128.

[ayaan098]

What about in PROS?

[turbodog]

K. If you’ve got more than 128 concurrent running processes… maybe your team programmer needs a break.

[spaghettoid]

Also does anyone know what the memory limit on the brain is

[spaghettoid]

Challenge accepted ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ