cannot connect to duet 2 Wi-Fi or board
-
@droftarts I do not have a hub and I uploaded a profile to the board and it's disconnecting from Wi-Fi and then reconnecting and then disconnecting and then reconnecting and disconnecting where before I loaded the profile it wasn't doing that it was staying on Wi-Fi. And not everything is correct such as my fan for my hot end is not coming on and the printer is moving real real real real real slow do and when I load a model into the printer now when that has worked before that is even going even slower. On the tuning videos that I've been watching they use USB to type in code to be able to change our parameters by g-code My USB is not working with the printer what do you suggest
-
@Blunt2007 Okay, I think your problems are:
- WiFi disconnecting and reconnecting all the time
- Fan not coming on
- Printer moving slow
- Entering Gcode commands
- Still can't connect via USB
WiFi disconnecting and reconnecting all the time
I'm going to need to see a full M122 output, as the Network/WiFi diagnostics are at the end. It could be one of a number of reasons, like poor WiFi signal, congested WiFi channel, aerial not connected, router band switching... there's lots of reasons. If you are not having to set the SSID and password each time with M587, then it is probably solvable.
When you can connect via DWC, click on the 'Console' menu option, and type
M122where it says 'Send code...' in the middle of the screen. You should get a response in the area below. Copy and paste that into your reply.Also see this troubleshooting section: https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshooting
Fan not coming on
This could be configuration, or wiring. Did it work before? Is it the hot end cooling fan or the part cooling fan? Post your config.g. Do this by going to the the System menu in DWC, right-clicking on config.g and either 'Edit' or 'Download' File. If you edit, copy and paste the contents of config.g into your reply. If you download it, you can drag and drop the file into your reply.
To check the wiring, you could plug it into the 'always on' fan header (see the wiring diagram here). If it works, great. If it doesn't work, check the fan fuse, which is the 1A blade fuse on the board.
Printer moving slow
If you've posted your config.g (see above), we can see what speeds you are using; these may just be too low. Slicing software has a bad habit of changing your settings. Open the Gcode file (in a text editor) and check the first 50 lines, and see if it sets any Gcodes for speed and acceleration. Look for any line that starts with Gcodes M201, M203, M566 or M204. If you find them, post that section of the Gcode, along with what slicer software you are using.
Entering Gcode commands
I'd fix the other problems first, particularly the 'moving slow' one. When you want to send commands, you can send them in DWC from the 'Console', like how you sent M122 for the WiFi problem. It does that same thing as sending them over USB.
Still can't connect via USB
I really don't know why this isn't connecting. Have you tried other USB leads? Many USB leads are just for charging, and don't have the wires inside for carrying data, so you may have to try a few. Look for cables that are a bit fatter, they may have 4 wires rather than 2. Otherwise, there's very little difference between them, just try all the USB cables you have!
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
1/23/2024, 8:52:22 AM M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.2 (2023-12-14 10:30:41) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6B2-NJ4S4-6JTDG-3S46L-1V0YM Used output buffers: 1 of 26 (16 max) === RTOS === Static ram: 23084 Dynamic ram: 74980 of which 12 recycled Never used RAM 15068, free system stack 170 words Tasks: NETWORK(1,ready,14.4%,221) HEAT(3,nWait,0.1%,328) Move(4,nWait,0.0%,363) MAIN(1,running,85.6%,743) IDLE(0,ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 01:10:55 ago, cause: power up Last software reset at 2024-01-22 16:59, reason: User, Gcodes spinning, available RAM 14972, 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 MCU temperature: min 14.2, current 24.8, max 25.3 Supply voltage: min 24.1, current 24.3, max 24.6, 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 n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-01-23 08:52:21 Cache data hit count 4294967295 Slowest loop: 10.88ms; fastest: 0.20ms 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 9.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === 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 -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks 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 Q0 segments left 0 Code queue 0 is empty === Network === Slowest loop: 15.57ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 1.26 MAC address bc:ff:4d:e8:23:dc Module reset reason: Power up, Vcc 3.40, flash size 2097152, free heap 27104 WiFi IP address 192.168.1.21 Signal strength -32dBm, channel 0, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 1/23/2024, 8:51:55 AM Connected to 192.168.1.21 -
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.4.0 on Mon Jan 01 2024 15:36:02 GMT-0600 (Central Standard Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"1 Ender 5 plus" ; set printer name ; 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 Z800.00 E130.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E150.00 ; set maximum instantaneous speed changes (mm/min) M203 X3000.00 Y3000.00 Z3000.00 E3000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z100.00 E5000.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 X350 Y350 Z400 S0 ; set axis maxima ; Endstops M574 X2 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F120 T12000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z2.51 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; 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 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C 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 S450 ; set temperature limit for heater 1 to 450C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 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 H-1 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H1 T45 ; set fan 2 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 M501 ; load saved parameters from non-volatile memory T0 ; select first tool -
@Blunt2007 For your WiFi problems:
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 1.26
MAC address bc:ff:4d:e8:23:dc
Module reset reason: Power up, Vcc 3.40, flash size 2097152, free heap 27104
WiFi IP address 192.168.1.21
Signal strength -32dBm, channel 0, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
1/23/2024, 8:51:55 AM Connected to 192.168.1.21This generally looks fine. -32dBm is a good, strong signal. Does your Duet have an external aerial?
A possible problem is that it is set to channel 0; I think this is reporting incorrectly (there is no channel 0, only 1 to 12) as you are on a slightly older version of the WiFi firmware, 1.26.
As you are using the latest RRF version 3.5.0-rc.2, you could update the WiFi version. From https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0-rc.2 upload the "DuetWiFiServer.bin" file. You will need to input your SSID and password again, using the "runonce.g" script.
Also make sure you are using the same version of DWC as firmware. Check by looking at the Setting > General and Machine-specific tabs. If it is not the same, upload the "DuetWebControl-SD.zip" file from the firmware release.
Then send M122 again, and see what channel you are connected on. If you don't have an external aerial that plug in, the following might be the cause of disconnections:
Particularly if using channel 1, change the router WiFi channel. Duets with onboard WiFi antennas may be more susceptible to interference from the Duet itself at this frequency. Try channel 6 or 11.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts every time I try loading a m 420 bad leveling it kicks me off. And then I got to restart my browser to access board again and then when I try entering m420 bed leveling it kicks me off again I'm trying to get this on there because the screen is coming up with a m 420 does not exist. I got the fan working that was wires were reversed fan is working now now I'm trying to get my BL touch to work
-
M420 is not supported in RepRapFirmware. Are you maybe running G29 or G32?
<>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>
-
-
@Blunt2007 printer moving slowly I sent you a config file the code list that you sent me there's a bunch of them on there can you look at it and I'm using cura 5.2.1 as my slicer I haven't updated it in about 6 months and when I load a file from there it goes real real real real real real real real slow thanks for your wisdom and understanding
-
@oliof how can I tell what code I'm running I'm not sure it comes up on the screen as a m420
-
@Blunt2007 Okay, new problem,
Bed levelling problem
Whatever guide you're following, don't. It's meant for Marlin firmware, not RepRapFirmware. Don't use M420. See this page for bed mesh levelling: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_mesh_bed
Moving slow problem:
Your config.g speeds aren't that fast, but they are not that bad. M203 X3000 Y3000 is 50mm/second. What speeds are you expecting?
If you are using Cura, make sure you have 'RepRap' chosen in the Machine Settings > G-code flavor
Otherwise it will put in speed and acceleration settings in the Gcode that will mess up the ones in config.g
Fan problem
Your config.g shows:
; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 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 H-1 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned onThe fan connected to the Fan0 output is your part cooling fan, and is controlled by Gcode.
The fan connected to the Fan1 output is set up the same, ie controlled by Gcode
The fan connected to the Fan2 output is set to be your hot end cooling fan, and comes on when the hot end gets to 45C.Make sure the correct fan is connected to the correct output.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts I am still having problems with the Wi-Fi how do I change the channel from zero to six or 12
-
@droftarts I give up on duet
-
@droftarts I am unable to connect Wi-Fi or USB so this duet board is more trouble than what it's worth I've been trying in between going to the hospital for my dad he fell and broke his hip that's why I haven't Post it you earlier. Can I get a refund
-
@droftarts I'm sorry I'm just so frustrated I just wanted to work
-
@Blunt2007 sorry you have been having issues with the configuration. We already provided a warranty replacement and this makes it clear its not a hardware issue but a issue with configuration. Please review the documentation, for example you asked about changing WIFI channel:
https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshootingAs you can see, a wifi router sets the wifi channel in use, not the client:
- Try changing the channel on your WiFi router. Most routers default to Auto, but can be set to use a fixed channel instead. The channels overlap, so it is common to use channel 1, 6 or 11. This may also help if another device is causing interference.
- Particularly if using channel 1, change the router WiFi channel. Duets with onboard WiFi antennas may be more susceptible to interference from the Duet itself at this frequency. Try channel 6 or 11.
-
@T3P3Tony yeah I know you guys replaced the previous board and this board was working good for a while but now it will not connect to the Wi-Fi and from the beginning it wouldn't connect to USB if I turn the machine off and then turn it back on it loses its Wi-Fi if I reload runonce.g it will connect to the Wi-Fi again but if I turn the machine off it will not reconnect to Wi-Fi unless I reload runonce.g then it will reconnect to Wi-Fi but as soon as I turn the machine off it will not connect to Wi-Fi this board was not working properly from the beginning because it would not connect to USB this board was working correctly except it would not connect to USB from the beginning so this board is messed up it is a default board from the beginning because it would not connect USB so clearly this board is a default board from the beginning it will connect to USB if I push the reset button but as soon as I disconnect it and try reconnecting it it will not connect to USB unless I push the reset button so clearly this board was default from the beginning and I was trying to work with you guys to get this going and it did work for a little while but now it's not connecting to you to Wi-Fi are you guys going to back up your product or not
-
@T3P3Tony I am willing to look into buying a new router what router do you recommend that works with this product just to make sure that it is not my hardware
-
@Blunt2007 We're a bit confused about the board replacement. We don't have any record of you submitting a warranty request, at least not from the name and email address you registered with. From where and when did you buy the original board?
If you did replace the board, I find it very unlikely that you would get two boards that exhibit exactly the same problem. Did you send back the original board before receiving the replacement, or is it possible you could have kept the original board by mistake?
Please can you post a picture of the whole board, if possible.
What make and model of router are you currently using? It may be that there is a setting that continually tries to force the Duet to use 5GHz WiFi, but the Duet can only do 2.5GHz WiFi.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
  @droftarts The new board would not connect by USB from the beginning so I did load runonce.g to the system file and I was able to connect buy Wi-Fi to the board and I was configuring the board but just recently I was not able to connect by Wi-Fi it was working fine but now it will not connect by Wi-Fi to the board I mailed the old board on June 28th 2024 I will include a picture of the drop off slip. The new board is set to channel 10 and it is running at 2.4 G and I'm still not able to connect via Wi-Fi! I purchased the original board from printed solid
[17079263815565014596051133997642.jpg](Request Entity Too Large)
