Connecting an BTT Octopus v1.1 F429 Version via SBC | RepRapFirmware for LPC and STM32

How to connect to an BTT Octopus v1.1 F429 Version via SBC

Overview

The BTT Octopus v1.1 F429 Version is a STM32F407VGT6 based board.

Warning: There have been a small number of users who have been suffering from random disconnects between the board and the SBC during printing. This has been due to the type of communication connection used by the DuetSoftwareFramework on the SBC to talk to the board being affected by electrical noise from either something on the printer or equipment near by.
There are a number of steps that can be done to limit this issue.
1. Keep the wires between the controller and the Pi short
2. Use either a ribbon cable, or if using jumper wires then use ribbon-style jumper wire strips with the individual conductors separate only at the ends
3. Use multiple ground connections between the two
4. Beware of ground loops. Problems are likely if more than one of the the PSU supplying the controller, the PSU supplying the Pi, and any other equipment that the Pi is connected to (other than via Ethernet) has its signal ground connected to the mains ground in the 3-pin plug that supplies the power. RPi PSUs are usually not grounded. ATX PSUs always are. Meanwell-style PSUs have a ground connection, but it is up to you whether you link mains ground to PSU negative output.
In short, these disconnects may happen to you or they may not. If they happen and you are unable to fix them, then the only remaining options are track down the noise by changing components one by one or switch to using WiFi rather than an SBC.
For STM32 based boards, there is little gain from using an SBC at this current time, especially as ESP32 is now available.

Firmware File

Choose the correct corresponding firmware (firmware-stm32f4-sbc.bin) from here. Remember to rename it to firmware.bin. Put it in the root of a FAT32 formatted SD card. The maximum size supported card is 32GB.

SBC

Connecting a Single Board Computer, such as a raspberry pi 3B/3B+/4.

Prepare the Raspberry Pi

Follow the instructions detailed here.

Tip: If you want to use a board other than a Raspberry Pi, please follow the guide here

BOM

5 x 100R resistor
jumpers or other ways of connecting to the BTT Octopus v1.1 F429 Version

Connecting the SBC to the BTT Octopus v1.1 F429 Version

The pinout for the BTT Octopus v1.1 F429 Version can be found here and the schematic for the Duet 3 for reference can be found here. The raspberry pi GPIO pinout can be found here.

The table below shows the pins required on the SBC and what they are connected to on the BTT Octopus v1.1 F429 Version. Please ensure that your cables are no longer than 30cm although they should ideally be as short as possible.

SBC Pin	BTT Octopus v1.1 F429 Version	Resistor Value
23/BCM11/SPI0 Clk	PB_13	100R
21/BCM9/SPI0 Miso	PC_2	100R
19/BCM10/SPI0 Mosi	PC_3	100R
24/BCM8/SPIO CE0	PB_12	100R
22/BCM25	PG_7	100R
20/GND	GND	None

Prepare the SD Card

All the SD card on the BTT Octopus v1.1 F429 Version needs is the board.txt file with the following contents.

//Config for BTT Octopus v1.1 F429 Version
board = biqoctopus_1.1
sbc.TfrReadyPin = PG_7

heat.tempSensePins = { PF_3, PF_4, PF_5, PF_6, PF_7 }
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.

TMC22XX UART Drivers

The drivers must be continuous and start at unit 0 (unless TMC5160 are also used, which case they must be installed after them). So, for the BTT Octopus v1.1 F429 Version, if you have say 3 TMC2208s and 1 other driver, the 2208s must be in slots 0, 1, 2 and the remaining driver in slot 3 or 4. You can use RRF to assign any of those slots to an axis/extruder.

TMC5160 SPI Drivers

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

stepper.num5160Drivers = X
stepper.spiChannel = 0

Where X is the number of TMC5160 drivers fitted. The drivers must be continuous and start at unit 0. So, if you have say 3 TMC5160s and 1 TMC22XX and 1 other driver, the 5160s must be in slots 0, 1, and 2, the TMC22XX in slot 3 and the remaining driver in 4. You can use RRF to assign any of those slots to an axis/extruder.

Sensorless Homing

Supported by only the TMC2209, TMC2226 and TMC5160 If using sensorless homing/stall detection with TMC2209 or TMC2226 the following line must be added to the board.txt file. It is not needed with TMC5160.

stepper.TmcDiagPins = { PG_6, PG_9, PG_10, PG_11, PG_12, PG_13, PG_14, PG_15 }

Please only include the diag pin numbers where you intend to use sensorless homing on that axis.
For example, if you only intend to use sensorless homing/stall detection on driver 0 and driver 1, only include PG_6 and PG_9 in your board.txt file.

For more information about setting up sensorless homing, please read this.

Board.txt Location

Place the board.txt file in a directory called “sys” on the SD card and install the SD card in the BTT Octopus v1.1 F429 Version.

Tip: If you have to make changes to the board.txt going forwards, then you must remove the card from the board and edit it that way. Board.txt is not accessible through DWC.

Finally…

Turn it all on and you should be good to go.

You can either navigate to duet3.local or find the IP address of the rasberry pi using your router. If you don’t have access to that, use something like Fing to scan your network.

Once you’ve connected to the raspberry pi through your router, start to customise your config.g file etc or upload the outputted zip file from the Configurator to the pi using the system tab of DWC.

Important: DWC with load with an error of DCS not started if the board is not connected to the pi. If the board is connected and you still receive that error then there is an issue with your wiring.

Errors

Please report any disconnects on either the forum or discord.

Changing the SBC hostname

This is an optional step if you only have a single duet3 on your network. It is required if you have more than one SBC configured RRF setup (as each setup on a network needs a unique host name) or you just want to change the name from the default “duet3”.

The name of the printer is its hostname on the network, you will need to connect to the SBC over SSH in order to run the Raspberry Pi configuration utility and change the hostname.

Note: you cannot currently use the gcode command M550 to set your printer hostname, as you can when using a WiFi setup

Connect via ssh
At a command prompt type
```
sudo raspi-config
```
Select “System Options” -> Hostname-> “OK”-> and set the new printername/hostname.
Select “Finish” and reboot.

Note: The hostname must confirm to certain limitations to be valid. Valid characters for hostnames are letters from a to z, the digits from 0 to 9, the hyphen (-).

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: