Apologies if this was addressed before but I was wondering why the choice of using the 5160 and it's built-in encoder input was not used?
Posts made by madmattco
-
RE: Duet3D 1HCL - Closed Loop Controller Beta test
-
RE: Toolboard fan rpm reading
@Phaedrux Yes it is. Glass beaded pa-12
-
Toolboard fan rpm reading
Greetings programs.
I was wondering if anyone had encountered any problems with fam rpm signals not showing properly. I know its nothing to be concerned about, but for those of us who have a touch of the ocd, well then you will know what I am talking about.
When on 100%, fam rpm is correct. But anywhere in-between 1-99%, my values are horrifically overpowered. These values are skewed on both out1 and out2 if I try said fan on those channels. I am starting to think its just the quality of the tach sensor inside the fan as my noctua does not show any of these signs. Pictures will be attached below.
My current fan section looks like this.
; Fans
M950 F0 C"121.out2+out2.tach" Q500
M106 P0 S0 H-1
M950 F1 C"!121.out1+out1.tach" Q500
M106 P1 S1 H1 I0 T50 F25000The fan I am using for my part cooling is this one: http://www.nidecpg.com/fanpdfs/gamma26.pdf
I have the A33998-58 variant
-
RE: Duet 3 with SBC and 5V fan
I am using one of these to power it all.
https://www.amazon.com/gp/product/B07ZQB6S3L
5v feed to the duet3 is also disabled
-
RE: Duet 3 with SBC and 5V fan
@bearer
https://www.amazon.com/gp/product/B07R45W1LN this is the top board
https://www.amazon.com/gp/product/B07MCW4KCM this is the right angle pin adapter
And if you're interested, this is the nvme adapter im using
-
RE: Tool board pwm header
I got it working after a reboot. But now I have another problem.
My hotend fan is running even though it is supposed to be under thermostatic control.
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Apr 05 2020 04:11:56 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"FT-6" ; set printer name ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S0 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P121.0 S0 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E121.0 ; set drive mapping M350 X256 Y256 Z16 E16 I1 ; configure microstepping with interpolation M92 X1280.00 Y1280.00 Z720.00 E409.00 ; set steps per mm M566 X900.00 Y900.00 Z6.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z150.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z10.00 E250.00 ; set accelerations (mm/s^2) M906 X1200 Y800 Z1500 E750 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X690 Y330 Z400 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!io0.in" ; configure active-low endstop for low end on X via pin io0.in M574 Y1 S1 P"!io1.in" ; configure active-low endstop for low end on Y via pin io1.in ;M574 Z1 S1 P"^io2.in" ; configure active-low endstop for low end on Z via pin io2.in ; Z-Probe M558 P8 C"121.io1.in" H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:650 Y15:300 S100 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"121.out0" T1 ; create nozzle heater output on out1 and map it to sensor 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"121.out2+out2.tach" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"121.out1+out1.tach" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 S1 H1 T50 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C G31 P500 X-23.5 Y-24.5 Z1.85 ; Probe offsets ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory
When the hotend reaches 50 degrees the fan actually turns off
-
RE: Tool board pwm header
@dc42 Can you not use 2 tacho signals at the same time?
; Fans
M950 F0 C"121.out2+out2.tach" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"121.out1+out1.tach" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 S1 H1 T50 ; set fan 1 value. Thermostatic control is turned on -
Tool board pwm header
I was looking at replacing my regular heat sink fan with a pwm model. I looked up the wiring from noctua and they list the pwm signal at 5v. The tool board wiring diagram lists the pwm as 12v. I assume I won't be able to use a 4 wire fan, but instead will have to use a regular 3 pin or just use 2 pins for power it?
-
RE: DuetPi DWC differences
@chrishamm said in DuetPi DWC differences:
@chas2706 Clear your browser cache or try force-refreshing the page by pressing Ctrl+Shift+R in DWC and you should be good to go.
All is well now. Thank you
-
RE: DuetPi DWC differences
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 2.2.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.01-RC12 (2020-05-06b1)Duet Web Control 2.1.7
-
DuetPi DWC differences
Has anyone noticed, when using a display on the pi, that the heater messages are showing calls instead of actual text? Also fan rpm section has an added reading.
-
RE: Tool board configuration
@Danal That worked for me sir. Cheers
-
RE: Tool board configuration
@Danal You wouldnt happen to have a bl-touch on your toolboard would you?
-
RE: Tool board configuration
@dc42 I am using the firmware you posted the other day. https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC12
My problem ended up being the wrong temp sensor connector.
I was also wondering if everything is in place to have a bl-touch running off of the IO_0 port on the tool board.
-
Tool board configuration
Evening all. I hooked up my tool board this evening to update the firmware. After some fiddling with the can bus wiring, I got it to update. Then I started working on my config.g to read the sensors from the tool board. This is where I am having some troubles.
I was using examples from https://miscsolutions.wordpress.com/2020/03/04/converting-the-e3d-tool-changer-to-duet-3-with-hemera-tools-part-2/
This is my config.g file currently. I have left the default can bus address of 121 set.
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Apr 05 2020 04:11:56 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P121.0 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E121.0 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X1200 Y800 Z1500 E750 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X690 Y330 Z400 S0 ; set axis maxima ; Endstops M574 X1 S0 P"io0.in" ; configure active-low endstop for low end on X via pin io0.in M574 Y1 S0 P"io1.in" ; configure active-low endstop for low end on Y via pin io1.in M574 Z1 S0 P"io2.in" ; configure active-low endstop for low end on Z via pin io2.in ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"121.temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"121.out0" T1 ; create nozzle heater output on out1 and map it to sensor 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"121.out1" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"121.out2" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory
As you can see, my extruder temp is still showing nothing. Any ideas to remedy this?
Thank you. Also, all firmwares are up to date.
-
Missing dsf version from repo
Apologies if this is in the wrong section. I was updating to the latest rc version that DC42 released a few days ago. I saw in the notes to upgrade to 1.3.0 dsf. but only 1.2.4 was showing on the repo. I did the obligatory apt update and even did an apt search but never found it. I did find the latest unstable version though when i switched branches. Was 1.3.0 removed for any particular reason?