I need some help!

[Phaedrux]

Your Z home file is setup to work as though you have a Z Probe.

Comment out the G30 probe bed command and replace it with

G91 ; relative movement
G1 S1 Z-400 F600 ; Move Z axis to endstop

Again, all of these details are in the cartesian printer setup guide.

[cyoung]

@phaedrux said in I need some help!:

Your Z home file is setup to work as though you have a Z Probe.

Comment out the G30 probe bed command and replace it with

G91 ; relative movement
G1 S1 Z-400 F600 ; Move Z axis to endstop

Again, all of these details are in the cartesian printer setup guide.

Sorry, not trying to waste your time, but I havent been able to read the guides and get through this.

I did this, no help. I am reading through the cartesian setup guide more carefully. My main config file matches what the setup guide says for the general preference and for the movement section.

When I try to home y or z, i get movement out of both steppers! (stuttering)

[cyoung]

I just checked the wire pairs on the steppers and as far as I can tell, they are correct.

[Phaedrux]

No worries, I don't mind helping to solve problems, but a lot of the basic setup is covered in the documentation far better than I can describe.

After you've made the motors stutter, run an M122 command in the console and paste the contents here.

[dc42]

1. Panel Due running but not connecting. The usual causes are:

• bad connection in the Din or Dout wire of the 4-pin cable
• Din and Dout wires swapped
• mismatched baud rates. Both default to 57600 but both can be changed.

2. Stepper motors not moving. Usual causes:

• Bad crimp connection between the cable and the connector.
• unsuitable current setting. Please provide a link to the datasheet for your stepper motors.
• trying to move the motor too fast or accelerate it too fast. Use low M201 and M203 parameters until your printer is working.
• Wires not paired correctly into phases. In this case the motor will vibrate loudly.
• blown driver.

[cyoung]

@phaedrux said in I need some help!:

No worries, I don't mind helping to solve problems, but a lot of the basic setup is covered in the documentation far better than I can describe.

After you've made the motors stutter, run an M122 command in the console and paste the contents here.

M122
=== Diagnostics ===
Used output buffers: 3 of 32 (10 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3SN6L-T2ZMY
Static ram used: 21176
Dynamic ram used: 95928
Recycled dynamic ram: 1680
Stack ram used: 1304 current, 4840 maximum
Never used ram: 7448
Last reset 00:00:18 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7448 bytes (slot 2)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 25.2, current 29.2, max 29.4
Supply voltage: min 24.0, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2018-07-08 15:31:31
Slowest main loop (seconds): 0.008299; fastest: 0.000034
=== Move ===
MaxReps: 0, StepErrors: 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 heater = 0, chamber heater = -1
=== 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 state is running
WiFi module is connected to access point
WiFi firmware version 1.19
WiFi MAC address 5c:cf:7f:a4:a2:4c
WiFi Vcc 3.13, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39360
WiFi IP address 192.168.2.114
WiFi signal strength -76dBm
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

[cyoung]

@dc42 said in I need some help!:

unsuitable current setting. Please provide a link to the datasheet for your stepper motors.

I dont have a data sheet handy. The steppers came with a folgertech printer kit. I've looked at their website but cant find any technical info on the steppers. There is a no part number on the motor. I could try to email them and get a data sheet.

[dc42]

My understanding is that Folgertech used 12V 0.4A motors on their early kits. That was a terrible choice and if you have those motors, your best bet is to replace them. You could try reducing the motor current to 400mA in case that improves things.

In later kits, I understand they supplied more suitable motors for 3D printer use.

[cyoung]

I have 2 steppers motors for the y axis, they are wired to each other and plugged into the y driver on the board.

I'm not sure this wire is assembled correctly. On y stepper 1, paired wires 1a and 1b dont connect to 1a and 1b on y stepper 2.

This is what the wiring looks like for the y steppers.

Before I added the duet hardware, I was running an MKS board with Marlin on it and the printer worked correctly. All of the wiring and other components that arent Duet are reused from the MKS setup. I had to swap some pins on the e-stop connectors but everything else (wiring wise) is unchanged.

[cyoung]

@dc42 said in I need some help!:

My understanding is that Folgertech used 12V 0.4A motors on their early kits. That was a terrible choice and if you have those motors, your best bet is to replace them. You could try reducing the motor current to 400mA in case that improves things.

On the stepper motor, it says "1.8deg 5.0kg/cm 1.5A"

Ill try lowering the current and see what happens.

[dc42]

If they are rated at 1.5A then they should be ok.

[cyoung]

So I got the paneldue to work. There was a bad crimp on one of the pins in the plug. So at least one issue is sorted. Still havent been able to figure anything out with getting the steppers to work the right way.

[dc42]

The X and Z motor issues are probably also caused by bad crimp connections, if the motors really are rated at 1.5A and you have set the steps/mm about right. The error message when you command Y movement suggests a short in the wiring or a faulty driver.

[cyoung]

So worked on the printer some more yesterday. I took one of the legs off the 2 stepper motor wiring harnesss for the y axis. Used this harness (with a junction block in the middle) and the motor works correctly! I can plug any stepper into any axis on the board and, as long as i use this specific wiring harness, the stepper works as expected. I tried a few other things and I am now under the impression that I need to rewire the steppers. We tested the "bad wires" every way we could with a multi-meter. Conductivty, resistance, cross-talk/shorts....we couldnt find anything wrong with the bad wires. Not sure what that means but Im thinking Ill try rewiring and see how that turns out.

Even the Y axis works in this setup so I'm hopeful that I dont have a blown driver.