nUsageReporting

[nightpool]

So, we're having problems with our drive code. The first time we call it, it takes around 2 seconds to return. It consists of a single call to RobotDrive::TankDrive(). In TankDrive, there's a one-time call to nUsageReporting::report()


static bool reported = false;
if (!reported)
{
nUsageReporting::report(nUsageReporting::kResource Type_RobotDrive, GetNumMotors(), nUsageReporting::kRobotDrive_MecanumCartesian);
reported = true;
}


What does this call do? Is there something we could be doing that would cause it to take a long time to return?

[MisterG]

Bump.

We are still experiencing this problem intermittently.

When it happens, its immediately after we enable. It will hang for some period (~20 seconds) and then returns.

Our proposed workaround is to override all of the RobotDrive motion methods and remove the nUsageReporting::report() call.

At this point we are living with the problem but we will need to take action before competition.

Is anyone else experiencing anything like this?