Posts made by Pitsweer

@günter-jibben said in Z hight Issue:

Printbay

Yes I adjusted all those according to my setup. But the way you level each leadscrew works perfect.

@günter-jibben DUDE....Thank you so much. I did everything you said and its working. I can finally have a print start normally

@phaedrux Ok...So the esteps are good...ask for 50mm and get 50mm.

but...checking the Z probe trigger height revealed a problem( I think)
Each corner gives a different value. It varies from 1.71mm to 2.05mm.
that is with the bed at room temp.

@phaedrux nope...problem is still there

@phaedrux Yes I did...but I see now I never used M561 before I did...trying that now to see what happenes

@phaedrux Hi, Sorry for the late responce. Its a new problem since adding the mini IR probe and going to a biggger nozzle.(Need to print faster because we get power cuts 3 times a day)

Does the G90 have to be before or after something in my start gcode?

bed.g

7/13/2022, 7:26:43 AM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
7/13/2022, 7:25:56 AM m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SS-6JTDD-3SN6M-TVU7G
Used output buffers: 3 of 26 (24 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 75656 of which 36 recycled
Never used RAM 12456, free system stack 118 words
Tasks: NETWORK(ready,13.9%,219) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,274) DUEX(notifyWait,0.0%,24) MAIN(running,86.0%,440) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:10:04 ago, cause: power up
Last software reset at 2022-07-10 09:35, reason: User, GCodes spinning, available RAM 12216, slot 1
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
Step timer max interval 0
MCU temperature: min 25.2, current 25.7, max 25.9
Supply voltage: min 12.8, current 12.9, max 12.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2022-07-13 07:25:55
Cache data hit count 4294967295
Slowest loop: 6.16ms; fastest: 0.17ms
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 0.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 585116ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 12, completed 12, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0
=== 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
=== DueX ===
Read count 0, 0.00 reads/min
=== Network ===
Slowest loop: 203.37ms; fastest: 0.08ms
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 1
  WiFi firmware version 1.26
  WiFi MAC address ec:fa:bc:31:72:0f
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 25120
  WiFi IP address 192.168.0.182
  WiFi signal strength -43dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

This gcode was for a 0.3 layer height

config.g
homeall.g
homex.g
homey.g
homez.g

And the first part of the gcode

;FLAVOR:RepRap
;TIME:2739
;Filament used: 7.04348m
;Layer height: 0.3
;MINX:150.051
;MINY:160.801
;MINZ:0.36
;MAXX:219.949
;MAXY:209.2
;MAXZ:30.71
;Generated with Cura_SteamEngine 5.0.0
T0
M190 S100
M104 S245
M109 S245
M82 ;absolute extrusion mode
G32
M82 ;absolute extrusion mode
M107 ;turn off fan
G28 X0 Y0 Z0 ; home X, Y and Z axis end-stops
G29 S1 P"heightmap.csv"
G0 X360 Y0 F4000 ; Go to front
G0 Z0.2 ; Drop to bed
G92 E0 ; zero the extruded length
G1 Y50 E25 F300 ; Extrude 25mm of filament in a 4cm line
G92 E0 ; zero the extruded length
G1 E-1 F500 ; Retract a little
G1 Y150 F6000 ; Quickly wipe away from the filament line
G1 Z0.3 ; Raise and begin printing.
M83 ;relative extrusion mode
M141 S0
M83 ;relative extrusion mode
G1 F1500 E-4.75
;LAYER_COUNT:100
;LAYER:-5
M107
G0 F6000 X150.955 Y162.411 Z0.36
;TYPE:SUPPORT-INTERFACE
G1 F1500 E4.70842
G1 F1350 X150.647 Y162.86 E0.13039
G1 X150.406 Y163.329 E0.12627
G1 X150.227 Y163.828 E0.12695
G1 X150.113 Y164.337 E0.12491
G1 X150.054 Y164.975 E0.15344
G1 X150.051 Y204.872 E9.55425
G1 X150.107 Y205.581 E0.17032
G1 X150.215 Y206.132 E0.13446
G1 X150.39 Y206.629 E0.12618
G1 X150.622 Y207.096 E0.12487
G1 X150.925 Y207.547 E0.13011
G1 X151.273 Y207.947 E0.12697

So I'm using duet 2 wifi with RRF 3.4.1 and duet mini IR probe on coreXY setup.
I've set the Z hight and its fine. When I tell it to go to Z0 it goes to Z0...as it should....however when I start a print it starts probably 2 -3 mm too high even though first layer is set to 0.2 in the slicer.

I've checked and I can not see anything wrong...ANY idea what it could be?

@phaedrux So I got that fixed...just had the pin name wrong. But now I get an error every time I try to heat the chamber.
Error: Heater 2 fault: temperature rising much more slowly than the expected 1.4°C/sec

Hi. So I added a chamber heater. I've set it to use heater 4 on the duex5 and thermistor 4.
the probles is when I set it to heater 4 then heater 3 goes on when I power up the printer and stays on. When I adjust config.g to heater 3 then heater 2 goes on and stays on. and the same goes for every other heater. I'm using RRF3.3

Hi. Is it possible to use Z_PROBE_MOD pin for something else...like sening a pulse to arduino and still use Z_PROBE_IN for the probe signal?

I'm using Duet wifi with RRF 3.x

@dc42 the chip I'm using can do 80hz. Normally they do 10.

Ok so I've got the load cell and all that goes with it. I'll be using the adruino nano to send probing signal to the duet wifi. What I'm not sure about is if I can get 5v from the duet or duex5 so give power to the nano and where to connect what so I can send M42 to zero the load cell beforw every probing sequence. And how do I get the nano to tell the duet that a probe has been done.