Please note: the forum is closed.
No new user registrations are accepted. For more info, please click here.
No new user registrations are accepted. For more info, please click here.
Nozzle is scratching on the bed
Frank01x
Posts: 20Member
Hi to the community,
I own a JGAurora A5S since April 2019 and have printed various things, mostly PLA, without any problems with the original firmware.
At the end of July, at the end of a project, I wanted to change the firmware to the Marlin version of Samuel to use bed mesh leveling. After a test print had succeeded, I saw that a new update was available for download at the end of July. With this latest version, I can no longer print, because the Nozzle after the leveling and saving the configuration, the print bed damaged! I use the JG Slicer (a modified version of Cura). The start code entered there reads:
G28; Home
M420 S1
G1 Z15.0 F6000; Move the platform down 15mm
Prime the extruder
G92 E0
G1 F200 E10
G92 E0
Does anyone know this problem? I am full of hope!
(My native language is german, sorry!)
I own a JGAurora A5S since April 2019 and have printed various things, mostly PLA, without any problems with the original firmware.
At the end of July, at the end of a project, I wanted to change the firmware to the Marlin version of Samuel to use bed mesh leveling. After a test print had succeeded, I saw that a new update was available for download at the end of July. With this latest version, I can no longer print, because the Nozzle after the leveling and saving the configuration, the print bed damaged! I use the JG Slicer (a modified version of Cura). The start code entered there reads:
G28; Home
M420 S1
G1 Z15.0 F6000; Move the platform down 15mm
Prime the extruder
G92 E0
G1 F200 E10
G92 E0
Does anyone know this problem? I am full of hope!
(My native language is german, sorry!)
Comments
Axel
I installed the community Firmware, did the mesh bed leveling and add
What is wrong with the Firmware and how can i fix it.
I used the baby step function to check the the hight.
Totaly 0.5625 to deep
This is how i modify my Start Gcode
M420 S1
M117 Use Mesh
M290 Z0.5625 ; move up 0.5625mm on the Z axis
M117 BabyStep 0.5625
M500
G1 Z15.0 F1500 ;Move the platform down 15mm
;Prime the extruder
G92 E0
G1 F200 E10
G92 E0
Unfortunately, I encountered the same problem. As I was late for abort the print, the scratched area is bigger than @Frank01x's. I plan to buy a bed surface, because first layer does not stick to scratched area properly. I installed the community firmware 3 days ago for trying mesh bed leveling. It did well for 2 days, but then this issue happened.
How can I fix this?
Thanks
I propose to take the firmware offline till this issue has been located, otherwise a lot of people get damages. I will rollback to the original firmware.
-Calibrated the levels using the sheet and the 5 corners/area.
-When printing, after heating the Z level is a lot lower and scratches the nozzle into the bed.
The first time I had it, I thought I made an error. I already have this printer for approx 1 year and never did I had this issue.
Then the 2e time the scratch was so deep that the entire glass was damaged
Then I saw this post and suddenly recall that all this only happened after I upgraded the firmware. I have now rolled it back to the factory version.
This costs me 2 nozzles, 1 glass bed and one heated bed. :-(
I agree the current situation is not ideal. It is extremely difficult as one person to do everything, I wish there were other willing volunteers. If I had more time, I would like to create a video showing how to use the mesh bed levelling feature, and how to double test if it is actually working before running a test print. Maybe that will be possible in early November.
I’m particularly concerned about the reports of mesh bed levelling failing to enable intermittently. However, intermittent issues are really the most difficult of all to solve, and at this time I don’t have anything left to give at the moment - I’m writing this message at 2am. 😞
I don’t think pulling the firmware does any good at this point. Perhaps I could put a warning there? If you have a suggestion I’m all ears.
Finally, I would suggest trying the “beta 6” version and seeing if you have different results with that one.
Best regards,
Sam
1) After flashing firmware, run M502, M500, M501 in that order.
2) Connect to printer using prontorface. Send M851 (Z-offset) see if it is a negative number. I would send M851 Z0 to make sure it's set to 0. Then store EEPROMs again with M500.
One another note, because my 3D printer was broken I ordered a Prusa MK3S. I honestly must say the difference with the jgaurora is day and night.
With the jgaurora more than 50% of the prints failed. I have now a 100% success rate and focus on creativity.
I still keep my jgaurora and might give it to my nephew. ;-)
Howdy, Stranger!
RegisterIt looks like you've been lurking for a while.
If you register, we will remember what you have read and notify you about new comments. You will also be able to participate in discussions.
So if you'd like to get involved, register for an account, it'll only take you a minute!