CubePro Compatibility

[joshhartung]

Hmm, this might be the problem? Your old file comes up with no carriage returns...

[habloIngles]

whoops my mistake

[joshhartung]

Okay this one got though startup just fine but appears to be on an extremely low extrusion rate. It laid down a thin "breadcrumb" trail on the sidewalk before I stopped it. During the startup sequence you can see the printer dump a bunch of filament into the catch bin, so it's not clogged.

**Edit, added M108 S35.0 where there was a repeated M103 and it's printing now. I'll get back to you. In the meantime, updated headers (untested) from the KISSlicer forum:

Current Prefix

Code: Select all

^Firmware:V1.00
^Minfirmware:V0.00
^DRM:0000000000000
^PrinterModel:CUBEPRO
^MaterialCodeE1:-1
^MaterialCodeE2:-1
^MaterialCodeE3:-1
^MaterialLengthE1: 0.000
^MaterialLengthE2: 0.000
^MaterialLengthE3: 0.000
^ModelHeight: 0.000
^LayerCount: 1
^LayerHeight:0.2
^Supports:-1
^Raft:-1
^Density:Hollow
^Pattern:Diamond
^Version:321-636
^Time:20 
M404 S40
M227 P250 S250 G300 F700
M228 P0 S250
M231 P0 S0
M232 P2500 S2500
M233 P1850
M106 P100
G4 P0
M601 P2 S30 F5
M228 P0 S1
M227 P1 S1 G1000 F1000
M240 S1400

Current extruder select:

Code: Select all

M<EXT+1>04 S<WARM<EXT+1>> P1
M<EXT+1>04 S<TEMP> P1
G1 X128.000 Y136.000 Z5.2000 F9000.0
G1 X128.000 Y161.000 Z5.2000 F9000.0
G1 X128.000 Y157.000 Z5.2000 F9000.0
M<EXT+1>04 S<TEMP>
M55<EXT+1> P1500 S50
G1 X128.000 Y136.000 Z5.2000 F9000.0
M601 P2 S30 F5
M404 S0 P1

"CubePro has offsets set in the firmware/setup-options so any extruder will goto the correct location simply based on the previous M word. this is the cube pro Wipe section- normally ended with ^InitComplete"

Current extruder deselect:

Code: Select all

^ BfB-style
M<EXT+1>04 S<WARM<EXT+1>> P1

Current postfix:

Code: Select all

M104 S0
M204 S0
M304 S0

"CubePro will detect the EOF and park"

credit to Epop for the above and the attached file (http://www.kisslicertalk.com/viewtopic. ... 7&start=40)

[joshhartung]

Much better! Right now it looks like the machine is just making too big a stroke when filling walls, resulting in some spill-over. Probably because the head has such high inertia.

Also the finishing layer looks really "goopy". Could this be because we're extruding at 265 instead of the normal 225 for ABS?

Any thoughts on the GCode posted above this?

[joshhartung]

And more pics.

[loffler]

We have been making pretty good progress with Kisslicer over on the other forum and getting prints to run on this problematic printer - how are things progressing with simplify3D?
Are you any nearer to integrating cubepro support?
I can provide help in terms of Kisslicer and bfb files that I know work to help disect and copy Gcode etc, but I cant help with the actual slicing or settings as I dont have a simplify3D license.
I would be willing to help test out bfb files produced by simplify3D to test on the cubepro machine though.
Let me know if I can help.

[JoeJ]

@loffler - As of their latest release (V2.2.2), the software is already compatible with the CubePro. I know many people (and businesses!) that are already using S3D with their CubePro's since it adds a ton of capability over the stock software.

If you need the instructions and profiles, go here: http://forum.simplify3d.com/viewtopic.php?f=8&t=2177

[loffler]

Yes, I am aware of that thread and the claim that Cubepro is supported, but it appears to be in trial stages at best.
I am using 2.2.2 and imported the profile - CubePro Double.fff
I have output the bfb files without modifying any settings and encoded with Codex. The file is not recognised by the printer - file format error.
I have tried editing the file manually to inject known working Kisslicer code, but I always get file format error or it actually crashes the printer.

Has anyone actually got it working on a cubepro printer without any manual editing or hacking - just using S3D and the profiles?
If it indeed works, I suspect its something not quite right in the script page with the gcode additions or the post processing.
I would love to get it working, it is a great program.

[MichaelHerron]

Having dialed-in KISSLICER to work with our CubePro Duo, we finally got Simplify3D to hopefully improve our workflow.

It is somewhat frustrating to have to start from scratch to dial-in the printer, but I think we've made great progress:

First, the gcode formatting was all wrong:
sometimes it would lack line-feeds, other times it would look fine, but there would be a leading-space in each line.

Deleting the "{REPLACE "\n" "\r\n"}" in the post-processing line fixed this. (not sure if this is a windows thing or not)
Changing the firmware version in the first line of the script was also necessary.
After that, we were able to load the .cubepro file into the cubepro software to send to the printer.

We're working on dialing in the speed right now, but setting the M108 SXX to about 1/100 of the movement speed seems to get close (slight underfill so far, but close)
Other key params are:
Layer height: .2mm
nozzle dia: .4mm
Auto Extrusion width

haven't optimized temp yet, but working at 240C

[loffler]

Seems you are having the same formatting issues I was, glad to see its not just me.
See the other post linked to above, but on the advise of support, I now use {REPLACE “\n\n” “\n”} & {REPLACE “\r\r” “\r”} which fixes the formatting for me.
I have edited the post processing and gcode prefix a lot to get what I want ans now works very well.

I have been dialing in S3D for the last week or so and and close to having good settings too. Agreed that 1/100th feed rate is close. Im curretly working with a speed of a little over 2000 and a feed rate of 17-20. I have had it running much faster but was getting a lot of jumps resulting in steps in the model.
I have got the same temp and cooling profiles as the official cubify software and works pretty well, first layer at 260 and the rest at 250. Cooling coming on after 10 layers.

PLA is a lot easier to dial in than ABS and I even tried a dual head print this morning with mixed results.
I am having issues with what appears to be nozzle offsets or something. Single head prints are fine, but dual head prints position the 2nd nozzle over the waste bin and prime the 1st nozzle into thin air. On dual head prints, the offset is also present. It wouldnt be a problem but its extruding at the time!
I cant see the offset in the gcode, so its either in the firmware or something else.