big box madness

magdi

so the x axis is working fine, y axis now doesnt work and same with z
have z is in series with 2 steppers attached.
have just spoken to ooznest and they have said to ask here not really sure what else to say!
here is this badboy,
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSJ-6J1F6-3SN6R-1TRZ9
Used output buffers: 5 of 20 (11 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98580 of which 0 recycled
Exception stack ram used: 272
Never used ram: 6696
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3860) IDLE(ready,200)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:41 ago, cause: software
Last software reset at 2019-02-27 10:25, reason: User, spinning module GCodes, available RAM 6696 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 34.2, current 34.5, max 34.9
Supply voltage: min 24.1, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-02-27 10:29:18
Cache data hit count 842240654
Slowest loop: 2.92ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 14.03ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address cc:50:e3:0d:20:f3
WiFi Vcc 3.31, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 14328
WiFi IP address 192.168.0.31
WiFi signal strength -76dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

magdi

have also tried all the motors on another mother board and they're working fine.
i'm getting errors on both z and y axis saying :
Warning: motor phase A may be disconnected reported by driver(s) 2/1
Warning: motor phase B may be disconnected reported by driver(s) 2/1

sorry for the essays haha

edit: am also getting temperature shutdown error on driver 2 now

dc42

Please post your config.g file.

When you said "have also tried all the motors on another mother board and they're working fine.", was that with the same cables, or different cables?

magdi

@dc42 ; have taken it from the bigbox forum page as the reprap online configuration was also not working.
and yes used the same wires and all.

Configuration file for BigBox 3D printer

; Communication and general
M111 S0 ; Debug off
M550 PBigBox ; Machine name and Netbios name (can be anything you like)
M551 Preprap ; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
;*** Wifi Networking
M552 S1 ; Enable WiFi

M555 P2 ; Set output to look like Marlin
M575 P1 B57600 S1 ; Comms parameters for PanelDue
; Movement section
M569 P0 S1 ; Drive 0 goes forwards (change to S0 to reverse it)
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M574 X1 Y1 Z1.2 S1 ; set endstop configuration (X and Y endstops only, at low end, active high)
M906 X800 Y600 Z800 E600:600 ; Set motor currents (mA)
M201 X800 Y800 Z15 E1000 ; Accelerations (mm/s^2)
M203 X15000 Y15000 Z100 E3600 ; Maximum speeds (mm/min)
M566 X600 Y600 Z30 E20 ; Minimum speeds mm/minute
M208 X300 Y200 Z200 ; set axis maxima (adjust to suit your machine)
M208 X0 Y0 Z-0.2 S1 ; set axis minimum (adjust to make X=0 and Y=0 the edge of the bed)
M92 X160 Y360 Z1600 ; Set axis steps/mm
M92 E417.5:417.5 ; Set extruder steps per mm
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolation

; Z probe section
M558 P1 X0 Y0 Z1 H3 F200 T5000 ; Smart IR Z probe, used for homing Z axis, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
G31 Z1.4 P500 ; Set the probe height and threshold (put your own values here)

; Heater and thermistor section
;*** If you have a Duet board with 1K thermistor series resistors, change R4700 to R1000 to the following M305 commands
M305 P0 T100000 B4388 R4700 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 X200; B4388 R4700 H30 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 X201; H0 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M301 H1 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 0
M301 H2 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 1
M570 S120 ; Increase to allow extra heating time if needed

; Fans
M106 P0 F10 ; Fix for Bigbox Blower
M106 P1 T40 H1
M106 P2 T40 H2

; Tool definition section
M563 P0 D0 H1 ; Define tool 0 to use extruder drive 0 and heater 1
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
;*** If you have a dual-nozzle build, un-comment the following 2 lines
M563 P1 D1 H2 ; Define tool 1
G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures

; Bed probe section (not needed if you use a bed.g file)
;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of your Z probe
M557 P0 X60 Y0 ; Four...
M557 P1 X60 Y165 ; ...probe points...
M557 P2 X200 Y165 ; ...for bed...
M557 P3 X200 Y0 ; ...levelling
;M557 P4 X141 Y82.5 ; 5th probe point for levelling (un-comment this to get a 5th point at the centre of the bed)

; Epilogue
;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here
T0

Veti

@magdi said in big box madness:

M350

why have you got no M350 for Z?

Veti

@magdi said in big box madness:

M92 X160 Y360

also are your steps correct for y?
This if from the github marlin config
define DEFAULT_AXIS_STEPS_PER_UNIT {160,180,1600,417.5} // default steps per unit for Titan BigBox

magdi

@veti cheers for the help, have tried to change it still the same error messages

Warning: motor phase A may be disconnected reported by driver(s) 1
Warning: motor phase B may be disconnected reported by driver(s) 1

dc42

@magdi said in big box madness:

M906 X800 Y600 Z800 E600:600 ; Set motor currents (mA)

I am not familiar with the BigBox, but 600mA for the Y motor current sounds rather low to me. What motors are you using?

magdi

@dc42 have changed to the x axis 800 amount as this works for the X but still no fix

just upped to 1A still no movment of the Y and Z, X still runs though at 1A
motors are 42BYGHM809 Wantai 1.7A

Veti

@magdi said in big box madness:

Warning: motor phase A may be disconnected reported by driver(s) 1
Warning: motor phase B may be disconnected reported by driver(s) 1

Check the cable. if both phases are not connected no wonder that it does not move.

dc42

I suggest you test the motors using G1 S2 moves at low speeds (send G91 first to put axis motion in relative mode).

If you plug the X motor into the Y or Z output, can you get it to move? Power down before connecting or disconnecting motors.

magdi

Right im with you guys. Am now in the process of testing all the wires and getting the stepper sorted will then re-wire and hopefully be sorted.

Cheers for the help will confirm once complete

Phaedrux

@magdi said in big box madness:

M574 X1 Y1 Z1.2 S1 ; set endstop configuration (X and Y endstops only, at low end, active high)

Z1.2? I don't think that's valid.

Ryan Lock

Hi @magdi,

Thanks for posting your config.g file and the model of your motor. You want to see it to no more than 1.45A.

That error normally relates to a wire being disconnected or not properly connected. As DC42 suggested try the known working X-Axis wire with either the Y or Z-Axis motor.

If that fails try plugging the known working X-Axis wire AND motor into the Y-Axis or Z-Axis port.

Best Regards

Ryan Lock

magdi

So I've unplugged every wire on the motherboard, tested everything on another motherboard including all the wires for steppers and the steppers that I've been using. They all work there. Now I plug one motor into the duet (currently working with z motors) and nothing happens. Have tried every combination of pin connection and everything ugh.
I'm just pulling my hair out at this point im so confused.

What have I done wrong?!

dc42

I already made a suggestion to try to pin down the problem, but you appear to have ignored it.

magdi

@dc42 have tried that i get the same error for connection sorry I didn't reply to it so that's with putting the x axis motor on another axis.

I was just doing what you then later said but I tested all the hardware to see if it worked first

magdi

@ryan-lock thanks for the advice. I have tried moving around the x axis motor to other ports, with and without the same wire. And using that working X wire on other motors. Still the same errors unfortunately. Even got some new wires and the same issue

dc42

Let's start with getting the X motor working when it is connected to the Y motor output. Please add the following command to the start of config.g:

M584 X1 Y0

That will swap the X and Y motor outputs over. Also connect the X motor to the Y motor output, and vice versa. Then try moving X and Y again. If the X motor (connected to the Y motor output) moves correctly when you command X movement, but the Y motor (connected to the X motor output) doesn't, then it is a configuration problem. If the X motor stops working but the Y motor starts working, then it is a problem with the Y driver.

magdi

@dc42 said in big box madness:

M584 X1 Y0

right i have tried what you have advised. problem still persists with the Y driver, driving the x axis.