Jump to content

Recommended Posts

Posted · BQ Witbox 2

I have a problem where I can't print because the print is misaligned. I have used Cura many times before, but for the past week, I haven't been able to print because of this issue that it displays. I would like help with this. I've tried both STL and MF3 formats as well

BQ witbox 2.png

  • Link to post
    Share on other sites

    Posted · BQ Witbox 2

    There is a text at the bottom of the screenshot, and I don't know how to fix it. This is what it says: "make sure the g-code is suitable for your printer and printer configuration before sending the file to it. the g-code representation may not be accurate."

  • Link to post
    Share on other sites

    Posted (edited) · BQ Witbox 2

    If you have loaded a Gcode file, what you see on screen is the representation of the Gcode movements.  It cannot be changed in Cura (there is no model in a gcode file).  The message is just to remind you that the gcode should have been sliced for the printer you intend to print with.  You should be able to click on the "X" in the top right corner of that "Information" message box and dismiss it.  The "X" is very hard to see because you are in Dark mode.

    image.thumb.png.86b9701f86e524489a364143f3c2e7c7.png

     

    Are you attempting to print via USB?  That should work.

     

    Edited by GregValiant
  • Link to post
    Share on other sites

    Posted · BQ Witbox 2
    5 hours ago, GregValiant said:

    Are you attempting to print via USB?  That should work.

    Please don't encourage people.

     

    As @GregValiant said, that warning is just there to say that Cura renders gcode files by reading the files and drawing the path the nozzle will take assuming that it follows the standard behaviour for that flavour of gcode.

     

    There are lots of printers with little (or big) quirks in how they follow most gcode commands fine but treat some differently. Cura can't know what printers might do this or how they'll do it so the warning is just there to get you to double check that that gcode is going to be compatible with your printer.

  • Link to post
    Share on other sites

    Posted · BQ Witbox 2

    First of all, thank you very much for the quick feedback, but the problem is that when I insert the SD card into the printer and the printing starts, everything starts to shift.

     

    Somehow, it doesn't really work with USB, I don't know why, but I can't use it.

  • Link to post
    Share on other sites

    Posted (edited) · BQ Witbox 2

    Hi there.

     

    I'll think about a little statement here, Cura will give this message to any "gcode" file opened like this, even the file sliced with this given version! This is a reminder to ensure that the user know the origin of the file to be uploaded are made for this printer. -And if this did not work, "normally" -the firmware in the printer "may"/will (?) ask question saying; this will reset (or something like this) the original setting -are you sure about this?  And you have to answer Yes or No in order to start this print.

     

    I thought that same way as Greg did here, -as this is more an assumption due to the "question" and the "setup" present here.

     

    On the older versions of "Cura and windows", people used to print over USB. However with later versions, Ultimaker advice not to use USB with Windows, -as this communication might be interrupted by other "ongoing" hi priority services!

     

    This might stop you valuable print, half done after 15 hour...    So always use the SD card or USB stick. 

     

    Written about 6 hour ago..

    ----------------------------------------------------------------------------------------------

     

    This is kind of weird, what do you mean by "everything starts to shift"?  Please explain in more details.

    Looks like a printer problem, but might also be a printer definition issue..

    The project file of your print object may also help in this issue.

     

    In Cura, make sure your printer are selected, then check that the model with related setting are correct, then select "Slice".  When the model are sliced, press Ctrl+S and this will save the project file at a given place, when you conform it.

    Post this file here.

     

    I'm sure someone will answer.

     

     

    Thanks

    Torgeir

     

     

     

     

     

    Edited by Torgeir
    Better wording.
    • Like 1
    Link to post
    Share on other sites

    Posted · BQ Witbox 2

    Thank you very much for your reply @Torgeir. What I mean is that it shifts while printing, and after about 20 layers, it shifts forward and continues from there, then it happens again. The printer doesn’t have a newer firmware version, but the one that was on my SD card has been printing fine for a long time; it's only with the new ones that this happens. Here are the G-code, STL, and MF3 files.

    BQW2_Project.gcode Project STL.stl Project 3MF.3mf

  • Link to post
    Share on other sites

    Posted · BQ Witbox 2

    "What I mean is that it shifts while printing..."

     

    Ah!!  It isn't the gcode.  The "Layer Shift" is most likely caused by a loose belt or other problem with the "Y" axis on the printer.  You need to take a close look at the mechanicals and maybe do some maintenance.

    I see that the BQ Witbox 2 is set up for Acceleration at 3000mm/sec.  Enabling "Acceleration Control" in Cura at 500 (for everything including travel) may allow this to print without shifting.  Hard starts-and-stops combined with mechanical problems can cause layer shifts.

    Not enabling "Acceleration Control" in Cura doesn't turn it off in the printer, but rather allows the printer to use it's current defaults.

     

    When you open a Gcode file in Cura, a separate app (Gcode reader) reads the gcode into the preview.  There is no relationship between the slice and the gcode preview.

    You can see here that the gcode is correct with no "forward shifts".  I could read it into AutoCAD to double-check but there really isn't a point.  It would show the same thing.

    image.thumb.png.39560d9b69e5b1ed9917fb3779fa2b8c.png

    • Like 2
    Link to post
    Share on other sites

    Posted · BQ Witbox 2

    Hi @ttamas,

     

    I've been pretty busy lately, so not much time for 3d "business".

    But I've seen the reply from @GregValiant and very much agree in his assumptions -as this kind of error "normally" do not address a faulty SD card.

     

    I would like to add another issue that also can give the same problem as shifting (layer offset)..

    This can happen if the bed sliding "bearing" have lack of lubrication or be come a little corroded.

    The above situ may make the stepper motor loosing steps and create Y axis offset.

    In such case, clean of the bearing lubricate and make it smooth.

     

    Well, good luck.

    Torgeir

     

     

    • Like 1
    Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.9 stable released!
        Here comes Cura 5.9 and in this stable release we have lots of material and printer profiles for UltiMaker printers, including the newly released Sketch Sprint. Additionally, scarf seams have been introduced alongside even more print settings and improvements.  Check out the rest of this article to find out the details on all of that and more
          • Like
        • 5 replies
      • Introducing the UltiMaker Factor 4
        We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
          • Heart
          • Thanks
          • Like
        • 4 replies
    ×
    ×
    • Create New...