Topic: Alignment problem when changing reel mid-print

Home Forums Technical Support Alignment problem when changing reel mid-print

This topic contains 6 replies, has 5 voices, and was last updated by Profile photo of click click 4 months, 3 weeks ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #28474

    Zara Gough @zarahg
    My Robox is a Blue Commercial Version

    Hi everyone,
    I want to print a simple object using 2 different colors. I tried doing this by changing the reel mid-print and just pausing, ejecting the old one, and loading the new reel before resuming. The only problem is, both times when I tried to do this, the alignment had shifted by a few mm (and in the same direction both times).
    You can see what I mean in the attached photos. It’s supposed to be the shape of a cone with the top cut off. Is there some way to fix this? Did I do something wrong when I changed the reel? I’m new to 3D printing so I’d really appreciate some help!
    Cheers

    • This topic was modified 4 months, 3 weeks ago by  Zara Gough.
    Attachments:
    You must be logged in to view attached files.
    #28497

    hagster @hagster
    My Robox is a Blue Commercial Version
    UK

    @zarahg i think this has been reported already. Looks like a bug in Automaker 2.00.01. The current solution is to downgrade to AM1.03. If you do then be sure to look at the downgrade intructions first as you need to reflash the firmware before installing the old software.

    I would hope the bug is fixed in the new update that is due any day now. So if you can hold on for a few days this would be much easier.

    pause-resume not accurate

    How to downgrade from 2.00.xx to previous versions - firmware incompatible

    #28507
    Profile photo of BHudson
    BHudson @bhudson
    I have several Robox units Kickstarter and Commercial
    Arizona, USA

    @zarahg This is a bug in the firmware 741. It has been fixed in AM 2.00.02.

    I operate two Betas and one Production Robox.
    See my 3D Hub site at https://www.3dhubs.com/phoenix/hubs/ben

    #28516

    Andy @originalcaruso
    I have several commercial Robox units
    Belton, North Lincolnshire, UK

    Thanks for posting this - I experienced the same issue with AM 2.00.01 and thought it was something I had caused when changing reels

    Locksmith, software developer, Jaguar fanatic
    http://www.247guardian.co.uk/

    #28521
    Profile photo of click
    click @click
    My Robox is a Green Kickstarter Limited Edition

    @bhudson you’ve been saying that for a while now, but AM 2.00.02 is probably weeks away for rest of us. Shame CEL takes so long to release new version and then introduce more problems and we have to wait again even longed to sort them out 🙁

    #28522
    Profile photo of BHudson
    BHudson @bhudson
    I have several Robox units Kickstarter and Commercial
    Arizona, USA

    @click I have been saying it for about a week now because I received the latest RC about a week ago and was told that it should be one to two weeks at that time. I have not heard anything more about it from CEL so I am guessing that it should be one more week, barring any other issues.

    Personally, I would much rather have a smoother release than the more frequent buggy releases. I also know they are working on an issue where older printers are not recognized due to old firmware so this may be adding a slight delay.

    I operate two Betas and one Production Robox.
    See my 3D Hub site at https://www.3dhubs.com/phoenix/hubs/ben

    #28532
    Profile photo of click
    click @click
    My Robox is a Green Kickstarter Limited Edition

    As I said before - I would rather like small, incremental releases where bugs are fixed quickly. Look what happened between 1.03 and 2.00 releases - long, long delay and then loads of bugs. Was the software released sooner, we would sooner spotted issues and we wouldn’t need to wait long time for them to be sorted out.

    At least that’s the current flavour of software development process: make small, incremental releases and have really quick release, spot issues, fix issue cycle. That way there’s perception that it is dynamic and company is very responsive. This way - we have long periods of alpha and beta states and software is again delivered with loads of broken things (again AM 2.00.01 which broke some things that worked perfectly well before). I see it not being anyhow more stable than smaller releases.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.