This is the author of Quick Code script,

I sent you a message on the contact form of fixitus.com, not sure if you received it.

Can we have a chat on whatsapp: https://wa.me/971547854069 

All the best to you!

1. Accessing RouterOS

• Web Interface: Open a web browser and enter the router's IP address to access the web configuration interface.
• Winbox: Use the Winbox utility if you prefer a Windows application for configuration.
• Command Line Interface (CLI): SSH into the router using a terminal for more granular control.

1. Basic Network Configuration

• Interface Management: Ensure all physical and virtual interfaces are recognized and named according to your setup.
• IP Addressing: Assign IP addresses to the router interfaces, such as eth1, eth2, etc., either manually or using DHCP.
• Routing: Configure static routes or enable dynamic routing protocols like OSPF, BGP if needed.

1. Firewall Setup

• Firewall Rules: Define rules based on your security policy, determining what traffic can enter or leave the network.
• NAT: Network Address Translation, useful for sharing a public IP address among internal devices.

1. Wireless Configuration (if applicable)

• SSID Setup: Configure the wireless network name (SSID) and security protocols (WPA2, WPA3).
• Frequency and Channels: Choose the appropriate frequency band (2.4GHz or 5GHz) and channel to minimize interference.

1. VPN Setup

• VPN Protocols: Decide on VPN types like PPTP, L2TP, or OpenVPN depending on your needs.
• VPN Users and Permissions: Define access levels for different users.

1. Monitoring and Logging

• Resource Monitoring: Use built-in monitoring tools to keep track of bandwidth usage and performance.
• Logging: Set up logging to capture important events and troubleshoot issues.

1. User Management

• User Accounts: Create or alter user accounts with specific access rights.
• SSH Keys: For secure access, consider using SSH keys instead of passwords.

On a Voron 2.4 with a Duet 3 6HC, the motors are typically mapped as follows. Since the 6HC has six integrated stepper drivers (Driver 0–5), here's the recommended motor-to-driver mapping, assuming you're using the Stealthburner or Afterburner toolhead with coreXY kinematics:
🔧 Motor Numbering (Voron 2.4) and Duet 3 6HC Driver Mapping
Motor Function Voron Name Duet 3 6HC Driver Notes
X Motor X Driver 0 Part of CoreXY system
Y Motor Y Driver 1 Part of CoreXY system
Z Motor (Front Left) Z1 Driver 2
Z Motor (Front Right) Z2 Driver 3
Z Motor (Rear Center) Z3 Driver 4
Extruder Motor E0 Driver 5 Orbiter, LGX, etc.
🔌 Duet Wiring Notes:

The order of Z motors doesn’t matter for physical connection, but you must define them properly in firmware for bed leveling and Z tilt correction.

You may optionally add a toolboard or expansion board for a second extruder or other devices.

🧱 RepRapFirmware config.g Snippet:

; Motor remapping for CoreXY
M584 X0 Y1 Z2:3:4 E5 ; 

Driver 0=X, 1=Y, 2/3/4=Z, 5=Extruder
M671 X-10:310:150 Y10:10:345 S10 ; Z screw coordinates for bed leveling (adjust as needed)

M584 maps the drivers.

M671 defines physical Z lead screw locations for G32 Z-tilt correction.

Let me know if you're using CAN toolboards, expansion boards (like 3HC), or independent Z motors with sensorless homing—those details can change your configuration.
You said:

ok im going to have to deep dive this, mine is wired different but it works and was working great until the right rear z motor error-ed for phase short. the motor would just quit. so i replaced the motor and it still happened on occasion, so i replaced the duet3 6hc and it's happening again. this has a 1lc tool board if that makes any differance. it has to have a config error or software issue. I will identify the driver numbers and their location on the duet 6hc and verify which driver is driving which motor then provide this with the config file to see if i can sort this out

Chat said:

That’s the right approach — if the problem persists across two different 6HC boards and a new motor, it’s almost certainly a wiring issue, driver misassignment, or software/configuration bug.

Once you:

Identify each motor’s physical connection and its corresponding driver (0–5),

Provide your current config.g (and optionally config-override.g if it's in use),

…I’ll walk through the setup and pinpoint any mismatches or conditions that could be triggering false shorts or misbehavior.

Also helpful: are you using shielded motor cables, and are the wires crimped cleanly with no exposed strands near connectors? Duet boards are very sensitive to noise and intermittent connections.
You said:
orignally i thought it was a cable issue and it appeared to be , i installed a new motor that had wires coming out of the motor, steppersonline , they are 4 single wires and i dont believe shielding is present

Chat said:

Thanks — that detail matters a lot.

Unshielded stepper wires (especially long ones or wires running near other high-current lines) can definitely cause:

false phase errors

driver overheating

intermittent shutdowns, especially during fast moves or Z-lift

Here’s what’s likely happening:

Duet 3's TMC5160 drivers constantly monitor coil current balance.

If signal noise or poor continuity causes an imbalance between A and B coils, it throws a “phase short” error even when there's no real short.

Having 4 unshielded individual wires (instead of a twisted pair or proper shielded cable) amplifies this effect — especially on the Z axis where all motors share motion and are often driven at lower current.

✅ Recommended Fixes (Immediate and Long-Term)
Short Term:

Reduce Z motor current slightly (e.g., from 1000mA to 800mA) in config.g using:

M906 Z800

That can reduce stress on detection circuitry.

Tighten acceleration & jerk on Z:

M566 Z4 ; Jerk in mm/min (default often too high)
M203 Z300 ; Max speed
M201 Z20 ; Acceleration

Try a different driver port temporarily (e.g., move that motor to Driver 5 or external board) to rule out driver-specific faults.

Long Term:

✅ Replace with shielded, twisted pair cable (24 AWG or thicker), or buy stepper wire specifically made for 3D printers.

✅ Use crimped JST VH or Molex connectors — don’t just twist and tape. Duet boards are very unforgiving about clean power signal integrity.

Once you ID the driver/motor assignment and share config.g, I’ll help cross-reference any logical mismatches or electrical stressors in the current setup.
You said:
this is the driver wiring driver 0 = z3, drv 1 = B, drv 2 = A, drv3 z0, drv 4 = z1, driver 5=z2

this is the sys.cfg
; Configuration file for RepRapFirmware on Duet 3 Main Board 6HC
; Executed by the firmware on start-up
;
; Generated by RepRapFirmware Configuration Tool v3.5.4 on Wed Jul 24 2024

; General
G90 ; Absolute positioning
M83 ; Relative extruder moves
M550 P"Duet 3" ; Set hostname

; Kinematics
M669 K1 ; Configure CoreXy kinematics
; Network
M552 P0.0.0.0 S1 ; configure Ethernet adapter
M586 P0 S1 ; configure HTTP

; Wait for CAN expansion boards
G4 S2

; Accelerometers
M955 P121.0 I20 ; Configure accelerometer on board #121

; ==================================
; DRIVERS
; ==================================
M584 X4 Y5 Z0:1:2:3 E121.0 ; Set drive mapping
M569 P0.0 S0 D3 ; Z0 Front Left
M569 P0.1 S1 D3 ; Z1 Rear Left
M569 P0.2 S0 D3 ; Z2 Rear Right
M569 P0.3 S1 D3 ; Z3 Front Right
M569 P0.4 S0 D2 ; X (B Motor)
M569 P0.5 S0 D2 ; Y (A Motor)
M569 P121.0 S0 ; Extruder motor (Toolboard 121)

M671 X400:400:-55:-55 Y340:-90:-90:340 ; Define Z belt locations
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E708.00 ; Half the X/Y steps
;M92 X160.00 Y160.00 Z400.00 E708.00 ; Steps per mm
M906 X1200 Y1200 Z1000 E550 I50 ; Motor currents (mA)
M84 S30 ; Idle timeout

; ==================================
; SPEEDS
; ==================================
M566 X450 Y450 Z250 E300 ; Set jerk (mm/min)
M203 X18000 Y18000 Z2400 E7200 ; Max speeds (mm/min)
M201 X8000 Y8000 Z350 E2000 ; Max accelerations (mm/s^2)
M204 P4000 T6000 ; Printing & travel acceleration

; ==================================
; AXIS LIMITS
; ==================================
M208 X0 Y0 Z0 S1 ; Set axis minima (home position at 0,0)
M208 X350 Y350 Z300 S0 ; Set axis maxima (full bed size)


;M208 X0 Y0 Z0 S1 ; Set axis minima
;M208 X0:349 Y0:350 Z0:300 ; Set axis min:max

; Extruders
M584 E121.0 ; Set extruder mapping
M906 E700 ; Extruder current
M92 E735 ; Steps per mm
M566 E120 ; Max instantaneous speed changes
M203 E3600 ; Max speed
M201 E250 ; Acceleration
M200 D1.75 S1 ; Volumetric flow

; ==================================
; Z-PROBE
; ==================================

M558 P8 C"!121.io2.in" H5 F600 T6000 ; Faster probe speed (more practical for daily use)
;M558 P8 C"!121.io2.in" H5 F120 T6000 ; Z probe configuration
G31 P500 X-25 Y-10 Z.07 ; Adjust offsets (X, Y for position, Z for trigger height)
M557 X0:325 Y10:340 P5 ; Adjust for probe offset and bed limits
;M557 X20:330 Y20:330 P7
;M557 X10:330 Y80:430 P5

;G31 P500 X0 Y0 Z0.7 ; Probe trigger value and offset
;M557 X10:330 Y80:430 P5 ; Mesh grid probe points

; Endstops
M574 X1 S1 P"121.io0.in" ; X endstop
M574 Y1 S1 P"io3.in" ; Y endstop
M574 Z1 S2 ; Z-probe used as endstop

; ==================================
; SENSORS
; ==================================
M308 S0 P"temp1" Y"thermistor" A"Heated Bed"
M308 S1 P"121.temp1" Y"pt1000" A"Nozzle"

; ==================================
; HEATERS
; ==================================
M950 H1 C"121.out0" T1
M307 H1 R2.43 D5.5 E1.35 K0.56 B0

; Bed Heater
M950 H0 C"out9" T0 Q10
M307 H0 R0.639 K0.863:0.000 D5.22 E1.35 S1.00 B0
M140 H0
;M143 H0 S80
M143 H0 S120 ; Allow bed to go up to 120C for ABS

; ==================================
; FANS
; ==================================
M950 F0 C"121.out2" Q500
M106 P0 S1 H-1 ; Part cooling fan
M950 F1 C"121.io1" Q500
M106 P1 S1 H1 T45 ; Hotend fan (thermostatic control)

; ==================================
; TOOLS
; ==================================
M563 P0 S"Rapido" D0 H1 F0 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Tool offsets
G10 P0 R0 S0 ; Initial tool temp

; ==================================
; MISCELLANEOUS
; ==================================
M572 D0 S0.065 ; Pressure advance
M593 P"mzv" F41 S0.1 ; Input shaping
T0 ; Select Tool 0
M501 ; Load saved parameters
ChatGPT said:



┌───────────────────────┐
│ DRIVER 3 (Z2?) │ ◄ Top Left corner driver
│ DRIVER 4 │
│ DRIVER 5 │ ◄ Bottom Left
│ DRIVER 2 │ ◄ Middle column, top
│ DRIVER 1 │
│ DRIVER 0 │ ◄ Bottom left-most
└───────────────────────┘

You said:
time to re calibrate our sensors. i was looking at the duet upside down. human mistake
drivers in order
0 = z0
1 = z1
2 = z2
3 = z3
4 = B
5 = A
ChatGPT said:

Perfect — thanks for the reset. Let’s wipe the slate clean and rebuild from your correct physical wiring.
✅ Confirmed Driver-to-Motor Mapping (with Duet 6HC held correctly)
Driver Connected Motor Function
Driver 0 Z0 Front Left Z
Driver 1 Z1 Rear Left Z
Driver 2 Z2 Rear Right Z ✅ ← (this is your problem motor)
Driver 3 Z3 Front Right Z
Driver 4 B motor X axis (CoreXY)
Driver 5 A motor Y axis (CoreXY)
🧠 Now Your M584 Should Be:

M584 X4 Y5 Z0:1:2:3 E121.0

Which is exactly what you're currently using. ✅

So:

Physical wiring = ✅ correct

Driver assignments in config = ✅ correct

This confirms: your repeated Z2 (rear right) error is not a config mismatch, it's a hardware-layer issue (likely EMI or contact failure).
✅ Action Plan from Here

Since config and driver mapping are valid, here’s what will actually fix it:
🧪 1. Run M122 after error

Look at the last section:

Driver 2: ...

It will say:

short-to-ground

open-load

or show driver status flags (hiccups, stst, drverr, etc.)

🧰 2. Fix Physical Layer

Twist wires tightly if unshielded, or replace with shielded 4-wire cable (24 AWG or better)

Make sure all 4 crimps are solid and inserted fully into connectors (Duet is very picky about connector integrity)

Check that wires don’t run directly beside heater/bed power or motor cables without spacing

🔧 3. (Optional) Lower Motor Current Temporarily

To reduce false trips during tests:

M906 Z800

🛠️ 4. Reduce Z Axis Jerk and Acceleration

M566 Z100
M201 Z100

Let me know if you'd like a config snippet with lower Z acceleration/current for testing — or if you want help reading the M122 fault output. You're in the home stretch now.
You said:
here is my cura settings, i'm using .4 nozzle
ChatGPT said:

Great — thanks for sharing your Cura machine settings. This helps verify whether your slicer is aligned with your RepRapFirmware Voron 2.4 setup.

Here’s a quick audit based on what I see:
✅ Cura Machine Settings Review
🔧 Printer Dimensions
Setting Value Comment
X, Y, Z 350 mm ✅ Matches Voron 2.4 350 spec
Build plate Rectangular ✅
Heated bed ✅ Enabled ✅
Origin at center ❌ Off ✅ — Voron does not use center origin
G-code flavor RepRap ✅ Correct for RRF / Duet
🧠 Toolhead Offsets (Printhead Settings)
Axis Min Max Meaning
X -35 35 Head moves 35mm left of nozzle center, 35mm right — width = 70mm
Y -50 65 Head moves 50mm back, 65mm forward — depth = 115mm
Gantry Height 30 mm ✅ Typical Voron value

These offsets are important for proper purge line placement and nozzle clearance during skirt/brim.

So far, this all looks good.
🔎 Two Tweaks You Might Consider
1. 🔁 Start G-code: Add homing and purge line

Right now, your start G-code is minimal. Here's a more complete, Voron-friendly start sequence for Cura:

G90 ; Absolute positioning
M83 ; Relative extrusion
G28 ; Home all axes
G32 ; Bed level / quad gantry align (if configured)
G92 E0 ; Reset extruder
G1 Z0.3 F6000 ; Lift nozzle
G1 X5 Y5 F10000 ; Move to corner
G1 Z0.2 F300 ; Lower to purge height
G1 X100 E10 F1000 ; Purge line
G92 E0 ; Reset extruder again

You can append this after Cura's generated temperature lines.
2. 🧪 Cura Z Offset

If you're using a Z offset in your firmware (G31 Z...), you don’t need to adjust Z height in Cura.

Leave “Build Plate Adhesion Z Offset” at 0 in Cura

Let firmware handle Z probing and offsets

✅ You're Good To Slice

You’re on track — with the .4mm nozzle, RepRap flavor, and correct bed size, you're ready to start printing (once we finish fixing that Z2 motor issue).

Let me know if you'd like optimized Cura start + end G-code blocks tailored for your Duet 3 + Voron setup.
You said:
start + end G-code blocks tailored for your Duet 3 + Voron setup. also i have tap its ChaoticLab CNC Voron Tap V2
ChatGPT said:

Perfect — since you're using a Voron 2.4 350 with Duet 3 + RepRapFirmware, and have the ChaoticLab CNC Tap V2, here are fully optimized Cura Start and End G-code blocks tailored for your setup.
🧩 Key Assumptions:

You're using G32 for quad gantry leveling with TAP

You're using G29 optionally for mesh compensation

Your TAP is already configured in config.g with M558, G31, etc.

Your Duet is set to handle all Z offsets, so Cura doesn't need to

🟢 Start G-code

; --- START GCODE FOR VORON 2.4 + TAP on Duet 3 ---
G90 ; Absolute positioning
M83 ; Relative extrusion
M106 S0 ; Ensure fan is off
G92 E0 ; Reset extruder
M190 S{material_bed_temperature_layer_0} ; Wait for bed temp
M109 S{material_print_temperature_layer_0} ; Wait for hotend temp

G28 ; Home all axes
G32 ; Quad gantry leveling (Z tilt)
;G29 ; Optional: uncomment to probe mesh

G92 E0 ; Reset extruder again
G1 Z0.2 F300 ; Drop to purge height
G1 X5 Y5 F6000 ; Move to front corner
G1 X150 E15 F1000 ; Purge line across front
G1 E-0.8 F3000 ; Retract a little
G1 Z2 F300 ; Raise head
G92 E0 ; Reset extrusion distance

🔴 End G-code

; --- END GCODE FOR VORON 2.4 + Duet ---
G91 ; Relative positioning
G1 E-2 F300 ; Retract a little more
G1 Z5 F300 ; Lift nozzle
G90 ; Absolute positioning
G1 X0 Y350 F6000 ; Park head at back-left
M106 S0 ; Fan off
M104 S0 ; Hotend off
M140 S0 ; Bed off
M84 ; Disable steppers

💡 Optional Notes:

If you don’t want to probe mesh every time, just use G32 for fast quad gantry alignment.

If you're using input shaping or pressure advance (M593, M572), you can handle those in config.g, not Cura.

You can add M564 H0 at the start if you want to allow movement before homing (usually not needed).