-
:) 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.
-
2 Attachment(s)
These are the two Cube3 files I am using for testing.
The c3sg.exe is the latest as is the Cube3Editor.exe
Attachment 3301