Jump to content
Ultimaker Community of 3D Printing Experts

mutley3d

Member
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

3 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ouchies. I dont use the solder pads, my eyes cant cope with that small. I put a bridging wire across pins config1 and gnd, and i'm assuming from the results i see that i am getting spreadcycle mode. Certainly feels like more torque
  2. Ive hacked about with these machines quite a bit over time. They both run Flex3Drives with a suitably modified firmware but none of the changes caused the issue. I may have had an accident at some point tinkering where the board switched off but then reset, so I don't know if maybe there was a damaged component on the board, or partial failure of a driver. Having said that I have reverted to "from scratch" firmware to make sure no old late night forgotten changes playing tricks, mapped to the spare driver chip, and plenty other tests and checks, and replacement of donor parts to no avail. Goin
  3. A quick before and after photo. I think something might have been seriously wrong with the drivers on board, or maybe i'm just used to the finer prints from my other machines, but I swear my UM2's used to print better than the result on the left side. But I have same issue on both the machines. Piece on the right is after TMC mod. I think the stepper carrier approach is a right royal PITA, it took a while to get the second TMCdriven axis to work, testing different remapped pins. However I think the result is pretty conclusive, at least in my case. This machine is now back to produc
  4. Well i'm almost there. Got each axis running when mapped and connected individually one each to on-board, and off-board driver. When I map both axis to off board drivers, i get odd behaviour from one axis. Calling it a night for now, as one of the off board driver carriers blew the voltage regulator, through plugging in an old blown driver (4988), it happens when tired. The odd axis behaviour might be down to how I was grounding both carrier boards (as per manuf' instruction), and sods law just when I'm about to eliminate that concern with separate ground wires, the magic smoke escapes.
  5. Hi tinkergnome and good shout on inverting the enable and step signals. I am (perhaps dangerously) assuming that because the drivers i'm using are "usually" drop in replacements for 4988's, that I shouldn't have to make changes to those. But I will certainly keep this in mind now that you mention them. Using the analogue pins seems to be working, although I am having a bit of trouble. In diagnosing, if I fit just one external driver, and set the pins accordingly, I have both X and Y running (one from the offboard driver, one from the original onboard 4988). But if I wire in both of
  6. OK so I think I have worked out what to do with those analog pins to define them as digital pins. Its so easy. I now have motion on one axis testing with some spare 8825 drivers (instead of blowing tmc2100's). I have to recheck the other axis closely as it is lifeless, might be wiring, might be a dud carrier board. @neotko yea but does it have the bed levelling routine? @halfie seems to be having probs with it. Ill check it out once I have these drivers sorted, but taking one step at a time, too many changes in one go is dangerous. For now just using the Ultimaker/Marl
  7. Some sort of progress. I have remapped pins in pins.h, and now have 2 external driver sockets wired in. I am using 6 pins from connector J25 (ADC0 ADC1 ADC2 for X axis) along with (ADC5 ADC6 ADC7 for Y axis) for STEP DIR and ENABLE signals respectively. Firmware has been flashed and I have managed to not let any magic smoke out, but i'm not quite there yet. The Y axis motor seems to get enabled, but wont move, the X axis has no response. The 2560 data sheet appears to indicate these pins can be analog input, or signal output. I am not sure if or how I set these pins to become signa
  8. I am looking into that board and have contacted the seller to request TMC drivers with it, along with some spares. I suspect you may well have had the voltages set incorrectly on the drivers, and cooling them helps as they can get hot. Also if you had them in stealthchop (silent) mode, you get less torque, so possibly cumulative unfavourables working against you. Putting them into spreadcycle mode with a bridging wire increases available torque, but also noise, although my experience tells me you can get them pretty quiet with some tuning of the vref, especially when compared to or
  9. OK so I wont be doing that however I think you just altered my train of thought and pulled me out of a rabbit hole. I will update more shortly but I think I have a solution. Thank you for your response.
  10. Maybe this should be a new thread, but posting here as it is directly relevant to this thread. I am Suffering the same issues on my 2 x UM2 machines. Want to finally do something about it. Done all the tweaks and mods, shorting ROSC pins, diode smoothers etc, none really "FIX" the issue. I have Duet boards available to upgrade like Neotko above, but kinda thinking I would like to retain as close to original as possible ie keep existing LCD. I also have a couple spare Arduino/RAMPs boards to hand. So my thinking is use a RAMPS board with TMC2100. I have these drivers on
  11. I go away for five minutes and look what happens. This is very nice. How can I not do this to one of my machines? baahaawaaa
  12. Guys, Real intereting stuff in this thread. Im around but just incredibly snowed under so trying to clear backlog. Sorr i havent added much here...yet! @Macua85 can probably work something out Ive got a couple interesting titbits on the way too will update as son as i can
  13. Just seen this thread for first time - foehnsturm thanks for bringing it to my notice. Let me digest and consider the options. 30x30 easy - possibly a bit smaller depending on how its attached. Macua85 - dont be shy plus, all the parts in the Flex3Drive will be interchangeable into anything developed here. Have also been looking at nema8 solutions - got a couple on order from a couple weeks back, waiting on delivery. Ill be monitoring here closely from now on.
  14. I also found turning up material flow to around 120% made a lot of difference with some filaments. Ill soon write a new post dedicated to Flex3Drive as I dont want to steer this topic, off topic
×
×
  • Create New...