Cube3 File Editor

I have been working with @TommyDee to refine a tool for working with Cube3 and a little with CubePro files. I am relatively new to 3D Printing, but I am not afraid of trying things.

I have an EKOCYCLE printer that I have updated the firmware to be a Cube3, and have also modified the firmware to no longer decrement the cartridge filament count. I have also built Tomuro's cartridge programming device and have reprogrammed both EKOCYCLE cartridges to be PLA.

I have been printing things pretty well, but wanted a bit more control and started looking at how to get files fine tuned. So, after reading many posts on this form and others, and using the command line utilities to decode from CUBE3 to BFB, edit the file, and then encode from BFB to CUBE3, I decided there must be an easier way. Thus began my app that I call Cube3Editor.

You can download a zip file, which contains the binaries (if you have the necessary .NET frameworks installed), or an MSI installer that will install any missing frameworks.

Update March 18, 2021
*************************************************
Since Google is complaining about the primary executable containing a virus, I have moved the files to a download server.
https://gofile.io/d/Ghjr0U

Updated November 5, 2019
*************************************************
New versions posted to the google site.

Binary Zip: https://drive.google.com/file/d/1gdM...ew?usp=sharing


*************************************************

This is a work in progress, but please report any issues here, or PM me directly.

With some ideas from TD, I have also begun to implement the ability to script the utility so that it could be used to modify CUBE3 files from the command line. Here is the current script documentation, which is subject to change and is not implemented in the version currently available for download:


SET [FIRMWARE|MINFIRMWARE|MODEL|E1|E2|E3] "value"

FIRMWARE: sets ^Firmware: to "value"
example: set FIRMWARE "V1.14B"

MINFIRMWARE: sets ^Minfirmware: to "value"
example: set FIRMWARE "V1.14B"

MODEL: sets ^PrinterModel: to "value"
example: set MODEL "CUBE3"

E1: sets ^MaterialCodeE1: to "value"
example: set E1 "82"

E2: sets ^MaterialCodeE2: to "value"
example: set E2 "82"

E3: sets ^MaterialCodeE3: to "value"
example: set E3 "82"

MODIFY TEMPERATURE [LEFT | RIGHT | MID] <XXXX> BY [PERCENTAGE [+/-]<YYYY> | ADD [+/-]<YYYY> | REPLACE <YYYY>]

This modifies all existing occurances of XXXX by one of the following methods:

PERCENTAGE [+/-]<YYYY>: adjusts XXXX by percentage. Increase can be specified by specifying a positive value for YYYY. Decrease can be specified by specifying a negative value for YYYY.

ADD [+/-]<YYYY>: adjust XXXX by YYYY. Increase XXXX by specifying a positive value for YYYY. Decrease YYYY by specifying a negative value.

REPLACE <YYYY>: Replace each occurance of XXXX with YYYY.

• Maximum temperature is 265. If any adjustment results in a larger value, it will be set back to 265.

• Minimum temperature is 0. If any adjust results in a negative value, it will be set back to 0.

If LEFT is specified, then only the left extruder is modified. If RIGHT is specified, then only the right extruder is modified. if MID is specified, then only the mid extruder is modified. If none of these are specified, then the temperature adjustment affects all entries that match the given <XXXX> temperature.

MODIFY RETRACTSTART <XXXX> BY [PERCENTAGE [+/-]<YYYY> | ADD [+/-]<YYYY> | REPLACE <YYYY>]

This sets the P/S values of M227 command by percentage, addition or replacing the exising value with a new value.

PERCENTAGE [+/-]<YYYY>: adjusts XXXX by percentage. Increase can be specified
by specifying a positive value for YYYY. Decrease can be specified by
specifying a negative value for YYYY.

ADD [+/-]<YYYY>: adjust XXXX by YYYY. Increase XXXX by specifying a
positive value for YYYY. Decrease YYYY by specifying a negative value.

REPLACE <YYYY>: Replace each occurance of XXXX with YYYY.

If <YYYY> is calculated to be less than 0, then the value stored will be 0.

MODIFY RETRACTSTOP <XXXX> BY [PERCENTAGE [+/-]<YYYY> | ADD [+/-]<YYYY> | REPLACE<YYYY> ]

This sets the S values of M228 command by percentage, addition or replacing the existing value with a new value.

PERCENTAGE [+/-]<YYYY>: adjusts XXXX by percentage. Increase can be specified by specifying a positive value for YYYY. Decrease can be specified by specifying a negative value for YYYY.

ADD [+/-]<YYYY>: adjust XXXX by YYYY. Increase XXXX by specifying a positive value for YYYY. Decrease YYYY by specifying a negative value.

REPLACE <YYYY>: Replace each occurance of XXXX with YYYY.

If <YYYY> is calculated to be less than 0, then the value stored will be 0.

=====EXAMPLE=====
An example script may look like:

Code:

---

set FIRMWARE V1.14B
set MINFIRMWARE V1.14B
set MODEL CUBE3
set E1 82
set E2 -1
set E3 -1
set TEMPERATURE LEFT 210 BY REPLACE 195
set TEMPERATURE LEFT 265 BY REPLACE 215
set TEMPERATURE LEFT 250 BY REPLACE 210
set TEMPERATURE LEFT 240 BY ADD -35
set RETRACTSTART 450 BY PERCENTAGE -50
set RETRACTSTOP 450 BY PERCENTAGE -50

---

and the command line may look like:

Code:

---

cube3editor example.cube3 example.scr

---

this would result in an updated example cube3 that has the updates specified in the script. If for any reason one of the lines in the script is badly formed, no changes will occur to the cube3 file.

- - - - - - - - - -

New versions of binaries uploaded and ZIP of the binaries is attached here.

- - - - - - - - - -

Just for fun, @TommyDee asked me to create a utility to generate a basic file from a given CUBE3 file.

https://drive.google.com/file/d/1gdM...ew?usp=sharing

This is a console mode app that will take a cube3 file and generate a script that could be modified to change the parameters using the other, Cube3Editor. The script file will contain the following details:

FIRMWARE
MINFIRMWARE
MODEL (printer model)
E1 (MaterialCodeE1)
E2 (MaterialCodeE2)
E3 (MaterialCodeE3)

then a it will list
unique temperature lines with the current temperature and a "replace" value (Which is just the temperature repeated).
retract start lines (M227) with the current retraction rate (P/S must match) and a "replace" value (Which is just the retract rate repeated).
retract stop lines (M228) with the current retraction rate (S only) and a "replace" value (which is just the retract rate repeated).

Let me know what you think.

- - - - - - - - - -
06/17/2019

Cube3Editor -- the BFB can now be edited and saved to a BFB file from the UI. Currently, this DOES NOT affect the loaded file, I added it mostly as a convenience to assist in debugging. It could grow into a more useful feature.

One of the upcoming changes I am thinking about is allowing the script to be generated, edited and saved from the UI.


Added command line utilities:

c3sg.exe -- this will read a cube3 file and generate a script that can be used to modify cube3 files. The script can be cased to the cub3editor executable along with the a cube3 file to apply the changes to the cube3 file without using the GUI.

cube3decoder -- this will convert a cube3 file to a BFB (bit from byte) file. This will either put the output a file with the same name as the cube3 file with an extension of BFB or to a filename supplied on the command line. This will work with CUBE3 files that have been previously encoded with cube3encoder or with files generated by cube_print.

cube3encoder -- this will convert a BFB file to a cube3 file. The cube3 filename will be the same as the BFB file, but with the extension CUBE3. Or the output can be overridden by specifying the cube3 file on the command line.

Finally got the chance to start the beta test.
This is what I have in the execute folder exactly what was in the zip file:

Attachment 3288

First observance was the reduced size of the encoder and decoder.
Drag and drop a .cube3 file on the decoder and it created a .BFB file where the file came from (desktop).
The Cube3Decoder.exe also stripped the image from the .cube3 file. Nice!

A note on this operation; I normally have EOF at the end of the M107 (no CR) when I edit files with notepad.
A strange thing first time I opened the .BFB in notepad; it had 2 spaces (hidden characters(?)) after the last M204 S0 but cannot reproduce that phenomenon.

Windows10 complains about non-signature files but that is just once.


Next I drag and drop the .cube3 file onto c3sg.exe. And out pops a .SCR file from whence the .cube3 file came (desktop).
Parcing of all the unique values for retract and temperature neatly bound in an ascii format and includes the basic header settings.
Love this feature. .SCR may not be the best extention as I cannot figure out how to make it open with notepad by default, or even have the choice with the RMB.

I've lost the interface. Running c3sg.exe standalone has no user interface. Is that some of the previous files?
Also, running the encoder appears to overwrite the original .cube3 file.

Thank you for the testing.

Yeah, I didn't sign the files with a certificate. I suppose I could get a free one and do that for the next release.

Yes, I wanted the utility to strip the leading text as well as the image at the end, based upon what I've read on the forums. I can modify the code to strip the last CRLF.

Interesting about the M204 call with hidden characters. If you do reproduce that, let me know if you are able to come up with steps, or a model that can reproduce that.

You are correct, running c3sg does not have a UI, if you provide it a CUBE3 file and a SCR file, then it will use the SCR file to modify the CUBE3 file.

I will double check the cube3encoder, I thought I had it creating backup files. They will be named like file.cube3.XXXXXXXX with 8 digits. It supports up to 5 backup files, and then starts overwriting the oldest one. I will double check that. If you want the ui, run Cube3Editor from the other binary zip. You can put it in the same folder as the utilities...

Understood, thanks. I like this command line editor thing. Still need to write the batch file.

Found this cool thing... the previous decoder chopped off the header... your's doesn't! THANKS

Attachment 3289

There's a reason I am interested in this.

BTW, how hard is it to put an M108 list in the .SCR?
Turns out extrusion pressure is set with M108 for both nozzles.
It would be useful to access these in this type of script.
A duplication of M104 calls within your code I would presume.

I'm assuming this simple extruder pressure tweak to CubePro print files will make CubePro sliced print files compatible on Cube3.
The CubePro slicer does have many more options.

I need to see what your decoder does with v2.02 print and config files for CubePro. After testing V1.87 which is loaded.

- - - - - - - - - -

I'm getting some kind of remnant in the translation of the .xml files.

Attachment 3290

You're going to find that the encoder does strip off the header though. :| If you'd rather that I didn't strip the header upon encoding to CUBE3, I can make that change.

As for adding M108 to the script processing, I don't see why not, it's just another code I have to filter and replace. I already do it for others. Let me look at that over the weekend and I will post an update when I have something.

Can you send me the encoding you are seeing this issue on? it may be something specific to cubepro files? I noticed that I did have a slight bug removing the image, and it left a few bytes of code. It doesn't seem to bother the Cube3 though.

Correct. I've been beating up the 'coders and they are robust on the print files. Was able to endlessly loop the decode/encode process. Also saw the resulting file in CubePro 1.87, even with .Cube3 files. CubePro 1.87 print files worked fine for generating .SCR files.

There are a couple of config and build files I am very interested in getting access to. They use the same encoder/decoder. They exist in the ...(x86)/3dsystems folder structure. If you throw one of the XML's on the decoder you'll see what I mean. When I re-encode it is identical in notepad++ except this footer imaged above. Their XML version (binary) is fairly consistent. The garbled header made a mess when encoded again before.

Thanks for looking into the M108's.

Need to eval 2.02 pro files next... Cube3 you got locked!

Attachment 3291Attachment 3291Okay, Here is what I did tonight:

1. Added -xml to cube3decoder to treat the file as an encoded XML rather than CUBE3. :)
2. Added backup capabilities to cube3encoder so that you don't overwrite the original CUBE3 file.
3. Added support for modifying M108 values, I think -- it is really untested. I added a new tab in the UI which displays the M108 values and the first line in the file at which it appeared. I am thinking of adding a count so that you know how many are included. You can just type in the field for the new pressure value and it will be saved to the BFB.
4. Added support in the script file for M108 as well. The command is EXTPRESSURE and it looks similar to the RETRACTSTART/STOP. Here is a sample:

Code:

---

MODIFY EXTPRESSURE 29 BY REPLACE 29
MODIFY EXTPRESSURE 22.5 BY REPLACE 22.5
MODIFY EXTPRESSURE 40 BY REPLACE 40
MODIFY EXTPRESSURE 39 BY REPLACE 39
MODIFY EXTPRESSURE 32 BY REPLACE 32
MODIFY EXTPRESSURE 37 BY REPLACE 37

---

New version can be found here

Or attached Attachment 3291

Sweet!

Just to explain my thinking on "feed and speed" which is the hallmark of any CNC machining operation, Cubify/BFB uses a determined pressure associated with a given velocity of the extruder head. 3D Systems has given much attention to this in the CubePro implementations where the Cube3 has had fairly consistent extruder pressures. Rather than mess with the speed issues (the F-value on G1 commands) I was thinking we could do this with extrusion force adjustments. This should open up the CubePro slicer to Cube3 with minimal effort. This is where CubePro tries to be very precise with where they place how much filament. Bottom line, we should be able to make truly solid parts on Cube3.

I'll get back to testing this evening... thanks for adding this!

About the extension SCR. I was thinking of changing it to CUBESCR This would be more specific and maybe allow you more easily add a Windows mapping. What say you?

Yes, that solves it. I can assign notepad to .cubescr in Win10.

Here you go. Attached: Attachment 3292

I'm getting errors trying to run these latest versions. Norton is lighting up on every file it seems.
Attachment 3293

Attachment 3294
It turns out that I built an administrator version... Okay, I was tired last night. Try this one.

Same errors. Something is really messing with Norton. I got the last one working except the decode was permanently removed although yesterday's is fine with Norton. I had to restore all the files in the latest version.

Okay, I am not sure what is up, but instead of uploading as an attachment, here is a link to the file uploaded on my google drive. I have scanned these with several scanners and I am not seeing any issues. F-Secure, Trendnet, MSDefender...

https://drive.google.com/open?id=1gd...mhQ_f28-DhOI6e

I have deleted all attachments. I am wondering of something was happening there.... I scanned with a few more online services, but no problems...

Norton has gotten a wild hair up it's bumm. It is not flagging anything with the same name elsewhere on this PC but that may be the reason it is upset. I can't get anywhere at the moment. Norton keeps deleting the .exe files.

Can you provide the norton logs?

I can get to this... they all have this warning.

Attachment 3295

Windows 10 also warns me... and that might be what is keeping bouncy castle from being found.

...but, I can still run a version from yesterday without any complaints.

- - - - - - - - - -

Okay, I got all 10 files accepted by Norton by marking them "user trusted". But I still get the bouncy Castle not found error. No UI in the editor. No output on the others.

- - - - - - - - - -

Oh, recent versions lacked the two *.config files. Didn't help using the older ones but just noted that in the file list.

- - - - - - - - - -

Here are the windows log screenshots for when I get the bouncy castle window.
Attachment 3296
Attachment 3297
Attachment 3298
Attachment 3299

I find it interesting that the version from 3 days ago works. I have posted another version. I assume that I am not seeing this because I am the developer. I will have to download a test VM and get things tried out.

https://drive.google.com/open?id=1gd...mhQ_f28-DhOI6e

Okay, whatever you did fixed it! ...now Win10 challenges my sanity and I say run anyway, and another popup needs confirmation and all is good. Editor opens as it should. Phew! Thanks for sticking with it!

Let's call that Beta #1. I'll use that for testing.

Same command line as before? editor>printfile>resource

- - - - - - - - - -

All the executable's are functioning. Haven't done any actual conversion yet but we are back were we were with improvements. Decode and encode works. Opened .cube3 files with CubePro 1.87. ...and the Script Generator is Killer!

:) Glad to hear that this is working. Yeah, Beta1 is probably step. The command lines did not change.

The change I made was to sign the EXE an DLL files, as well to include the config files for the EXEs. Now to get Windows 10 to allow them past the smart screen.

I find nothing smart about Windows 10! Paranoid and intrusive I'll buy.

Heh-heh. I agree! Try this one, I created a new version that doesn't flag the Windows 10 Smartscreen on a Windows 10 VM that I tested with

https://drive.google.com/open?id=1gd...mhQ_f28-DhOI6e

Give this a try. I did some special digital signing of the binaries.

- - - - - - - - - -

Okay, so I have been looking at the CUBEPRO v2.02 File format of the header. The following are Hexadecimal file offsets:

000000000-00000004: 4 bytes Little Endian count of files in the model
000000005-00000008: 4 bytes Little Endian count of bytes in the model.
000000008-00000009: 2 bytes Little Endian size of each File Header (file size and file name length combined)

Then each file seems to have the following setup:

000000000-00000003: 4 Bytes Little Endian size of file
000000004-00000107: 260 Bytes Filename

It looks like the Cube3 files have the same layout, and I am going to write some code take advantage of this format.... Maybe come up with a way to split the various pieces of a cube3/cubePro file (An extractor) of sorts.

There seems to be 3 different sections to the CubePro 2.02 files; an ASCII header, the BFB section, and then the image; if that helps.

:) Yeah, I stayed up too late last night, and I didn't finish this post.

Added new utility CubeExtractor. You should be able to extract this into the same folder as your other apps, but for now, don't. This is a work in progress and I have modified the FileHelper.DLL and so it could break everything else...

https://drive.google.com/open?id=1oU...cDgFEzI7OzJeV8

I ran this on a CubePro v2.02 file and received the following files:

Code:

---

06/23/2019  09:41 AM            2,716 index.xml
06/23/2019  09:41 AM        3,212,288 m3d_pla.cubepro
06/23/2019  09:41 AM            2,201 isoimage.png
06/23/2019  09:41 AM            15,838 frontimage_g.mrl
06/23/2019  09:41 AM            15,838 frontimage.mrl
06/23/2019  09:41 AM            1,013 frontimage.png
06/23/2019  09:41 AM                4 archivecheck.bin

---

There is more than one file within the image area as well has the XML at the beginning which describes the model. In the Cube3 files, it looks like a folder structure is created and they don't contain the "archivecheck.bin" file. I haven't processed that file yet, but I am wondering if it is some sort of checksum.

By removing the XML from the beginning of the file and removing all of the file headers, I wonder if that is the reason we're not able to send these across wifi. I am going to create a "cubepackage" app that will take a list of files and package them back into a cube3 file and see if that is able to be sent to the cube via wifi....

That makes sense. There is an image and an overlay. The MRL is the "scanner". Images in CubePro are pretty small by comparison.

The lack of image is the reason the app won't open them. But I suspect I can send the CubePro print files via WiFi considering the app will open them if they have a compatible material specified.

- - - - - - - - - -

...which means, of course, that if we paste an image and the scanner of any kind, it should open in the app. I suspect the older decoders don't faithfully convert the image segment of the file.

The only thing that concerns me is the archivecheck.bin file in the CubePro v2.02 files. It is not present in the v1.87 nor in the Cube3 files. If we can figure out what the Checksum/CRC method that was used, then I could rebuild any CubePro or Cube3 file once the modifications are complete on the ... oh wait, Can the CubePro v2.02 read CubePro v1.87 files? If that is the case then by removing not including the archivecheck.bin file, we may be able to get away with having CubePro v2.02 think they are older versions and fix them up.....

- - - - - - - - - -

I may need to compare a v1.87 index.xml to a v2.02 index.xml -- I am betting there is something in there, or even possibly in the CubePro file itself...

It is not a critical thing as old files work perfectly with 2.02 firmware on CubePro.
The only issue I've run into with the CubePro printing mod'd files is the lack of a "signoff". It appears to just hang but it is completed.

I ran a batch file to see if I could make it work.
Tell me what's missing please: This is the beta I loaded last night running everything from the Cube3Utils folder...

C:\<path>\Desktop\Cube3Utils>Cube3Editor.exe ORG_testcube_la12101.cube3 ORG_testcube_la12101.CUBESCR
cubeFile = 'ORG_testcube_la12101.cube3'
scriptFile = 'ORG_testcube_la12101.CUBESCR'


Unhandled Exception: System.InvalidCastException: Specified cast is not valid.
at Cube3Editor.MainEditor.CommandLineLoad(String newFWStr, String newMinFWStr, String newPrinterModel, String newMCE1, String newMCE2, String newMCE3, List`1 tempMods, List`1 retractStartMods, List`1 retractStopMods, List`1 pressureMods)
at Cube3Editor.Program.Main(String[] args)


C:\<path>\Desktop\Cube3Utils>pause
Press any key to continue . . .

- - - - - - - - - -

Latest installed... same batch file error.

Can you send me a zip file of the two files you are using -- it seems I missed, ah, something.

These are the two Cube3 files I am using for testing.

The c3sg.exe is the latest as is the Cube3Editor.exe

Attachment 3301

Hey, this is fun. With your files, I discovered an issue with the BFB generation. :) I forgot to put a space between M108 and S<val>, so it came out as M108S40, for example, then the subsequent decoding would fail. :) That's what I get for writing code while sleepy.

Anyway, added a routine to fix any pressure lines that I discover with that issue and fix them.

Here is the latest signed version of all the utilities, including the extractor. https://drive.google.com/open?id=1gd...mhQ_f28-DhOI6e

- - - - - - - - - -

And I also fixed the exception you were seeing as well.

Something went wrong. We went back to Norton deleting files.

Well that is just frustrating. I wish I had a trial norton license so that I could do some testing before I sent it to you.

New version posted, https://drive.google.com/open?id=1gd...mhQ_f28-DhOI6e

This has the signed binaries too.... (Just discovered that I have a norton subscription through my internet provider ...) Lets see if I can see this on my Win10VM

- - - - - - - - - -

I have now seen this on my norton installation on my VM after downloading. This seems like an issue with the "new"ness of the files. Hmm, maybe I need build all of this into an installer...

Attachment 3303

Is this what you were seeing?

- - - - - - - - - -

What I found is that if I download the MSI installer, and run it, I get the Norton File Insight display that allows me to "trust" the publisher. I am then able to run each executable without that display popping up or the Windows 10 display that pops up to stop you from running this...

What I don't want to do is to go spend $400 or more per year to have a signed certificate. This whole scenario is starting to feel like a way to get people to pay money to run apps....

Yep, you're starting to understand M$ :p

No, that error is benign. It is the one where the files are permanently quarantined and restricted for use.

Okay, Win7 opened Cube3Editor with only the Download Insight you posted. I can bypass that and it only does it once (per version).

- - - - - - - - - -

testing the rest ;p

- - - - - - - - - -

Mine is Comcast provided Norton.

This is what I get on Win10

Attachment 3304

- - - - - - - - - -

No joy on Win10. Will try Win7 some more.

I am finding that dll, well, maybe I should just trim it down to what I need rather than the entire DLL......

Oh not just that one. It took out a host of files and now I get the bouncy castle error again.
I can run v.7 without issue.

Well, ugh. Just ugh. I am not sure how to proceed. I can get them to run on my Windows 10VM which also has Norton as supplied by Comcast. I just have to allow Windows and then Norton to allow it to run.

https://drive.google.com/open?id=1gd...mhQ_f28-DhOI6e

Latest version with everything self-signed. You are still going to get those popups because it is not officially signed with a certificate from a Certificate Authority.

I wonder if there is a way for you to export your Norton Settings so that I can import them for testing. Or maybe you install Visual Studio 2019 Community edition, download my project from github as well as the BouncyCastle and SourceGrid projects and build it yourself. :) I never really thought about distributing my own software ...

- - - - - - - - - -

I am in the process of getting a code signing certificate just so that we can get past this, and so that if anyone else wants to use this software with their cubes. I don't know how long this process takes, but hopefully not long. (I found a reasonably priced solution, but this still feels like a scam for the individual developer who just wants to create tools for himself and his friends...)

I run Norton plain Jane. Not a lot of options.
I suspect it has to do with pre-loading software where there are two different versions of the same file and that sets off Norton.

The normal warnings don't bother me as they only annoy once. This one is debilitating.
I don't know what you did different in one round when it was solved because I changed nothing else.

I can move forward on Windows 7 until we figure this out.

- - - - - - - - - -

This is looking better...

I renamed all the old files with a prefix "_"... and copied the latest (11) to my desktop.
Ran the editor and it worked after the normal hooplah.

Ran the c3sg.exe an same warnings and all worked as it was suppose to.
Norton did not go off on its own and start deleting things. So this one is also stable.

Just to capture the process to bypass signatures on W10 w/ Norton is as follows:

Start the Cube3Editor.exe
Receive this message -

Attachment 3305

upper left; More Info... and you get this -

Attachment 3306

Select Run Anyway and Norton takes over with this -

Attachment 3307

With a final selection to run anyway, this is is now valid to run on the PC without further disturbances.

So yes, this is normal and acceptable.

What is not normal is Norton deleting files at will. Something to do with prefetch or simply having multiple versions of the same file on the PC.

- - - - - - - - - -

Now we are making headway!

Got the batch file to work after some boneheaded errors.

Still not quite sure how to interface with the editor. It is not returning data as expected.

Maybe give me a tutorial on how to change a set scenario...

Create an Ekocycle print file...
Convert the temps down to 250C...
And replace the retraction settings to "minus 75"
Save to .cube3

I noticed we could not open the cubescr file when the editor is open.
Also could not generate a cubescr file from within the editor, or at least, couldn't find the file if it generated one.

Setup is all cubeutil files in one folder and dragging files from the desktop.
I do not subscribe to filenames with spaces so that is not a test I will be performing.

Great tests!

So for the editor -- the command line for the editor to apply the script file is cube3editor <cube file> <cubescr file>

When you say "replace the retraction settings to minus 75" you go into the retraction tab and change say 400 to 325, right?

While I don't normally subscribe to spaces in filenames, I have to plan for them. :)

- - - - - - - - - -

Oh, and I think I mapped the script generator from the Cube3Edit UI to Ctrl-G (or check the file menu). I will check in a couple of hours.

Yep, That is a typical routine I run on Ekocycle files to run non-3DS ABS or PETG on Cube3. This is also the best solution I know for 3rd party ABS.

I noted that %1 works for the source .cube3 file dropped onto the batch file. That makes for excellent recipe management. If you know you have a simple standard routine, it can capture only the required changes in a static .cubescr file... I'm assuming. I'll give that try for my next test.

From a technical standpoint, I assume I can have additional "swap" statements in the .cubescr file and it will simply ignore them if they do not exist. That way you can capture single L or R or Both extruder prints with the same .cubescr file.
The command set that this is useful for is a generic retraction reduction routine that is useful with 4mm bowden tube setups which have less springiness than the stock tubes. This is one reason for the "blobs" and can manage them better than the stock slicer ever did.

Okay, more testing...

- - - - - - - - - -

fat-finger'd tommydee did that! Sorry.



I'm getting exception errors using the batch routine. One error was a blank line at EOF in the .cubescr. Fixed that and another pops up. It only seems to work if you change nothing :o

Using the editor is working. I noticed the source .cube3 file is replaced and a backup is created. Had read only on my source print file and it didn't like that, obviously :p

Findings... If a material is specified for 'sidewalk:' (and probably for supports) it also should be changed (assuming it will confuse the printer).

Percentage is still not working. 98% of 255 returns 255 in the editor.

- - - - - - - - - -

Batch editor is working. The error was down to retraction settings in the .cubescr file...

C:\user-pc\yadayada.\Cube3Utils11\Cube3Editor.exe testcube_EKO12201.cube3 testcube_EKO12201.CUBESCR
cubeFile = 'testcube_EKO12201.cube3'
scriptFile = 'testcube_EKO12201.CUBESCR'


Unhandled Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(T Key key)
at BitForByteSupport.BitFromByte.updateRetractionStar tLines(Int32 index, String retractCmd)
at Cube3Editor.MainEditor.UpdateStartRetractions(Grid gridStartRetracts)
at Cube3Editor.RetractionStartChangedEvent.OnValueCha nged(CellContext sender, EventArgs e)
at SourceGrid.Cells.Controllers.ControllerContainer.O nValueChanged(CellContext sender, EventArgs e)
at SourceGrid.Cells.Controllers.CellEventDispatcher.O nValueChanged(CellContext sender, EventArgs e)
at SourceGrid.Cells.Controllers.ControllerContainer.O nValueChanged(CellContext sender, EventArgs e)
at SourceGrid.Cells.Models.ValueModel.SetValue(CellCo ntext cellContext, Object newValue)
at SourceGrid.Cells.Cell.set_Value(Object value)
at Cube3Editor.MainEditor.CommandLineLoad(String newFWStr, String newMinFWStr, String newPrinterModel, String newMCE1, String newMCE2, String newMCE3, List`1 tempMods, List`1 retractStartMods, List`1 retractStopMods, List`1 pressureMods)
at Cube3Editor.Program.Main(String[] args)


...

So changing the machine type worked fine; changing material worked fine; hanging temperatures worked fine;...restractions popped this error up.
I've got this test down on a routine so let me get back to the good output and complete the test.
...edit; and yes, the extruder pressure works in batch file mode (command line mode).
One more test... M227 or M228? :)
...that's odd! I got them all to work! I was zeroing in on one of four entries and one failed but worked a second time around.

- - - - - - - - - -

attaching test files...