Posts made by Deanethiro

@dc42 you saved the day again! It was a lose wire crimp that must have come undone over time!

@phaedrux I see no obvious damage on the pin or anywhere else for that matter.

I also ran a test to run the probing routine but pull the pin out manually beforehand it it did not work that way either

@phaedrux I am using a duex5, it is connected with the ribbon cable and running 3 of the Z motors.

When I do the boot up and it self tests it does not flash it stays with the LED on like everything is normal

If I pull out the pin it moves smoothly and the light turns off like it is operating correctly, when I put the pin back the light turns back on

the pin never deployed so damage to the pin seems unlikely through that route

I will disassemble it now and see what I can glean

@phaedrux

It is a BL touch I have been using, it was working just fine before this issue started.

I am using the deployment macros and test macros I am posting below

here is the config file
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M667 S1 ; Select CoreXY mode

; Network
M550 P"Hypercube 25" V1" ; Set machine name
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P1 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M569 P5 S1 ; Drive 5 goes forwards
M569 P6 S1 ; Drive 6 goes forwards
M569 P7 S1 ; Drive 7 goes forwards
M569 P8 S1 ; Drive 8 goes forwards
M569 P9 S1 ; Drive 9 goes forwards
M584 X0 Y1 Z6:7:5:2 ; Z Motor Mapping
M671 X-22.75:670.0:-22.75:670.0 Y500.0:500.0:127.0:127.0 S5. P8.0
M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E145.45:420.00 ; Set steps per mm
M566 X500.00 Y500.00 Z12.00 E120.00:120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z400.00 E1200.00:1200.00 ; Set maximum speeds (mm/min)
M201 X900.00 Y900.00 Z20.00 E250.00:250.00 ; Set accelerations (mm/s^2)
M906 X800.00 Y800.00 Z800.00 E800.00:800.00 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 X625 Y610 Z625 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 S1 ; Set active high endstops

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F600 T8000 X0 Y0 Z1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed the bed moves
G31 P25 X-27.0 Y0.0 Z1.7772 ; Set Z probe trigger value, offset and trigger height
M557 X30:550 Y30:550 S25 ; Define mesh grid

; Heaters
M141 H5 ; Assign chamber heater to heater 0
M307 H6 B0 S1.0 ; Enable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
M305 P2 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 2
M143 H2 S280 ; Set temperature limit for heater 2 to 280C
M305 P5 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 6
M143 H5 S120 ; Set temperature limit for heater 6 to 120C

; Fans
M106 P0 S0 I0 F500 H-1 C"Parts Cooler Fan0" ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 C"Hotend Fan Fan1" ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P3 S255 I0 F500 H-1 C"LED Strip Fan3" ; Set fan 3 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 ; Define tool 1
G10 P1 X25.784 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C

; Automatic saving after power loss is not enabled

; Custom settings are not configured

; Miscellaneous

MACROS

M280 P7 S160 ; Alarm Release and Push-Pin UP

M280 P7 S10 ; Send PWM channel 7 the s10 (angle) command

M280 P7 S90 ; Send PWM channel 7 the S90 (angle) command

M280 P7 S120 ; Send PWM channel 7 the S10 (angle) command

It was working fine and then I went to run a g32 and it didnt deploy the pin so I had to emergency stop it and it has not responded to commands since. I have power cycled it as well and same thing, but it does the self test and appears normal but is entirely unresponsive

Like the title says, my BL touch when the printer is turned on does its self test but then ignores all the commands I try to send to it after that. Anyone have any ideas?

@dc42 Ok I will change that over to right handed and see if that sorts everything out, the "back corner" on the height map shows it as low but the front in actually low and it sounds like the printer is just confused because of all the screwy coordinates

@dc42

Here is what I am talking about

EDIT: forgot to mention on the picture X0 Y0 Z0 is the back left corner but it shows on the back right corner fro the bed mesh

@dc42

My Main issue is that the G32 seems to level it backwards I guess, the front side of the bed is always too low and the back side of the bed is always too high, it is close enough to print stuff but say when I print a benchy, the skirt on the front is almost not wanting to stick and the skirt towards tho back of the printer is almost transpartent because its being squished so much.

I just tried to use G29 height map and it seems to be doing the same thing. I will draw a diagram to explain what I think it happening

@dc42 said in G32 not acting as expected:

Yes, the bug in 4-leadscrew levelling was fixed almost a year ago in firmware version 1.20.

I noticed reading about the M671 command that "For printers that print directly onto a desktop and have levelling feet, this command can be used to define the coordinates of the levelling feet, so that bed probing can be used to calculate and display the adjustments needed to the feet. In this case the displayed corrections must be reversed. For example, "0.2 turn down" means the bed needs to be lowered or the printer raised by 0.2 turn lower at that screw position."

My printer is a Hypercube that has the bed move down in +Z movement do I need to change anything due to that? The height map generated by a g29 seems to be upside down when I tried that so maybe that is the source of my issue?

@dc42

Ok good to know, the number has ALWAYS decreased when I did multiple G32 commands. I will give that F parameter a try and see what that does.

I am using firmware 2.02(RTOS) so It sounds like I am safe from math errors?

@phaedrux Ok so I changed everything and made the probe points closer to the lead screws and it seems to be doing a better job. I am going to run the tests you suggested and report back with those results.

@phaedrux said in G32 not acting as expected:

I assume you're using a BLtouch as your probe. How consistent are the probe results? If the probe isn't consistent that could explain poor leveling results. I notice you're using the older P5 probe type. Consider switching to the dedicated BLTouch probe type P9. You can then also reduce the trigger threshold value in G31 P500 to G31 P25, both of which may help make the BLTouch trigger more responsive.

Great tips I will try all that and report back!

@phaedrux said in G32 not acting as expected:

Using 4 lead screws isn't recommended due to the added potential for binding, which seems possible in this case. What happens if you even them up manually and then run G32? Does it stay level or get worse? What happens if you run G32 a few times in a row, does it improve?

If I run it a few times in a row the deviation number gets lower and lower but it still looks uneven , when I print the side that looks like it is sticking up slightly has a more crushed layer line. I have not tried manually fixing it and running it again but I will try that once this print finishes and report back. If I have to go to three I will but I really liked the idea of 4 points of control

@Phaedrux Yes it does that, is that not okay? I read this and it did not imply that I needed to do it in any sort or order besides the order that the motors were defined. So how should I change this to make it better?

@phaedrux Also ignore the comments on the bed file I never bothered to label them correctly oops that's embarrassing haha

Here they are, also here is my config section dealing with that

M584 X0 Y1 Z6:7:5:2 ; Z Motor Mapping
M671 X-22.0:670.0:-22.75:670.0 Y127.0:127.0:500.0:500.0 S5.

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves
G31 P500 X-27.0 Y0.0 Z2.3117 ; Set Z probe trigger value, offset and trigger height
M557 X30:550 Y30:550 S25 ; Define mesh grid

bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Feb 11 2019 12:17:42 GMT-0500 (Eastern Standard Time)

M561 ; clear any bed transform
G29 S2; Clear bed height map
; Probe 3-point
M401 ; Deploy probe - deployprobe.g
G30 P0 X45.0 Y45.0 Z-9999 ; Front Right
G30 P1 X550.0 Y45.0 Z-9999 ; Front Left
G30 P2 X45.0 Y550.0 Z-9999 ; Front Left
G30 P3 X550.0 Y550.0 Z-9999 S4 ; Center Rear
M402 ; Retract Probe - retractprobe.g

I am setting up the G32 auto level for my Hypercube build and it works pretty good but weirdly it does not level the bed correctly. The back corners are higher up than the front 2 corners and it always repeats that way. I am using 4 separate Z motors and probing 4 points. Another curious thing, whenever I finish a print or do the G32 command it says deviation is about 1.100mm or something like that and "corrects" itself, but from there if I run a print and do it again it is off by about that same amount, anyone have any ideas on that?

Yup there we go turns out I am just stupid thank you so much

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Feb 11 2019 12:17:42 GMT-0500 (Eastern Standard Time)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

M667 S1 ; Select CoreXY mode

; Network
M550 P"Hypercube 25" V1" ; Set machine name
M552 S1 ; Enable network
M587 S"MkMachine2.4" P"9545725995" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M569 P5 S1 ; Drive 5 goes forwards
M569 P6 S1 ; Drive 6 goes forwards
M569 P7 S1 ; Drive 7 goes forwards
M569 P8 S1 ; Drive 8 goes forwards
M569 P9 S1 ; Drive 9 goes forwards
M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z1600.00 E420.00:420.00 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00:120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; Set accelerations (mm/s^2)
M906 X800.00 Y800.00 Z800.00 E800.00:800.00 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 X625 Y625 Z625 S0 ; Set axis maxima

; Endstops
M574 X1 Y2 S1 ; Set active high endstops

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y-25 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:550 Y15:550 S40 ; Define mesh grid

; Heaters
M141 H5 ; Assign chamber heater to heater 0
M307 H6 B0 S1.0 ; Enable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
M305 P2 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 2
M143 H2 S280 ; Set temperature limit for heater 2 to 280C
M305 P5 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 6
M143 H5 S120 ; Set temperature limit for heater 6 to 120C

; Fans
M106 P0 S0 I0 F500 H-1 C"Parts Cooler Fan0" ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 C"Hotend Fan Fan1" ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P3 S255 I0 F500 H-1 C"LED Strip Fan3"

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 ; Define tool 1
G10 P1 X25.784 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C

; Automatic saving after power loss is not enabled

; Custom settings are not configured
M584 X0 Y1 Z6:7:5:2 ; Z Motor Mapping
M671 X-22.0:670.0:-22.75:670.0 Y127.0:127.0:500.0:500.0 S5. P2.

; Miscellaneous

@dc42 said in Board unresponsive:

How did you try to use the stepper drivers on the DueX5?

Here is the M122 results
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MSJ-6JTDJ-3SD6Q-TVN7A
Used output buffers: 3 of 20 (14 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98924 of which 0 recycled
Exception stack ram used: 328
Never used ram: 6296
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:31:47 ago, cause: software
Last software reset at 2019-02-20 10:53, reason: User, spinning module GCodes, available RAM 6296 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 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 32.3, current 33.6, max 33.9
Supply voltage: min 24.3, current 24.4, max 24.6, 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
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2019-02-20 11:24:49
Cache data hit count 4294967295
Slowest loop: 5.27ms; 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 = 5 -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 ===
Slowest loop: 14.07ms; 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 80:7d:3a:3f:f5:90
  WiFi Vcc 3.44, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 15664
  WiFi IP address 10.1.10.178
  WiFi signal strength -35dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

I have 3 of the drivers ( 5 6 7 ) along with 2 as Z motor drivers and I have them mapped but when I try to do any Z moves only drive 2 moved