The Accordion A2 Build is a configuration of the Accordion test platform — the same chassis, control system, and software stack as the Lite and Plus bundles, assembled to a specification matched to a single test bench. Where the Lite and Plus ship with fixed module sets, the Build is assembled from the standard Accordion module library to fit a specific application: power profile, channel count, communication interfaces, instrumentation, and form-factor constraints.
The A2 chassis is software-defined. Every channel is addressable by name; every protocol bus and every supply rail is configured at runtime. Modules are slot-mapped into the chassis (top-side SO-DIMM and N-TOP, front-panel M.2, dedicated communication TOP), and a custom configuration stays consistent with the Accordion naming convention so existing Pilot workspaces, TestStand sequences, and Python or C# scripts continue to work as the bench evolves.
A custom build is appropriate when the bundled configurations do not fit — for example, when the test program needs more programmable rails than the Plus carries, an instrument the standard bundles do not include (precision ADC/DAC, battery simulation, audio), or a specific mix of channel types the Lite cannot provide. The chassis is the same in every case; only the populated modules differ.
A custom A2 is a fully fledged Accordion node — reachable on the network by hostname or IP, addressable through Accordion’s standard channel-naming convention, and controllable through the Accordion API — Python, C#, TestStand, LabVIEW, or REST. Lifetime licenses for Accordion Pilot and Accordion Shell are typically included; bundled software depends on the configuration agreed during specification.
Further information: https://esharp.se/products/item/accordion-a2-build/.