What things does a license axis count include?

What is measured by a license’s “Axis Count”?

Each license has an “Axis Count” associated with it.

What exactly is this counting?

  • real axis objects on the network (that show up in RapidSetup as an axis)?
  • RSI::RapidCode::Axis objects (including phantoms)?
    • Whatever shows up in RapidSetup’s “Axis Count”?
  • RSI::RapidCode::MultiAxis objects?

Anecdotal evidence suggests that it corresponds to the value returned from MotionCountGet().

I’m debating about how to implement some behavior, and I need to know whether adding another object will ding the axis count (and incur additional expense).

It is counting RMP Axis objects (real or phantom), it’s using the same thing you can read using AxisCountGet(). RapidSetup shows you the Axis License Count.

MotionCount does not have any licensed restrictions.

1 Like

[RMP 10.3.1]

In RapidSetup, if I set the axis count equal to the axis count in the license, then try to add a single multi axis, I see this error:

Control: motionCount is invalid :: {control.c, line 8820} : MPIControlConfig.dynamicMemAlloc.motionSupervisorCount: 65 is out of range, the valid range is 0 to 64. (Error 1549) (MotionController::ControlConfigSet) (Object 0) (File motioncontroller.cpp) (Line 1297) (Version 10.3.1.0)

If I reduce the axis count by one, then adding a single multiaxis succeeds.

MotionCount does not have any licensed restrictions.

The RMP has a hard limit of 64 motion supervisors, axes, etc. (Each Axis uses a motion supervisor.)

1 Like

Ahh. OK. I was testing this with a developer license. Thanks.