Duet wifi controlled dbot corexy based
-
hi, I have problems with the printer I'm building:
-
when I move the y-axis automatically also moves me the x-axis
-
if you do G0 X20 Y30 command moves just the x and if you do a command G0 Y30 X20 then I get the right shift
-
when I give the command G28 X Y carries the x zero and then when it moves y to the endstop moves the x removing it from 0
how can I solve these problems? thank you very much and sorry for my english
This is mi configuration
; CoreXY sample config file for dc42 Duet firmware M111 S0 ; Debug off M550 GMAX ; Machine name (can be anything you like) M551 Preprap ; Machine password (used for FTP connections) ns) ;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address ;*** Wifi Networking M552 S1 ; Enable WiFi M555 P2 ; Set output to look like Marlin M575 P1 B57600 S1 ; Comms parameters for PanelDue ; Machine configuration M569 P0 S1 ; Drive 0 goes forwards (change to S0 to reverse it) M569 P1 S0 ; 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 ; If you use an endstop switch for Z homing, change Z0 to Z1 in the following line, and see also M558 command later in this file M574 X1 Y1 Z0 S0 ; set endstop configuration (X and Y and endstops only, at low end, active high) M667 S1 ; set CoreXY mode M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolation M92 X64 Y64 Z400 ; Set axis steps/mm M92 E420:420 ; Set extruder steps/mm M906 X1200 Y2000 Z2000 E800 ; Set motor currents (mA) M201 X800 Y800 Z100 E1000 ; Accelerations (mm/s^2) M203 X15000 Y15000 Z100 E3600 ; Maximum speeds (mm/min) M566 X600 Y600 Z30 E20 ; Maximum jerk speeds mm/minute M208 X640 Y430 Z550 ; set axis maxima (adjust to suit your machine) M208 X0 Y0 Z-0.5 S1 ; set axis minima (adjust to make X=0 and Y=0 the edges of the bed) G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Z probe M558 P1 X0 Y0 Z1 ; Analog Z probe, also used for homing the Z axis G31 Z1.20 P500 ; Set the probe height and threshold (put your own values here) ; The following M557 commands are not needed if you are using a bed.g file to perform bed compensation ;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of the Z probe M557 P0 X60 Y0 ; Four... M557 P1 X60 Y165 ; ...probe points... M557 P2 X222 Y165 ; ...for bed... M557 P3 X222 Y0 ; ...levelling ;M557 P4 X141 Y82.5 ; 5th probe point for levelling ; Thermistors and heaters ;*** You can use S and B parameters to define the parameters of the thermistors you are using M305 P0 R4700 H0 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction M305 P1 R4700 H0 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction M305 P2 R4700 H0 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction M301 H1 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 0 M301 H2 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 1 M570 S120 ; Increase to allow extra heating time if needed ; Tool definition M563 P0 D0 H1 ; Define tool 0 G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures ;*** If you have a dual-nozzle build, un-comment the following 3 lines ;M563 P1 D1 H2 ; Define tool 1 ;G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures ;*** If you are using axis compensation, put the figures in the following command M556 S78 X0 Y0 Z0 ; Axis compensation here T0 ; select first hot end; homeall file for use with dc42 Duet firmware on CoreXY printers ; This file assumes the endstop switches are at the low end of each axis. ; Reverse the X and Y movement for high-end switches. ; Adjust the bed upper and lower limits in config.g (M208 commands) to get the correct homing positions G91 ; relative mode G1 S1 X-240 Y-240 F3000 ; course home X or Y G1 S1 X-240 ; course home X G1 S1 Y-240 ; course home Y G1 X4 Y4 F600 ; move away from the endstops G1 S1 X-10 ; fine home X G1 S1 Y-10 ; fine home Y ; If you are using a microswitch for Z homing, insert similar code for the Z axis here, ; but use lower feed rates suitable for your Z axis. G90 ; back to absolute mode ; If you homed the Z axis using an endstop switch, you can insert a G92 command here to correct the height. ; The following code assumes you are using a Z probe to do Z homing. Remove it if you are using a microswitch. ; Adjust the XY coordinates in the following to place the Z probe over a suitable spot, ; preferably near the centre of the bed if your Z probe supports that G1 X100 Y100 F2000 G30 ; This file leaves the head at the zprobe trigger height so that you can slip a piece of paper under it and then do G0 Z0 to check the height. ; If you prefer to send the printer to X0Y0Z0, un-comment the following lines ;G1 X0 Y0 F5000 ;G1 Z0; X axis homing file for dc42 Duet firmware G91 G1 Z4 F200 G1 X-640 F3000 S1 G1 X4 F600 G1 X-10 S1 G1 Z-4 F200 G90; Omerod 2 Y homing file for dc42 Duet firmware G91 G1 Z4 F200 G1 Y-440 F3000 S1 G1 Y4 F600 G1 Y-10 S1 G1 Z-4 F200 G90[[language]] -
-
Have you run the tests on indvidual motors to check that they are moving correctly, as described at https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_CoreXY_printer#Movement_section ?
No need to apologise for your English. I'm sure it's better than I can speak your language!
-
Check that your homez.g file and the Z homing section of homeall.g is set up to use a microswitch, not a Z probe. See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_files
-
hello thanks for the advice works well now … how do I know the values to be set for acceleration, velocity and jerk? thank you so much
-
Sorry for the trivial question… but I'm trying to learn
-
It depends a lot on your printer mechanics.
Acceleration: values of 1000 to 3000 are typical for X and Y. Start with 1000, then later you can try increasing it. Too much acceleration and you will lose steps on travel moves and/or see ringing artefacts in the print. For the Z axis of a Cartesian printer, use a much lower value, for example 50.
Jerk: too much jerk will cause jarring sounds, ringing or missed steps. Too little and curves will print in a jerky manner. Try 1200 for X and Y jerk. The Z jerk value should again be much lower on a Cartesian printer, perhaps 30.
-
hi, thanks I will test all the values that you told me. I bought a npn sensor for auto-leveling and reading the wiki is written using a diode .. what type of diode does it take? thank you
NPN output normally-open inductive or capacitive sensor Connect its output wire to the cathode of a diode, and the anode of the diode to the E0 STP pin. Connect the sensor ground wire to a ground pin on the Duet, and the sensor's + power wire to a suitable voltage (typically to VIN because these sensors usually need between 6 and 30V power). The diode should preferably be a small-signal Schottky diode such as BAT43 or BAT85, but a small signal silicon diode such as 1N4148 works for some people. Select mode 4 in the M558 command. If using firmware 1.15e or earlier, include M574 E0 S0 in config.g to select active low logic level for the Z probe. If using firmware 1.16 or later, include parameter I1 in the M558 command instead. -
As stated in the text you quoted, a small signal Schottky diode is recommended. Some users found that a 1N4148 or similar didn't work.
-
Why not a voltage divider? I used this on my npn for now since I didn't have a scotcy diode lying around. Are you worried about the effect needed by the sensor?
-
You don't need a voltage divider because an npn output sensor connects the output to ground. The purpose of the diode is to protect the Duet in case the ground wire to the NPN sensor gets disconnected, which would typically result in the sensor putting nearly +12V or +24V on its output pin.
-
I connected npn but the LED on the sensor is always on … in the videos I've seen on youtube, the LED should light up only when you approach the plan?
-
I entered the command M558 P4 X0 Y0 Z1 I1 in the config file but the LED is always on … when I give the g30 s-1 command me error "Z probe Already triggered at the start of probing move" something wrong ?? thank you so much
p.s. i'm used the but85 diode for the signal probe... -
If the LED on the sensor is always on, there is something wrong with the sensor. Does it have a sensitivity adjustment?
-
I tried to change the sensitivity but always remains a link light. The positive I take it directly by a 24v is wrong? the negative and the signal on the pins instead dell'e0 stop … could be the sensor ?? thank you
-
is the broken sensor or I do something wrong?
-
I suggest you try connecting the sensor to just +24V and ground, directly to the power supply terminals or to an always-on fan output (make sure you get the polarity right). Leave the output wire unconnected. If the sensor light is still always on now matter how the sensitivity adjustment is set, then the sensor must be faulty.
-
I managed to run the npn sensor … the problem is that after the homing the duet has disconnected from the Internet and now you do not connect via usb even more I unplugged all the outlets but not goes ... what could this happen ?? It worked great before
-
-
Thank you very much… now it works maybe I accidentally pressed erase ... to make the sensor was enough to put the aluminium plan to grounded ... which means?
-
hi I just plugged the PT100 sensor but when I go to extrude me error:
Error: Temperature reading fault on heater 1: sensor hardware errorHow can I fix the problem? thanks
