Help: Temp Sensors and Homing Issues
-
my z axis is at the top of the printer hitting my z endstop and loud grinding this happens every time i home the z and have to trigger an emergency stop and reset. Wiring is solid All Crimps and Ferrells i can send a current pict.(https://drive.google.com/open?id=1C2ZJ8UMBzF1jl2yiAGesEVCoj4MjkdAC)
-
@94118 said in Help: Temp Sensors and Homing Issues:
my z axis is at the top of the printer hitting my z endstop and loud grinding this happens every time i home the z
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Feb 06 2020 14:52:27 GMT-0800 (Pacific Standard Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current positionAt the start of the homing files there is usually a Z move to lift the Z axis to get it out of the way for travel. perhaps this is what's running it into the endstop?
But if that's the case, then I think you have the direction of the Z motor incorrect, because that Z move should be moving the bed AWAY from the endstop, not into it.
-
okay i just changed the direction of the drive from backward to forward in the
-
BTW does anyone know how to wire an RGBW Led Strip to a duet
-
@94118 said in Help: Temp Sensors and Homing Issues:
okay i just changed the direction of the drive from backward to forward in the
And did that fix it?
M126 S[fan_speed_pwm] M140 S[bed0_temperature] P0 M134 P0 ; stabilize bed temperature M104 S[extruder0_temperature] H1 M133 H1 ; stabilize extruder temperature G130 X127 Y127 Z40 A127 B127 ; default stepper Vrefs A0 ; zero extruder G1 Z0.4 ; position nozzle G1 E25 F300 ; purge nozzle G1 X-115 Y-65 Z0.15 F1200 ; slow wipe G1 X-110 Y-60 Z0.5 F1200 ; lift G92 A0 ; zero extruderDo you actually have all that as part of your config.g?
-
@94118 said in Help: Temp Sensors and Homing Issues:
Yes it is part of the Priming and Purge code for the hotend when it was on my FFC
-
it was running Sailfish on a mightyboard and it worked
-
Some of those gcodes aren't supported in reprapfirmware. (M134, M133, G130) And the extruder in RRF is E, not A and B.
It would be best practice to not have heating and axis movement commands in config.g since it is executed at startup.
-
ok i will rework the config.g file
-
console.txt Temp sensors register via RRF Ver 3.0
Please see the enclosed file for errors in motor phases.
-
Now i cannot update the firmware for the paneldue 5i BOSSA software does not see the panel in windows 10 drivers database. I now have a blank white screen. Still have not seen any replies about the homing issues cause DWC states when i command the home buttons it states Insufficient Axis Homing and also my heaters tend to fail when i run the auto tune command. I Need so advice please!
-
Post your current config files please.
For the PanelDue, did you have it detected at one point and it no longer detects? Try a different USB cable/port/pc.
I assume you're using this for updating steps? https://duet3d.dozuki.com/Wiki/PanelDue_Firmware_update
For the rgb leds take a look here: https://forum.duet3d.com/search?term=rgb&in=titlesposts
What exactly is the homing problem currently? For the insufficient axis take a look at this and see if it matches your situation: https://duet3d.dozuki.com/Wiki/FAQ#Section_I_get_this_error_message_Error_G0_G1_insufficient_axes_homed
What error do you get when you try and tune the heaters? What command are you using the tune them?
-
My Current Config File:
Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Feb 08 2020 14:13:05 GMT-0800 (Pacific Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Flashforge Creator" ; set printer name ; 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 backwards M569 P1 S1 ; physical drive 1 goes backwards M569 P2 S0 ; 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 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 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 S0 P"xstop" ; configure active-low endstop for low end on X via pin xstop M574 Y2 S0 P"ystop" ; configure active-low endstop for high end on Y via pin ystop M574 Z1 S0 P"zstop" ; configure active-low endstop for low end on Z via pin zstop ; 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"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 M143 H0 S150 ; set temperature limit for heater 0 to 150C M307 H0 B0 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"spi.cs1" Y"thermocouple-max31856" ; configure sensor 1 as thermocouple via CS pin spi.cs1 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S230 ; set temperature limit for heater 1 to 230C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; 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 definedAuto tuning Failure Heaters did not reach peak temp after step 2
BOSSA Refuses to find my com port for the panel due i have tried different cables also knowing that it might be a connection issue Windows listed it as USB Generic Host but was not seen in BOOSA as a comm port.
-
I got my panel reflashed Successfully Still does not show reads from duet board
-
@94118 said in Help: Temp Sensors and Homing Issues:
I got my panel reflashed Successfully Still does not show reads from duet board
How is it connected?
-
Please post your homing files as well.
-
; homeall.g ; called to home all axes M98 Phomex.g; Calls to the file homex.g M98 Phomey.g; Calls to the file homey.g M98 Phomez.g; Calls to the file homez.g; homex.g ; called to home the X axis M913 X30; Set X motor current to 30% of its normal current to avoid ramming in case of crash G91; Switch to relative positioning G1 Z5 F300; Lower bed by 5[mm] in travel speed 5[mm/sec] to avoid crashing ; First pass (Corse movement) G91; Switch to relative positioning G1 X-295 F1200 S1; Move X axis to towards the endstop at travel speed of 25[mm/sec] (F1500) stop when endstop triggers (S1) G92 X0; Set X to home positions ; Go back a few mm G1 X5 F600; Move X axis by 5[mm] ; Second pass (Fine movement) G1 X-10 F300 S1; Move X axis to towards the endstop at travel speed of 6[mm/sec] (F360) stop when endstop triggers (S1) G92 X0; Set X to home position G90; Switch to absolute positioning M913 X100; Reset X motor current to normal current; homey.g ; called to home the Y axis M913 Y40; Set Y motor current to 40% of its normal current, to avoid ramming in case of crash ; First pass (Coarse movement) G91; Switch to relative positioning G1 Y-165 F1200 S1; Move Y-axis to towards the endstop, at travel speed of 20[mm/sec] (F1200), stop when endstop triggers (S1) G92 Y0; Set current Y-axis position to home position G1 Y5 F600; Move back Y-axis by 5[mm] ; Second pass (Fine movement) G1 Y-8 F300 S1; Move Y-axis to towards the endstop, at travel speed of 6[mm/sec] (F360), stop when endstop triggers (S1) G92 Y0; Set Y position to home position G90; Switch to absolute positioning M913 Y100; Reset Y motor current to normal current 100%; homez.g ; called to home the Z axis ; Prepare for Z-axis homing M913 Z80; Set Z motor current to 80% of its normal current, to avoid ramming in case of crash G91; Switch to relative positioning G1 Z5 F300; Move bed 5[mm] down, at travel speed 5[mm/sec], to avoid nozzle crash in case the bed is above the nozzle G90; Switch to Absolute positioning G1 X120 Y70 F3000; Move carriage to bed center, at travel speed 50[mm/sec] ; Home Z-axis G91; Switch to relative positioning G1 Z-175 F240 S1; Raise bed all the way up, at travel speed 5[mm/sec], stop when hit the endstop (S1) G1 Z3 s1; Lower bed by 3[mm] G92 Z6; Set Z position G90; Switch to absolute positioning M913 Z100; Set Z motor current back to 100%https://drive.google.com/open?id=1DM7rDGNchCwpNt-39v5gZfGMFRHqOjn3
https://drive.google.com/open?id=1DLPIYKRbN8US3hoOfUVw61BeYE6xptRiAll Homing files plus Picts of Current setup and wiring
-
A couple notes.
You don't need to use G92 to set the axis position after homing. When the endstop is triggered during a homing move it will automatically set the position to either the axis minima or maxima as defined by M208. I suggest you remove the G92s from homex and homey. You can use them in homez if you wish.
For homing moves you're using S1, in recent firmware versions it's now recommended to use H1 instead.
Your homey.g is moving the axis to the negative, but your endstop position is defined in your config.g as being at the positive end.
M574 Y2. So confirm where your Y endstop is, and make sure your homing move direction is correct. Assuming that 0,0 is the front left corner, Y+ would move towards the back of the machine. and M574 Y2 would indicate that the endstop is also at the back of the machine. But your homing move is negative. If a negative move is moving towards the back of the machine, you'll need to change the motor rotation inM569 P1 S1to beM569 P1 S0.In your homez you have a Z move at the start to lift the head, but you don't have the H2/S2 switch to allow you to move an axis before the axis is homed. Then later in the file you have G1 Z3 S1 after the axis has already been homed, but now it's moving away from the endstop, so will never hit it.
-
Homing is still problematic:
https://drive.google.com/open?id=1DQIW6JYFjs98MKeYba2B8x68rQdA3NQP
https://drive.google.com/open?id=1DSTCgvE8K6eaykKuqAlEWPQI_KsIg7DNPanel still states (Not Connecting) When i got it New from 3d Printed Solid it was able to connect. i think it might be a baud speed issue i read in some posts that the panel tries to connect 203600 when it is supposed to be 57600.
-
2/20/2020, 9:00:45 AM: Connected to 192.168.0.133 2/20/2020, 9:01:04 AM: G28 X: Error: G0/G1: insufficient axes homed 2/20/2020, 9:01:57 AM: G28 Y: Error: Bad command: [/c] 2/20/2020, 9:02:04 AM: G28 Z: Error: G0/G1: insufficient axes homedThe G28 X and G28 Z error states that you're trying to move an axis before it's homed. I pointed out in my last post why that happens.
The G28 Y error indicates that you have a
[/c]somewhere in your file that shouldn't be there. Probably a copy and paste error.Please repost your homing files as they currently are.
