1 · Identify the board
Let the reader match the physical board and choose the right column before looking up a rating.
Explore the board references and the printable datasheet for Prime and Core.
Download draft PDFBoard names open the matching captures. Each row recommends specific information to carry into Smoothieboard V2 documentation. Source sections are grouped by function so manuals and shorter datasheets can be compared.
No boards match. Change the search or choose another category.
| Board | Sections and information | Apply to Smoothieboard V2 |
|---|---|---|
| Mesa 7I96SEthernet step/direction and machine I/O | Pinouts, jumper modes, isolated I/O ratings, encoder thresholds, firmware/reference registers, mechanical drawing | Use one table per terminal and separate ratings by output type. Keep register details in the firmware reference. |
| Mesa 7I76EEthernet motion and isolated field I/O | Field and logic power, expansion jumpers, connector pinouts, step/dir timing, field I/O, encoder modes, firmware and fault indicators, min/max tables | Show current with an explicit load condition and specify the exact rail. Expand serial register tables only in the integration reference. |
| Mesa 7I92TEthernet FPGA motion interface | Power and jumper options, connector variants, FPGA pin mapping, flash recovery, operating conditions, dimensional drawing | Show connector and power-source variants and label what changes with configuration. |
| Centroid AcornMill, lathe and router controller | Kit and bench setup, controller power, grounding, digital inputs, relay outputs, external drives, spindle and troubleshooting | Specify what the input expects electrically, including ground/common. Mark which hardware lives on the board versus an accessory. |
| Centroid AcornSixSix-axis step/direction controller | Logic supplies and bench test, inputs, output modules, drive wiring, spindle, encoder, PLC I/O, mounting | Document output state at startup and faults, and show mounting datum and connector clearances. |
| Centroid HickoryIndustrial EtherCAT motion controller | Drive compatibility, bench setup, grounding, isolated digital I/O, analog input/output specs, encoder setup, fault diagnosis | Identify input topology and signal reference. Keep drive compatibility and firmware setup in an integration appendix. |
| Centroid OakExternal servo-drive motion controller | Board overview, power, analog drive interface, encoder inputs, selectable input voltage, PLC expansion and connector pinouts | Describe each configurable input mode with its electrical requirements. Separate expansion capacity from populated ports. |
| PoLabs PoKeys57CNCEthernet/USB CNC and plasma I/O | Board layout, power, connector tables, motion and isolation, peripheral examples, electrical specifications, troubleshooting | Place minimum/maximum and signal type by connector function. State when several connectors share one supply budget. |
| Makerbase MKS DLC32 MAXLaser engraver and small CNC controller | Features, board diagram, dimensions, supply and laser interface specs, accessory inputs, configuration and firmware | Pair the board map with electrical notes for each connector. Put firmware-gated inputs in a support table. |
| MachBob2 MB2CNC breakout board for Ethernet SmoothStepper | Board specification, isolation, pin assignments, output circuits, power, setup, terminal diagrams and mounting | Show the host/accessory boundary and the domains of any isolated circuits. Publish a mechanical drawing with mounting information. |
| Board | Sections and information | Apply to Smoothieboard V2 |
|---|---|---|
| Arduino UNO R4 MinimaGeneral microcontroller board | Features, operating conditions, block diagram, board topology, power tree, pinout, accessories and declarations | Adopt a compact min/typ/max table with units and a separate board-level signal-flow diagram. |
| Arduino UNO R4 WiFiNetworked microcontroller board | Features, operating ratings, block diagram, board view, processor and radio, power tree, pinout and declarations | Show a labeled board view and call out the distinction between main and auxiliary processors. |
| Arduino GIGA R1 WiFiSTM32H7 development board | Operating conditions, block diagram, board topology, dual-core processor, communications, power tree, pin tables and declarations | Use clearly named silicon and firmware roles. Put the power tree beside the ratings that refer to its rails. |
| Arduino Nano EveryCompact microcontroller board | Features, operating conditions, power consumption, topology, connectors and pins, mechanical and compliance information | Keep power consumption and supply limits adjacent with measurement status and conditions. Use a numbered pin diagram and tables. |
| Raspberry Pi PicoEmbedded microcontroller board | Pinout, mechanical and operating specs, power use, ADC notes, ways to power, schematic and revision history | Illustrate alternate supply paths and explain shared returns and analog reference limits. |
| Raspberry Pi Pico WWireless microcontroller board | Pinout, mechanics, operating conditions, ADC limitations, powerchain, wireless integration, revision history | Add layout and integration constraints where an interface depends on the physical assembly. Document shared pins and their operating mode. |
| Raspberry Pi Pico 2Embedded microcontroller board | Pinout, mechanical specification, recommended conditions, measured consumption by workload, power, schematic and revisions | Give the bench configuration and workload for typical consumption. Keep an unpublished value open until it can be measured. |
| Raspberry Pi Compute Module 4Embedded computer module | Variant matrix, interfaces, mechanical data, absolute limits, operating conditions, pinout, carrier-board power and thermal information | Lead with a variant matrix. Keep stress limits distinct from recommended conditions and describe the load and ambient assumptions. |
| BeagleBone BlackEmbedded Linux board | Silicon and board features, block diagrams, power modes, consumption by state, connectors, expansion and mechanical drawings | Make a board power diagram and distinguish boot, idle and loaded consumption. Record which peripherals were powered during each reading. |
| Electro-Smith Daisy SeedEmbedded music and audio module | Pinout, absolute limits, pin functions, electrical characteristics, application circuits, document history | Publish one absolute-limits table with clear pin families. Show alternate functions and give worked interfaces in an appendix. |
Selected original pages illustrate the patterns in the table. Click a capture to enlarge it. Page numbers follow PDF order, including covers and front matter. Each full source PDF is linked at its publisher. Browse the full source catalog.
| Content | What the references show | Smoothieboard V2 treatment |
|---|---|---|
| Identity and variants | Compute Module 4 and the Arduino board sheets give the reader the product identity and main differences up front. | Identify the two Prime driver designs and the Core logic board. Include hardware revision, identifying marks, firmware target, and shared versus revision-specific interfaces. |
| Ratings and test conditions | The Mesa boards tabulate limits by signal and load. Raspberry Pi and Daisy distinguish operating conditions from stress limits. | Separate recommended min/typ/max, absolute limits, and typical measured performance. State temperature, cooling, rails, loads, channel count and current basis. Keep unverified cells visible. |
| Power and protection | The Pico and BeagleBone diagrams show where current comes from. MachBob2 identifies isolation domains. | Draw motor and switched-load rails, logic power selection, power returns, shared current limits, rail sense, and the output cutoff boundary. Add source-priority and startup/fault behavior when verified. |
| Motion, loads and sensing | Centroid and PoLabs explain what individual external circuits expect to see. | Specify motor phases, step/direction timing for external drives, heater/fan/bed and control outputs, input thresholds and polarity, ADC range and accuracy, probe jumper modes, and return pins. |
| Connectors and mechanical fit | Makerbase and AcornSix use board-facing views and dimensioned drawings. Arduino and Daisy number pins and list their alternate functions. | Provide a correctly oriented connector map and individually numbered tables. Mark shared nets, pin 1, mounting datum, screw hole pattern, component height, and required cable clearance. |
| Firmware and qualification | Pico 2 reports power with workload conditions. CNC manuals pair hardware with access, startup or compatibility notes. | Record minimum verified firmware, features and file names, confirmed host protocols, environmental and regulatory evidence, and published document revisions. Move setup walkthroughs and full schematics to linked references. |
Eight schematic page layouts show the reading order and what belongs together. The boxes represent information blocks. A short datasheet can combine adjacent panels if the electrical tables stay readable.
Let the reader match the physical board and choose the right column before looking up a rating.
Show where motor, switched loads, logic and accessory rails get power. Label dependency on the source and any shared cutoff.
Give phase-current basis, output load limits and simultaneous-load restrictions. Keep driver chip capabilities tied to the driver.
Give input modes, thresholds and required returns. Show which values depend on jumper state and board revision.
Use the board layout as the spatial index. Each connector table gives contact order, signal role, electrical notes and shared functions.
Distinguish physical ports, available firmware features and reserved or shared nets.
Use revision-qualified CAD for nominal geometry and assembly checks for clearances. Publish thermal limits with test conditions.
Link hardware and firmware revisions, qualification reports, declarations, and changes to ratings.
Full pages from the downloadable PDF. Select a page to enlarge it. Jump to electrical limits, wiring, firmware updates, mechanical drawings or settings and defaults. CAD contact inventory (CSV) · Solder jumper locations and pad nets (CSV) · Nominal mechanical envelopes (CSV). The jumper and envelope files use the top-left PCB datum on page 15 with USB at left in the component-side view. Verify fitted jumper states and allow space for plugs, cables and moving parts.
Electrical limits · Power paths · Motor bus transients and bulk capacitance
The wiki’s Prime pr.bin matched the SmoothieV2 v1.0.12 smoothiev2.bin release asset on 2026-11-21. The file is 889,896 bytes. Its whole-file SHA-256 is:
755fdebee168bab984e0f09b3b31059ea65656d75a7996dbc95315b2c5c1f13d
The published pr.md5 covers every byte before the final 32 ASCII checksum characters, including the Prime target marker. To check the entire downloaded file, use the SHA-256 above. Verify the running build and board profile after an update.
The wiki and release checked list the Prime download. A separate Core image is absent from those listings. Installed build, profile and loader compatibility still need checks on each shipping assembly.
Feed hold and resume. The v1.0.12 source can recognize ! and ~ even inside an incoming line. The later reviewed source requires an empty line buffer. Use the sender’s supported controls and verify handling of partially received lines with motion energy isolated. See startup, halt and recovery.
Backlash compensation. The later reviewed CNC example adds [motion control] backlash_enable (fallback false) and per-actuator keys such as [actuator] alpha.backlash_mm (fallback 0.0 mm). Those keys and the M425 handler are absent from the release-tag source. On a build that supports them, M425 can report or change the live settings. M500 does not retain those changes. Confirm the installed build before selecting a sample profile.
Firmware and recovery · Firmware downloads · Release v1.0.12 · Source comparison
With heater power disconnected, use a sensor-only configuration on one buffered input. On J21, select ADC1_1 and set heater_pin = nc for the enabled temperature controller. With the board off, substitute a measured resistor between the sensor contact and ground. Power logic only. Compare the connector voltage and the temperature reported by M105.
| Test resistance | Nominal contact voltage | Calculated reading |
|---|---|---|
| 100 kΩ | 3.15 V | 25.0 °C |
| 4.7 kΩ | 1.65 V | 111.2 °C |
| 1.0 kΩ | 0.58 V | 177.0 °C |
These examples apply to J21–J23 on all three variants, using the nominal 3.3 V and 4.7 kΩ divider and the unmodified firmware fallback of 100 kΩ at 25 °C and β = 4066 K. A different preset changes the expected temperature. Meter loading, component tolerances, buffer and ADC error affect real readings. Use a sensor-specific reference for acceptance.
Open and short conditions drive the input toward opposite rails. In the reviewed firmware, M105 displays −100 °C when conversion returns infinity. Check the connector voltage to distinguish a high-side fault from a low-side fault. Keep heater power disconnected throughout.
Thermistor connections · Heater fault response · Temperature conversion
Measure the standoff gap from the PCB underside to the nearest enclosure surface. These nominal projections come from the three assembly models.
| Assembly | Deepest part without BT1 | With BT1 |
|---|---|---|
| Prime 2660 P11 | 2.37 mm · J1 USB-B | 3.65 mm |
| Prime 2590 P12 | 2.85 mm · J5–J8 motor terminals | 3.65 mm |
| Core P1 | 2.37 mm · J1 USB-B | 3.65 mm |
A 3.00 mm gap leaves about 0.63 mm on P11 or Core P1 and 0.15 mm on P12 without the holder. With the modeled holder over a flat enclosure surface, it produces 0.65 mm interference. These figures are before tolerances. Measure the actual tails, solder and optional holder. Account for enclosure hardware, flex, electrical spacing and the intended chassis bond before selecting standoffs.
Above the PCB, check clearance with the plugs installed, the microSD card in its removal position, and the external driver breakout fitted on Core.
Mounting drawing and STEP files · Nominal component envelopes (CSV)