-
:) I looked again last night, spent way too much time looking, and refreshed my memory. The rest of this file are an encoded set of M and G commands. They take it byte by byte after doing the decode with our normal key. I have an idea that using the existing algorithm, I may be able to decode the rest of this file. I will work on it and get something out as soon as I can.
- - - - - - - - - -
Hey Yamaruchi, sorry you are having trouble with the editor. Can you use the Snipping Tool or Snip-n-Sketch (both are in Windows 10), to take screen shots of the editor at each step to show us what exactly you are doing?
-
Buddy has made these programs to allow for a canned function. Drag and drop basically.
Please work with Buddy to find out what failed in your attempt. This is kind of important to know why some user have trouble and others not.
-
so I am going to film the process and send it to you! Can you give me your email or can I upload to the forum?
-
You can link youtube here.
-
-
Marked as private. I will send you a DM with my email so you can share.
-
sorry I reopened the video to youtube because the video file is too large to send it via email
-
Awesome. Thank you for the video. First thing to try is to not change the printer to a Cube3, leave it at CubePro. Then do your temperature updates and then generate. Is the result the same?
- - - - - - - - - -
Well, to go back to the CubePro 2.02 files. The data after that G50 in the code, is all command based. Here is a zip file dump from the file you provided. These never get convered to BFB, and are sent to the printer as is. So, it must be the material in the header that is sent along that is used by the printer to determine the necessary information about the temperatures, retraction rates and extruder pressures, etc...
Here is the link to the zip: https://drive.google.com/file/d/1jZw...ew?usp=sharing
The good news, is that I think I figured out how to use the existing 3DSystems DLLs and I am hopeful that I can soon find a way to send a file to the printer wirelessly.
- - - - - - - - - -
I did a little further spelunking, and I cannot find anywhere in the v2.02 version that does any conversion to BFB, it just deals with the data as I present in the above link and sends that to the printer, which , I assume is able to parse it. I don't have a CubePro, so I am unable to guess more intelligently. I also assume, that if you have an older BFB (CubePro 1.87), it is passed down as BFB, since I cannot see anywhere that it does BFB conversion one way or another. So the updated firmware on the CubePro printers must support both the BFB and the newer Opcode format.
-
You are exactly right Buddy. They've removed the BFB from code. It is likely in the firmware. The header sets up the mode and extrusion pressures and temps are all managed based on the command line being read. One way to look at it is that it is processing BFB based on the native slicer command language. BFB is a CNC language conversion after all. BFB is their origin. Now it appears they removed it for more direct control. Smart move for where they were headed with this.
-
Who wants to beta test, okay, alpha test, okay, proof-of-concept test a console utility that will allow you to send a Cube3 file via wifi to Cube3 printer? :)
