Help me get connected to my Duet2Wifi
-
Having YAT installed is a good idea regardless in case you ever need to communicate with the board in the future. It's a handy fall back for cases just like this.
-
I'm going to sleep, but regardless of how the ping goes, going through the getting connected guide should get your duet at least connected to the wifi network. From there it's just a matter of having the web interface files on the SD card. All the links provided in this thread should get you there. If you get stuck, ask for clarification and someone will likely be able to answer you in short order. Remember, you catch more flies with honey than vinegar. If you get stuck and no one comes to help, I'll be back tomorrow. Eventually we will get you sorted out, it'll just take some time and effort.
-
@Phaedrux Good Morning. So I used YAT to connect to the board and verified the firmware being used. I also used M552 it says the modal is connected to my network. I disabled the modal and re entered my network information and turned it back on but still not connection to my wifi. I also went through my folder structure and confirmed all the files are there. I went through the documentations but Im not sure what to do next
-
@bearer There is no Index.htm.gz file on the card nor is it listed in the SD folder structure. I also downloaded the SD contents Zip and no such file is there either. I don't see any documentation about creating such a file so not sure where this file is supposed to come from the config tool or if Im supposed to write it myself there is not source material for me to do so.
-
When you send M552 in YAT, did it reply with what IP address it's connected to?
That would be the address to connect to in the browser.
Can you also send M115 in the console to get the installed firmware version? We'll need to know that to ensure we're using the right DWC files.
-
@Kwad3d said in Help me get connected to my Duet2Wifi:
I don't see any documentation about creating such a file so not sure where this file is supposed to come from
@bearer said in Help me get connected to my Duet2Wifi:
which says
If your Duet 2 WiFi is running main firmware 1.19 or later:
- Upload the new DuetWebControl.zip file through the General tab on the Settings page of DuetWebControl.
- If the web interface is not working, then move the SD card to a PC, delete or rename any existing /www folder, create a new one, and extract the contents of DuetWebControl.zip into it. Do not unzip the individual .gz files, leave them as they are on the SD card.
You'll find the zip file on the duet github , the config tool offers to download the latest version, and its bundled inside the reprapfirmware releases like 3.1.1
-
@Phaedrux Yes M552 comes back saying "WiFi module is connected to access point NETGEAR19, IP address 192.168.1.10<LF>ok<LF>" but when I go to that Ip address I get this message "Your Duet rejected the HTTP request: overflow".
M115 comes back with "FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2<LF>ok<LF>"
-
@bearer So being that firmware 1.19 and earlier are not supported anymore shouldn't the SD continents be updated? I don't even think boards are shipped with firmware that far back are they? I confirmed the config on the board was never updated so why would I need to alter any files on the SD when It worked fine before?
-
Ok, so next step will be to try replacing your web interface files on the SD card. So pull the SD card and put it in your PC.
There should be a WWW folder in the root. Delete the contents of the WWW folder.
Download this zip file and extract it into the /www folder.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.03/DuetWebControl-1.22.6.zip
Inside of the www folder there should now be a CSS, JS, and FONTS folder and a few other files.
This version matches your installed firmware version 2.03.
Then put the SD card back in the duet, power it up, and try hitting the IP address in your browser again.
-
@Phaedrux Success. I have re-established a connection to the board. I have swapped to board to a new machine that will be using a BLtouch. I have a V3.1 and in the config tool is says to use 3.3v or risk damage to the board. but the documentation shows it connected to a 5v power source. Which is the correct power for my version of the BLtouch?
-
Congratulations.
First thing, it's time to update your firmware.
When connected to the web interface go to the system tab and upload this zip file. Don't extract it or anything first, just upload the zip file. It should detect it and take care of updating things.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
Then after it reboots, use M115 from the DWC gcode console to check that firmware is now 2.05.1
If you're going to be setting up a new machine, now is probably a good time to also update to RRF3 and getting a fresh config for the printer. If you tell me what kind of printer it is and some details about it, I can produce a config file set to use. That would make the BLtouch setup moot since it would contain all those files as well.
As for connecting the BLtouch, the new BLtouch since v2 and the new duetwifi will all work fine with 3.3 or 5v, so you don't have to do anything anymore.
-
@Phaedrux Forgive me its been a while since I have seen the interface. Im not finding a system tab... I do see a settings tab that has a "upload file(s)" option
-
Ah, forgive me. I forgot how old of a web interface version you're on.
It's the settings tab on the left, and then there is a big blue button saying upload files.
If it doesn't update properly by uploading the zip file we can use a modified method. But hopefully that works because it's definitely the easy way to update.
-
@Phaedrux Ok it was successful I think.
-
When the web interface reloads does it look different? You may need to do a hard refresh or go to the base IP address again.
You can send M115 to get the firmware version.
-
@Phaedrux Yes after I refreshed the page the interface changed. here is the info that came back with the M115 command
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
-
Alright, you're up to date on the RRF2 versions. Up to you if you want to move to RRF3 and want help configuring the printer.
Otherwise you can get a config from the online tool.
-
@Phaedrux what are the benefits on RRF3? Also do I need to use 3.3v or 5v for the BLtouch V3.1?
-
RRF2 is no longer being updated, so future development is on RRF3.
It's more flexible in how pins can be used and assigned. It allows for conditional gcode and soon variables for doing some programming of macros and things like skipping the homing sequence if it's already homed, or automating the leveling sequence.
More detail here: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
For the most part the difference isn't huge. If you're already really familiar with RRF2 config files it can take a bit of getting used to, but if you're new to the firmware, it's no different than learning RRF2. It's really just the formatting of a few commands that has changed.
For the BLtouch, connect it like this: https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_2_WiFi_Ethernet_without_a_Duex_2_or_Duex_5_expansion_board
Since I assume you don't have an existing configuration for this printer already I figured it might make more sense to go with RRF3 off the bat.
Either way the web config tool would generate a new config file set for 2 or 3.
-
@Phaedrux Ok since I have not been connected to the board in a while and need to relearn the workings I agree I should update the firmware to RRF3 then. I can update firmware from the interface correct?
The BLtouch documentation you linked says to use 5v but the config tool says it will damage the board. Kind of confused by the contradictory info on the power input. "Make sure you change it to use +3.3V instead of +5V before you connect it or you risk damaging your board!" is what it says in the config tool in the BLtouch section. Either that message is incorrect or the documentation is out of date.
