Mark Dee

@gid YOU’RE BACK! WoooHOO! Good to hear you’re better, and good to have you back

@pelgrim , thanks for this. When you get your plate, you could give me your impressions?

Thanks for the detailed response. I do have access to a dial indicator, and would appreciate that STL file.

At room temp, the bed appears twisted, but makes a snug fit on the clips holding it. I find that the BED i have (however even in thickness it is) bows a bit too much at working temperature. Thus for larger prints, if the nozzles are…[Read more]

@bhudson

Hmmm … should be relatively straightforward to laser cut the bed according to required dimensions.

I found someone who has a waterjet cutter (capable of slicing through an inch of steel, and that got me thinking about getting some material cut to size to mitigate the annoying uneven bed of my Robox.

Any ideas on what I could try?…[Read more]

On a completely separate topic (and I do apologize for this), @bhudson did you receive your geckotek build plate?

Can someone in the US please test this material out on their Robox?

If it works, a few of us could pool together to ship a box to the UK. Shipping costs $59 outside the US for a multiple of 6 reels.

Anybody interested if this works?

Oh I have been waiting to print some flexible filament on my Robox!

Hi @davidmason83

Got Blobs? Think Slic3r

Check out this thread about acne on your prints. It appears to be an artefact from the slicing process.

I have experienced a few proud layers, and have no theory for them. They generally disappear when I have done a regimented calibration before a print.

If you are…[Read more]

Hi @stevekrn , sorry to hear about your issues:

From the picture you have uploaded, the leak appears to originate from a height higher than the metallic tubes bringing material in.

In simple terms, and I am sure you would agree, this suggests that there is a buildup of molten material without enough being ejected, leading to a busted seal.

I…[Read more]

Hi @stevekrn , sorry to hear about your issues:

From the picture you have uploaded, the leak appears to originate from a height higher than the metallic tubes bringing material in.

In simple terms, and I am sure you would agree, this suggests that there is a buildup of molten material without enough being ejected, leading to a busted seal.

I…[Read more]

@clicky Apparently it was the cause of the dreaded B axis error. Ref: some previous thread.
Also, if you look carefully, there isnt a bearing guide for that bar.

Hi @paulsroom, welcome!
let me guess: you’re using Abs? This material tends to curl upwards on smaller sections that do not have enough surface area of attachment on the bed.
This is what Brim is used for, requiring some clean up.

Now each time the print finishes, the bed violently hits the front of the machine to open the door. The shockwaves…[Read more]

Check this out! Straight from the horses mouth:

my first prints

AM is going to be implementing CURA quite soon.

This should be interesting…..exciting! wooo

Here are my 2 cents to the above conversation:

1. Simplify 3d already supports a lot of printers, many of which traditionally use Slic3r.

2. Robox has a few extra bits of code to account for the innovation in the product. ‘Chris’ from CEL has alluded to these in the excerpt above.

3. The chaps at Simplify have undoubtedly got a Robox with them,…[Read more]

@pelgrim If the links aren’t working, try navigating to their forum and searching for ROBOX

@clicky Thanks! If Simplify3d manage to crack the Robox before CEL do, I WILL spend $140.

IMO, the hardware of the robox is held back by the software, and without the advanced functions, it is slowly becoming obsolete on my workplace. I hate…[Read more]

OMG!! A friend recently showed me the INSANE!! (AND I MEAN INSANE) improvements on his prints using Simplify3d.

It does everything that is needed in AM oh so well. i.e.

slices according to best geometry
allows for rafts to be created
slows down the print for slices with low distance of travel so that the next layer isn’t squished on…[Read more]

@smitty if we know exactly what features this occurs with, we could request a fix in the ‘feature request’ section.

I feel an experiment brewing!

Here is the GCODE file for you to examine at gcode.ws

Any theories on what the offending layers / features are?