Why can't I now set the motors to hold mode when the robot is in the disabled period?

[lacsap]

@jpearman

This seems like another case where I’m being honest and transparent about changes that were made getting me into trouble

I appreciate your explanations, they have always been straight forward.

I was going to take offense to the same post, but if people would go back to the Game Manual, it has always been clear about the need to not score until all objects (robot included) have reached a rest state, so the VEXos change is consistent with the intent and all platforms past, present, and, hopefully, future.

[Foster]

Id rather have the transparency and the cool additions you do off books (like the VEXIQ interface to other hardware posts.)

I always take the “until the elements come to rest” as being more for the ball games where things roll around. But then I was here for Hanging A Round where we had a locking mechanism for the hang.

[Mentor_355U]

@jpearman

This seems like another case where I’m being honest and transparent about changes that were made getting me into trouble, the same thing happened a couple of weeks ago on another topic, but I’m sure this small change to the motor control has been explained more than once in the past.

We make many small changes to vexos, most are either bug fixes or improvements that you probably wouldn’t notice.

Apologies; my intent was more of a gentle ribbing than a dig. I do appreciate the transparency, and there is always a considerable gray area for release notes between too much and not enough.

[lacsap]

@Foster

But then I was here for Hanging A Round where we had a locking mechanism for the hang.

^ ^ ^
this - a real world problem…

robot knocking into platform end of match causing to unbalance? DQ or not?

Robot balancing platform through some weird oscillating motion and loses balance ? lost elevated points?

Real world life is rough - don’t we all know it! Thanks Covid-19! (not)

[technik3k]

@Connor

I remember in 2019 there was a bug that made the motors go full 127 while the field was disabled.

I think I remember reading something like that, but, it wasn’t a firmware bug.

If memory serves me right, it was some sort of an issue with the field control, that would momentarily turn autonomous mode on before going into disabled mode. Naturally, robots that were programmed to drive forward at the beginning of autonomous would try to do just that.

I cannot find relevant forum thread but, I believe, people were discussing issues with USB drivers for VEX match controller after recent Windows 10 updates and recommended having manual control as a backup. Back in the cortex seasons it was usually bad RJ45 cables and joystick ports that were prime suspects when field control would be acting up for individual robots.