Geeetech GTM32 Board

From Geeetech Wiki
Revision as of 08:58, 23 May 2018 by Admin (Talk | contribs)

Jump to: navigation, search

Introduction

GTM32 is a fully self-developed control board by Geeetech for high-performance 3D printers. It keeps Geeetech’s uniformly optimized interface specifications, easy to assemble and with compact layout, high integration and high performance. GTM32 control board (hereinafter referred to as the control board) adopts the current mainstream high-performance Cortex M3 core chip STM32F103, with its running frequency of up to 72MHz.The control board supports up to 4 stepper motors, namely, XYZ axial motor and an extruder. Users can replace the driving modules, such as A4988 and TMC2100 modules, according to their own needs. Besides, it employs the high performance USB serial chip FT232RL, which enables users to manipulate the control board via USB cable. Its output voltage is 12V.

Features

a. Adopting high-performance Cortex M3 core chip STM32F103, with its running frequency of up to 72MHz.

b. Using high-performance USN serial chip FT232RL, manufactured by FTDI, compatible with Windows, OS X, Linux etc. mainstream operation system.

c. The output voltage of GTM32 control board is 12V. It is characterized by dual power supply design, powering up the hotbed and other electronic components respectively. The current for hotbed is 9A and 7A for other parts.

d. The main circuit adopts in-line fuse, with overcurrent protection and reverse protection. The USB power supply interface has a restorable fuse, with its current at 500mA.

e. The control board features three interfaces for PWM fans.

f. Supporting up to 4 stepper motors, namely, XYZ axial motor and an extruder. The common stepper motor drivers are A4988 and TMC2100.

g. Dual temp sensor input: one for the extruder, the other for the hotbed. 100K thermistor is recommended.

h. The control board comes with expansion interfaces for LCD display and SD card, supporting stand-alone printing.

i. With a buzzer on board.

Interfaces

Development Environment Setting

Firmware

FAQ