Duet3 mini5+ Wifi EA die Firmware bleibt nicht im Speicher
-
Hallo nach dem installieren von der Firmware, hat es wohl geklappt, beim nächsten
booten ohne SD Karte, scheint es als währe die Firmware gar nicht in der Steuerung,
das Display hat uhr zustand. -
@Micha-1 said in Duet3 mini5+ Wifi EA die Firmware bleibt nicht im Speicher:
Hallo nach dem installieren von der Firmware, hat es wohl geklappt, beim nächsten
booten ohne SD Karte, scheint es als währe die Firmware gar nicht in der Steuerung,
das Display hat uhr zustand.And In English
Hello after installing the firmware, it probably worked out the next time boot without SD card, it seems as if the firmware is not in the control at all, The display has clock condition.
Are you purposefully attempting to boot without a mounted SD card ?
If so why?
If not (and you cannot connect to the DWC) I would advise that you connect to the board via USB then using a suitable program (E.G. YAT) and send M115 to see what the firmware reports as being.
And also send M122 to see what diagnostic info is displayed to see if the SD card is being mounted or not.
You can follow SD card diagnostic procedures here
Also Please provide a FULL copy of your config.g
Versuchen Sie absichtlich, ohne gemountete SD-Karte zu booten? Wenn ja, warum? Wenn dies nicht der Fall ist (und Sie keine Verbindung zur DWC herstellen können), würde ich empfehlen, dass Sie die Platine über USB mit einem geeigneten Programm (z. B. YAT) verbinden und M115 senden, um zu sehen, was die Firmware meldet. Senden Sie auch M122, um zu sehen, welche Diagnoseinformationen angezeigt werden, um zu sehen, ob die SD-Karte gemountet ist oder nicht. Sie können die SD-Karten-Diagnoseverfahren hier befolgen [Hier] (https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card) Bitte stellen Sie auch eine VOLLSTÄNDIGE Kopie Ihrer config.g zur Verfügung.
-
Is it possible that the installed firmware is defective?
Even after updating from the SD, the firmware does not change
An IP is not created either, the control cannot be reached with DWC, I can only access the control with pronterface.
Would it make sense for me to install new firmware on the controller with Bossa?
Plays?
Just which firmware do you have to install?- Duet3Firmware-Mini5plus.uf2
- Duet3-SDiap32-Mini5plus.bin
- DuetWiFiServer.bin
What function does the file have? DuetWebControl-SD.zip
The Duet3 mini5+ Wifi control
If you would please support me in this
Thanks !m115
SENDING:M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+
FIRMWARE_VERSION: 3.4.0 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-03-15 18:59:17Connecting...
Printer is now online.m122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: X8FMB-6N6KL-K65J0-409ND-26W1Z-77SBQ
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 96528 of which 0 recycled
Never used RAM 41500, free system stack 170 words
Tasks: SBC(notifyWait,0.0%,972) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.0%,123) MAIN(running,99.1%,582) IDLE(ready,0.1%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:21 ago, cause: power up
Last software reset details not available
Error status: 0x00
Error status: 0x00MCU revision 3, ADC conversions started 141657, completed 141657, timed out 0, errs 0
Step timer max interval 1490
MCU temperature: min 19.5, current 24.0, max 24.2
Supply voltage: min 0.4, current 0.9, max 1.0, under voltage events: 0, over voltage events: 0, power good: no
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: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 324918251
Slowest loop: 0.22ms; fastest: 0.00ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock 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 ready with "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 709, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 709/0/0
Tx timeouts 0,0,708,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 0, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
State: 0, disconnects: 0, timeouts: 0, IAP RAM available 0x0f1ec
Buffer RX/TX: 0/0-0, open files: 0 -
@Micha-1 RepRapFirmware benötigt die SD-Karte, da sich darauf sowohl die Konfigurationsdateien (config.g, Macros für homing etc.) als auch die Dateien für das Web Interface befinden.
