New firmware release 1.16rc2
-
I have just released this at https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge. For a full list of changes and upgrade notes since 1.15e, see https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW. This version works best with chrishamm's DWC 1.13rc1 which I have put in the same location.
Please report any bugs you find in it in this thread. The issues that I already know about are:
- When you edit and save the config.g file, DWC no longer asks you if you want to restart the Duet.
- After you edit a macro or a system file in DWC, the Last Modified date/time shown for that file in the files list is not updated until you click the Refresh icon.
Issues fixed since RC1 include:
- AJAX errors if you have a lot of files (typically more than 40) in the /gcodes folder on a Duet 0.6 or 0.8.5
- M42 and M280 commands not working with unused heater channels on a Duet 0.6 nor 0.8.5
-
It looked like it did update to latest firmware however the system screen still shows previous update
Software Information
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Version: 1.15e (2016-10-02)
WiFi Server Version: 1.02
Web Interface Version: 1.12
Web Interface by Christian Hammacher
Licensed under the terms of the GPL vFiles in System directory:
DuetWebControl-1.13-rc1.bin 3.0 MiB
DuetWebControl.bin 3.0 MiB
DuetWiFiFirmware-1.16rc2.bin 248.7 KiB
DuetWiFiServer-1.02.bin 288.3 KiB
DuetWiFiServer.bin -
Thanks David! So I am getting a PWM (or technically PPM in this case) signal on the heater pins now, but it's in 1ms frames rather than the typical 20ms most hobby servos expect.
Is the frequency something I need to configure, or can the firmware simply default to 20ms when M280 is used since that's what servos expect anyway?
The top trace is the signal as it is on the Duet expansion header, the bottom trace is the signal inverted with a small N-channel MOSFET which I have connected to the servo.
-
Just updated to this version. What does this mean for just homed delta printer and still energized at 100% steppers?
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstillDuring long vertical movement to X0 Y0 Z1:
Driver 0: ok
Driver 1: ok
Driver 2: ok
Driver 3: stalled standstillAnd after movement to X0 Y0 Z1:
Driver 0: stalled standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: stalled standstillSeems like this values a bit random for me at this moment (values changing randomly depending on motor position). Or I'm doing something wrong?
Also turned off motors (M84 command) does not change driver's status. -
The stall detection threshold has to be tuned to match the motors and it is not reliable at low speeds. So you can ignore the stall status. The OK status just means that nothing else was reported. Other status items that can be reported are temperature warning, temperature shutdown, short to ground, and open load.
-
Any thoughts on my observation? I'm not getting any servo movement from the 1khz signal, but I'm certain slowing it to 50hz would do the trick.
-
It looked like it did update to latest firmware however the system screen still shows previous update
Software Information
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Version: 1.15e (2016-10-02)
WiFi Server Version: 1.02
Web Interface Version: 1.12
Web Interface by Christian Hammacher
Licensed under the terms of the GPL vFiles in System directory:
DuetWebControl-1.13-rc1.bin 3.0 MiB
DuetWebControl.bin 3.0 MiB
DuetWiFiFirmware-1.16rc2.bin 248.7 KiB
DuetWiFiServer-1.02.bin 288.3 KiB
DuetWiFiServer.binIt looks like the update failed. Did you update over the web interface? If instead you copied the files directly on to the SD card on a PC, then you need to rename them to DuetWiFiFirmware.bin and DuetWebControl.bin before running M997 S0 and M997 s2.
-
Thanks David! So I am getting a PWM (or technically PPM in this case) signal on the heater pins now, but it's in 1ms frames rather than the typical 20ms most hobby servos expect.
Is the frequency something I need to configure, or can the firmware simply default to 20ms when M280 is used since that's what servos expect anyway?
The top trace is the signal as it is on the Duet expansion header, the bottom trace is the signal inverted with a small N-channel MOSFET which I have connected to the servo.
I'm sorry, I missed this post earlier. Which heater channel are you using? I am getting 20ms repeat interval in my tests, but I haven't tried every heater channel yet. Also, it is a Duet WiFi or a wired Duet?
-
Where can I download chrishamm's DWC 1.13rc1 for Duet 0.8.5? in chrishamm github the newest version is 1.12
-
No problem! It's a Duet 0.6 and I'm using heater 3 which is pin 21 on the expansion header.
I setup the pin for PWM using the following in config.g:
[c]M307 H3 A-1 C-1 D-1 ; Make Heater 3 (Exp Pin 21) available for PWM use[/c]
And commanding a servo angle using [c]M280 P3 S90[/c]
I'm sorry, I missed this post earlier. Which heater channel are you using? I am getting 20ms repeat interval in my tests, but I haven't tried every heater channel yet. Also, it is a Duet WiFi or a wired Duet?
-
Where can I download chrishamm's DWC 1.13rc1 for Duet 0.8.5? in chrishamm github the newest version is 1.12
It's at https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-0.6-0.8.5/Edge alongside the firmware.
-
No problem! It's a Duet 0.6 and I'm using heater 3 which is pin 21 on the expansion header.
I setup the pin for PWM using the following in config.g:
[c]M307 H3 A-1 C-1 D-1 ; Make Heater 3 (Exp Pin 21) available for PWM use[/c]
And commanding a servo angle using [c]M280 P3 S90[/c]
I'm sorry, I missed this post earlier. Which heater channel are you using? I am getting 20ms repeat interval in my tests, but I haven't tried every heater channel yet. Also, it is a Duet WiFi or a wired Duet?
OK, I just tested all 5 external heaters on a Duet WiFi and they all have 20ms period, but I didn't check the interval on the wired Duet. I'll do that next.
-
Excellent, thank you for all your hard work!
OK, I just tested all 5 external heaters on a Duet WiFi and they all have 20ms period, but I didn't check the interval on the wired Duet. I'll do that next.
-
Where can I download chrishamm's DWC 1.13rc1 for Duet 0.8.5? in chrishamm github the newest version is 1.12
It's at https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-0.6-0.8.5/Edge alongside the firmware.
Thank You!!
-
I have just released 1.16rc3 for the wired Duet only to correct this issue. Thanks for reporting it.
-
I'm heading over to my bench to try this out now, thanks!!
I have just released 1.16rc3 for the wired Duet only to correct this issue. Thanks for reporting it.
-
Perfect, that did the trick! I'm now able to control a BLtouch using M280. Thanks! Now to mount it on my ORD Bot and figure out how to setup Z-probing with a servo activated switch…
https://www.youtube.com/watch?v=W2N8Pkw_umM
Timing looks great… The voltage of the inverted signal is a little low due to the BLtouch dragging down the 100K pull-up resistor, but it doesn't seem to matter.
-
100K is a very high value for a pullup resistor on an output. Try 4.7K.
-
I hav Duet 0.8.5 I upload 1.16rc3 firmware and DWC 1.13rc1 and I have a problem:
When I upload a gcode using Upload&Print button DWC gives me the error (I don't know if DWC or the firmware adds a "s/" in the begining of the filename )M32 s/GCODE_FILE_NAME.gcode
Failed to open
-
Chrishamm has kindly fixed this in DWC 1.13rc3, which I have just added to the Release folders of my RepRapFirmware repository.
