print gcode files to miniMaker (Page 2 of 16)

Ok, there is a new version of the minimover app.  Overall this is mostly a fix to the UI but there are a few small improvements to the command line.  In particular I now parse the z: zOffset command from the status and I properly read all the return characters when printing a file. 

On the UI side I dumped the tree widget in favor of a list for the status info and I cleaned it up so it no longer flickers.  Now that it behaves well I can poll 2x a second automatically so you don't have to update the status by hand.

I also added in some locks so it is impossible to attempt to make two requests to the serial port at the same time.

Finally I added in some code to monitor print progress and pause/cancel a print.  I still want to clean this up more, it is not as clean as it could be, but it should be fully functional.

Everything works fairly well and it should now be a lot more resilient.  Previously it had a hard time recovering from even the smallest communications errors.

I put up a new version that has a much improved handling of the printer status message.  This has now been tested against a da Vinci Pro 1.0 and it does work (with some small issues).  This also fixes a new bug I introduced that can cause the ZOffset to be set wrong on some models of printer.

I managed to get my hands on some 3w files from the original da Vinci 1 and 2 machines, these files use some sort of zip compression on the gcode before encrypting them.  I can pull out the zip file but it is not a standard zip, and can't be decompiled by regular zip libraries.  I'm probably going to end up rewriting a zip reader/writer from scratch to make this work.

Anyway, once I can read/write these files then you can use my tool to convert from gcode to 3w and back for any xyz printer.  I still won't have support for the older communications protocol so you have to use XYZWare to send the print but at least you can modify the file at will.

If anyone else has a clue about the zip file format then let me know.

Thanks Yizhou, that is a help.

I spent a lot of time looking over this and feeling very confused but last night on the way to bed the answer popped into my head.  When decrypting a zip file they change how the data is read out and actually read it in fixed size blocks compared to the non zip file format.  I think that the zip file is zero padded when encrypting, even though the code is not explicitly attempting to zero pad the file, it is just a side effect.  That results in me decoding too small of a block on the end of the file and that in turn is causing some corruption to the file without completely destroying it.

If that is not the case then they are resetting the decrypter every n blocks, but I don't see any code that explicitly resets the decryptor.  They do call a decryptFinal() call on each set of blocks and I have not been able to work out what the final part means, does it reset the key back to the initial value at the end of each block of decryption?

Either way I have a plan, and a reasonable explanation why my zip file appears good but is slightly corrupted.

XYZWare.exe is written in .NET and it can be decompiled. I'm not familiar with these area but it might help you find out how XYZWare doing it. I think someone else in this forum decompiled it and generated something like XYZWare advance version. (modfreakz I think)

http://www.soliforum.com/topic/16978/xy … de-v21261/

Good luck.

Hi, David,

I did not try to do this. But I want to share some of my past experience in this kind of troubleshooting.
1. The order of decryption and compression may make difference. Also the checksum or CRC may contribute to the difference.
2. I don't know if it worth the time and effort, but try generate .3w file from your apps and corresponding XYZware and compare the result and sometime can help you find out if you are on the right direction.

3. I think old .3w file are just just a base64 encoded gcode file. Only new version .3w file are AES-encrypting ZIP-ed gcode.

4. I'm not sure if I misunderstood your previous post (#31). If I understand it correctly, this may be something you need.

I guess this is what you are after:
"uploadGCodeText"        = "XYZ_@3D:4";
"latestBlockSent"        = "XYZ_@3D:90”;

Just need to find out how big each block is.

"prefix"              = "XYZ_@3D:";

//"disconnect"           = "XYZ_@3D_S10_X";
//"connect"              = "XYZ_@3D_S10_0";
//"start print"          = "XYZ_@3D_S10_1";
//"test case"            = "XYZ_@3D_S10_2";
//"uploadFirmwareBinary" = "XYZ_@3D_S10_3";
//"uploadGCodeText"      = "XYZ_@3D_S10_4";

//"extruder Temperature" = "XYZ_@3D_S10_101";
//"get standard info"    = "XYZ_@3D_S10_102";
//"get advanced info"    = "XYZ_@3D_S10_103";

"disconnect"             = "XYZ_@3D:-1";
"connect"                = "XYZ_@3D:0";
"startOnlinePrint"       = "XYZ_@3D:1";
"test print"             = "XYZ_@3D:2";
"injectManualCommand"    = "XYZ_@3D:2";
"uploadFirmwareBinary"   = "XYZ_@3D:3";
"uploadGCodeText"        = "XYZ_@3D:4";
"latestBlockSent"        = "XYZ_@3D:90";
"uploadBinaryDidFinish"  = "XYZ_@3D:91";
"uploadGCodeDidFinish"   = "XYZ_@3D:92";
"machineLife"            = "XYZ_@3D:5";
"read eeprom A"          = "XYZ_@3D:6";
"read eeprom B"          = "XYZ_@3D:7";
"machine status"         = "XYZ_@3D:8";
"printer status"         = "XYZ_@3D:8"; // same as machine status

"get standard info"      = "XYZ_@3D:201";
"get advanced info"      = "XYZ_@3D:202";

//example "XYZ_@3D:101,1"
//example "XYZ_@3D:101,2"
//example "XYZ_@3D:103,2"
"extruder on"           = "XYZ_@3D:101";
"extruder off"          = "XYZ_@3D:102";
"extruder Temperature"  = "XYZ_@3D:103";

http://www.soliforum.com/topic/6279/xyz … 0-hacking/

Looks like the trick is to pkcs7 unpad each encrypted block rather than just unpadding the full buffer after decrypting.

Congratulations！

Hey David, keep up the good work! Also, please continue to document and publish your findings, it helped me already here and there :-)

I am not a code monkey and not a davinci owner so can not really appreciate this project. But thank you for your hard work and commitment to this.

On a side note, if anyone has an old busted xyz printer they would like to donate to the cause I would be happy to pay shipping.  It does not need to work but should have enough of its internals left so you could send a print job to it using XYZWare. I would love to get my hand on one of each, but anything would be a big step forward at this point in time.

Hello i am a french teacher

i have a problem

when i launch minimover and i try to print a file a have a message PROCESS FAILED. If i see minimover, for extruder temp, i have 20°C/198654465423°C

Is anyone have an idea ?

Thanks a lot