New firmware release 1.16rc2
-
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.
-
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, I loaded the on the SD card and that did the trick. I am up and back to printing.
-
Chrishamm has kindly fixed this in DWC 1.13rc3, which I have just added to the Release folders of my RepRapFirmware repository.
I download DWC 1.13rc3 and install in my duet and I try it and now it works!!!
Thank you Chrishamm and dc42 !!!!!!!!
-
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…
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.
Is your bltouch working properly? If so then maybe a 3.3V drive signal would be enough for it, which means you could dispense with the inverter/level shifter and use inverted PWM.
I see that the bltouch instructions say you need to add an external 240 ohm resistor on the output for 3.3V electronics.
-
Is your bltouch working properly? If so then maybe a 3.3V drive signal would be enough for it, which means you could dispense with the inverter/level shifter and use inverted PWM.
I see that the bltouch instructions say you need to add an external 240 ohm resistor on the output for 3.3V electronics.
I haven't had a chance go any further with my testing yet. I'm in the process of modifying the Ord Bot extruder carriage to allow the use of Prusa type extruder mounts. This will open the printer up to a large variety of BLTouch mounts and part fan designs that I didn't have available to the less-common Ord Bot carriage design.
I will certainly follow up once I make more progress throughout the week.
-
Something wrong with time in M122 command output:
Current date and time: 2016-11-08 16:31:37
But current computer clock is 16:44.
My config:
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.16rc2 (2016-11-05)
WiFi Server Version: 1.02
Web Interface Version: 1.13-rc3 -
As there is no 32kHz crystal on the Duet WiFi, the RTC (real time clock) is driven by the internal RC oscillator, which is not very accurate. I thought that the RTC was synced with DWC every time you connect in DWC, but from testing it appears that it only gets synced the first time you connect DWC after starting the Duet.
The RTC is not used for anything yet, so it doesn't matter that it runs slow (the time stamps for uploaded files are passed separately by DWC). The RTC will be used for time stamping log entries in a later firmware version, but before that I will add code to correct the RTC periodically using the main clock frequency as a reference.
-
Thank you for your answer. For internet-enabled setups it's also possible to use NTP from ESP8266 side.
