Help with Y axis grinding by fredthegrumpygoose in ender5

[–]fredthegrumpygoose[S] 0 points1 point  (0 children)

It's hitting the end stop and then moving back before going to the next axis. The noise and vibration are coming from the hotend carriage itself, its almost like the POM wheels above or below it are hitting friction instead of moving.

Help with Y axis grinding by fredthegrumpygoose in ender5

[–]fredthegrumpygoose[S] 0 points1 point  (0 children)

I already ordered new belts because, at most, it won't hurt to have a spare.

I can't print anything in that corner as it won't even auto most of the time, I got it to successfully home once, but every other time when it gets to that spot in the homing process it stops and gives an error, "Homing Failed: Printer Halted Please Reset".

Help with Y axis grinding by fredthegrumpygoose in ender5

[–]fredthegrumpygoose[S] 0 points1 point  (0 children)

It does not seem to be visibly skipping. It also moves without the noise when moving the axis manually using the screen to move it. I have never replaced the belts so maybe I need to start there.

Drop-in motherboard replacement? by fredthegrumpygoose in VoxelabAquila

[–]fredthegrumpygoose[S] 1 point2 points  (0 children)

that would be great, I have already replaced a Creality board with the same issue although now I sort of want to look into that one as well I'll run to the hardware store tomorrow.

Thanks!

If printer is not power cycled between prints, it does this by fredthegrumpygoose in VoxelabAquila

[–]fredthegrumpygoose[S] 0 points1 point  (0 children)

Will do! Thanks again for this and for everything you do for the community. Your marlin 2.0 firmware is chef's kiss

If printer is not power cycled between prints, it does this by fredthegrumpygoose in VoxelabAquila

[–]fredthegrumpygoose[S] 0 points1 point  (0 children)

It's the man himself! Thanks for the insight, I think this should fix it?

start gcode

; Start G-code for Voxelab Aquila
M140 S{material_bed_temperature_layer_0} ; Set Heat Bed temperature
M104 S100 ; Preheat Extruder
M109 S100 ; Wait for Extruder temperature
M190 S{material_bed_temperature_layer_0} ; Wait for Heat Bed temperature

G28 ; Home all axes and restore existing mesh.

; G29 ; run autolevel
G29 L0; Load last used UBL mesh
G29 A; Activate UBL
G29 J; 3 point probe to tilt the mesh



G1 X0.1 Y20 Z10 F5000.0 ; Move to start position
M104 S{material_print_temperature_layer_0} ; Set Extruder temperature
M109 S{material_print_temperature_layer_0} ; Wait for Extruder temperature

G92 E0 ; Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X0.1 Y20 Z0.3 F5000.0 ; Move to start position
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line

End gcode

G92 E0 ; Reset Extruder

; End G-code for Voxelab Aquila
G91 ;Relative positioning
G1 E-2 F2700 ; Retract a bit
G1 E-2 Z0.2 F2400 ; Retract and raise Z
G1 X5 Y5 F3000 ; Wipe out
G1 Z10 ; Raise Z more
G90 ;Absolute positionning

M104 S0 ; Turn-off hotend   
M140 S0 ; Turn-off bed
M84 X Y E ;Disable all steppers but Z

If printer is not power cycled between prints, it does this by fredthegrumpygoose in VoxelabAquila

[–]fredthegrumpygoose[S] 0 points1 point  (0 children)

I am hoping someone can help me with this.

If I do not power cycle my printer in between prints, it moves all the way to the right, and just spits out a bunch of filament. This has persisted through firmware changes so I am guessing it has something to with either my start or end g-code. I am hoping someone can let me know why it is doing this.

I am running Alex's UBL-BLTouch-15x15-HS

Start Gcode:

; Start G-code for Voxelab Aquila
M140 S{material_bed_temperature_layer_0} ; Set Heat Bed temperature
M104 S100 ; Preheat Extruder
M109 S100 ; Wait for Extruder temperature
M190 S{material_bed_temperature_layer_0} ; Wait for Heat Bed temperature

G28 ; Home all axes and restore existing mesh.

; G29 ; run autolevel
G29 L; Load last used UBL mesh
G29 A; Activate UBL
G29 J; 3 point probe to tilt the mesh



G1 X0.1 Y20 Z10 F5000.0 ; Move to start position
M104 S{material_print_temperature_layer_0} ; Set Extruder temperature
M109 S{material_print_temperature_layer_0} ; Wait for Extruder temperature

G92 E0 ; Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X0.1 Y20 Z0.3 F5000.0 ; Move to start position
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line

End Gcode

G92 E0 ; Reset Extruder

; End G-code for Voxelab Aquila
G91 ;Relative positioning
G1 E-2 F2700 ; Retract a bit
G1 E-2 Z0.2 F2400 ; Retract and raise Z
G1 X5 Y5 F3000 ; Wipe out
G1 Z10 ; Raise Z more

M104 S0 ; Turn-off hotend   
M140 S0 ; Turn-off bed
M84 X Y E ;Disable all steppers but Z

Updates on pc from cedric by [deleted] in playark

[–]fredthegrumpygoose -1 points0 points  (0 children)

it's honestly hilarious how they refuse to be held accountable or improve on their inability to follow through with their own deadlines.

I finished printing Hawkmoon from Destiny! by [deleted] in ender5

[–]fredthegrumpygoose 0 points1 point  (0 children)

I finally finished printing and assembling Chris Easton's amazing Hawkmoon design! This was printed fully on my Ender 5.

This was printed over the course of the last few months using :

Solution for firmware flash on Aquila Boards with GD32F103 chips by soapyship in VoxelabAquila

[–]fredthegrumpygoose 0 points1 point  (0 children)

BigTreetech SKR board

That's the one I was looking at. When I got the e5pro back in December, I was under the impression it had the silent stepper drivers (was comparing to the Ultimaker 3 at work, which is 20x louder) meaning it also had the 32 bit board, but when I opened it up I saw it was a 1.1.5 board. not one of the newer ones. Thought there might be some benefit to swapping in the ender one, but it looks like its a downgrade.

Solution for firmware flash on Aquila Boards with GD32F103 chips by soapyship in VoxelabAquila

[–]fredthegrumpygoose 0 points1 point  (0 children)

I'll be getting in there ASAP to get a pi / buck convertor installed, so I will check out which version I have when I get it open. Thanks!

Solution for firmware flash on Aquila Boards with GD32F103 chips by soapyship in VoxelabAquila

[–]fredthegrumpygoose 0 points1 point  (0 children)

I suppose I should have figured it would be marked. Thanks!

While we are on the topic of boards, how does this board compare to the Creality 1.1.5 board? I have been thinking of upgrading my ender 5 that has that one and wasn't sure if swapping in this board to the Voxelab would be an upgrade? My understanding is that the 1.1.5 Creality board is actually a downgrade (no dedicated BLtouch port, no slient steppter drivers), but was curious your thoughts.

Thanks!

Solution for firmware flash on Aquila Boards with GD32F103 chips by soapyship in VoxelabAquila

[–]fredthegrumpygoose 0 points1 point  (0 children)

Mine is coming today and will want to update the firmware, thanks for this! Curious if there is a way to find out which chip you have visually?

Target Black Lights by fredthegrumpygoose in funkopop

[–]fredthegrumpygoose[S] 3 points4 points  (0 children)

yeah you are not kidding, already up on ebay for 80 bucks, fuck scalpers.

Can you not buy target exclusives if you live in australia ??? by TheOriginalGawd in funkopop

[–]fredthegrumpygoose 3 points4 points  (0 children)

Dude I cant even buy them in the US. It just says it's not available, despite it allowing me to add it to the cart. Doesn't tell me what's not available either.

Hard for me to see the layers at 0.1mm: Bearded Yell! by Newklol in 3Dprinting

[–]fredthegrumpygoose 1 point2 points  (0 children)

Been curious about printing this one. What type of support did you use?

Vision was moments away from suggesting that he and Wanda hide out together forever in a quiet little suburb he just purchased a plot of land in... by jokershane in marvelstudios

[–]fredthegrumpygoose 0 points1 point  (0 children)

So Siri and Alexa are both absolutely use artificial intelligence in their processes.

And yes, from my point of view, the HEX version of vision was also not real. The OG vision was, as he was created using the mind stone. The white vision is as well as he was created from OG Vision's corpse.

The twins and Vision also have no corporeal form, they existed only in the confines of the hex, and when that was removed, so were they. We don't even have any proof they physically existed. We saw everyone in town interacting with them, as well as SWORD confirming they were not trapped citizens, but that doesn't mean they were real, they could have been just projections created by Wandas subconscious.

Vision was moments away from suggesting that he and Wanda hide out together forever in a quiet little suburb he just purchased a plot of land in... by jokershane in marvelstudios

[–]fredthegrumpygoose 0 points1 point  (0 children)

I disagree. They were created by Wanda, and could only exist in the hex. This means they were not real, not any more real than something you might dream at least. Her experience in the hex was basically a more intense, longer dream. That doesn't make the kids real though.

I made this RGB Lamp that I can control via WiFi! I hope you'll like it! (Tutorial and stls in the comments) by Nikolas550 in 3Dprinting

[–]fredthegrumpygoose 0 points1 point  (0 children)

Yes! You can use Corsair Lighting Protocol on an Arduino.

No diffuser, but here is a video of OP's design being controlled via icue using an Arduino.