With all the header/ini settings at zero(or -1) my Cubepro v1.08a will not run without chipped cartridges. What settings did you get yours to run on (or do you just have firmware v1.00-1.03)?martini wrote:Update: I have printed many times using fixed bfb files and noticed that I can set everything to 0 and the printer won't even ask for a cartridge which is fantastic. On the other hand, it looks like the cubepro needs to know the material, not just the code but at least 0.001 length otherwise it gets really fast and messy.
I have tried a big build size, a 20x20x20cm box (I wanted to see if with headers settings on 0 it would still run without enough material) and an organic shape with meshmixer supports of about 100mb but both .bfb files came out with 0 bytes. In fact, any file bigger than 20mb has come out empty.Epop wrote:What are you calling a 'big' file? (build size or file size and how much) I've run ~15MB builds through it without issue... it took a few min though.
CodeX.exe is the only utility I've found to turn *.bfb files into *.CubePro files(compile them so they'll run). The machine will read *.bfb, but it won't print them unless they've been processed. (*.bfb seems to be the file extension 3DS used to use)
With all the header/ini settings at zero(or -1) my Cubepro v1.08a will not run without chipped cartridges. What settings did you get yours to run on (or do you just have firmware v1.00-1.03)?
I didn't notice a difference on mine... I just ran a ~25mm dia. puck. I could imagine that the firmware picks up some of the information for speed/ acceleration /deceleration, though, I don't think that would be the case.
One of the (few) things I picked up is the screen shows the build options. It has little icons for build strength, color, pattern etc. I thought that's all it was doing.
Cubeit is converting the files wrong, it's removing ALL M227(global retract/return?) words from the program. At the moment it looks like all its doing is removing kisslicer comments and code for reprap machines that CubePro isn't using. I'll try doing it manually and see what I get.
Unless any of you have seen it doing something else?
... Okay... big file.martini wrote: I have tried a big build size, a 20x20x20cm box (I wanted to see if with headers settings on 0 it would still run without enough material) and an organic shape with meshmixer supports of about 100mb but both .bfb files came out with 0 bytes. In fact, any file bigger than 20mb has come out empty.
I am running on v1.03. It doesn't make much difference if I change the rest of the headers or not, I if set material length on 0.000 it won't ask for a cartridge but unless an ABS or PLA icon is there (by setting material length) the printer goes nuts. Does your printer write the chip with filament used even with all settings at zero? Mine does. I wouldn't mind inserting a chipped cartridge if the printer is not writting it.
I am a mac user and kisslicer has a mac version but not cubeit nor codex seem to have one or at least I can't make them work yet; so I got virtual windows but kisslicer crashes. I'd totally buy kisslicer pro but it hasn't been useful for me so far, I just use native cubepro files, decode and recode back again.
I got the first layer to print!Yodajammies wrote:Just dropping in to confirm the current procedure for running Kisslicer files on the cubepro.
Running v1.08 using stock materials
I've replaced the header initialization values and the file is accepted by the machine but throws a filament error after warming up.
To confirm, is this about as far as we have progressed in getting a KS file to properly run on a cubePro?
Code: Select all
...
^InitComplete
M103
M561 P400 S500
G4 P1
^Select extruder, warm, purge ---------yes... its purging... again... :B
G4 P0
M601 P2 S30 F5
M228 P0 S1
M227 P1 S1 G1000 F1000
M240 S1400
M104 S220 P1
M104 S265 P1
G1 X108.000 Y136.000 Z0.4000 F750.0
G1 X108.000 Y161.000 Z0.4000 F9000.0
G1 X108.000 Y157.000 Z0.4000 F9000.0
M104 S250
M551 P1500 S50
G1 X108.000 Y136.000 Z0.4000 F9000.0
M601 P2 S30 F5
^ExtChangeComplete
M227 P1 S1 G1000 F1000 <<<<added
M106 P100
M304 S260 P1
M228 P0 S250 <<<<added
M227 P250 S250 G300 F700 <<<<added
M103
^ 'Perimeter Path', 45.5 [RPM], 10.0 [head mm/s]
G1 X-23.6 Y5.8 Z0.20 F2175.0
G1 X-23.6 Y5.8 Z0.20 F2175.0
^ extruder on
M108 S35.0 <<<<added
M101
G1 X-23.67 Y6.21 Z0.20 F2175.0
G1 X-24.38 Y6.82 Z0.20 F2175.0
...
...
...
G1 X-23.38 Y5.94 Z0.20 F2175.0
G1 X-23.79 Y5.97 Z0.20 F2175.0
^ extruder(s) off
M228 P0 S1 <<<<added
M227 P1 S1 G1000 F1000 <<<<added
M103
^
^ 'Loop Path', 45.5 [RPM], 10.0 [head mm/s]
G1 X-23.97 Y5.8 Z0.20 F9000
^ extruder on
M108 S35.0 <<<<added
M101
G1 X-24.72 Y6.44 Z0.20 F2175.0
...
<skipped to error>
...
G1 X-24.02 Y5.17 Z0.20 F2175.0
^ extruder(s) off
M228 P0 S1 <<<<added
M227 P1 S1 G1000 F1000 <<<<added
M103
^
^ 'Solid Path', 45.5 [RPM], 10.0 [head mm/s]
G1 X-28.32 Y7.41 Z0.20 F9000
----no M227/228
^ extruder on
M108 S35.0
M101
<<<error>>>
G1 X-34.92 Y7.58 Z0.20 F2175.0
...
Code: Select all
M103
G1 X-27.28 Y-13.12 Z1.5 F30000
G1 X-27.28 Y-13.12 Z1.5 F3285
G1 X-37.24 Y-12.87 Z1.5 F3285
G1 X-37.27 Y-12.85 Z1.5 F3285
G1 X-37.27 Y-12.85 Z1.95 F210
... Okay... big file.
Thank you so much for all your testings
Code: Select all
^InitComplete
#Vector T22
M204 S260
M228 P0 S250
M227 P250 S250 G300 F700
M103
G1 X12.160 Y13.167 Z0.4000 F9000.0
M108 S40.0
M201
G1 X12.970 Y12.375 Z0.4000 F1650.0
G1 X13.732 Y11.527 Z0.4000 F1650.0
G1 X14.435 Y10.635 Z0.4000 F1650.0
G1 X15.080 Y9.697 Z0.4000 F1650.0
G1 X15.662 Y8.717 Z0.4000 F1650.0
G1 X16.185 Y7.710 Z0.4000 F1650.0Code: Select all
^Firmware:V1..38.276
G21
G90
M542
M304 S230
M227 P296 S118
M228 P44 S44
M553 P700 S80
M543
M308 S346
M103
G1 X25.7 Y-44.27 Z0.45 F12000
G1 X25.7 Y-44.27 Z0.2 F210
M301
G1 X25.61 Y-44 Z0.2 F896.5
G1 X24.12 Y-42.63 Z0.2 F896.5
G1 X23.03 Y-41.82 Z0.2 F896.5
G1 X21.16 Y-40.64 Z0.2 F896.5
G1 X19.04 Y-39.69 Z0.2 F896.5
I cancelled, I wasn't sure if kisslicer/cubeitmod (cubex) are harmless to the printer, are they? I wonder if the bed leveling and messy drops come from missing information of a whole layer, from Z0.2 TO Z.04Thanks for your feedback! Out of half a dozen forums/groups I've joined during the trouble with CubePro this has been the only forum that people haven't jumped in with "oh... that sucks. Here! buy *MY* printer!"martini wrote: ...
Thank you so much for all your testings
I thought I had v1.3 but actually it's v1.5. Please let me know how it goes on your empty cartridge, do you think I should upgrade?
When there is no ABS/PLA icon it drops material at specified x, y points but doesn't run smoothly from one point to the other, instead the bed levels up and down to get to each point. If you look at the following code (from codex) you will see that the model starts to extrude at Z0.4000 but layer height was set on 0.200mm.
...
I also sliced the same model on Kisslicer and it starts to extrude at Z0.2:
...
I mixed codex headers with kisslicer g1 codes and it worked and moved like printing but no material came out
We'll see how far I go down this CubePro road before getting off on the 'expensive' exit.Me too! I am very determined to trick my machine into bulk filament first. Once I get there I'll have cheap material to mess with kisslicer settings. That's my planThanks for your feedback! Out of half a dozen forums/groups I've joined during the trouble with CubePro this has been the only forum that people haven't jumped in with "oh... that sucks. Here! buy *MY* printer!"
I would NOT upgrade unless you're going to commit to buying 3DS filament- typically any loopholes your version has would be closed if you upgrade to v1.08A.
I concur... I've noticed some funky movements going on in Z though the odd z height might be the 1st layer settings for Kisslicer/cubit (bed roughness is one setting that will change Z)
YES Kisslicer & Cubit (also if they are setup incorrectly) CAN Damage the equipment... wrong coordinates/heights, wrong temperatures, trying to feed way too fast, certain G&M words in the wrong places etc... can damage the parts, especially since they are lightweight.
personally IDC... the 90day warranty is long over and the prints coming from 3DS/CubePro @factory settings are weak IF they run at all, or IF you can remove the only support option you have (yes, or no) without destroying your part.
So...
Todays experiments were...
Home position grinding is... partially my fault it seems. After a fault I haven't been dragging the gantry off the Y limit switch(if you do it, turn the power off first). If I don't x,y is still messed up- if it attempts to return home it will grind depending on where it alarmed out (no m227 is different than no m108) and if I get a 'not enough filament' error it returns home properly if I have reset after fault. on either Cubepro.exe or Kisslicer/Cubit.
I corrected M227/M228 but ran into a layer that M108 was not directly above M101(for extrude start) so it seems it is required. (filament feed error)
My machine doesn't seem to be writing to the EEPROM on the good cartridges I have plugged in, or I just haven't printed enough for it to show.
The tallest build I have made so far was 5.4mm ... at that point there was ANOTHER check for 3D Systems filament. which it failed... I did not see any abnormal G code, and I've swapped out PLA & ABS cartridges and it doesn't seem to care as long as there is a cartridge with 'enough' filament in the machine to start. I don't know if its a timer built into the firmware or tied to my lack of #Vector T(11, 4, 12) words in the file... or its reading the Gcode and catches I have no cartridge in the extruder it's printing from... or what.
So, yeah, now I see... 3D Systems is not in the buisiness of 3D printers... they're in the business of selling filament at 400%-700% markup.
I didn't get much time to play with it today... that's all I got.
It is very frustrating but quite fun at the same time.Of course!joydisee wrote:Please let us know what's his proposition !
Thanks !
), you can give your email address and I`ll send them to you.