No. It exists to exercise as many board functions as possible. Create a machine-specific copy with correct mechanics, safety, limits, spindle/laser, and accessory settings.
V5.77 is a carrier board. The ESP32-S3 module provides the processor, Wi-Fi, USB, and firmware storage. Seat it in the silkscreened orientation only while power is off.
The test YAML uses GPIO.38 for Z limit. Choose GPIO.38 when the module's RGB LED occupies GPIO.48. If a newer module uses GPIO.38 for its LED, move the jumper to GPIO.48 and change the YAML pin.
Wait about 10 seconds after boot, check the antenna/module, and confirm the board reached normal startup. Disconnect RJ12 equipment temporarily because GPIO.0 held low can force download mode.
The sensor/contact type does not match the YAML polarity. Verify wiring, then add or remove :low for that pin and confirm both idle and triggered states with $limits.
Not from the shared SW-VCC rail: item 5 selects one voltage for all ten headers. Use external suitable sensor power and safe common-ground/isolation practice for a mixed system.
They do not. V5.77 has no onboard driver sockets. Use the six PH2.0 EN/STP/DIR/GND connectors with compatible external drivers.
In the test YAML, M64/M65 P0-P5 control the six reserved I2SO outputs. The two MOSFET channels use coolant commands: M7 (GPIO.4), M8 (GPIO.5), and M9 off.
The analog speed signal and run contacts are separate. Check GPIO.7 Fwd / GPIO.8 Rev with Out Common, the VFD terminal mode, analog input type, common, minimum frequency, and interlocks. For RS485, check address, baud, model commands, and A/B polarity.
No. Use 12-24 V at VIN Main with correct polarity; 24 V is recommended. USB is for data and flashing.
Not when the native secondary USB channel is unused. Send $USBCDC/Enable=OFF if you are not using that channel. Re-enable/configure it before the optional USB-host test.
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.77-specific pins and settings unchanged and edit only the stepping.engine value in a backed-up YAML copy.