Cambio elettronica

droftarts

@Leblond "the static test gave me a positive result, so the sensor works,"

Do you mean that you get a response in the DWC, with the probe value going from 0 to 1000 when you put something under the probe, here?

Screenshot 2020-04-01 at 13.15.56.png

If correct, then the probe should work, and it's your config.g and probably homing files you need to edit. I know you have posted these before, but please post your current config.g, homeall.g and homez.g files.

Ian

Leblond

@droftarts si scusa ho fatto macello, appena possibile ti mando il tutto, perdonami ancora

Leblond

Eccomi

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 02 2020 16:46:31 GMT+0200 (Ora legale dell’Europa centrale)

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

M667 S1 ; select CoreXY mode

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

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 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 X330 Y330 Z400 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P5 C"zprobe.in" I1 H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X60:300 Y50:300 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; 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
M143 H1 S280 ; set temperature limit for heater 1 to 280C
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 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 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

; Custom settings are not defined

Leblond

Leblond

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 02 2020 16:46:31 GMT+0200 (Ora legale dell’Europa centrale)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-335 Y-335 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-335 ; home X axis
G1 H1 Y-335 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-335 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-335 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X60 Y50 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

Leblond

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 02 2020 16:46:31 GMT+0200 (Ora legale dell’Europa centrale)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-335 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 H1 X-335 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

Leblond

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 02 2020 16:46:31 GMT+0200 (Ora legale dell’Europa centrale)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y-335 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 H1 Y-335 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

Leblond

non ho sistemato i file di homing perche' trovo piu' necessario il sensore per adesso, una volta appurato che il sensore fa fermare il piatto allora mi ci mettero' dietro

Leblond

console.txt

Leblond

ragazzi non so che cacchio ho fatto, ma il piatto si ferma, l'unica cosa che ho fatto e' stato togliere la sd da duet, portarla sul pc, riformattarla e ricaricargli tutto il sistema, una volta fatto cio' ho reinserito la sd nel duet, son dovuto ricorrere a yat, una volta fatto tutto ho riprovato ed incredibilmente funziona, ora vediamo di risolvere gli assi di home

Leblond

houston abbiamo un problema

Leblond

This post is deleted!

Leblond

l'asse z risponde come dovuto +25 si abbassa e -25 si alza anche in automatico
l'asse x e y sempre in manuale rispondono bene
ma quando vado a fare l'homing come mi aspetto l'asse z si abbassa, ma gli assi x e y se ne vann dalla parte opposta e in diagonale, i finecorsa sono dalla parte opposta cioe' asse X davanti a sx e l'asse Y davanti a dx e si spostano di 10 / 15cm poi si fermano e l'asse z va a trovare il sensore come dovuto

Leblond

nella configurazione il comando M569 P0 S1 e M569 P1 S1 li ho cambiati in M569 P0 S0 e M569 P1 S0
ma non riescono ad andare dove ci sono i stop perche' si fermano prima ed in manuale gli assi x e y vanno al rovescio

Leblond

Mi passate per cortesia una configurazione esempio per la corexy sulla movimentazione?

Leblond

toc toc... c'e' nessuno?

Leblond

ok chi fa da se fa x tre

Phaedrux

It sounds like you're having a common problem experienced with corexy setups. I will copy and post a description of what must be done. Consider it an order of operations. It will hopefully get you on the right track. Please post if you have any questions.

https://forum.duet3d.com/topic/12676/mirrored-x-axis/9?_=1585861769573

In general, here's what you need to do to define your coordinate system. The FT5 is a little tricky because by default it puts the origin at the rear right, and has some printed grid on the bed surface (I think?) but really it's all arbitrary.

First, choose a FRONT for the printer so that when you're looking at it standing in front of it 0,0 is the front left corner, X+ goes to the right, Y+ goes to the back. This does not change because it's describing the physical layout of the printer.

Next, Measure the axis length for X and Y and enter that in your M208 command to set the axis limits. 0 at the low end (or even negative if the head leaves the bed surface to hit the endstop). This does not change because it's describing the physical layout of the printer.

Now identify where your endstops are located. They can be at the low or high end of the axis. Define them with M574. M574 X1 Y1 for low side, M574 X2 Y2 for high side, or any combo thereof. This does not change because it's describing the physical layout of the printer.

Now setup your homing movements. If the endstop is at the low end of the axis, the homing move must be negative. And vice versa. This does not change because it's describing the physical layout of the printer.

Now test the motor movement direction. If X+ moves to the right, you're good to go. If it moves left, you need to change the motor rotation for the X driver by changing the M569 S0/S1 command in config.g. Same goes for Y+ moving to the back. If you've connected the motors to their default drivers, it should be mapped like this:

M569 P0 S0 ; Drive 0 (x) goes backwards
M569 P1 S0 ; Drive 1 (y) goes backwards
M569 P2 S0 ; Drive 2 (z) goes backwards
M569 P3 S0 ; Drive 3 (e) goes backwards
If you follow those steps your printed parts will match the orientation in the slicer and won't be mirrored.

You can use these steps to test your motor movement and make changes accordingly: https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter#Section_Testing_motor_movement

droftarts

@Leblond Sorry, I'm using google translate, but I don't really understand what problem you are having. I think you say your motors are moving the X and Y axes correctly, but not towards the endstops.

First, check the X and Y axis are moving in the correct direction for CoreXY. See https://duet3d.dozuki.com/Wiki/Test_axes_or_motors_individually

Once the X and Y axis move correctly, then get the endstop configuration correct. You have the endstops set in config.g at the low end, X0 Y0.

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop

Your homeall.g moves X and Y to the minimum, by moving X-335 and Y-335 towards the endstops. Is this not correct?

It may be a good idea to draw a picture to show where everything is on your printer, like this, which will help us understand where everything is without using Google translate:

dbot axis.png

Ian

Leblond

ti capisco ho problemi di comunicazione anche io, scrive cio' che pare a lui e adesso ne ho capito la causa, il problema e' che devi srivere senza la correzione del traduttore, ma attivarlo solo quando leggi, si ho risolto per fortuna il problema del sensore, riformattando la SD, e si ho il problema di movimentazione degli assi x e y, grazie per il momento @droftarts ci guardo e poi ti dico.