At no point I was so rude to argue ad personam like you.
And everything you say about me, tells people a lot about you but nothing about me.
I had not the best days recently.
And my original board is fully functioning and I can turn back any day, if I like.
But I wanted to install that super firmware on one of the extremly good Duet3d boards to see, my printer functioning much better.
I fell for a guy, who did clickbait on youtube.
I am sure that I will not stick with Duet3d hardware. Reprap firmware is so convoluted that I must admit it was a mistake trying to install.
anyway what ever it is, it needs to stop the movement if installed. And i find no solution for this.
Also the printer does not move up when running as a probe and just stays down and forces the probe along the bed
I just want to install a firmware not learn a complicated, non or bad documented ecosystem made by people who do not care about customer experiences.
crimped it for the other slot but does not work either...
by the way I could not even google anywhere if green or blue is grnd.
I think I had it wrong.
days of work - if I give me a low salary of 20 bucks for every hour spend on this, I better buy a bambolab now... it will be cheaper
interesting: there is a dedicated probe slot on the board but with four pins... which means crimping
probably then it will work without all that defining of e1_stop or e1stop to a probe. Which I could not figure out if it is with _ or not with the documentation.
e1stop or e1_stop
documentation... no info on the wiring documentation...
I had reverted it and now fan and wifi stay on.
But still even with
M574 Z1 P"e1_stop" S2 ; Z-Probe
or
M574 Z2 P"e1_stop" S2 ; Z-Probe
the probe does not stop Z-movement in any way...
maybe this behaviour is defined somewhere else...
I am so far now, that I have the Z-Probe kind a working...
but it does not stop Z-movement but WLAN and fans.
I am sure, that I will get this working somehow. But oh boy...
This is not fun.
Doing everything by gcode and then not getting a gcode syntax and some examples when searching but long text that have nothing to do with figuring out what the existing commands mean...
The only thing that I do like, is the wifi and web interface.
It may be nice, once the printer is configured to just send the files, without having to target small sd card slots.
Also the editor inside and the refresh is nice to have.
But it would even be nicer if you could mark a gcode number and get the syntax with description of the parameters like in a programming interface.
It takes minutes to google the commands each time and scroll to the relevant part of information.
Back to the endstop... go through every file to find something suspicous connected to e0-stop that may be changed to something with Z instead of Fan and Wifi...
great thanks.
my printer is not there, but at least some effort to provide something for a few printers.
I bought it on the equivalent of craigslist...
Had bought the firmware for my maschine from a guy on youtube, who has not delivered but taken the money.
Someone who did praised Duet to the extreme. Probably got some boards for free...
Is there a page with firmware for the most common printers like ender 3, prusa and so on?
Or is this meant, that everyone should invest maximum time to do again, what others have done before?
old post are to find solutions for problems solved...
The answers may be somewhere else, but the search function on this side is not showing any relevant hits, when I search..
I wish I knew before installing the board.
A lot of Post are linked to a not existing wiki in dozuki.com
What is this kind of stupid, to post solutions to a place, that does not provide after only one or two years?
Who is leading this Duet3 buisness like this?
Worst first impression of a company in years.
you just closed two of my threads... if this is your hobby, then be it...
But however I have written to Duet3D and demand compensation for their moderator linikng files that bricked my board. Can t be that they not tested it and bricked another board 2 years before without removing the faulty firmware in the meantime.
I just followed your instructions and it bricked the device.
You want to fuck me now?
It will cost you more than my device in the future, I will not forget and tell everyone about your way damaging things and standing in for the repair.
Maybe I even will make a vid about it.
I hope you go broke with this kind of support.
what about I send you my board and I get it back with the newest firmware installed at your cost?
why cant your firmware function when uploaded, are we in the stoneage here?
I mean you take premium prices for this shit and then it just should work every time.
does not work
m552 s0
ok
m977 s1
Warning: M977: Command is not supported
ok
m991 s1
Warning: M991: Command is not supported
ok
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok
Hello,
I tried to get my firmware upgraded, but have a bricked board now.
What can I do to repair the damage caused following the instructions of the support?
Duet 2 wifi - " another SPI transfer is pending"
Kind regards
Martin
m552 s1
Turn off the current WiFi mode before selecting a new one
ok
Warning: VIN under-voltage event (9.3V)[Warning: 1 byte already buffered but not sent anymore.][Warning: 5 bytes already buffered but not sent anymore.]
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
m552
WiFi module is being started
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
Warning: VIN under-voltage event (9.4V)Warning: VIN under-voltage event (9.4V)
m587
m587
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
m552
WiFi module is being started
ok
m552 s1
Turn off the current WiFi mode before selecting a new one
ok
m112
Emergency Stop! Reset the controller to continue.
ok
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
m552
WiFi module is being started
ok
m552 s0
ok
m552
WiFi module is being started
ok
m552 s1
Turn off the current WiFi mode before selecting a new one
ok
m552 s0
m552 s0[Warning: 8 bytes already buffered but not sent anymore.]
m552
WiFi module is being started
ok
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6JTD4-3SN6T-1TXV8
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 73064 of which 300 recycled
Never used RAM 17176, free system stack 168 words
Tasks: NETWORK(ready,7.9%,521) HEAT(suspended,0.0%,386) MAIN(running,91.9%,458) IDLE(ready,0.1%,29), total 99.9%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:22:59 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 0
MCU temperature: min 22.7, current 24.6, max 25.4
Supply voltage: min 2.0, current 26.5, max 26.5, under voltage events: 2, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 34982, standstill, SG min/max not available
Driver 1: position 34982, standstill, SG min/max not available
Driver 2: position 34982, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 101.36ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.25ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8