I will be a TESTER.
I own a Rep-MAN 3.2, 3D Touch and a CubeX I also have the time to do what ever you need. I also have an extensiveness back ground in electronicsdigital systems and assembler and PIC processors.So count me in.Cheers
Daid
How do you explain, that when I am printing to extruder #2, my native CubeX print file only shows an M108 and NOT an M208 code?
You don't need special special firmware to eliminate the proprietary cartridge requirement. You just send a text based BFB GCode file to the printer with a simple "^Firmware" header line... We can use the CubeX just fine with generic (BFB) slicers with very little modification of the output. What are you hoping to gain by changing the controller and firmware?
I have success. I could now supply an after market Controller for the CubeX.
Using there software in a reengineered controller using the same PIC processor. The PIC32mx440 and running the standard BFB file KISSlicer was written for I could make a after Market controller with there software that would be a straight swap over.
You would plug in and work just as it did before same display use files BFB extensions with no need for aftermarket filaments and all other locks gone.
It will be cheap and under warranty it would also not fail by using different peripherals circuits. The key is another microcontroller piggy backing the other system processing other electrical signals and replacing them making it compatible.
I have added a separate Lcd display and key pad to this little chip
so the user can if they want to make alteration on the fly.
I will continue for now refining the software and testing the system.
On my prototype is all birds nest wired and Vero board.
I already have some very nice prints.
Can you give us a status update on Cura's BFB support?
Is the latest version in the GIT repository ready for testing?
Do you have a link to compiled versions somewhere?
Any questions / support needed?
I like the initial look / feel of Cura.
It is very intuitive for working with models.
I save all my STL models in inches, so after opening them I have to scale them by 25.4 to get them in mm.
After generating GCode and comparing with KISSlicer, it looks like I guessed my settings all wrong.
The speed / position / flow values are very large compared to what KISSlicer generates.
Do you control the flow with E-Steps per 1mm filament?
Do you control the starting offsets with Head size towards X min?
The first line of GCode MUST be the ^Firmware:V1.07, is there a place to set that? I tried start/end GCode, but it is not the very first thing.
The extension must be bfb for the Cubex printer to detect it (minor issue)
Cubex is very sensitive to the order of M227, M228, M55?
The Cubex file may require CR+LF for line termination, but I'm not 100% sure on that one.
KissSlicer + CubeItMod startup GCode:
^Firmware:V1.07
G21
G90
M107
M542
M104 S190
M227 S118 P296
M228 S44 P44
M551 P1500 S80
M543
M108 S10
M103
G1 X-17.24 Y-12 Z0.45 F12000
G1 X-17.24 Y-12 Z0.2 F210
M101
G1 X-17.33 Y-10.84 Z0.2 F873.6
G1 X-17.59 Y-9.71 Z0.2 F873.6
G1 X-18.01 Y-8.63 Z0.2 F873.6
G1 X-18.59 Y-7.63 Z0.2 F873.6
If you get the numbers to look right in the GCode, please post your settings for others to use.
Also, you might want to post where the options are in the windows version for the BFB flavor setting.
Thanks!
Peter
^Firmware:V1.07The rpm is off exactly a factor of 10. The output might read M108 S413 when it should be M108 S41.3 To work around this I divided the flow rate by 10. Cura gave a warning that this was too small but it worked.The Cubex likes to have the first layer at Z0.5mm. Set the initial layer thickness to 0.5. Cura gave a warning that this was too large but it worked.Still working on the start.gcode and end.gcode. Cura is adding some stray lines at the beginning and the end that the Cubex will not accept. The work around is to cut and paste a new beginning and end.Open the .gcode file in notepad or the text editor of your choice.At the beginning of the file find the line that says "Layer Count". Delete everything above that line. Now paste the following in its place.
Find the end of the file. Find the line that says "M304 S0". Delete everything after that line.Save and close the .gcode file.Rename to .bfbRun with care!
I could not find a separate setting for Z axis speed in Cura. I experimented with manually changing the speed in the gcode. Still working on it. May not be necessary.
Thanks Toranarod. Sounds like you have done some interesting work. Unfortunately I have zero EE skills. Only software and mechanical.
I will see if I can test multiple tools sometime this week.
Steven
Kisslicer uses 2963 for steps per 1mm of filament.
In the start/End-Gcode tab you can customize the beginning and end of the program. I created file called toranarod.ini for you to try. Click File -> Open Profile then navigate to where you saved toranarod.ini. I have not figured out how to enter a different prime and suck into Cura. For now I am putting the M227 command in the Start/End-Gcode tab and manually deleting the one that Cura generates. Your Kisslicer output indicated that you are using nozzle 3. Can you use nozzle 1 for this phase of the testing? Right now I think the biggest thing that we can do for Daid is help him get the rpm and basic gcode right. Then add multiple nozzles later. I also added a new preferences.ini that hopefully matches the 3D Touch. Copy this file to your cura installation directory\cura.
Try the above and see if that helps you get started.
What do you want me to do next? I'll try whatever settings and geometry that will give you the most insight. Let me know.
First test at 400% and .5mm shell/nozzle. She'll ended up at .61-.63. What % do you think I should try?
http://i1280.photobucket.com/albums/a493/uatmah/C959BC9E-E00A-45A2-8FB3-201129379D6C_zpsnl7f7qb7.jpg
http://i1280.photobucket.com/albums/a493/uatmah/6ED41A31-CA60-4FA2-9F41-3119A2313DC5_zpshwxlw0oc.jpg
http://i1280.photobucket.com/albums/a493/uatmah/213FDE9C-37BD-4F78-A1A4-58B46E53678D_zpsbniyr71k.jpg
Thanks
Matt