Thanks for your explanations. It turned out to be other issues.
First of all, the fan I used for testing doesn't support PWM, I can get it running by tuning the F parameter, but overall I can't get it running consistently.
Second, it turned out that I accidentally reversed the polarity of my other fans yikes. Luckily no damage.
And at last I can highly recommend adding the H-1 parameter just to ensure it wasn't configured as a fan for a tool.
@Phaedrux said in Issues upgrading to 3.2.2 firmware:
iles, one at a time i
Cool, thanks. I used the tool to create a new config, and then i diffed both configs old and new to see where I forgot something. Machine is moving and not killing itself, and the delta calibration works.
Mesh bed calibration not working yet: Error: G29: No valid grid defined for bed probing
Issue was my M557 command which used a too low S value, I had it set to 5. Now that I set it to 20 it works
@danal said in Delta auto calibration without z probe:
Thank you very much, turned out that I had the wrong delta radius. I thought it's the size of the print bed, so I set it to a safe smaller value. But of course that was completely wrong. I'm now using a proper calculated value.
@alankilian said in Arduino as Z-Probe questions:
The Z_PROBE_MOD pin is an output from the DUet tht can control a servo to deploy a BLTough for example.
Does that mean, I can use that pin, to ouput a servo pwm signal from the duet using the following configuration?
M950 S0 C"zprobe.mod" ; assign GPIO port 0 to heater3 on expansion connector, servo mode
...
M280 P0 S80 ; set 80deg servo position on GPIO port 0
Can I hook that pin up to the Arduino to read the signal issued by the M280 command?
I couldn't find anything using the search. Is it possible to create a custom gcode command for a g-code which doesn't exist yet?
I'd like to create a M601 command which simply executes M226. Is that somehow possible?
[Edit] Nevermind, I just created a M601.g file in the sys folder with the following code
; M601 is the command Prusa printers issue to pause print
; However in duet/reprap firmware that command doesn`t exist
; And therefore we can bind it to the actual reprap pause command which is M226
M226
Well, turned out it was something completely different. I just hooked up the board again and the panel due was blank. Suddenly everything stopped working.
It was also weird, that the Serial port changed. The working one was no. 4, the not working one was no.3. Then I thought ... wait a minute ... I've got two usb ports on my laptop, let's use the other one.
Turned out that connecting the duet to one port works, but connecting the duet to the other one doesn't.
I just used a usb tester. On the working port the duet board consumes about 300mA, on the non working port it consumes only 100mA.
And I thought the usb-port survied that 12V incident a couple of years ago. But even if the fuses seem to have recovered, that port is no longer able to deliver enough power.
So the entire problem all the time was having the duet connected to a broken usb-port which doesn't provide enough power.
Well, seems like my perimeter overlap was so small, that the infill layer didn't properly connect and was "bridging" mid air. I increased the perimeter overlap and now the issue is gone ....
Well, turned out it was something completely different. I just hooked up the board again and the panel due was blank. Suddenly everything stopped working.
It was also weird, that the Serial port changed. The working one was no. 4, the not working one was no.3. Then I thought ... wait a minute ... I've got two usb ports on my laptop, let's use the other one.
Turned out that connecting the duet to one port works, but connecting the duet to the other one doesn't.
I just used a usb tester. On the working port the duet board consumes about 300mA, on the non working port it consumes only 100mA.
And I thought the usb-port survied that 12V incident a couple of years ago. But even if the fuses seem to have recovered, that port is no longer able to deliver enough power.
So the entire problem all the time was having the duet connected to a broken usb-port which doesn't provide enough power.
@phaedrux
WOHOOO finally. Your reflow idea was great. I just used my hot air rework station set it to 350°C and heated the thing up. I saw some vapor/smoke coming (could have been some remaining flux from my soldering attempt).
But now ...
m21
Error: M21: No SD card present
ok
m21
SDHC card mounted in slot 0, capacity 31.91Gb
ok
My panel due is also lighting up now.
Cool, thanks for your help guys
M997 S1 doesn't work, because the file is never found. I put one in the sys, one in the firmware and one in the www directory, I even specified the path myself
m588 S"*"
Failed to reset the WiFi module to factory settings
ok
This is also kinda interesting. Why doesn't that work?
@dc42
Still the same with 3.4.1. When I use 3.4.1 RC2 and run M122 I hear the windows device disconnect sound and I don't get any output at all
@adras
Maybe I broke the firmware, I think at one time I accidentally flashed DuetWifiServer.bin with bossa.
Is there a way to make a complete reset of the processor? Because even after erasing it, my wifi settings are still present. Maybe there's something stuck in the memory somewhere
@jay_s_uk
Yes, it is. Got it from china yikes
@Norder
I copied the files over and over again so many times that I should have gotten it right just by accident. No, files are definitelly in the right place.
@Phaedrux
I just tried the 16gb sd-card from my other printer which also uses a duet board. Also didn't work at all.
What was also weird is that when I connected the working printer via usb to my laptop the panel due turned on (without an sd-card in the duet).
For my new duet board the panel due doesn't turn on.
I also tried resoldering the pins as you can see in the picture. Pin 1 from the left looks a bit weird to me, I'll give it another bit of solder
I've got a new duet 1.04 board, but it seems like I messed up the firmware upgrades.
Right now, it seems like the SD-Card is no longer working. Or at least it seems to be working only during startup. After I got issues with a 64gb SD card which I formated with one partition at 30gb to FAT32, I replaced it with a brand new 32gb sandisk card today which still shows the same issues.
Here's my output from a M122 command:
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3beta3 (2021-04-22 16:27:28) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-958DA-F64T8-6J9DD-3SN6K-K6SR2
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23156
Dynamic ram: 73784 of which 0 recycled
Never used RAM 17476, free system stack 205 words
Tasks: NETWORK(ready,10.0%,461) HEAT(delaying,0.0%,371) Move(notifyWait,0.1%,214) MAIN(running,87.7%,605) IDLE(ready,2.3%,19), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:09 ago, cause: reset button or watchdog
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 130.9, current 177.8, max 187.2
Supply voltage: min 0.0, current 0.0, max 0.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
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, 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 434084813
Slowest loop: 300.01ms; fastest: 0.12ms
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.1ms, 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: 1.36ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- WiFi -
Network state is active
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21RC2
WiFi MAC address 44:17:93:0f:e3:65
WiFi Vcc 2.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 21536
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0
ok
And here are M22 and M21
m22
SD card 0 may now be removed
ok
m21
Error: M21: Cannot initialise SD card 0: Card is unusable
ok
Seems like it's working at first, but then not anymore.
Config.g seems to be loaded during startup, at least I can enable FTP and WIFI which works.
However when I connect via ftp (no user and password), I don't get the directory content in my client, and the YAT interface is spammed with WIFI SPI errors.
Using M501-M503 commands also gives me write errors.
I also can't install firmware using M997 command, since I'm always getting file not found errors.
My Panel Due also doesn't turn on anymore. I can only get it to flicker when I have the erase jumper set.
config.g for reference:
; General preferences
;M575 P1 S1 B57600 ; enable support for PanelDue
M550 P"My Printer" ; set printer name
; Network
M552 S0 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; disable FTP
M586 P2 S1 ; disable Telnet
Does anybody have an idea how I can fix this?
