@CaLviNx seriously stop commenting. I do beta testing and bug fixing for a living. I took the steps I did for a reason. Everyone else has been trying to help while all you've been doing is throwing jabs in and out of this thread. I don't need you to tell me what the "smart approach" is because "the whole point of the exercise" is to figure out what happened and to see if I could fix it, not applying a band-aid.

@ratrig0331 It tells you what pin on the accelerometer plugs into what pin on the Duet 3 Mini.

@oliof in the end it was solved by reflashing the firmware with bossa. He was using a 10 foot cable. Told him to use a shorter USB cable and it worked.

@Phaedrux Actually I just tried it out and it worked without a hitch. Took probably 5 minutes

So it happened again. I swapped to a Raspberry Pi 4 with new firmware.

11/6/2020, 12:04:08 AM	Cancelled printing file 0:/gcodes/a1.gcode, print time was 0h 20m
11/6/2020, 12:04:08 AM	Warning: Controller has been reset
11/5/2020, 11:48:41 PM	Height map saved to file heightmap.csv
11/5/2020, 11:48:41 PM	16 points probed, min error -0.018, max error 0.070, mean 0.034, deviation 0.027
11/5/2020, 11:48:41 PM	Leadscrew adjustments made: -0.027 -0.025 -0.033, points used 3, (mean, deviation) before (-0.028, 0.003) after (-0.000, 0.000)
11/5/2020, 11:48:41 PM	Leadscrew adjustments made: -0.059 -0.023 -0.016, points used 3, (mean, deviation) before (-0.031, 0.014) after (0.000, 0.000)
11/5/2020, 11:48:41 PM	Leadscrew adjustments made: -0.022 -0.039 -0.054, points used 3, (mean, deviation) before (-0.039, 0.010) after (0.000, 0.000)
11/5/2020, 11:46:07 PM	Height map loaded from file heightmap.csv
11/5/2020, 11:44:01 PM	M32 "0:/gcodes/a1.gcode"
File 0:/gcodes/a1.gcode selected for printing

11/6/2020, 12:12:01 AM	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 163392 of which 64 recycled
Exception stack ram used: 544
Never used ram: 74612
Tasks: ETHERNET(blocked,824) NETWORK(ready,1960) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,60) MAIN(running,2672) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 03:23:27 ago, cause: power up
Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 39.7, current 39.9, max 41.4
Supply voltage: min 24.3, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/160
Driver 1: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/400
Driver 2: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/384
Driver 3: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1023
Driver 4: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1023
Driver 5: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1019
Date/time: 2020-11-06 00:12:00
Slowest loop: 9.38ms; fastest: 0.21ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 322, MaxWait: 302820ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 3599, completed moves: 3599, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.77ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: establishingLink
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages sent 7459, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 8
Last transfer: 19ms ago
RX/TX seq numbers: 2795/56430
SPI underruns 13, overruns 11
Number of disconnects: 3
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.12

DWS2.txt
DCS.txt

You should post this on the Facebook page as their's more users familiar with the BLV Cube and the creator of the sketch is on there as well.

@Phaedrux Thanks!

Do you know if this instructable would work?
How-to-Make-Raspberry-Pi-Webcam-Server-and-Stream

Disconnected panel due

11/6/2020, 5:23:22 PM	Connection established
11/6/2020, 5:21:46 PM	Connection interrupted, attempting to reconnect...
DCS has been stopped
11/6/2020, 5:21:16 PM	Cancelled printing file 0:/gcodes/a1.gcode, print time was 0h 19m
11/6/2020, 5:21:15 PM	Warning: Controller has been reset
11/6/2020, 5:06:52 PM	Height map saved to file heightmap.csv

11/6/2020, 5:23:59 PM	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 163392 of which 140 recycled
Exception stack ram used: 544
Never used ram: 74536
Tasks: ETHERNET(blocked,832) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1384) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2672) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 03:50:47 ago, cause: power up
Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 39.5, current 39.8, max 40.3
Supply voltage: min 24.3, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Driver 0: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/1023
Driver 1: standstill, reads 32787, writes 8 timeouts 0, SG min/max 0/226
Driver 2: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/1023
Driver 3: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/179
Driver 4: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/175
Driver 5: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/127
Date/time: 2020-11-06 17:23:58
Slowest loop: 9.29ms; fastest: 0.21ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 323, MaxWait: 541330ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 3364, completed moves: 3364, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.76ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: establishingLink
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages sent 5531, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 22
Last transfer: 20ms ago
RX/TX seq numbers: 1766/48405
SPI underruns 38, overruns 14
Number of disconnects: 2
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.03

11/6/2020, 5:24:21 PM	M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 351C

DWS3.txt
DCS3.txt

I connected the 2 ground wires together and it's been fine

I haven't loaded my config file but I flashed Duet3Firmware_MB6HC.bin through Bossa. It looks like it's communicating with the RPI again.

M122

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 161360 of which 20 recycled
Exception stack ram used: 236
Never used ram: 76996
Tasks: NETWORK(ready,1980) HEAT(blocked,1452) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(suspended,252) MAIN(running,5184) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:09:59 ago, cause: power up
Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 15.0, current 25.8, max 25.9
Supply voltage: min 0.2, current 0.3, max 0.3, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 0.1, current 0.1, max 0.2, under voltage events: 0
Driver 0: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 1: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 2: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 3: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 4: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Date/time: 2020-11-08 14:26:06
Slowest loop: 2.36ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.03ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 0, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 12ms ago
RX/TX seq numbers: 19460/19461
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 5.64

M122 DSF

m122 DSF
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 161360 of which 20 recycled
Exception stack ram used: 236
Never used ram: 76996
Tasks: NETWORK(ready,1980) HEAT(blocked,1452) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(suspended,252) MAIN(running,4512) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:12:41 ago, cause: power up
Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 25.6, current 25.8, max 26.0
Supply voltage: min 0.3, current 0.3, max 0.3, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 0.1, current 0.2, max 0.2, under voltage events: 0
Driver 0: ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 1: ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 2: ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 3: ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 4: ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max not available
Date/time: 2020-11-08 14:28:49
Slowest loop: 1.97ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122 D0 S0 F0" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.03ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 0, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 12ms ago
RX/TX seq numbers: 24793/24794
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.80

I have a duet 3 mini running my cnc controlling DWC with my tablet. I use a digital edge finder to find 0,0 of my workspace. Occasionally while dialing in 0,0 instead of hitting .05, .5 gets hit moving the axis too far.

I'm wondering if there's a way to use a toggle switch connected to one of the open input pins as a trigger that could override the axis movements to make sure it doesn't move over .05mm each time a move button is pressed.

@droftarts Genius. That fixed the problem. Thanks!

Setting up my Duet 3 Mini 5+ with RRF 3.5.4, DWC 3.5.4 and Wi-Fi server 2.2.0, no SBC. I'm sure something is wrong with the config but I'm not sure what.

I receive the following error:

M98 P"config.g"
Error: exactly one of EFHJPSR must be given
Error: unconfigured spindle
Error: in file macro line 52: M568: Invalid tool number

I used the configurator to build the config file.

; Configuration file for Duet WiFi (firmware version 3.4.6)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.4.6 on Wed Oct 10 2023 (Central Standard Time)

; General preferences
M552 S1                                     ; enable wifi
G90                                         ; send absolute coordinates...
M83                                         ; ...but relative extruder moves
M550 P"CNC"                                 ; set printer name

; Kinematics
M669 K0                                     ; configure Cartesian kinematics

; Drives
M569 P0.0 S0                          		; physical drive 0.0 goes forwards
M569 P0.1 S0                          		; physical drive 0.1 goes forwards
M569 P0.2 S0                          		; physical drive 0.2 goes forwards
M584 X0 Y1 Z2                               ; set drive mapping

M350 X16 Y16 Z16 I1               	    	; configure microstepping with interpolation
M92 X800.00 Y800.00 Z800.00         	    ; set steps per mm
M566 X300.00 Y300.00 Z300.00                ; set maximum instantaneous speed changes (mm/min)
M203 X3000.00 Y3000.00 Z3000.00             ; set maximum speeds (mm/min)
M201 X150.00 Y150.00 Z150.00                ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 I30                  ; set motor currents (mA) and motor idle factor in per cent
M84 S30                               	    ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                        	; set axis minima
M208 X289 Y183 Z56 S0                       ; set axis maxima

; Endstops
M574 X2 S1 P"0.io5.in"                       ; configure active-high endstop for low end on X via pin
M574 Y1 S1 P"0.io6.in"                       ; configure active-high endstop for low end on Y via pin
M574 Z2 S1 P"!0.io4.in"                       ; configure active-high endstop for high end on Z via pin

; Heated beds
M140 P0 H0                                  ; configure heated bed #0

; Spindles
M950 C"io1.out+io2.out" Q500 L60:12000 ; configure spindle #0

; Tools
M563 P0 H1 R0                       ; create tool #0
M568 P0 R0 S0                          ; set initial tool #0 active and standby temperatures to 0C

; Miscellaneous
M453                                        ; configure CNC mode
T0                                          ; select first tool

; Custom settings are not defined

@Phaedrux Sunday afternoona

I've been trying to get a Bluetooth controller connected the my RPI 4 in SBC mode controlling my Duet 3. It occurred to me it might be disabled. When I go to the Bluetooth Manager I receive the error:

I'm not sure what I'm missing but I've already update the pi and the firmware.

I know there are other slicers that have different features that may or may not be better than S3D. I've tried other slicers and I don't like them. I've used S3D for years and there's no reason for me to switch.

@dc42 With post processing scripts you can still use G10/G11. I set mine up like this

{REPLACE "G1 E-0.5000 F4500\n" "G10\n"}
{REPLACE "G1 E0.0000 F4500\n" "G11\n"}

@chrishamm Wow really? You'd think it would be... Thanks for letting me know.

S3D has a feature where you can send the file and start printing after you slice it but I'm having issues getting it connected.

This is the instructions on the page:

Most network-enabled 3D printers support auto-discovery, meaning that the software can automatically detect the printer on the network and determine the appropriate connection details. To test this process, go to Tools > Machine Control Panel within Simplify3D and click “Add New” to launch the New Connection Wizard. Select the “Network Connection” protocol, choose the “Search for Connections” option, and then click “Search for Devices” to begin the auto-discovery process. Note that this process will only work if your firewall and network rules allow UDP traffic back between the printer and your computer. In many cases, you will need to add a firewall exception to allow Simplify3D to detect the 3D printer.

If the software cannot find your 3D printer, you can still enter the connection details manually. Select the “Manual Connection Details” option and then enter the IP address for your 3D printer. This information can typically be found using the LCD screen on the 3D printer to browse to the info or network status page. The software can typically select the correct port automatically based on your printer profile, but you can also enter the port number manually if needed. Common port values used by different manufacturers are listed below:

FlashForge: port 8899
Ultimaker: port 80
MakerBot: port 9999
Dremel: port 80
Qidi Technology: port 3000
XYZprinting: port 9100
Once you have entered the correct details, you can click Next and press “Begin Connection Test” to establish a connection with the printer. If the software fails to connect, it typically means that the firewall or network settings are still blocking the connection. Make sure a firewall exception has been properly configured and consult your network IT manager to make sure traffic between the printer and your computer is permitted. Once a connection is successfully established, Simplify3D will automatically save the correct settings for the future, so you only need to perform this setup process once.

While trying to connect I enter my printers IP and for port number I select automatic but it fails.

@jay_s_uk Go figure I completely forgot to change that. That worked thanks.