NPBuilder is a Windows application designed for faster prototyping and development of motion control projects for the Commander Motion Controller. NPBuilder runs on most PCs/Tablets which run a WIN32 (32 bit) application. It provides a workspace for writing controller programs, sending command sequences, organizing project workflows, and creating product-specific APIs.

NPBuilder separates motion-control development into tools for controller logic, PC-side automation, and project-level organization. This structure allows starting with simple commands that grow into more complete systems as a project develops.

On this page

• NPBuilder Organization
• AScript Editor
• BScript Editor
• Code Block Builder
• Extend NPBuilder with Plugins
• Create APIs with NPBuilder
• Communication Model
• NPBuilder Uses

NPBuilder Organization

NPBuilder includes three working areas:

• AScript development for standalone applications, runs in the Commander controller
• Hybrid Bscript (combination ASCII commands and Bscript) for external control, runs in NPBuilder on the PC
• Large Projects using Code Block Builder, runs in NPBuilder on the PC with a GUI for user control during testing

AScript Editor

The AScript Editor is used to create programs that run directly on the Commander. These programs can control motion, respond to inputs, run homing routines, and continue operating without relying on constant PC control.

• Write BASIC-like motion-control scripts for the Commander.
• Compile scripts to PCode and download them to the controller.

Use AScript when the controller needs to manage tasks such as:

• Homing routines
• Coordinated motion
• Safety logic
• Embedded state machines
• Multi‑axis synchronization

BScript Editor

The BScript Editor is used to automate command sequences from the PC. It allows users to create and send repeatable ASCII command routines to the Commander over USB, serial, or Ethernet connections.

Use BScript for activities such as:

• Automated testing
• Repetitive ASCII command sequences
• Simple PC‑side logic
• Parameterized command templates for use in Code Block Builder
• Quick driver/axis validation

Code Block Builder

Code Block Builder aids in combining BScript routines into larger project workflows. It is useful for demos, test stations, prototypes, and operator-facing tools that need a simple way to run predefined actions.

• Combine multiple BScript routines into one project
• Add buttons, history, and terminal views for project operation
• Control multiple Commander devices from a single project

Extend NPBuilder with Plugins

NPBuilder includes a plugin system to add custom tools, setup dialogs, or code-generation features. Plugins make it possible to tailor the environment to a specific product or workflow without changing the main application.

Plugins are commonly used to add:

• User interaction for tasks not already built into NPBuilder
• AScript code generation, such as wizard-style dialogs
• BScript code generation, such as wizard-style dialogs
• Configuration dialogs for Commander setup
• Code generation that converts Code Block Builder projects to a target programming language

Create APIs with NPBuilder

NPBuilder can aid in moving from individual Commander commands to a reusable API that is easier to call from an application, test system, or product interface. Developers can use NPBuilder to define higher-level actions such as home an axis, move to a position, run a dispense cycle, start a test sequence, or reset a device.

A typical API workflow begins with testing the required Commander commands in NPBuilder, grouping them into BScript routines or Code Block Builder actions, then converting the validated routines into functions in the target programming language. This approach allows validation motion behavior before exposure through a software API.

Communication Model

NPBuilder communicates with the Commander by sending ASCII commands over the selected connection method. This makes it easier to test commands, automate routines, and integrate the controller into a larger PC-based system.

NPBuilder Uses

NPBuilder is designed to support the early stages of Commander based product development, from quick command testing to organized prototype workflows.

1. Controller-side motion scripting
   AScript and PCode allow motion logic to run directly on the Commander, reducing dependence on PC timing.
2. Multi‑axis coordination
   The Commander supports common multi-axis motion tasks, including:

• Stepper control
• Coordinated motion
• Embedded homing
• Multi‑threaded motion logic

NPBuilder provides access to these capabilities through editors and project tools.

3. Hybrid control model
   AScript runs on the Commander, while ASCII commands run externally from the PC. Both can run at the same time.
   This provides flexibility when deciding which logic should run on the controller and which logic should remain on the PC.
4. Plugin system
   Plugins allow the addition of custom tools, setup dialogs, and code-generation features without modifying NPBuilder.
5. Code Block Builder
   Code Block Builder can organize larger projects by combining smaller BScript building blocks into repeatable workflows.

• Prototype larger, complex projects.
• Generate code for target programming languages.

6. Clean ASCII protocol
   The ASCII command model maintains clear integration because commands can be issued from multiple programming environments.
7. Multi‑device support
   NPBuilder manages multiple Commander units at once.