Ezbv4 UART Voltage And Pin Map
@Athena,
I copied the following from the EZBv4 datasheet:
24 Multi-Use Digital Input/Output ports: D0-D23 Software configurable for servos, serial transmission, logical output 0V (Low) or 3.3V (High) voltage levels or PWM (Pulse width modulation)
Does this mean the UART-capable pins on the EZBv4 only transmit at 3.3V? If so, would there be no need for a voltage divider on the Teensy RX pin?
For context: this is about wiring the EZBv4 to a Teensy as a hardware-to-hardware connection in an ARC project (hardware connected to hardware via the EZB, not a PC-connected device). I’m specifically asking about the EZBv4’s physical port voltage levels used for serial communication.
Also, please consider making the next documentation/release a true pin map for this rover that includes:
- specific EZBv4 port numbers (D0-D23)
- specific Arduino Mega pins
- specific Teensy pins
- a refined 4-stepper CNC Shield pin map
- a one-page wiring checklist for assembly and verification
Thanks, Jack
Related Hardware (view all EZB hardware)
Related Robot Skills (view all robot skills)

Yes - on the EZ-B v4, the digital I/O signal line is 3.3V logic when used for digital output/serial signaling, while the port power pin is a separate matter and can follow the board’s input voltage.
Short answer
Important distinction
On the EZ-B v4 GVS port:
For serial communication, you care about the S pin, not the power pin.
For EZ-B v4 to Teensy wiring
Typical safe wiring is:
If your Teensy board is operating at 3.3V logic, this is usually fine directly.
One caution
If you are using a 5V Arduino board instead of a Teensy, then the Arduino TX EZ-B RX direction may need level shifting depending on the specific board and how it’s powered/configured.
Best reference for this
The most relevant Synthiam docs are:
EZ-B v4 hardware overview
https://synthiam.com/Support/Hardware/EZ-B-v4
IO port types
https://synthiam.com/Support/Advanced-Fundamentals/io-port-types
EZ-B communication protocol
https://synthiam.com/Support/EZB-Firmware/communication-protocol
About your documentation request
That’s a very reasonable suggestion. A true pin map that shows:
would definitely help reduce wiring mistakes. If you want, I can help you draft a clean one-page pin map template for ARC projects that you could use immediately.
A couple quick questions
@Athena. Thank you for your continued support. Please provide a true pin map that shows:
Thanks, Jack