NILEDYNAMICS / ASPIRE BOARD
Your first motion.
Then your next idea.
Connect your board. Run a motor without writing code. Add feedback when you’re ready.
Start the walkthroughReview draft · Not yet validated as a complete hardware walkthrough. Amber notes identify details still to confirm.
01 / PREPARE
Start with one motor.
Aspire Board is a two-channel DC motor control board. Aspire Studio is its Windows application: use the motor tools for no-code control, or create and upload your own firmware over USB.
Have these ready
- Aspire Board and Aspire Studio installed on a Windows computer.
- A USB data cable, one supported DC motor, and a motor-appropriate external supply within the board’s operating limits.
- Secure wiring and a firmly mounted motor with its shaft clear of people and loose objects.
- A suitable heatsink for operation at the stated continuous-current rating.
Choose a supply voltage and current limit suitable for your motor. USB provides communication; external power drives the motor.
02 / NO CODE NEEDED
Make your first move.
Start with Motor A only. Motor B has equivalent controls. Opening the motor tools stops the running main program; a factory-firmware restore is not needed to use the tools.
Wire with all power off
Disconnect USB and external power before wiring. Connect the motor to its labeled channel terminals and the external supply to the labeled power input, observing polarity. Do not guess connector orientation.
Connect USB, then external power
Attach the USB data cable to the computer and board. Apply the external motor supply only after checking the wiring and clearing the shaft.
Open Realtime Motor and connect
In Aspire Studio’s Pin Configurator, open Realtime Motor. Select the board’s COM Port and press Connect. Use Refresh if needed.
Center, enable and set the current limit
Keep the open-loop slider at its central zero position. Press Enable for Motor A, enter a motor-appropriate value in Limit A, then press Set before commanding motion.
0 means no limit, not zero allowable current. Do not leave this at zero for the beginner walkthrough. The documented protection is an overcurrent trip, not an instantaneous current clamp.
Move a little, then stop
Move the upper, open-loop slider a small distance from center. Its controls are labeled left: CW and right: CCW. Observe the shaft and the current/telemetry display. Press Centre (stop) to return the command to zero.
Your first checkpoint
You can command a small movement, return to zero, and see board telemetry. If the motor does not respond or readings are absent, stop here and use troubleshooting. Do not increase the command to compensate.
Emergency stopping and restarting
Each channel has its own EMERGENCY STOP A or EMERGENCY STOP B button. Use the button for the affected channel; do not assume it stops both.
NileDynamics confirms that motion processes stop when USB disconnects. This is not a substitute for a hardware power-disconnect arrangement; stopping latency and braking behavior are not established here.
Resolve the cause, restore USB communication if disconnected, return the command to zero, and press Enable again. Check the current limit before another command. Automatic slider reset and automatic COM reconnection are not yet confirmed.
What does “Test motors” do?
Motor detection applies a brief test pulse, so the shaft may move. Keep it clear before testing. The documented library can latch a channel off after an absent-motor result. Inspect wiring with power removed before retrying.
Draft: confirm where Test motors and Start Real-Time Smart Motor belong in the shipped application’s startup sequence. Their presence in the supplied screenshot alone does not establish that either is a required first-run step.
03 / ADD FEEDBACK
Control velocity, not just power.
Open-loop control commands motor drive without correcting for measured speed. Closed-loop velocity control uses encoder feedback to adjust drive toward a target speed.
Connect the encoder
Power everything off before adding wiring. Each motor has a dedicated encoder connector with 5 V, GND and one signal input. NileDynamics confirms signal compatibility with both 3.3 V and 5 V logic.
The connector’s supply is still 5 V: do not power a 3.3 V-only encoder from it. Check your encoder’s supply requirements and the board’s connector labels. This is a single-channel speed input, not a two-signal quadrature interface; the library infers direction from the commanded drive.
Configure pulses per revolution
Reconnect using the startup sequence above. In the correct motor panel, select Encoder present and enter the encoder’s Pulses/rev. Use the encoder specification, not a guessed value.
Draft: confirm edge-count interpretation and shaft reference for geared encoders before providing a numerical PPR example.
Send and check feedback
Warning: Send briefly spins the motor to check the encoder. Clear the shaft first, then press Send. The documented library requires a passed encoder check before velocity mode can engage.
Enter starting gains
Open Velocity PID gains… for the intended motor. With the motor stopped, enter P = 2, I = 1, D = 0. These are NileDynamics’ supplied starting values, not universal settings for every motor or load.
Try a small velocity target
Start with a zero velocity setpoint, select Velocity Control Mode, then use the rad/s field and Set for a small motor-appropriate target. Compare Measured and Setpoint. Return the target to zero to finish.
Known issue under review: closed-loop slider direction labels disagree with the open-loop controls. NileDynamics suspects a UI bug. Do not rely on those labels to establish physical direction; a verified closed-loop direction instruction is pending.
Understand P, I and D
- P · Proportional
- Responds to the difference between target and measured velocity.
- I · Integral
- Helps remove a persistent speed error.
- D · Derivative
- Adds damping based on measured speed changes.
The gains window says edits apply live. Change settings with care; begin stopped, test small changes, and stop if operation becomes unstable. The documented controller includes anti-windup and preserves its integrator during gain changes. That does not guarantee every gain change is safe.
Set all to 0 clears the gains; it is not the Emergency Stop control. Automatic loading and persistence of gains have not yet been confirmed.
04 / WHEN YOU’RE READY
Make the behavior your own.
You do not need this path for the no-code walkthrough. Aspire Board ships with a USB bootloader; Aspire Studio bundles the build and upload tools.
- Choose New Project from Home and select a name and folder.
- Open Pins, configure the required peripherals and motor channels, and generate code.
- Edit and save your application, then press Build. Resolve reported errors before uploading.
- Enter the board’s documented USB DFU bootloader mode, then use Upload. A COM connection for motor tools and DFU mode for uploading are different device states.
05 / KEEP MOVING
Help, without the guesswork.
No COM port or no telemetry
Check that the USB cable carries data, reconnect it, then Refresh the COM list and select the board’s port. Close other applications using the same port. Check whether the board is in application mode rather than DFU mode. Do not command motion until communication is established.
Motor does not move or stops unexpectedly
Return the command to zero. Check the external supply, selected channel, enable state and current limit. Inspect wiring only with power removed. For an overcurrent or detection fault, investigate the cause before pressing Enable again; do not repeatedly re-enable a stalled motor.
Velocity mode is unavailable
Check the correct motor’s encoder wiring and Pulses/rev value. Complete the encoder check successfully before enabling velocity mode. Repeatedly raising the target will not fix missing feedback.
Upload says “No DFU capable USB device available”
The uploader has not found a usable DFU device. Verify the board’s bootloader state and USB connection using the shipped-revision instructions. A visible COM port alone does not establish DFU readiness. Keep the full firmware log for diagnosis.
Build tools point to an old installation
In Settings, choose Reset to bundled defaults, then Save. Aspire Studio’s installer includes its build tools; saved old paths can override the bundled defaults.
Reference library
- Board reference & fixed pin mapping ↗
- Motor library & programming API ↗
- Pin Configurator ↗
- Data Logger ↗
Installer: purchaser download delivery is planned; the file and delivery link have not yet been attached. No download button is active in this draft.
Release checklist: approved connected-state screenshots; revised ratings/datasheet; validated motor, supply and current limit; supported Windows and installer version; bootloader/driver steps; closed-loop direction behavior and PPR interpretation; gain persistence and return-to-main-program behavior. Source baseline: Aspire documentation commit b1853e0 plus owner confirmations.