Heyo!
I tried to flash My Taz 4 to get Linear Advance to work and I used this guide:
Everything seemed to be going well, and I got autobuild Marlin to seemingly give me the all clear. But as soon as I uploaded it through OctoDash, only the screen updated with all of the x,y and Z co-ordinates flashing between 0 and ?, octodash dropped but not before giving me an error message that looked like something out of an eldrich novel.
I can try to upload the file and drop a link here if you think that could help but I’m at a loss.
Is there a known issue with this firmware or am I missing something entirely?
Kind regards,
Corgi.
Update! I switched to Drunken Octopus Marlin and used the relevant profiles. However, the Issues With the XYZ and Z flashing is still occuring however I can move the XY and Z axis’ through pronterface however, the Z axis only triggers one motor to move not both? Any Ideas on this one?
Your likely thinking of a axis switch related that’s the most I can think of
If you’re doing a custom marlin build, the official forums here aren’t the best source for help, you’d have more plentiful help in a Marlin group.
But without seeing your configuration.h and configuration_adv.h I’d be guessing. The compiled firmware won’t help at all.
XYZ flash until the machine has been homed, and it shouldn’t go down in the Z until the homing has happened in order to prevent driving the nozzle through the plate.
The Z motors share outputs from a single stepper driver, so there’s no reason (beyond a bad motor, or wiring problem) they shouldn’t move together.
1 Like
Thank you so much, that’s incredibly helpful! I’m Actually doing a bog standard Lulzbot Build but for some reason a plain marlin install with the set profile just didn’t work.
So I tried the alternative Drunken Octupus marlin build and that seemed to clear up most of the problems.
However, whenever I try to home the printer, the normal sequence happens. 1. Goes to the switch on the left. 2. drops down the Z axis to hit the switch on the bottom. but then this weird 3rd thing happens; it moves to the middle of the board and screams… it seems to be moving the Z azis motors, but very very slowly and making this horrific noise. I was worried that I was breaking something, so I turned it off.
This is the thing that made me all confused and worried that I was bricking something or had something enabled that wasn’t meant to be there.
Do you have any idea what that might be?
Can you post a video of the attempted homing to youtube and link it here?
Is the nozzle dragging against the bed and stalling the motors out?
Did you get the right firmware? Like, are you trying to run a BLTouch version? DO has a lot of variants.
Is this just the homing from the screen, or are you trying to run a print?
1 Like
Heyo!
I made a folder with the video showing the issue, the Config and the Config-H files.
I am only trying to get the printer to home.
I think I got the standard Drunken Octo Print. I think I got the right Variation as I don’t see a bl-touch enablement in the files?
Cheers and thank you so much for the help!
I’ve requested access to your Drive to look over the issue. My experience with DO has been, they cram too many features into the builds and it really strains the 8-bit Rambo boards sometimes. Unless you have a bltouch or filament sensor there is no functional gain to using Marcio’s builds. Marlin hasn’t changed all that much since Lulzbot’s official release and what build Marlin is on now - IF you are running stock.
1 Like
It’s trying to home Z at the center, I think? Also the config files don’t really look like DO config files. Did you use the DO firmware flashing tool?
1 Like
I did not, but I put a fiver into Marco’s Patreon to use the tool and now everything seems to be running smoothly! I think I may have a look back at Trying to get standard Marlin working again just to make sure!
So full disclosure here, I used the Marlin Builder tool in virtual studio to run Drunken Octopus through and that must have produced some weird issues.
Slow/noisy Z movement was probably due to a steps/mm misconfig:
Should be same as the Taz6 (1600):
While you have 400:
Feedrate should be max 5:
You have 8:
So that would have put it as potentially trying to turn something like 1.6x faster than usual, and with only 1/4 the necessary steps.
I also saw some of the max accelerations off from standard and stopped looking. Just lots of things that need to be verified against the official speed settings before you start tweaking.
Update: I don’t see anything setting the motor current in there either, so it could be too high/low
1 Like
