Connecting an SKR3EZ H743 via an ESP8266 or ESP32 WiFi Adapter

How to connect to an SKR3EZ H743 via an ESP8266 or ESP32 WiFi Adapter

Overview

The SKR3EZ H743 is an STM32H743 based board.

WiFi

You will need a BTT or MKS produced ESP8266 WiFi module or a Fly/Mellow ESP32 Module.
TeamGloomy recommend an ESP32 module over an ESP8266 module as WiFi performance with an ESP32 is superior.

Downloading the board firmware

Choose the firmware (firmware-stm32h7-wifi.bin) from here. You can choose to download either the latest release (marked latest and classed by us as stable) or the latest pre-release if available (marked pre-release and classed by us as unstable).

Once downloaded, rename it firmware.bin

WiFi firmware preparation

Choose the correct corresponding firmware from here.

DuetWiFiServer-X.XX-XX.bin for ESP8266
DuetWiFiServer-32-X.XX-XX.bin for ESP32

Once downloaded, rename it DuetWifiServer.bin

DWC (DuetWebControl)

The correct version of DWC should be downloaded from here.
The version you download should be of the same version number as the board firmware you downloaded above.
For example, if version 3.4.0 of the board firmware has been downloaded, 3.4.0 of DWC should be downloaded.

Generate a config

We provide a handy online tool to assist you in generating a set of config files for your 3D printer. The configurator doesn’t cover all options that RRF can be used for (such as dual motor axis control, which can be manually added later), however it does give a good start.

We also have a collection of user created configs which can be a useful reference. They can be found here

Manual board.txt Changes

If you are using a set of config files provided by someone else or have no need to use the configurator, you will need to create your board.txt file manually.

Below are the contents that should be used.

//Config for SKR3EZ H743
board = biquskr_3_ez
//WiFi pins
8266wifi.espDataReadyPin = PB_10
8266wifi.TfrReadyPin = PB_11
8266wifi.espResetPin = PC_14


//both RX/TX Settings
8266wifi.serialRxTxPins = { PD_9, PD_8 }
serial.aux.rxTxPins = { PA_10, PA_9 }
heat.tempSensePins = { PA_1, PA_2, PA_3 }
leds.diagnostic = PA_13

Smart Drivers

If using TMC5160 or TMC22XX drivers (where 22XX is either the TMC2208, TMC2209, TMC2225 or TMC2226), the following line must also be added to the board.txt file

stepper.numSmartDrivers = X

Where X is the number of drivers fitted in total.

TMC5160 SPI Drivers

If using TMC5160 drivers, the following lines must also be added to the board.txt file.

stepper.num5160Drivers = X
stepper.spiChannel = 3
SPI3.pins = { PE_14, PE_15, PE_13 }

Where X is the number of TMC5160 drivers fitted.

The drivers must be grouped together with the installed TMC5160s first. They can have gaps between each driver and/or driver type. So, if you have say 3 TMC5160s and 1 TMC22XX and 1 other driver, the 5160s should installed first (e.g. in slots 0, 1 and 2 or slots 0, 3 and 4), the TMC22XX in a slot after the 5160 and the remaining driver last. You can use RRF to assign any of those slots to an axis/extruder.

Sensorless Homing

Follow the instructions as found here

Manual board.txt Changes

If you are using a set of config files provided by someone else or have no need to use the configurator, you will need to create your board.txt file manually.

Below are the contents that should be used.

//Config for SKR3EZ H743
board = biquskr_3_ez
//WiFi pins
8266wifi.espDataReadyPin = PB_10
8266wifi.TfrReadyPin = PB_11
8266wifi.espResetPin = PC_14


//both RX/TX Settings
8266wifi.serialRxTxPins = { PD_9, PD_8 }
serial.aux.rxTxPins = { PA_10, PA_9 }
heat.tempSensePins = { PA_1, PA_2, PA_3 }
leds.diagnostic = PA_13

Drivers

Although the original method of having the firmware detect the drivers is still supported, as we have now added TMC2240 support, there is now a new method.
The following line should be added (obviously with the array entries matching your drivers and their locations):

stepper.numSmartDrivers = X
stepper.DriverType = {Tmc2208, Tmc2240, tmc2209, tmc5160, stepdir}

For the number of smart drivers, if you have the following installed (tmc2209, none, tm5160, stepdir, tmc2209) then numSmartDrivers needs to be set to 5 not to 3. Basically it means how many entries there are in the driver types array. Entries after that number get set to stepdir.

The DriverType array allows for any driver to be used in any slot so there is no order requirement like the previous detection method. The array must also include an entry for each driver slot up to the last one thats populated.
The following list of entries are valid:

none
stepdir
tmc2208
tmc2209
tmc2660
tmc5160
tmc2240

If using TMC2240 or TMC5160 drivers, you also need to add the correct spi channel:

stepper.spiChannel = 3
SPI3.pins = { PE_14, PE_15, PE_13 }

TMC2240 Driver Temperature

TMC2240 drivers support reporting their own temperature, rather than just hot and very hot like the other TMC drivers. To utilise this, add the following line to your config.g

M308 S11 Y"drivers"

This will return the highest temperature reading from any of the drivers, 2240s will return the actual temperature, other drivers will return 0, 100 or 150 (as before).

If you want to know the temperature of a particular driver you need to add the following line (as well as the above):

M308 S12 Y"drivertemp" p"S11.X"

Where x is the driver number that matches the driver number used by M569

Sensorless Homing

Follow the instructions as found here

SD Card preparation

Now all the required files have been gathered, the SD card structure needs to be created.

SD Card Specification

When choosing an SD Card to use with RRF, we recommend one with the following features:

a branded card with a speed rating of Class 4 or higher
of up to 32GB capacity, formatted as below. RepRapFirmware does not support SD cards formatted in exFAT format.

Formatting

Tip: We recommend formatting you SD card with the SD Memory Card Formatter from the SD Association. Do this regardless of whether the SD Card is brand new or has been used for something else.

If you can’t use the recommended formatting tool, then the following points should be taken into account:

If you need to reformat the micro SDHC card:

If the capacity of the card is 4GB or lower, use FAT16 format
If the capacity is more than 4GB (up to 32GB) then you will have to use FAT32 format
All cards should be formatted with 512 byte sectors
For best upload speed choose the largest cluster size available, which is normally 64kb for FAT16 and 32kb for FAT32

Warning: DO NOT use Windows ‘Quick Erase’. This generally does not create a clean FAT32 partition.

SD Card Structure

The following structure should be replicated on your SD card.

sd card root/
├─ filaments/
├─ firmware/
│  ├─ DuetWifiServer.bin
├─ gcodes/
├─ macros/
├─ sys/
│  ├─ bed.g
│  ├─ board.txt
│  ├─ config.g
│  ├─ homeall.g
│  ├─ homex.g
│  ├─ homey.g
│  ├─ homez.g
│  ├─ pause.g
│  ├─ resume.g
│  ├─ sleep.g
│  ├─ stop.g
│  ├─ tfree0.g
│  ├─ tpost0.g
│  ├─ tpre0.g
├─ www/
│  ├─ contents of DuetWebControl-SD.zip
firmware.bin

In the above example, the contents of the sys folder have come from the online configurator.

The contents of DuetWebControl-SD.zip should be extracted into the www folder.

Final Setup

Once connected, power up the board using 12-24v and connect to the USB port on the board. Connect to the board using a program such as putty. Follow the instructions here to set it up for RRF. Change the Com port to match the SKR3EZ H743 and connect. The baudrate doesn’t matter.

Tip: I (jay_s_uk) have a very handy little tool installed on my main laptop thats monitoring for any serial devices as they are plugged in and you get a popup with the Com port number. If you’re interested, it can be found here

Flashing the WiFi Firmware

Type in the following to putty

M552 S0
M997 S1

Wait for the uploading of the WiFi firmware to finish.

Sending your WiFi Credentials

Send the following

M552 S0
M587 S"your SSID" P"your password"
M552 S1

Warning: DO NOT USE PRONTERFACE it will convert all text to upper case. If you really must, please do the following.
If you wanted to use “PassWord”, you would write P”P’a’s’sW’o’r’d” with the ‘ indicating the following letter should be lower case. Explanation here.

Important: Both the SSID and Password used to connect to your WiFi are case sensitive.

The blue light on the WiFi chip shoould then flash blue and will go solid when a connection has been established. The ip address will be shown on the serial connection. It is also possible to type just M552 to get the current ip address reported back.

The final thing to do is add the line “M552 S1” to your config file. This can be done through the web interface. This just ensures that the WiFi connection is started at start up. There is no need to add the M587 command as this is written permanently to the flash of the ESP8266 chip.

Once up and running

You will need to PID tune your tools and your bed. Please be aware that bed tuning may take up to an hour and tool tuning normally takes around 15 minutes. If it takes longer, that is also fine as up to 30 cycles may be ran.

To tune the bed, run the following command, changing the temperature (the S value) if a different tuning temperature is required.

M303 H0 S60

To tune each tool, run the following command, changing the temperature (the S value) if a different tuning temperature is required. This proceedure will activate the part cooling fans during the final phase of the tuning process so their effect is taken into account. If your printer has more than one tool, make sure each one of them is tuned.

M303 T0 S220

Once the tuning is complete, either copy the M307 command into the heater definitions or send M500, ensuring you have M501 at the end of your config.g.
If the tuning fails at the end, carry on saving the values as in most cases the outputted values still work correctly.
If the values still result in a heater fault, please refer to this wiki page for information about how to adjust the values manually.

Tags: