Thanks Thanks:  10
Likes Likes:  27
Dislikes Dislikes:  0
Page 18 of 18 FirstFirst ... 8161718
Results 171 to 175 of 175
  1. #171
    3D Printer God(dess)
    Join Date
    Nov 2016
    Posts
    1,572
    Post Thanks / Like
    I guess scale matters

    Not at all... they perfectly grab the loops of the chip contacts.
    Add a couple of wires and a solder them to the chip and you have clip-on chip.

    Of course, it has to be used with an external spool hub

    - - - - - - - - - -

    This is for those looking for an adjustable filament driver mechanism...

    This is -NOT- mine. This is something I found and find intriguing.
    https://www.thingiverse.com/thing:2289203

    Shouldn't require too much modification for the Cube 3.
    This also makes the square drive stepper motor more tolerable to the function.

    x11.PNG

    - - - - - - - - - -

    Cube 3 torture test

    x10.PNG

    3DS way-cool purple ABS

    - - - - - - - - - -

    ...not every hack has to be printed!!!

    x13.PNG

  2. #172
    Administrator bolsoncerrado's Avatar
    Join Date
    Nov 2014
    Posts
    3,084
    Post Thanks / Like
    Lol

  3. #173
    3D Printer God(dess)
    Join Date
    Nov 2016
    Posts
    1,572
    Post Thanks / Like
    Quote Originally Posted by bolsoncerrado View Post
    Is the filaboat working fine with the dented spools?
    Finally gave this new FilaBoat a run for its money. Held up perfectly fine; no spills tumbles or tangles.
    Ran loose spools, stock spools, and tightly rewound spools. The neon green is bypassed in this image.

    b1.PNG

    - - - - - - - - - -

    Today I finally figured out what the Cube 3 is doing when it slows down...

    It has something to do with a G-code setting for "minimum layer time".
    Apparently, the Cube 3 deals with this two ways;
    1) It slows the print velocity...
    2) It parks and rests for a period.

    Not sure where the 3DS slicer makes the distinction, but now it makes sense.

    This is where the Cube Print 4.03 app differs from M$ 3D Builder app.
    3D builder knows to slow down on Marvin's loop when printing in ABS.
    Cube Print 4.03 just makes a mess of the loop.

    This comment applies to printing 1 marvin by itself.
    I am suggesting 3D Builder has better thermal management.


    I also found the "alternate" raft... literally, raft vs. skirt.
    It is an option that showed up in the decoded .cube3 file.
    Neither app lets you take control over this setting.

    - - - - - - - - - -

    I finally feel vindicated about the test print provided by 3D Systems.
    Yes, it is a 3D System sliced object...

    ...back from V1.00 with a minimum FW version of 0.00!

    And the notable difference that I've argued more than once...

    I've stated in the past that the test print does a sparse fill as compared to current prints on the build plate.
    I've tested and proven this to myself over and over again.

    Today I finally figured out why.

    The two test prints in the F/W drive (the internal SD) has both test prints in a "FT" folder.
    When I decompiled the test prints (welcome.cube3) it shows a first layer at 0.38mm
    If you look at any current print file, it is set to 0.25mm.

    This explains SO MUCH!

    And on another note, NONE OF THE KANJI CHARACTERS ARE THERE! In neither file!

    This is just further proof that the Kanji data is just the image on the screen.

    Here's the header data for both:

    PLA:

    ^Firmware:V1.00
    ^Minfirmware:V0.00
    ^DRM:000000000000
    ^PrinterModel:CUBE3
    ^MaterialCodeE1:86
    ^MaterialCodeE2:-1
    ^MaterialCodeE3:-1
    ^MaterialLengthE1: 501.027
    ^MaterialLengthE2: 0.000
    ^MaterialLengthE3: 0.000
    ^ModelHeight: 2.310
    ^LayerCount: 12
    ^LayerHeight:0.1925
    ^Supports:-1
    ^Raft:-1
    ^Density:Hollow
    ^Pattern:Lines
    ^Version:244-567
    ^Time:17
    M227 P550 S550 G450 F600
    M228 P0 S550
    M231 P0 S0
    M232 P5000 S5000
    M233 P1000
    M106 P100
    G4 P45
    M601 P2 S60 F5
    M542
    M228 P0 S5
    M227 P1 S1 G500 F500
    M601 P8 S60 F5
    M240 S450
    M204 S120 P1
    M104 S173 P1
    G1 X-103.500 Y0.000 Z5.3800 F750.0
    M104 S215
    G4 P15
    M551 P850 S50
    G1 X-88.500 Y0.000 Z5.3800 F7000.0
    G1 X-103.500 Y0.000 Z5.3800 F7000.0
    M104 S215 P1
    M601 P2 S60 F5
    M103
    M543
    M107
    G92 X0 Y0 Z-0.080
    ^InitComplete

    ABS:
    ^Firmware:V1.00
    ^Minfirmware:V0.00
    ^DRM:000000000000
    ^PrinterModel:CUBE3
    ^MaterialCodeE1:136
    ^MaterialCodeE2:-1
    ^MaterialCodeE3:-1
    ^MaterialLengthE1: 665.144
    ^MaterialLengthE2: 0.000
    ^MaterialLengthE3: 0.000
    ^ModelHeight: 2.310
    ^LayerCount: 12
    ^LayerHeight:0.1925
    ^Supports:-1
    ^Raft:-1
    ^Density:Hollow
    ^Pattern:Lines
    ^Version:244-567
    ^Time:18
    M227 P400 S400 G750 F1000
    M228 P0 S400
    M231 P0 S0
    M232 P5000 S5000
    M233 P1000
    M106 P100
    G4 P45
    M601 P2 S60 F5
    M542
    M228 P0 S5
    M227 P5 S5 G500 F500
    M601 P8 S60 F5
    M240 S450
    M204 S200 P1
    M104 S230 P1
    G1 X-103.500 Y0.000 Z0.3800 F750.0
    M104 S260
    G4 P15
    M551 P500 S50
    G1 X-88.500 Y0.000 Z0.3800 F7000.0
    G1 X-103.500 Y0.000 Z0.3800 F7000.0
    M104 S260 P1
    M601 P2 S60 F5
    M103
    M543
    M107
    G92 X0 Y0 Z-0.10
    ^InitComplete

    - This is really strange, Alex... When I pasted these from Excel, all my M601 Pn S60 F5 changed to S-60! Dangerous for sharing code!-

    My how little things change... <<== PDF BFB-3000 manual link
    Operation manual for the BFB-3000... LINK

    I wonder if we can glean stuff from the Axon BFB generator noted in this manual.
    It is obvious 3D Systems remained on a single freight train from day one of their consumer printer market.
    It even has some NASA references when you dig into this printer and the code. This means there is public record regarding this printer.
    We truly need to better understand the custom Mxxx codes used in the .cube() files.
    I have a feeling these routines and assigned codes spawned from the Axon app and were never fully adopted by the community at large.
    Yet, 3D Systems chose to maintain their legacy interpretations and continue building on them. That decision can really mess with conversion apps.
    The command set is so small that the required detailed information could be covered in a few pages.

    No matter what, today was a good day. Got rid of my woes with ABS on the Cube3! Resolved a nagging itch about the stiffer bowden tube on the Cube3.
    In all, I owe you, John Tee! A few simple words cleared the skies. Conversion is working perfectly. Shame to loose WiFi though.

    - - - - - - - - - -

    Here is some nostalgia...

    BFB_materials.PNG

    Anyone know the backstory between BFB and 3DS?

    - - - - - - - - - -

    When it rains it pours... and not just salt!

    I took a chance on the re-listing of the two red PLA cube3 carts on ebay by making an offer.
    Looks like I have 3 new cube3 carts coming my way.

    I may have to do a B2B upgrade offer on one or two of these.

    - - - - - - - - - -

    PETG IS UP AND RUNNING ON THE LITTLE WHITE CUBE3! Okay, color me intrigued. Sticks well to LokBuild, PETG has a nice thermal profile, and the EkoCycle slicer is gentler on the mechanics. Price to pay is a quick edit. Ouch! And I'm also going to suggest that this profile may work well with 3rd party ABS as well!

    - - - - - - - - - -

    One vote for PETG being wearable...

    f.PNG

    I got to hold it for about 5 seconds before it was no longer mine

    - - - - - - - - - -

    Finally designed an 18650 Li-Ion battery holder that I like.

    https://www.thingiverse.com/thing:3250065

    Also works well as a 18650 cell protector.

    - - - - - - - - - -

    I was doing some more work on the wiper in the Cube. Leather works but requires maintenance after the wipe. Not good for multi-color prints.
    Then I was using a jar opening pad... silicon... and it too worked well. The tip would melt the silicon but the filament was cool enough to not make a deeper groove.

    But it does have a small clearance under the tip that still drags filament onto the build plate all too often. Yesterday I had yet another bright idea...

    You know that 4mm Teflon tubing you have laying around... a small say 7mm piece? Slice it lengthwise with a good knife to allow flattening of the tube.
    Now stuff it in the little white waste bin clip. It should fit wall to wall where the normal wiper would sit. I faced the -arc- to the outside of the printer.
    I also made sure that the top edge of the Teflon is perfectly aligned with the bottom of the extruder tip. It has no way to not wipe perfectly flush with the tip!

    ...and then I run it a few times... making notes along the way. Sure enough, the wipe is perfect! However, I learned that the Cube 3 drools after wiping.
    The wiper appears to be functioning perfectly but the code is starting to extruder before it ever gets to the build plate. A 3mm turd was hanging off the extruder tip before it ever hit the build plate.

    I need to see if this is in the slicer. Certainly a routine I've been eyeing on changing for a more reliable initial trace being stuck to the build plate.
    Last edited by TommyDee; 09-08-2018 at 12:55 AM.

  4. Likes bolsoncerrado liked this post
  5. #174
    Regular 3D Printer
    Join Date
    Feb 2018
    Posts
    97
    Post Thanks / Like
    When the printhead is heating up over the waste bin at the beginning of a print, the material begins oozing out quite a bit BEFORE the purge step.

    In the bfb code, the first 'start extruder' (M101) doesn't occur until the head is in position over the first perimeter.

    I wonder if the blob is just a result of oozing after the purge (M551), rather than extrusion starting too soon? Although, there's a really short time for that to occur, between the wipe and finishing the move to the starting point.

    How about adding a short strip off to the side just before starting to print?

    <snip>
    ...
    M107
    M107
    ^InitComplete
    #Vector T22
    M228 P0 S450
    M227 P450 S450 G600 F800
    M103
    # add a small purge strip here
    G1 X-70.000 Y0.000 Z0.2200 F8000.0
    M108 S40.0
    M101
    G1 X-70.000 Y-25.000 Z0.2200 F1302.0
    M103
    # end of purge strip - back to our normal program
    G1 X-16.369 Y-19.283 Z0.2200 F8000.0
    M108 S40.0
    M101
    G1 X-16.853 Y-19.421 Z0.2200 F1302.0
    G1 X-16.853 Y15.931 Z0.2200 F1302.0
    G1 X-14.903 Y18.091 Z0.2200 F1302.0
    ...

    <etc>

  6. #175
    3D Printer God(dess)
    Join Date
    Nov 2016
    Posts
    1,572
    Post Thanks / Like
    Ooze I can see but it does have to do with the "blob" problem. It is all managed in the M227 and M228 calls.

    There is a G1 in the initialization that really doesn't need to be there. It is the one right after the purge.

    I plan to play around with the start routine to see if we can get a more reliable first touch.

    One thing I cannot seem to do with notepad.exe; how do you remove lines with a "replace all"?

    - - - - - - - - - -

    ...and I see something interesting that may just support my position on the extra G1:

    ^Firmware:V1.14B
    ^Minfirmware:V1.14B
    ^DRM:000000000000
    ^ConfigAndConfiguration:X562-X560
    ^PrinterModel:CUBE3
    <SNIP>
    M104 S210 P1
    G1 X-100.500 Y0.000 Z5.0275 F7000.0
    M104 S235
    G4 P15
    M551 P600 S50
    G1 X-95.500 Y0.000 Z5.0275 F7000.0
    M104 S235 P1
    M601 P2 S60 F5
    M103
    M240 X400
    M240 Y450
    M543
    M107
    M107
    ^InitComplete

    Cube3 test print:
    ^Firmware:V1.00
    ^Minfirmware:V0.00
    ^DRM:000000000000
    ^PrinterModel:CUBE3
    <SNIP>
    M104 S173 P1
    G1 X-103.500 Y0.000 Z5.3800 F750.0
    M104 S215
    G4 P15
    M551 P850 S50
    G1 X-88.500 Y0.000 Z5.3800 F7000.0
    G1 X-103.500 Y0.000 Z5.3800 F7000.0

    M104 S215 P1
    M601 P2 S60 F5
    M103
    M543
    M107
    G92 X0 Y0 Z-0.080
    ^InitComplete

    That means that at one time they actually went back over the wiper at initiation. They should have removed both lines so the housekeeping happened over the waste bin, not outside. This should be an easy fix. Replace the
    G1 X-95.500 Y0.000 Z5.0275 F7000.0 with G1 X-100.000 Y0.000 Z5.0275 F7000.0

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •