...
While powering the Motor controller and CAN-eth bridge, if your computer doesn’t automatically detect the two devices, you will need to manually add them in Profinity. This can be done by clicking on the ‘Add Device’ button and manually adding the two.
Note: add the tritium CAN-eth bridge, not the Prohelion one.
When connected and properly powered, it should look something like this.
It might take a bit of disconnecting and reconnecting cables to your laptop to make this work, as it’s a little finicky.
Characterizing the Motors
Motor Configuration
Now we can start to configure the motor. While this guide does go in-depth, I would strongly recommend reading the Prohelion documentation WaveSculptor Config Software User's Manual (especially Sections 4, 5, and 6).
If you right click on the WaveSculptor22 section on profiles, you should see something like this
...
Navigate to Setup and Configuration > tools > configuration to get to this screen
...
Depending on the type of testing you want to do, you will need to change the Sine, SixStep, and IDC current limits. These limits represent the AC rms sinewave current going out of the Wavesculptor, the DC stepped voltage current going out of the Wavesculptor, and the input DC current into the Wavesculptor, respectively.
Before any testing gets done, go to the configuration ‘motor’ tab on the configuration page and set the relevant settings based on the motor datasheet (pole pairs, motor type)
Line Resistance & Inductance configuration
To find the line resistance & inductance (in the coils) we need to do the ‘param extract’ test. This can be found under wsconfig > tools > paramextract.
To perform this test, the motor will apply a series of voltages to determine the resistance. Unfortunately, this will move the motor. When the motor moves, it generates a back emf which will cause the calculated resistance and inductance to differ. In order to avoid this, have someone hold the motor steady when the test runs.
When ready, press the ‘extract params’ button in the bottom left. The final result should look something like this
...
Ideally, the red and blue lines will match as similarly as possible. (It might help to get someone else to hold the motor in place, the less movement the better)
Phasor/Hall Angles
In this test, the motor determines at which angles to activate/excite the hall effect sensors, in order to maximize efficiency. To run this test, go to wsconfig > tools > phasorsense.
In order to do this test, have someone continually spin the motor, while the other member clicks ‘phase acquire’, if successful, the software will let you know. A correct reading will look something like this:
...
AFter this is done, you should be able to operate the motor!
Operating the Motors
WARNING: By using a power supply to test the motors, we do not want regen braking to occur because power flowing back into the power supply will damage it!
To prevent this, make sure ‘Motor Current’ is set to zero before changing the velocity.
When you want to spin the motors, set ‘Velocity’ to a certain speed, then ramp up ‘Motor Current’ and you should expect the motors to spin.
...
Note: if you set the motor current too low (i.e. < 1 A), the motors may not spin.