No. Like the other PiBot boards, it is a bench-commissioning file built to exercise the board's functions during the Check List, not a ready machine profile. Once the Check List passes, copy it and adapt mechanics, safety, limits, and spindle/laser settings to your own machine.
Yes, on all 6 dedicated axes — unlike the V5.77 Carrier, which is external-drivers-only. Each of the 6 channels provides an on-board Pololu-format socket and an external 5 V Step/Dir/Enable output, with per-axis SPI chip select for TMC2130/TMC5160.
6 dedicated motor channels (X, Y, Z, A, B, C) plus the Extra I/O signals (GPIO.3, GPIO.10, GPIO.15), which can be configured as one more Step/Dir/Enable group (7 axes total) or used as ordinary I/O — not both at once. In the factory test config.yaml, GPIO.3 stays as the toolsetter input and GPIO.10/GPIO.15 are mapped to user outputs P0/P1 (M64/M65).
It is officially listed in the grblHAL Controllers repository and Web Builder, but the target is marked Experimental, and the public Web Builder currently exposes a maximum of 4 axes even though the board is 6+1-axis capable on FluidNC. Use a fresh grblHAL build — do not reuse the FluidNC config.yaml.
12–24 V DC only; 24 V is recommended. 5 V is not enough to run the board, and voltage must never exceed 24 V — some on-board circuits are limited to 24 V even though the main regulator is rated higher. USB is for data and flashing only, not for powering the board.
Three jumper caps ship installed from the factory: SW-VCC Voltage Selection, Stepper Driver VDD Logic Voltage Selection, and GPIO.3 Function Selection. See 2.2 Check Jumpers and Power On for the correct position of each, and re-check them any time you change driver type or how Extra I/O is used.
Match the module orientation to the socket silkscreen before power-on; a module inserted 180° rotated can be destroyed as soon as power is applied. Never hot-plug drivers, motors, the OLED, or the pendant while the board is powered.
500 mA maximum per channel (io.4 / io.5, switched by GPIO.4/GPIO.5, mapped to mist/flood coolant M7/M8 with M9 to turn both off in the test config.yaml). Use an external relay or suitable power driver for heavier loads; overloading can burn the MOSFET.
Wait about 10 seconds after boot and check again. The network is created by the board itself: SSID fluidnc, password 12345678, WebUI at 192.168.0.1; your computer does not need to be on your home router for this.
No. It appears when the board is connected through the CP2102 USB port while the ESP32-S3's native USB channel is unused. Send $USBCDC/Enable=OFF once — it is stored in the controller and stays off after power cycles.
Use the shared bidirectional raster offset troubleshooting guide. The master guide is maintained in the V4.96 FAQ because that is where the documented before/after case was tested. The mechanical checks, one-way scan comparison and LightBurn Scanning Offset Adjustment also apply here. If comparing stepping engines, keep all V5.88-specific pins and settings unchanged and edit only the stepping.engine value in a backed-up YAML copy.