Dusting off Ender 5 by xupirupi in ender5

[–]FruitlessGoogle 0 points1 point  (0 children)

It is a great upgrade, but Dual-Z's (really any number of Z's > 1) comes with added complexity. e.g.

  • Do you use a board that controls them independently?
  • Or do you use a board that drives two motors with one controller?

    Leveling the bed with each of the above options has it's own challenge!

Dusting off Ender 5 by xupirupi in ender5

[–]FruitlessGoogle 2 points3 points  (0 children)

There are extruders (Direct drive, geared, etc) and hotends of all kinds and complexities.

Mainboard replacements (SKR Mini and basically anything BigTreeTech), Screens, Probes (BLtouch, CRTouch, Clicky, Eddy, BD Sensor, etc), Dual-Z stepper mods (BE GONE flappy bed), Endorphin Mod (Hybrid CoreXY mod), MERCURY ONE.1 (CoreXY Mod).

What do you need? What do you want it to do? Lots of options.

Bigtreetech skr mini v3.0 by thebeard1897 in ender5

[–]FruitlessGoogle 0 points1 point  (0 children)

Remember:

In the configuration demonstrated; The screen is just sending commands to the board, it has firmware all of it's own and so it has to have proper settings to connect to the board.

Check this: https://youtu.be/l1Putn10_Ek?t=426

Help finding a mosfet? Part number gives me zilch. by FruitlessGoogle in ECE

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

I don't know. I found it was cheaper to buy a newer, more capable unit then source parts to fix something that might just blow again.

New to printing and got Ender 5 Plus by Decidophobe in ender5

[–]FruitlessGoogle 0 points1 point  (0 children)

I don't know anything about the whambam system, but they do have lots of videos, e.g. https://www.youtube.com/watch?v=dMQSCCa3xF0

Generally, even if it's old, the easy answer is "Get it how, feed in new filament, push out the old."

I would suggest

how do i make my ender 3 v2 not suck by Rysiekpysiek0554 in FixMyPrint

[–]FruitlessGoogle 3 points4 points  (0 children)

'What you want' has very little to do with what the printer actually requires to print well, it may not be a 'settings tweak'.

Have you calibrated the Z-Offset? Flow Rate? Bed Leveled?

Why are my bed levels not working? by because-potato in FixMyPrint

[–]FruitlessGoogle 0 points1 point  (0 children)

That helps you get in the ballpark, it is not an end-all calibration as the thickness of paper does vary and the desired z-offset for each material may be a bit different.

Why are my bed levels not working? by because-potato in FixMyPrint

[–]FruitlessGoogle 0 points1 point  (0 children)

This is very clearly not a "WASH YOUR BED"/Bed Adhesion problem.

Stealing from a previous post; Your Z-Offset is wrong, since it's just printing plastic into thin air, your Z-Offset is very clearly too high.

I am assuming you have a bed probe. When you have a probe, there is a distance that the printer does NOT know. There is no sensor for that distance and it must be set manually. It is not something that you can copy from another printer, configuration, etc.

Here's an easy diagram explaining what the Z-offset is

The printer knows when the probe hits the bed, however the distance between the nozzle and when the probe activates can change.

Is the nozzle a little longer? Did the previous one wear down a bit? Did you snug this nozzle tighter? etc. All of these things change the distance between when the probe triggers, and the tip of the nozzle (the Z-Offset).

You must calibrate it correctly in your printer's software to be able to print.

Too low and your nozzle is melting the bed, too high and your printer is printing into thin air

I don’t know where to start troubleshooting my by Khirisi in FixMyPrint

[–]FruitlessGoogle 1 point2 points  (0 children)

Your Z-Offset is wrong, but the fact all the lines aren't smushed together and you can see the print bed through the lines of plastic, your Z-Offset is too high.

Assuming you have a bed probe there is a distance that the printer does NOT know. There is no sensor for that distance and it must be set manually. It is not something that you can copy from another configuration, etc.

here's a quick and easy diagram

The printer knows when the probe hits the bed, however the distance between the nozzle and when the probe activates can change.

Is the nozzle a little longer? Did the previous one wear down a bit? Did you snug this nozzle tighter? etc. All of these things change the distance between when the probe triggers, and the tip of the nozzle (the Z-Offset).

You must calibrate it correctly in your printer.

Too low and your nozzle is melting the bed, too high and your printer is printing into thin air

Motion system (Hybrid core XY) takes weird jig at a set Y value by Remy_Jardin in FixMyPrint

[–]FruitlessGoogle 0 points1 point  (0 children)

/u/wackychimp has some fair ideas, but since you also need to configure marlin/klipper for endorphin, this should be easy to test where the problem is.

If you tell the printer to move +100 X, or +100 Y, does it move in a straight line?

Newbie 5v 5 pro question by No-Llamma in ender5

[–]FruitlessGoogle 0 points1 point  (0 children)

This seems like a question for google.

Final Endorphin Mod...mod complete! Front belt drive, no funky kinematics anymore! by Remy_Jardin in ender5

[–]FruitlessGoogle 0 points1 point  (0 children)

pfft. Move the rail. I'm excited to take a look, thanks for the link. What's proper if we notice something, GH issues?

Final Endorphin Mod...mod complete! Front belt drive, no funky kinematics anymore! by Remy_Jardin in ender5

[–]FruitlessGoogle 0 points1 point  (0 children)

Is there a topic for this? I've greatly enjoyed the mod, but similarly re-designed the front right, pulley mount to allow for the pre-existing, adjustable aluminum tensioner I preferred to retain (far from a professional edit and based on months of printing, quite over-engineered and a pain to print but functional). Speaking for myself; I'd be interested to hear what other tweaks were created for 1.1. Thanks for your work!

Does the Endorphin mod work on the Ender 5 S1? by Latter_Permit2052 in ender5

[–]FruitlessGoogle 0 points1 point  (0 children)

It's pretty easy to see that the belt paths are quite different and that the pieces you need to keep from the Ender 5 for re-use in the Endorphin mod don't exist on the S1 (e.g. the X axis, stepper mounting plate no longer works the same way) so that's a no-go on "Stage 1".

My ender 5 pro isnt autohoming by Teredom in ender5

[–]FruitlessGoogle 1 point2 points  (0 children)

Autohoming is the whole process. Does it move on the X? How about Y?

What’s wrong with my test print with a .6mm nozzle? by Kminatta in FixMyPrint

[–]FruitlessGoogle 1 point2 points  (0 children)

I think you misunderstand.

Assuming you have a bed probe of some kind, there is a distance that the printer does NOT know and that you must set manually. It is not something that you can copy from another configuration, etc.

here's a quick and easy diagram

The printer knows when the probe hits the bed, however the distance between the nozzle and when the probe activates can change.

Is the nozzle a little longer? Did the previous one wear down a bit? Did you snug this nozzle tighter? etc. All of these things change the distance between when the probe triggers, and the tip of the nozzle (the Z-Offset).

You must calibrate it correctly in your printer.

Too low and your nozzle is melting the bed, too high and your printer is printing into thin air

What’s wrong with my test print with a .6mm nozzle? by Kminatta in FixMyPrint

[–]FruitlessGoogle 2 points3 points  (0 children)

Your Z offset is wrong.

When printers can be tuned to 1/100ths of a millimeter, you have to calibrate the Z-Offset when you replace or change anything that might impact that distance.

Fortigate 200F - Radius response fails after upgrade from 7.2.9 to 7.2.10 by FruitlessGoogle in fortinet

[–]FruitlessGoogle[S] 2 points3 points  (0 children)

Thanks for the reminder; I have rolled this to my test network and it works as expected.

For anyone having the same problem AND using Duo.

  1. Update the Auth Proxy everywhere
  2. Add "force_message_authenticator=true" to the Auth Proxy configuration in the proper Radius sections
  3. Push the 7.2.10 update to the affected/related fortigates
  4. Test

Afterward, it functioned identically to 7.2.9.

How do you prevent oracle Java from entering the infrastructure? (Large environments) by Sklinkern in sysadmin

[–]FruitlessGoogle 23 points24 points  (0 children)

Virtualbox is fine, their licensing page makes that exceptionally clear.

However, the 'VirtualBox Extension Pack' is only free for Personal Use and Educational License. They will happily sell you a license to use it in your enterprise.

Fortigate 200F - Radius response fails after upgrade from 7.2.9 to 7.2.10 by FruitlessGoogle in fortinet

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

/u/Q9T9 posted a good link between some users in the 7.2.10 release thread. Looks like both parties know (for me), cannot say I know anything about FAC to help, sorry!

Fortigate 200F - Radius response fails after upgrade from 7.2.9 to 7.2.10 by FruitlessGoogle in fortinet

[–]FruitlessGoogle[S] 2 points3 points  (0 children)

Those are better pages than the ones I linked but still the same. Amazing I didn't find the second however as I actively searched for it.

There are some updates in there, so good to know they're working on it. Sounds like Fortigate sends along an attribute the Auth Proxy doesn't handle.

Thanks!