From command line run:
rosrun muse_bldc_motor_drive muse_bldc_motor_drive
Now muse node publishes a list with Muse Drives that are visible on the network and is ready to listen to your commands.
Node runs in default frequencies: 1KHz for both feedback and control/state machine commands.
If you want to set another value for these frequencies, you can run:
rosrun muse_bldc_motor_drive muse_bldc_motor_drive <feedback_frequency(Hz)> <control_frequency(Hz)>
Note: There is no point in setting higher value for feedback frequency. However, you can decrease it, if you do not need it to be so high, or your network cannot handle such a high frequency.
Now you can create your own node, that publishes commands to muse node and subscribes to desirable topics.
Provides a list with all active Muse Modules, that are visible through current network and the number of them. The list provides some information for each module: module name, module ip, module status.
Provides the name of current Muse Module and also, feedback - current [A], speed [krpm], position [revs], bus voltage [V], temperature [C] - possible erros/faults, control mode and fsm state.
A command to open or close the topics needed for communication with a single Muse Module. You have to set the ip or name of desired Module and you choose the names of topics needed to send commands and get feedback from it. You can get Module's name or ip from muse/communication publisher and see if it's connected to the network.
- An interface to send control commands to Muse Module. Commands provided:
- An interface to send state machine commands to Muse Module. Commands provided:
control frequency(float64, default: 1000.0)
- This is the frequency that Muse Node can handle sent commands.
feedback frequency(float64, default: 1000.0)
- This is the frequency of published feedback from Muse Node.