Posts made by dakingofhearts2003

@jay_s_uk follow what instructions i set the z height to g92 z0 and it starts at 0.28 which i can find nowhere in my homing files or start script.

@alankilian . I need to know what settings in what section i can use to decrease the space between the hotend and the bed cause that stuff isnt working

I have a qidi tech 1 which is a flashforge clone and the bed moves up not side to side. How do i get the bed closer to the hotend for the starting print height. what sections do i change that in ive been trying to do it through the start script.

G28 ;Home
G29 S1
G1 Z10 F6000 ;Move the platform down 10mm
G92 Z0
G1 X40 Y140 Z0 F9000.000 ; Extruder Prime Dry Move
G1 X250 Y140 Z0 F1800.000 E25.000 ; Extruder Prime Start
G92 E0

@phaedrux You can close this one out but i have another question about how to level the bed manually. I cant use g32 if i dont have multiple z motors can i ?

@phaedrux No, M401 and M402 dont work i have M280 in my retract and deploy folders.

generated by RepRapFirmware Configuration Tool v3.1.1 on Thu Jun 04 2020 14:46:02 GMT-0400 (Eastern Daylight Time)
M280 P7 S10 ; deploy BLTouch

generated by RepRapFirmware Configuration Tool v3.1.1 on Thu Jun 04 2020 14:46:02 GMT-0400 (Eastern Daylight Time)
M280 P7 S90 ; retract BLTouch

@phaedrux said in BL TOUCH ONLY DEPLOYS WHEN I USE THE DEPLOY/RETRACT MACROS...:

M98 P"config.g"

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Pin 'fan1' is not free
Error: Fan number 2 not found
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C

@phaedrux said in BL TOUCH ONLY DEPLOYS WHEN I USE THE DEPLOY/RETRACT MACROS...:

M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS0-6J1FJ-3S46M-KSTRP
Used output buffers: 3 of 24 (10 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73420 of which 48 recycled
Never used RAM 15152, free system stack 191 words
Tasks: NETWORK(ready,162) HEAT(blocked,308) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:41 ago, cause: software
Last software reset at 2021-08-08 21:07, reason: User, GCodes spinning, available RAM 15116, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 24.7, current 25.4, max 25.7
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-08-08 21:08:20
Cache data hit count 48716574
Slowest loop: 7.78ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.0ms, write time 6.2ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.56ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.25
  WiFi MAC address 98:f4:ab:d1:f0:18
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 25360
  WiFi IP address 192.168.0.37
  WiFi signal strength -51dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

BL TOUCH WORKS WHEN I USE THE MACROS BUT WHEN HOMING Z OR TRYING TO SEND G30 COMMANDS IT SAYS "Z PROBE WAS NOT TRIGGERED..

config.g homeall.g homez.g

@phaedrux in the probe section i was trying to diagnose a bl touch not responding issue in the dark i figured i must have put the connector on in reverse because i heard a pop and then no more wifi or usb.

I have a duet wifi and i was having trouble with my bl touch so i unplugged it and it was dark so i plugged the black and wire in reverse and i heard a pop. It will come on and show the green light, the fuses are good, but the usb will only make a sound when connected with vin power, with usb only it does nothing. My wifi module is also not working. I have tools nothing looks burned what should i be looking for ?

@sebkritikel i think im going back i'm just tired of it...

@sebkritikel when i did the extruder calibration it was correct. I did make a start mark on the bed and did a 50mm in the x direction and i measured 42.17. I didnt know i was going to need to be an engineer to change boards and firmware i see why people buy prusas now cause im sick of tinkering and wasting filament...

@sebkritikel i tried the old numbers from the makerbot and used the 80 80 400 standard of marlin. the old makerbot numbers just made it print off the bed and etc. the marlin standard made the parts come out undersized

@3dpmicro 

one comes out the right size on my tevo but the duet board died and before that would always disconnect so im about to throw one of my old boards with marlin on it in it. I'd like to get this one right first though...

@alankilian @alankilian I have the duet wifi and it is a qidi tech 1 which is a flashforge clone. I am using the lastest version of the firmware it always has printed since i configured it but the parts are inaccurate since i changed boards.

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Jul 25 2020 12:56:48 GMT-0400 (Eastern Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Qidi nova" ; set printer name

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S1 ; disable Telnet

; Drives
M564 H0 ; allow not homed axis movement
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X32 Y32 Z32 E32 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z800.00 E909.59 ; set steps per mm
M566 X800.00 Y800.00 Z20.00 E400.00 ; set maximum instantaneous speed changes (mm/min)
M203 X40000.00 Y40000.00 Z200.00 E2200.00 ; set maximum speeds (mm/min)
M201 X4500.00 Y4500.00 Z200.00 E1000.00 ; set accelerations (mm/s^2)
M906 X800 Y700 Z500 E950 I15 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; pressure advance ;set pressure advance for direct drive nova hotend
M572 D0 S0.04

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X225 Y145 Z165 S0 ; set axis maxima

; Endstops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z0 ; configure Z-probe endstop for low end on Z
M558 P9 H5 F500 T4000 X0 Y0 Z1 :set probe type and mode. not using on xy but using it on z axis

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F6000 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P50 X-49.41 Y8.53 Z4.207 ; set Z probe trigger value, offset and trigger height
M557 X10:205 Y10:145 S10 ; define mesh grid

; autosave 911
M911 S21.0 R23.0 P"M913 X0 Y0MG91 M83 G1 Z3 E-5 F1000

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S1 H0:2 ; set fan 1 value. Thermostatic control is turned on
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H0:1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan1" Q500 ; create fan 2 on pin fan1 and set its frequency
M106 P2 S1 H0:1 T45 ; set fan 2 value. Thermostatic control is turned on

; Tools
M563 P0 S"Extruder" D0 H1 F0 ; 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

M501
M500
M564 H0
; Custom settings are not defined

Am i supposed to enable relative extrusion distances in the slicer ? And where do i start to deal with the issue of parts coming out smaller than they are supposed to. I can get them to print well but not dimensionally accurate...

@phaedrux I am having some serious issues that i don't think the retraction will help but i was going to do the retraction tuning anyway. Am i supposed to enable relative extrusion distances in the slicer ? And where do i start to deal with the issue of parts coming out smaller than they are supposed to. I can get them to print well but not dimensionally accurate...

@phaedrux I understand that part. Understanding those macros and how to alter them is what im looking for ...

@phaedrux Can you point me to a thread or an article about how to set up firmware retraction ?

@Phaedrux i'm going to try the negative numbers and see what happens