Awesome I will do the upgrade tomorrow. Thanks again!
Latest posts made by jtroutt19
-
RE: Worth it to upgrade from 2.02 to current?
-
RE: Worth it to upgrade from 2.02 to current?
@Phaedrux said in Worth it to upgrade from 2.02 to current?:
Well you can see the main difference here: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
Overall RRF3 is more flexible in how pins are defined and used. It's also where future development is going so eventually there may be some features you won't get access to. Conditional Gcode is one example already.
Going from 2.02 to 3.1.1 isn't too hard really.
Even if you don't want to go with RRF3 yet you can update to 2.05.1 to at least be up to date with RRF2, which would make it easier to jump to RRF when the time comes.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
Download that zip file and upload it as is to the system tab in DWC. Don't extract it first, just upload it.
If you're curious to see what the config changes look like you can generate a RRF3 config set and compare to your current files.
OK, so with bltouch being setup different. Does where it is plugged in on the board change. Or just how it is defined in the code?
-
RE: Worth it to upgrade from 2.02 to current?
RIght on that helps. I will have to read about condition Gcode. Thank you for your response.
-
Worth it to upgrade from 2.02 to current?
The title says it all. After reading the guide I am a bit intimidated by the upgrading process. What exactly do you gain from upgrading to current firmware?
-
RE: Fan settings not working
Well I think I know the issue. Cura cannot address fans. Being that my blower is P2 and not the default P0 the gcode command being sent wont work. So I think I need to rename my blower fan to P0 in order to get this to work. Well never mind, Seems pwm is not working on fan_0. A bit upsetting.
Is there any way to remap fan_2 and make it fan_0?
-
Fan settings not working
I am wanting to change fan speed according to layer. I have it set up in cura to do this but it doesnt happen when printing. I end up having to change it manually with the slider. Do I have something setup wrong? In the web portal for the printer it also shows three fans which I only have 2. It shows 'Tool Fan' being a fan along with 'Hotend' and 'Blower'
; Configuration file for Duet WiFi (firmware version 1.21) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2 on Wed Apr 17 2019 17:42:43 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Network M550 P"Ender3" ; Set machine name M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drives M569 P0 S0 ; Drive 0 goes backwards M569 P1 S0 ; Drive 1 goes backwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S0 ; Drive 3 goes backwards M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E106.29 ; Set steps per mm M566 X600.00 Y600.00 Z24.00 E300.00 ; Set maximum instantaneous speed changes (mm/min) If bad prints change to 600 M203 X30000.00 Y30000.00 Z800.00 E1500.00 ; Set maximum speeds (mm/min) M201 X500.00 Y500.00 Z100.00 E5000.00 ; Set accelerations (mm/s^2) M906 X500.00 Y500.00 Z500.00 E500.00 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S300 ; Set idle timeout ; Axis Limits M208 X-5.5 Y-10 Z0 S1 ; Set axis minima M208 X243 Y231 Z260 S0 ; Set axis maxima ; Endstops M574 X1 Y1 S1 ; Set active high endstops ; Z-Probe M574 Z1 S2 ; Set endstops controlled by probe M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch M558 P9 H5.0 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds G31 P25 X-40 Y0 Z1.78 ; Set Z probe trigger value, offset and trigger height M557 X50:185 Y50:185 S65 ; Define mesh grid ; Heaters M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0 M143 H0 S120 ; Set temperature limit for heater 0 to 120C M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1 M143 H1 S280 ; Set temperature limit for heater 1 to 280C ; Fans M106 P2 S1 I0 F10 H-1 C"Blower" ; Set fan 0 value, PWM signal inversion and frequency. M106 P1 S.5 I0 F500 H-1 C"Hotend" ; Set fan 1 value, PWM signal inversion and frequency. ; Tools M563 P0 D0 H1 ; 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 ; Automatic power saving M911 S10 R11 P"M911 S10 R11 P""M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss ; Custom settings are not configured ; Miscellaneous ;M501 ; Load saved parameters from non-volatile memory
-
RE: Suddenly Started printing higher than usual
Ahead of ya there. After getting home today I double checked everything. Made sure everything was still tight and square. I couldn't find any issues. But oh well its fixed now.
I am using the Petsfang 5015 mount for the hot end cooling with a noctua fan. The blowers other than being brushless and 24v I have not clue about. I ordered them off amazon and they sent me two. I am currently printing the duct to accommodate one of them. I just didnt know of 2 were ever going to be needed.
I dont know how much cooling I am going to need. Not sure how to even start answering that question.
-
RE: Suddenly Started printing higher than usual
@phaedrux
I reloaded the firmware and the temp is showing correct again.I dont understand how anything has changed. But I added .4 to my trigger height and it now is at the correct height.
Hey while I am here let me ask you. Dual 5015 blowers or just one?
-
RE: Suddenly Started printing higher than usual
I dont get why all of the sudden it started doing this if nothing got changed.
And today my bed is showing 84°c when its cool to the touch....
; called to home all axes ; ; generated by RepRapFirmware Configuration Tool on Sat Sep 29 2018 12:21:44 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 Z2.5 F6000 S2 ; lift Z relative to current position M98 Pdeployprobe.g ; deploy mechanical Z probe G1 S1 X-269 Y-261 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 X5 Y5 F6000 ; go back a few mm G1 S1 X-269 Y-261 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X51 Y20 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 S2 Z2.5 F100 ; lift Z relative to current position ;G90 ; absolute positioning M98 Pretractprobe.g ; retract mechanical Z probe
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool on Sat Sep 29 2018 12:21:44 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 Z2.5 F6000 S2 ; lift Z relative to current position G90 ; absolute positioning G1 X51 Y20 F6000 ; go to first probe point G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 S2 Z2.5 F100 ; lift Z relative to current position ;G90 ; absolute positioning
-
RE: Suddenly Started printing higher than usual
So I get .73 reported in the head position. The very first time I did it it reported back to me in the actual G-Code console. It doesnt do that this go round.
The first time I did this I followed that exact same procedure and that is where the .73 came from. But that exact value gets reported in the head position box for Z if I do it now. Just wanted to reiterate that.