Cubepro gcode

[Epop]

I'd like to see his info! I've seen guys using an eeprom resetter of some kind but didn't find information on how to make one. Wouldn't be of use if I could just stop it from looking for the chip in the first place.

I was playing with it today and face palmed myself just being dumb. So I had basically skipped cubit(totally missed the link to the setup notes at the bottom of the page) and went into manually/copy pasting to modify a kisslicer file to run... a LOT of copy and pasting.

I got a modified print running and let it run... yeah, it's still writing to the chip. it doesn't check what material is what but whatever extruder is printing, CubePro will subtract that length from the chip in that material bay. which is why it kept catching me with 'not enough material alarm. It ran until it hit a filament check, read the chip at 0%... and stopped. If there are chips with 'enough material' it keeps going. It'll take material off of any chip.

I got Kisslicer/Cubit running... poorly. If I replace the program header. It looks well enough to start but it's on crack. Which I think is where you guys are.
(its been a long time since I've uploaded to a forum... gimme a heads up if there is a better way)

first white 'fine tune'... I thought this was interesting because it was all over the place in the middle... but seemed to get back in position @ the top.

first black 'fine tune'... train wreck?

with black I just replaced M104 with M204- M551 with M552- M101 with M201. maybe I missed something?
Meanwhile if I do A LOT of copy and pasting I can get a Kisslicer file to run 'fine' but my settings are horrible atm. it runs without causing my machine distress though... Anybody know what CubeIt is doing? other than wiping Kisslicer header/footer, and adding the funny 'wipe' where it bounces back and forth in X?

Thanks.

[Hugues]

Hi,
I will try to reply to your answer about cubeitmod job.
-It change the header as you see.
-It calculate the readable RPM for cubex because it cannot go under 0.1 or cannot read the second number after the dot. Did you check this on cubepro ?
-It change the speed of short segments in the infill and solid to avoid over extrusion. But as some of us notice it's doing some error on those parts without reason. Your printer try to reach an unable speed and skip step. Maybe it's the reason of your "stepy" fine tune print.

You can download the au3 file of cubeitmod on the previous forum : https://groups.google.com/forum/m/#!top ... -k1hdxZA6I

The editor is free and the code is well documented. Maybe try to remove all unnecessary function to start.

Good luck guys !

[rassilon50]

Hey,

Got a CubePro Duo and need some help.

I've been following the forums but got very confused over what is the necessary code for the .ini files.

I already have the CodeX converter so I know what to do with the files once I've got the gcode.

Does anyone have a "definitive" set of .ini files that they know works for the CubePro Duo?

Thank in advance! You'll save my sanity!

[Epop]

Thanks Hugues.

I have not tried to extrude under .1 but I'll try it monday. ... the first print I got to extrude with Kisslicer had the extruder gain set at 1.0- this is the setting you're talking about... right?

Hey,

Got a CubePro Duo and need some help.

I've been following the forums but got very confused over what is the necessary code for the .ini files.

I already have the CodeX converter so I know what to do with the files once I've got the gcode.

Does anyone have a "definitive" set of .ini files that they know works for the CubePro Duo?

Thank in advance! You'll save my sanity!

"definitive" set... no... you can get the 'good place to start' files for CubeX from that link to google groups Hugues just posted, or goto http://www.cubexupgrade.com/ and download the cubeit files which are "the same" (?) as what you get off the google group post. They are what we(?) are using on the Pro which is, of course, slightly different from the X. The rest of us are trying to get it to work but not all of us are using the same Firmware versions so its a bit clumsy.

CodeX just encodes/decodes *.bfb files so they read on the CubeX/CubePro

Slice on Kisslicer with Cubeitmod in the post processor command in the printer firmware tab.
run through CodeX so the Cube will read it
Watch it freak out while it kindof... builds a part...

[rassilon50]

Epop thats brilliant! Thanks!

Got a CubePro for Christmas and it's been driving me mental, and almost no help from 3D Systems support either, who did finally admit that I could get better print file creation from other software!

I've been going round in circles trying to follow a multitude of different techniques, some with just inputting all the settings, and now CubeItMod, but didnt realise you still needed to use the CUbeX to recode it after the CubeItMod.

I'll give it a go and see what I end up with! Thanks again for your help, feel like I'm making progress now!

UPDATE - Right, I've now got the settings in and CUbeItMOD working so it creates a file / .bfb.bak file as well. I have used CubeX to Decode the .bfb file to a .cubepro file, but when I put it in the printer i get "Print File Protected"

Am I just being a muppet? It doesn't seem to be a locked file. Do I need to edit something? Thank!

[Hugues]

Sure they are not the same, your cubepro are well protected ! I don't say to use cubeitmod at this step to print with kisslicer because you will have to tweak it to mach with new functionality and protection. Codex is a good tool to identify gcode readable by the cubepro but it's not able to print file.

I also forget a functionality given by cubeitmod, the prime and suck (M227 M228) with custom value who are important to get a good print with bulk filament.

The extruder gain is not the right, i don't remember it now but you can use the one set in the ini file provided by Giovanni. The ini files are the same from the google group and my website, but as the hardware are the same between cubepro and cubex the gain value should be equal.

Your print is a good start, the step are due to the error done by cubeitmod, x y motor are lost by to high speed. The gain value is more about extrusion and rpm multiplicator.

[Epop]

"File protected" error appears when the ^DRM:000000000000 comment is missing or (as far as I've tested) anything other than 000000000000.

Add this to the G-Code(main tab) > Prefix(sub tab) in Kisslicer I've messed with a few variations of it... but this one will run.

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: 0
^LayerHeight:0.0
^Supports:-1
^Raft:-1
^Density:Hollow
^Pattern:Diamond
^Version:321-636
^Time:60

Yeah... the lengths they went to to sell their filament are a bit frustrating.

I'm going to run tests on getting it to extrude correctly tomorrow if I have time. I think it might be an issue with version incompatibility with Kisslicer and Cubeit.

[Epop]

Okay, first a few things to consider.

These settings are for CubeX I have NOT tweaked them AT ALL.
The second print is of Kisslicer v1.5-BETA(2.7) using *.ini files from the current build.
The CubePro accepted extrusion gain of 0.0225 (CubeX did not and required Cubeit mod)

$15 filament Kisslicer 1.4.5.10 (current stable build)@ .0225 gain

^NOT processed with Cubeit

$15 filament Kisslicer BETA v1.5+ Cubit

The side step/filling issues are (I'm assuming) from an error in the build(or because I copied setting files from the current build )... the 'top' is offset. and one side in Y overfilled while the other side in Y was underfilled.
There is an issue between the current release of Kisslicer +Cubit causing it to malfunction. The beta processed with Cubit. Feeds&speeds were comparable between Kisslicer ONLY and Kisslicer processed with Cubit.

The files look a bit cleaner(more like Cubepro.exe files I should say?) when run with Cubit though.

It still writes to the filament chip as others have mentioned. going to keep messing with it... maybe get it to error out at program end instead of 'end', anybody else try this?
(there are also a few more pictures from different angles if anyone wants to see)

[martini]

Hey!

@Epop seems like you have made great progress!!

For the chip hacking attemps I guess I am done for now. I have tried several options, including writing this company http://www.wctek.com/shop/ they have a chip resetter for Da Vinci cartridges but they explained it won't work on ours and he doesn't own a cubepro to develop one (I bet he never will). The programmer I have been in contact with offers to create a firmware for a similar microcontroller to reset the chips. He considers it would take 30-40 hrs to build ($12/hr). However, he is very honest about the circumstances (he doesn't own a cube either) and can't do any testings so it would still be experimental and may or may not work. I have paid for his assistance so far but this is out my budget

[Polynomial]

I just wanted to take a minute to check in with everyone on the topic of the CubePro and KISSlicer,etc...
I've had our CubePro Duo for about a month now, and would also like to try options for getting better print results as well as mostly, saving costs regarding the filament.
I run our systems on Mac OS X, so I've got KISSlicer installed along with CubeitNet45 and I've been able to generate a couple of .bfb files but with errors during their generation ("Failed Error 512").
Since CodeX is a Windows-only application so I'm not able to open and explore my .cubepro files to see what prefix lines I may need to use for printing, ABS primarily. I was curious if anyone had figured out anything any further with the prefix lines necessary to use bulk filament.

Lastly, if this isn't a reliable option just yet for us CubePro owners, then is it possible to downgrade firmware versions to get back to say, V1.04 from my current 1.08A, so that I could hopefully run once my cartridges are empty? I cannot for the life of me find a download link for 1.03 or 1.04 firmwares anyway on the net, thought maybe someone on here might have it achieved away and could share it....