Are you using the facility to have the firmware level the bed by adjusting the Z leadscrew motors individually? If so, then the locations of the probe points are in the G30 commands in the bed.g file. If you are not using that facility, then you need only run mesh bed probing.

@brandonh Thanks! I'll try this on a couple of deltas with duets. Will be a little while, both in long prints right now.

i ended up erasing the duet and starting over, had issues connecting to a new wifi router i installed, (2.4) so i plugged in my old router and it connected fine.

working now, but wish i knew why it wouldnt connect to new router (2.4)

@dc42 I looked at your commit and I agree that I think it will resolve the problem on the basis that it's similar to what I was going to try myself.

I've been running a couple of hours now with the change and all of the statistics, including custom debug code that I added which caused me to find the bug, all seem to be reporting correctly now.

I'll need to run longer to check if this resolve my other issues with layer shifting, I'll post in that thread if it works.

Thanks for your help.

Magically, I changed the USB port into another one, repeated the procedure and it worked.
I will never understand electronics.....

Thank you for your replies DC42!!!! Will create another post on bed leveling piezo issue I was having. Hopefully, I will solve that as well!!!!

I think it might be easiest to start with a config generated by the configurator since you can enter all the machine details that you know. (endstop type and position, thermistors, etc.) and from that you can go through it alongside the setup docs.

You can see what you'll need to know from the existing printer hardware and marlin config here: https://duet3d.dozuki.com/Wiki/Going_from_Marlin_on_Arduino_to_RepRapFirmware_on_Duet

Even though it's for cartesian, it starts with the basics. https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter

Then as fcwilt says above move to the CoreXY specific docs to verify motor direction, etc, https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter

We can sanity check things before going too far.

The configurator after the last update should be able to provide a good starting configuration for the BLTouch, but you can verify it with https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

Thank you!

That would be because I switched the file system to use UTF8-encoded file names instead of code page 850. Two questions:

If you upload a new file with accented characters in the name through DWC, is the filename displayed correctly in DWC?

If the answer to #1 is yes: if you then put the SD card in a PC, which of the 2 filenames does the PC display correctly? I doubt that it will be both.

@dc42 said in duplicate files in macro and setting:

iap4e

This solves the issue, I now have

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.0 or 1.01
Firmware Version: 2.02RC6(RTOS) (2018-12-15b2)
WiFi Server Version: 1.21
Web Interface Version: 1.22.5

This is solved Ok, so that's not an issue This is solved

Thanks!!

Antoine

@carlitototo said in Messed up duet wifi installation !:

Infortunatly, nothing will do ! still no ports recognize, after trying tothe erase procedure multiple times... Sad to say, but I think (3D :P) that my duet is dead snif

Try a different USB port on your PC if you haven't already, also try rebooting the PC - especially if it is running Windows. If you've already done that, then go ahead and contact your supplier.

SOLVED

hello, as often you are right and settled my problem

@wilriker said in Firmware 2.02RC5 now available:

@3dmntbighker This sounds a little bit to me a if you are using S3D as a print server - which is not recommended anyway.
But this line is totally ok. RRF complained about a line that did not start with a G or M or T. So my question was if such a (broken) line exists in the file but it does not.

Apart from all of that I hear a lot of complaints about S3D lately. Development has virtually ceased - probably because a lot of the developers seem to have switched to develop ideaMaker for Raise3D instead.

Print server = NO (upload to SD and print)

I opened the gcode file in BBEdit and searched for the string in the error. As I said the line in the file was completely normal. But there could be garbage elsewhere in the file that caused Duet to freak out. Quitting S3D and re-saving it after resulted in a working file.

yes
i was so stupid i took no back up from the sd before upgrading
anyway i formatted a new card and did everything from scratch..
i m connected i have the config file i saved and continuing with the calibration of the x y axis.....thanks anyway

@dc42 got it -- PS -- love how super simple it was to add T4 and T5 for different combination of duplicate printing -- really slick, I thought I would need to have different config modes for regular iQUEX vs duplication, but this is super neat, I just have T4 defined as duplication of extruders on gantry 1 and T5 as duplication of extruders on gantry 1 and one of the tools on gantry 2 -- (the other tool has a different nozzle diameter, so can't include it in duplication mode)
but I love how simple it was to setup and it worked the first time I tried it - both X an Y axis mapping in duplication -- really great.

Man I'm mixing all the file names up. What you just posted is what I knew to be true. I'm getting them all mixed up. Either way, I'll just delete the DuetWiFiServer.bin from the sd card and it should be all good. Thanks for the help.

Thanks man! that solves my issue. I should have known that... I figured it was easy.

Sounds good - thanks for the explanation!

@grenierc said in Duet Panel v3 update firmware / Unknown USB Device:

Hi,

here is my problem, I tried to update the 1.21.1 @ 1.22 frimware and here is the error that appears after pressing Erase and Reset ...Unknown USB Device (Device Descriptor Request Failed).

Is there a way to solve this problem?

Thanks

Chris

I used to get that message a lot, when I connected Duets to Windows 10 via a USB hub. Switching to another port on the hub fixed it. When I ran out of ports on the hub, sometimes disconnecting and reconnecting the hub would get all the ports working again. If not then I would have to reboot Windows.

I switched to a different make of USB hub and the problem went away.