Dave's the best

@monster-delta How fast should the image load? I've added the splash screen, but it takes almost 7 secs to load (starts from the bottom and goes up). And it waits for a few seconds before disappearing.

Is it possible to make it load the image faster? Can I adjust how long the splash screen remains presented after it loads? I don't mind messing around with the firmware.

Yeah you're all right, I would want it synchronized. I guess though that the solution might be more related to the slicing rather than the firmware.

My preference is to have it only pop up if I press the up arrow - then I could see the historical entries, and hit enter in order to select one. This is basically how Pronterface/Printrun worked and was extremely helpful for me (but it didn't have a popup window - it just autofilled one entry backwards with each arrow press).

@t3p3tony I thought I wasn't, but then checking the g-code, the slicer referenced the unused extruders (setting them to temperature 0). I removed these lines manually and it seems to have fixed it!

@t3p3tony in case I have mounted a tool imperfectly.

Its looking like a wiring issue... If I send the command once, the probability of the peripheral device reacting is low. But then if I hold the enter key down so that it is sent a hundred times rapidly, then at some point during that time, the peripheral acts as if it has received the message. These damn cheap jumper wires!

I tried a different Duet board and put the same 4 folders (and firmware) onto the SD. M997S0 worked fine (whereas the same 4 folders on the previous Duet didn't work).

On closer inspection I saw that the fan fuse was actually broken. I had replaced that fuse a while ago and the new one must have been damaged when inserting it in with pliers. I don't think that is the issue though because I then shorted the fuse manually with a metal piece and M997 still didn't work.

I don't have the time to troubleshoot the anti-M997 Duet board much, but I'm going to classify it as a hardware/electrical issue that probably happened when there was a fan-related short.

@T3P3Tony for the 2.5.1 wifi server, do you mean DuetWifiServer1.23.bin? That is the one I see here:
https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1

I'm using the DuetEthernet by the way, and don't have my internet working currently, so maybe it doesn't matter.

Thanks Tony I'll try that. Will let you know in a day or two, thanks!

I just tried via USB and mac terminal. Same response. M115 works fine. M997S0 just resets the board and the screen has no message or reaction.

Thank you for the suggestion. I downloaded the new Iap4 file, it did not help unfortunately.

I tried replacing the sys folder with a backed up sys file from November which I know had worked back then, but it also has the same result - M997 S0 just restarts the printer instead of installing new firmware.

The SD appears to work fine - I can launch a print or macro from the screen no issues there.

I have internet problems but can try uploading via DWC when it gets fixed. Is that worth a try, or do you think it might be something else? Should I try doing M997 S0 through USB connection? I have been doing it through the screen.

I’m on 2.01 because I had edited the firmware slightly back in those days and didn’t ever upgrade to anything newer. What I’m trying to upload is a modified 2.01 (simple custom gcode modification). I have been doing this for weeks on this Duet but it suddenly stopped working. I’ll try the download what was suggested above, thank you.

The SD card appears to be working correctly. Macros and gcodes are viewable from the screen.

From the screen, M21 outputs "SDHC card mounted in slot 0, capacity 7.95GB" and M39 outputs "SD card in slot 0: capacity 7.95GB free space 7.71Gb, speed 20.00MBytes/sec, cluster size 64kb"

I used to use "M997 S0" from the screen to make the Duet load the new Duet2CombinedFirmware.bin file. Normally the screen would output dialog saying that its installing new firmware.

But instead, it seems like the Duet just power cycles. The behavior appears identical to pressing the STOP button.

Has this happened to anyone before? How did you fix it?

Note I'm using Firmware version 2.01 on DuetEthernet. M997 S0 had been working fine for many months.

Anyway, I've tried the new 2019 q4 major update, and it is not improving the results at all. Still lots of the same error like undefined reference to `pow'. Hmmmm

For all projects except the WiFiServer projects, the files on github set it to {ArmGccPath}. You should not have changed that.

My bad - i was following old instructions that mentioned setting it to /usr/local/bin

Ok they are no all set to gcc-arm-none-eabi-9-2019-q4-major/bin

Still the same errors persist. Here is another example error:

/Users/John/Downloads/gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: ScaraKinematics.cpp:(.text._ZNK15ScaraKinematics21MotorStepsToCartesianEPKlPKfjjPf+0x7e): undefined reference to `sinf'

If I actually go to the paths, I do see the right things in those folders. I'm on Mac by the way, so I wonder if that has anything to do with it?