Can you confirm that you are using version 1.18.1 main firmware and version 1.03-ch DuetWiFiFirmware? If yes, ask your supplier for a replacement Duet.

Awesome!

"Bossa Port" is a good thing, that means the board is ready to accept firmware.

Away from the computer at the moment, but it looks like you have the wrong board selected in SAM-BA. Should be AT91SAM4E8-EK.

Update, sometimes it works. Sometimes resetting the wifi a few times works. Sometimes the whole thing goes wonky.

Is nobody else seeing this problem with 1.18.1 and 1.15b?

Thank you very much for your answers !

The Auto Bed Compensation button on the Control page of DWC 1.15a has a drop down menu next to it that includes the option to display the height map.

Problem solved, reformatting the SD card fixed the problem.
thanks again DC

also this is an older video but… i go through the steps ( i forgot i even made this video< DOH)

https://www.youtube.com/watch?v=hq1R38qeJ30

(if it fits you can add it to your blog David???)

it could be edited down as well but its to the point i think…

~Russ

I'm sorry that you appear to have been send a board with an empty SD card.

The production process is being changed so that in future, boards will be tested using the same SD card that they will ship with, instead of testing them with one SD card and shipping them with a different one as now.

UPDATE - RESOLVED:

Short Version: 3rd party ribbon cable used for Duex5 was causing problems, suspect voltage drop.

Long Version:

After another couple of weeks, the issue spread to attempting to boot with USB connected as well. Connected the DuetWifi to a known good USB3 port on a windows system to update the firmware. Did so successfully, then after hitting the reset button, followed firmware instructions to a T, the DuetWifi went into a reboot cycle. It was cycling about 1 - 1.5 times per second.

After some more troubleshooting, I identified that the longer ribbon cable I used to connect my Duex5 was causing the reboot cycle in some fashion. Exact root cause is unknown at this time, I suspect drop in voltage due to cable length / gauge. Replaced cable with one that came with the Duex5 and DuetWifi immediately booted and does so evertime now. Plus I no longer need USB connected to boot and serial over USB is working again.

So the longer ribbon cable was causing nearly every issue I was having. Not sure if it's just a cheap cable, got two in a pack, both exhibit the same behavior. Regardless I am back online and letting folks know in case they run into the same issue.

Dave, not sure if you have a warning on the Duex5 page about this, but you may want to add one. Use good ribbon cables… 🙂

Do you mean the settings that you have set the heaters to? Or do you mean the selections available on the drop down list?

I use macros to set the bed and hot end temperatures for the filaments that I commonly use.

Is there any progress on the G2/G3 commands?

@pcsentinel:

Hi DC42, just found an oddity, for a laugh I did mesh levelling with:
M557 X52:204 Y20:170 S12.5

I then printed 4 x 10mm square 1mm high at the edges of the plate, each of the squares had each layer in the Y direction slipped by about 0.2mm

Odd?

Is it reproducible? If so, feel free to remind me about this about a week from now, when I should have time to look into it.

I think you can adjust autotuning to more agressive temperature rise, even if it leads to a small overshoot.

Thanks for your report, I could reproduce this problem and will fix it in my next DWC release.

Finally got it flashing.

I did what you said but no difference but then I went through all your messages again. I realised VIN-power. I'm using an external 5V and relay to simulate ATX power. I just needed to do a M80 before flashing.

If you use external drivers, then the microstepping is set on the drivers, not in the firmware. So it can be as high as the drivers allow and the Duet can generate steps fast enough for.

Thanks for confirming that. The problem is fixed in the 1.18 release.

That did it - brilliant, all up and running again. Thanks everyone for your patience. Things mechanical, not a problem but the intricacies of programming syntax is best left to those who understand these things.

I will make a note for future reference.

Thanks again,

Mike

that seams to have fixed it , not sure what exactly happened but reinstalling the fw seams to have resolved my issues.
thanks