E 3d BIGBOX Duel head
-
@testpro If you chose CoreXY in the configuration tool originally, then yes, it would be better to go back through and generate a new set as Cartesian. Can you post a picture of the contents of the sys folder on the SD card? I'm wondering if you have other files left in the folder that may be conflicting. It may be best to delete all the files in the sys folder before uploading the new set.
Also, you can compare your config with the one here, which is a known-working config for an E3d BigBox: https://forum.duet3d.com/post/175431
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
Homing files should still be ok since they are based on the position of the endstops, but you may need to double check that the motors are turning in the correct direction to move the axis left or right front or back as expected.
-
@droftarts
ok done a comparison and changed several things but result has not changed. So deleted all files new make new files and reload and see what happens. any advice on new files? -
@testpro You could start by using the config.json file from this post in the configuration tool: https://forum.duet3d.com/post/174892
Do this by downloading the json file, then click on 'use existing configuration' in the configuration tool (bottom of first page) and select the json file.
That generated the config set for that machine, and should be mostly right for your machine. The caveat applies that I don't know how different your machine is from that one; for example, it was fitted with an IR probe for Z homing and mesh compensation. So check carefully.
Ian
-
@droftarts
Ok i have cleaned out the files several times and replaced with new set of files and i am getting the same thing.ok for drives moving in the right directions, i will home each axis and then on touchscreen i will go to move and state if negative and direction it moved when pushed.
X moves left to right and X -10 move left, while X +10 moves right
Y moves front and back and Y -10 moves front of machine while Y +10 move to back of machine.
Z move up and down and Z -10 moves up while Z +10 moves down.
Now as far as i know this seems to work well it just seems like that X axis is moving while the Y axis is moving as well. it this supposed to happen?
-
@testpro said in E 3d BIGBOX Duel head:
X axis is moving while the Y axis is moving as well. it this supposed to happen?
Are you still set to corexy mode?
-
@phaedrux i believe with what i had did last plus in the original program commented out the command to corexy mode. so i am going to say we should be out of this coryexy
-
Can you post your current config and homing files?
-
@phaedrux
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"big 3d box 1" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.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 X800 Y800 Z800 E800 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 X230 Y210 Z200 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z2 S2 ; configure Z-probe endstop for high end on Z; Z-Probe
M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X5 Y5 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 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
M575 P1 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-235 Y-215 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-235 ; home X axis
G1 H1 Y-215 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-215 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X10 Y10 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 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-235 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y-215 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 H1 Y-215 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X10 Y10 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 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@testpro said in E 3d BIGBOX Duel head:
M669 K1 ; select CoreXY mode
You're still in corexy mode. Remove that line. It's not a corexy printer.
-
@phaedrux Well crap! i thought i had this figured out. So i commented out the M669 K1 command.
but i have noticed the date for the program 25MAY2021, i done this program on Thursday night 27th.
So how do i know i have erased the old program and how to put in the new one might be a thing to cover.
-
Where are you looking to get these config files?
All the system config files are in the /sys/ folder on the SD card and can be viewed in the web interface in the system tab. Whatever you see in there is what is being used at startup.
To change the files you'd either edit the config files directly in the web interface, or upload a replacement copy of the file.
Maybe this helps, since most of the interaction with the printer will be through the web interface.
https://duet3d.dozuki.com/Wiki/Duet_Web_Control_v2_and_v3_(DWC)_Manual
-
@phaedrux ok i have gone over the program again and this time i changed the name to the printer.
now when i uploaded the new file and then opened it to make sure it was there and then saved it. then restarted the machine and old name for the printer is there. not the new name so i think i am not over ridding the old file.
-
Can you post a photo of your system tab? Are your files tucked inside another folder?
-
@phaedrux
I went to system tab and files are listed there. which i did not know. I was going to Display tab and changing things there. But now that i have changed the file Config.g.bak file and restarted everything and now works for homing without jumping after i reversed the wires for the stepper motor. so now all homes well with no issues.Now the PID for the heaters does not seem to work or heat up when bed and tool0 are set to a temp for active.
here are the files which are being used now.
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"big box 1" ; set printer name ;M669 K1 ; select CoreXY mode ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.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 X800 Y800 Z800 E800 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 X460 Y210 Z200 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z2 S2 ; configure Z-probe endstop for high end on Z ; Z-Probe ;M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds M558 P5 C"e0stop" H5 F120 T3000 ; Z probe connected to E0 endstop input M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X5 Y5 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 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 M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
@testpro said in E 3d BIGBOX Duel head:
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
You should remove that line I think. You don't have a delta. That's for sure.
@testpro said in E 3d BIGBOX Duel head:
But now that i have changed the file Config.g.bak file
What exactly do you mean by that?
@testpro said in E 3d BIGBOX Duel head:
Now the PID for the heaters does not seem to work or heat up when bed and tool0 are set to a temp for active.
What do you mean by that? How are you trying to set a temp? Have you done a PID tune and saved it with M500?
Send M98 P"config.g" and report any errors.
-
@phaedrux
1 yes i will remove the M558 H30 from program.2 i changed the config.g.bak file to not have the corexy setup.
3 on the dashboard tab in software it list tools like tool0 and bed and if you click where is states active for either tool0 or bed it sets a temperature and then click on the heater 1 or heater 0 to make them active, standby or off. they toggle as you click.
ok so far we are doing good the printer now homes with no skipping.
next issues are the heater bed does not heat up fast enough (you gave me something on that, so i will back tract and get that done.)
Leveling the bed
getting material to extrude
calibration of extruder with bed
how to print the stl file
thank you for all your help so far learning a lot but there is more to go.
any insights on these?
-
@testpro said in E 3d BIGBOX Duel head:
i changed the config.g.bak file to not have the corexy setup.
The .bak file is the backup of the main config.g file. It gets created each time the config.g file is changed so that you can undo your change if need be from the backup.
All edits should happen to config.g since it's the file that gets loaded at startup.
You can try following along with this guide
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40
-
@phaedrux will under systems i have a config.g.bak file and a config.override.g file and a config.json file
but there is not config.g file by itself. this is wrong right?second the extruder and bed pid turned fine and thank you for that. but now when i feed in a 1.75 ABS filament and it goes in just fine problem is it is not coming our the end. i think maybe the heat is to low?
i used a IR temp gun to read temp of aluminum block (with out fan running) and it reads in the 30's on the surface and when i turned tool0 temp up to 275 c the surface temp is reading 43 C so i know the heater is working but how do i know it has the correct temperature reading. How would i go about making sure what the reading states is actually correct?still working on level of bed and calibrate nozzle with bed for printing.
-
@testpro said in E 3d BIGBOX Duel head:
i have a config.g.bak file and a config.override.g file and a config.json file
but there is not config.g file by itself. this is wrong right?Sounds like the config.g is missing and it's probably falling back to config.g.bak. Right click on config.g.bak and download a copy of it as a backup. Then create a new file called config.g and then copy and paste the contents of config.g.bak into it. Then you'll be back to normal.
Any future edits should happen in config.g
