RRF 3 Z home not triggering.
-
@jay_s_uk this is a certain possibility. the way my gantry works is the lead screws are embeded into the x gantry, there is a clamp that holds the switches onto the underside of the gantry which is clamped onto the lead screws.
so to adjust them would put the entire weight of the gantry on one little screw which would move in the long run
-
-
First I wonder why you have three cables at your endstops, because my are looking the same and two cables are sufficient: using left and right means closed when not active and they open when endstop is triggered.
I would expect some pressure between left and right, so if you change direction of one Z side, it will stuck at the trapezoid spindle. First test would be to let fixed the spindle and the linear guide on one side (let's say it is left), but loose the other (right) side a bit (trapezoid screw and linear guide) (like a fixed bearing and a loose bearing at CNC machines for installing ball bearings). So the right side can move a bit horizontally if necessary.
-
@JoergS5 i just soldered on ones for the no, nc and common because i didnt want to have to dissasemble them to solder them if i ever needed to in the future, both of the NO contacts are disconnected underneith
-
@joehsmash ok I understand and it's ok of course.
-
@JoergS5 the construction of the lead screws are integrated into the stepper, so theres no adjustments that can be made.
i can how ever manually adjust where the screw lays on the endstop clamp but for reasons i have posted before i wouldnt put all that pressure onto the one little tiny screw.
-
And I cannot see exactly that this green connector is and how it is connected to the stepper, can you make a close picture of it please?
-
@JoergS5 the green your looking at it just tape, so i can visualize if each of the stepper is moving.
i use it to verify if the mesh is working or not.
-
-
So the trapezoid spindle is directly inside the stepper? Or is there a coupler between?
-
@JoergS5 these are integrated lead screws. there are no couplers.
-
Ok I understand now.
Now what do you mean by weak screw where you don't want the whole load on. Which "tiny little screw"?
-
@JoergS5 
-
Could you make a
M112M122 after a calibration test and look for error messages please? -
You can see where the top of the lead nut is embeded into the upper gantry. so technically i could cheat it and raise the gantry and tighten it down onto the lead nut with that screw.
-
@JoergS5 what do you mean after a calibration test?
-
I mean after you run your procedure for Z leveling which fails with 0.5 mm fault. After this test/macro/... make a
M112- sorry M122 -
here is the M122 pre leveling
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7JKDA-3S86M-9BAZN
Used output buffers: 3 of 24 (13 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93836 of which 32 recycled
Exception stack ram used: 264
Never used ram: 8960
Tasks: NETWORK(ready,416) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:00:52 ago, cause: software
Last software reset at 2020-06-03 01:05, reason: User, spinning module GCodes, available RAM 8720 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 34.4, current 34.9, max 35.4
Supply voltage: min 12.1, current 12.2, max 12.3, 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: 2020-06-03 01:06:17
Cache data hit count 86939936
Slowest loop: 5.44ms; fastest: 0.13ms
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 3.6ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.63ms; fastest: 0.00ms
Responder states: HTTP(2) 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.23
WiFi MAC address bc:dd:c2:2d:64:61
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 22208
WiFi IP address 192.168.1.44
WiFi signal strength -45dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
M292
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
9 points probed, min error 1.050, max error 1.650, mean 1.378, deviation 0.219
Height map saved to file 0:/sys/heightmap.csvM292
Error: Some computed corrections exceed configured limit of 0.50mm: 1.585 0.865post leveling
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7JKDA-3S86M-9BAZN
Used output buffers: 3 of 24 (20 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94036 of which 32 recycled
Exception stack ram used: 512
Never used ram: 8512
Tasks: NETWORK(ready,396) HEAT(blocked,1224) MAIN(running,1632) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:08:31 ago, cause: software
Last software reset at 2020-06-03 01:05, reason: User, spinning module GCodes, available RAM 8720 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 34.5, current 35.2, max 35.4
Supply voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/1023
Driver 1: standstill, SG min/max 0/437
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: 2020-06-03 01:13:56
Cache data hit count 854313108
Slowest loop: 14.99ms; fastest: 0.13ms
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 4.3ms, write time 2.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 85235ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 112, completed moves: 112, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 199.92ms; fastest: 0.09ms
Responder states: HTTP(2) 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.23
WiFi MAC address bc:dd:c2:2d:64:61
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 22208
WiFi IP address 192.168.1.44
WiFi signal strength -40dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0
- WiFi -
-
