Help me get connected to my Duet2Wifi
-
Connect to the board via USB terminal again and send M115 to see if the main firmware is now 3.1.1. If it is, then send M552 to see if the board has enabled the wifi module and got an ip or not.
If that doesn't give you an IP address to connect to, send M997 S1 to reflash the wifi firmware. Sometimes it needs to be reapplied going from 3.0 to 3.1.1.
After it's been reflashed, send M552 S1 to try re-enabling the wifi. It should reconnect at that point.
-
@Phaedrux Yes the new firmware is on the board. I confirmed the IP and reconnected to the board. At this point can I set up the BLtouch in the config tool and put it on the SD card or will I need to download and replace the www files again to match the new firmware?
-
Ok, good, now that you're connected and the firmware is up to date you're good to go on that front.
When you go through the configurator try and fill out all the boxes to the best of your knowledge with the details of your printer. It might help to load one of the premade printer profiles to look at just to see what a completed one looks like before making your own.
At the end of the configuration process it will give you a download link to get a config.zip file that will contain a bunch of files. You can go to the system tab in the web interface and use the upload button there to upload that config.zip file. It will reboot and your configuration will be in place.
At that point you can edit those files manually in the web interface if you need to.
When your config is in place you can use some steps like those described here for testing the motors and fans and heaters etc.
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39
Come back if you have any questions. If you get really stuck, you can describe the printer and we can generate a config for you to start with. Eventually it pays to get used to editing the config files yourself. If you're unsure what a command does, look it up in the gcode wiki. https://duet3d.dozuki.com/Wiki/Gcode#main
-
@Phaedrux Ok thanks for you help and patience. The printer was designed to use senseless homing so I will have to read the documentation on it and update the homex and home y files to get that working correct. I also had a question about how the mesh leveling works. Will the parts of the bed where the probe cant reach be estimated based on the mesh or does it revert to no compensation in these areas?
-
@Kwad3d said in Help me get connected to my Duet2Wifi:
The printer was designed to use senseless homing so I will have to read the documentation on it and update the homex and home y files to get that working correct.
You can choose sensorless as an endstop option in the configurator, but you will likely need to do some tuning.
https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing
@Kwad3d said in Help me get connected to my Duet2Wifi:
Will the parts of the bed where the probe cant reach be estimated based on the mesh or does it revert to no compensation in these areas?
Yes it will extrapolate to the areas it can't reach, but it's not perfect. If there is a unexpected peak or valley it won't know about it.
https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation
@Kwad3d said in Help me get connected to my Duet2Wifi:
Ok thanks for you help and patience.
You're welcome.
-
@Phaedrux Ok I will more than likely need some assistance fine tuning the mesh leveling to match my probe locating and the areas where the print head can move off the bed. I did find this post in the forums where you made some good references that I think will get me there though.
https://forum.duet3d.com/topic/18185/possible-pwm-port-issue-rrf3-question/18
-
@Phaedrux Ok I came across a bug or something. When testing my heated bed I got error message after 15-30 seconds saying it is heating up too slow. However I can see the temp rising in a acceptable manor. How can I correct this issue?
-
@Kwad3d said in Help me get connected to my Duet2Wifi:
How can I correct this issue?
It's not a bug. It's the thermal runaway protection kicking in because it doesn't have an accurate model of your heater yet so it thinks something is wrong.
The solution is to PID tune your heaters.
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40#s161
-
@Phaedrux LOL.. total DUH moment. Guess I assumed that "Bang Bang" didn't require it
-
This post is deleted! -
@Phaedrux Ok I have made some progress but having inconsistent results with senseless homing and not sure how to adjust the settings. This is on a CoreXY for reference so both motors have to move in tandem to home x and y. It will home some times and then sometimes it will move a little in the opposite diagonal direction ( one motor not turning with the other). Here is my HomeX code. My guess is its slightly too sensitive. Im gussing I need to increase the motor current a few percent but want to check
M400
M913 X70 Y70 ; drop motor current to 70%
M400 G91; relative positioning
G1 H2 Z10 F12000 ; lift Z relative to current position
G1 H1 X-320.5 F10000 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X20 F12000 ; go back a few mm
G1 H1 X-320.5 F7000 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-10 F9000 ; lower Z again
G90 ; absolute positioning
M400
M913 X100 Y100 ; return current to 100%
M400 -
What does your M915 command look like?
https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing#Section_Sensorless_Homing
Have you calculated what your M915 H value should be and your minimum homing speed?
In your example, remove the entire second homing move. With stall detection you need a short sharp shock during a steady state move. Backing off and slowly approaching from close up isn't going to generate a stall reliably. Since you're stalling the motor to a full step anyway, backing off and rehoming for more accuracy doesn't make sense here like it does when using an endstop switch.
So try this
M400 M913 X70 Y70 ; drop motor current to 70% M400 G91; relative positioning G1 H2 Z10 F12000 ; lift Z relative to current position G1 H1 X-320.5 F10000 ; move quickly to X axis endstop and stop there (first pass) G1 H2 Z-10 F9000 ; lower Z again G90 ; absolute positioning M400 M913 X100 Y100 ; return current to 100% M400@Kwad3d said in Help me get connected to my Duet2Wifi:
My guess is its slightly too sensitive. Im gussing I need to increase the motor current a few percent but want to check
Start with as low a motor current as you can still reliably move with and set the sensitivity to default. Then slowly increase (or decrease) sensitivity from there.
-
@Phaedrux So lower the full current setting that was set in the confit tool or the "drop motor" current in the M913 line? If im changing the full current that was set in the config (800) I can do that with a g code command in the console right? what is the code please if so
-
I mean lower the dropped current in the M913 command in your homing file.
M906 sets the full current in config.g. That one should be set at ~80% of your motors max current.
-
@Phaedrux Ok currently my M913 line is set to %70 for x and Y. lower to %60-65 and retest?
-
You can send M913 in the console to lower the current in steps. Send your homing move command each time. When the move doesn't work anymore, you've found the lower limit.
Example
M913 X30
G1 H1 X-300 F10000
M913 X40
G1 H1 X-300 F10000etc
If it still moves reliably sat 30% then maybe stick with that because I don't think you'd get much lower.
-
@Phaedrux Today im getting zero movement on homing x. The bed drops then X is just set to 0 while the nozzle is in the center of the bed. I can manually move left and right after the failed homing move. Here is my code for home X at the moment. anything wrong with it? I repeated testing with M913 increments up to 100% I would occasionally get it to home but fails %90 of the time. How do I get it to grind the x axis into the home location? where I want to be is obviously somewhere between there and where Im at now.
M400
M913 X80 Y80 ; drop motor current to 80%
M400
G91; relative positioning
G1 H2 Z10 F12000 ; lift Z relative to current position
G1 H1 X-320.5 F10000 ; move quickly to X axis endstop and stop there (first pass)
G90 ; absolute positioning
M400
M913 X100 Y100 ; return current to 100%
M400 -
I still haven't seen your m915 command. Can you post your config.g file?
-
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"SK GO" ; set printer name
M669 K1 ; select CoreXY mode; Network
M551 P"SK GO" ; set password
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 S0 ; physical drive 2 goes backwards
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 X200.00 Y200.00 Z400.00 E420.00 ; set steps per mm
M566 X600.00 Y600.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 X3000.00 Y3000.00 Z100.00 E10000.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 X10 Y36 Z0 S1 ; set axis minima
M208 X310 Y336 Z320 S0 ; set axis maxima; Endstops
M574 X1 S3 ; configure sensorless endstop for low end on X
M574 Y1 S3 ; configure sensorless endstop for low end on Y; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-26 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X36:290 Y46:290 S48 ; define mesh grid; 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 S90 ; set temperature limit for heater 0 to 90C
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
M143 H1 S280 ; set temperature limit for heater 1 to 280C; 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
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
May want to increase your max speed and decrease your acceleration.
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X3000.00 Y3000.00 Z100.00 E10000.00 ; set accelerations (mm/s^2)Try
M203 X12000.00 Y12000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X1500.00 Y1500.00 Z100.00 E10000.00 ; set accelerations (mm/s^2)It sounds like it's detecting a stall immediately, possibly due to the high acceleration.
Doing this calculation for minimum stall speed would help as well so we know how fast it needs to be going to stall, but not so fast that it stalls prematurely.
Hmin = full_steps_per_rev * rated_current * actual_current/(sqrt(2) * pi * rated_holding_torque)
