Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

Personal Information

  • Field of Work
  • Country

Recent Profile Visitors

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

  1. Is the chip the driver is set up for set up with the same selects and timing as the one on the flow sensor? It's grubby little details like that you have to sort through.
  2. Usually it's better to just sit down with the hardware spec sheet and write up the code for the actual device being used. That way you reduce the number of "surprises" when things aren't *quite* the same. At least that's the answer if you do this for a living ....
  3. To get the UM3 to play nice via I2C, you would need to write a driver that is specific to the target device. There is no generic protocol that "just works" in this case.
  4. Hi Two S5's ... nice problem to have ? Might it be "lost connection to the group" ? Bob
  5. Hi Isn't the aluminum build plate coming out this fall? Everybody who *buys* an S5 will get one. They just will not get it with the early printer shipments. .... or am I confused yet again ? ? Bob
  6. Hi A few things to research / ponder while you are waiting for your cool new printer: 1) The build surface is glass. If you drop it on a concrete floor, it can indeed break. At least for the earlier printers a genuine UM spare was relatively cheap. It's worth having an extra "just in case". 2) If you didn't get a bundle of filament with the printer, order some now. You will burn through what comes with the machine pretty fast. 3) Big prints can take a *long* time to complete. A couple of days is not unusually long. If there is any chance of a power outage happening where you will run the printer - get a UPS to run it on. Compared to the printer .... not a lot of money. Compared to the frustration of a three day print getting nuked ... money well spent. 4) Prints are done from models. Models come from CAD software. If you don't already have CAD experience, now is a fine time to start messing around. There are several free programs out there which seem to work for a lot of people. If this is a commercial venture, there are "paid for" versions to look at. 5) It's a big printer and yes you want to print *BIG* stuff. Resist the urge for at least the first few prints. Start small. Small prints run fast and give you a good idea how things all work. Yes, your cube collection will probably get tossed in the trash ... live with it ? Far better to make mistakes in 15 minutes and correct them in 20 minutes that to do it with a cycle measured in days. 6) To me one of the great things about the UM3 ( and the UM5) is the easy swap print cores. I have a few spares "in stock". There are a lot of people who ( rightly ) might say that's overkill. Have fun !!!! Bob
  7. Hi Simulation processing options = play the print in Cura ?? Bob
  8. Hi There's also a tolerance on the wheel / gear diameters that can get into this. If the filament is not quite round ( it never is perfect) a twist between the wheels could result in errors in either direction. As a practical matter - do I really *care* below some percentage? My. guess is that the don't care threshold is somewhere in the 1% region. I must admit this is the fist time I've seen a way to *test* that theory. Bob
  9. Hi Why not just stuff a little MCU into the mix and make your sensor look like their S5 sensor? As long as they have unified firmware across the platforms ( do they ???? ) it should just be a line in a config section to turn it on or off. Yes, this very much requires you have a bit of info about what their sensor "looks like" in terms of it's I/O data stream. Anybody taken a hammer to an S5 yet? Bob
  10. Hi I realize this isn't a democracy and you *do* have costs associated with any sort of retrofit kit. It's not just the cost of the parts. There is design time, time to write instructions, and inevitably support when things don't quite go right. All that said, I think a number of us would be very interested in even a labor intensive kit based retrofit process. The cable issue sounds like either a replacement cable / extension cable / splice job would do the trick. Not at all sure what the "new" back to keep the motor from grinding involves. Bob
  11. Hi One would guess that (except for crashes) the amount of filament commanded is always greater than what ultimately goes out the spout. Put another way, the feeder can slip, but it can't over step. The net result is that you over estimate how much filament has been used. If you write that back to the spool there will be a bit more on the spool than the NFC *thinks* is on it. As long as the result is not a hard stop I don't have any problem with that tradeoff. If it simply tells me "you need 127 grams and I think you have 119 on the spool" that's great. If it will not let me proceed .... not so great. Bob
  12. Hi I think that is a completely independent thing vs the partnership with the bulk material producers. Put another way - it's a software thing ..... You have to get a bunch of fiddly little things worked out in Cura and the firmware as well as on the chip it's self. There are a number of threads around going into all the details. What this *might* turn into is a set of "Ultimaker approved" filaments from various outfits. That would be a first step towards NFC integration, but only a first step. Given the ( unfortunately ) smaller size of the 2.85 mm filament market .....who knows how long it might take to get very many people interested. Bob
  13. Hi Good to know, !!! Unfortunately that's not what has me tied up in knots here. Thanks Bob
  14. Hi Interesting that you get the crash report / backup config screen. That's one I have never seen. Looks like there is some "variety" of code (or issues) out there. Bob
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!