@phaedrux
I did check my extrusion calibration and it's spot on. I tried with a couple of prints I found on thingaverse and got some okay prints but near the hole and starting the next layer it was under extruding. On one of my own prints (Which I've done many times before) about 2-3mm up and it just disintegrates (under extrudes). I'm currently working my way through upgrading to 3.2 so I don't know if this conversation would be mute anyway.. I'd say just mark this one as solved since the network was back up and running.
Best posts made by hbrownell
-
RE: Duet 3D Wifi error 99
-
RE: Under voltage issues.
It was loose cables and bad pins.. I replaced the pins and the problem went away.
Latest posts made by hbrownell
-
RE: Warning: motor phase B may be disconnected
@phaedrux Bad wire confirmed. I ordered a new one, hooked it up and no more problems. Thank you!
-
Dual Z doesn't come out level.
Is there a way to adjust either side of the dual Z setup? I found that I'm off by quite a bit. Thanks!
-
RE: Warning: motor phase B may be disconnected
@dc42 Okay, so this was the latest error I got today
M0 H1
Warning: motor phase B may be disconnected reported by driver(s) 3Which motor should I consider suspect?
-
Warning: motor phase B may be disconnected
I get this warning when my machine is working. It just started and I have no idea why.
Warning: motor phase B may be disconnected reported by driver(s) 3
-
Failed print using latest cura and 3.2
I was able to print a tiny robot perfectly with no supports last night. I tried to print a part I created and, again, with no supports it printed okay but the thinner portions failed at the top of the print where they had succeded before. I then tried it with supports but it failed misserably. This causes me to think of another calibration model I tried with a hole on the side and a relatively thin wall. The wall was fine up to the hole and then where the nozzle started to print again, the model failed at that point for a few mm and when the flow seemed to kick up again it resumed normal print.
Was there a change in the new Cura that might explain this? I tried a fresh profile to see if something might be different in Cura, but it had the same result. When I did a test extrusion, I noticed that I got a really thick stream of filament coming out of the nozzle, so I'm not sure where the problem lies at this point. Up until the power outtage a couple of weeks ago this printer was top-notch. I'm using PLA from Eryone and I've had great success with their products before and this spool has been the same up till now. I'm rather lost at this point. And for the record, all axis including the extruder are properly calibrated. -
G32 tries to go negative on X axis
Thanks for the help folks, moving on to the next round, G32. It does the first probe just fine, but then X tries to go negative and rubs the belt (that da-da-da-da-da sound) but then continues on to the rest. I can't find where the odd plot number is..
config.g
; Axis Limits
M208 X20 Y-19 Z0 S1 ; set axis minima
M208 X230 Y215 Z200 S0 ; set axis maximabed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 16 2021 20:01:34 GMT-0500 (Central Daylight Time)
M561 ; clear any bed transform
;G29 ; probe the bed and enable compensation
;Dual Z bed.g
G28 ; home
G30 P0 X20 Y105 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X180 Y105 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
G28 Z -
RE: Error M280
@hbrownell Never mind. I just needed to update the firmware to 3.22.. it was still on 2.05.
-
Error M280
So, I just did the update to 3.2 and my BL Touch is not connecting apparently.
Error: M280: Invalid servo index 0 in M280 commandFrom config.g
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P25 X29 Y-6.5 Z1.2 ; set Z probe trigger value, offset and trigger height
M557 X20:180 Y20:180 S80 ; define mesh grid; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 16 2021 20:01:35 GMT-0500 (Central Daylight Time)
M280 P0 S10 ; deploy BLTouchI followed this image to make my connections.
-
RE: Upgrading to 3.2, need a once over on code.
@phaedrux Last question (Hopefully) I erased the old drive but there were several folders and one zip file on it. The new build has but 2 folders sys and www. Do I need any other files to make this work or just plug it in and go?
-
RE: Upgrading to 3.2, need a once over on code.
@phaedrux Got it, but I think I caught another error. I'm missing M671 no? and M584 should be ;
M584 X0 Y1 Z2:4 E3 yes? Because Z is running 2 and 4?