Or read the forum, try this that I write about, had the same problem and now is totally fixed https://www.forum.makertech3d.com/forum/general-discussion/fix-for-temperature-fluctuation-and-other-issues

I want to know this information too. All I know is that is the version 1.1.9 and STRING_DISTRIBUTION_DATE "2018-08-01" but this doesn't help a lot to determine the specific version or commit that the firmware from Makertech is. I want to compare the Makertech version to the official version so I know all the changes made to marlin, but without a specific version or commit Im lost Can you help with this @Makertech ? or at least start publishing sources and updates since we haven't heard from you nor from your to do list in a year.

So for when this? you have been saying that you got list of things to do and yet we don't get any news or updates from your part. @Makertech please create Simplify3d profiles as promised and also create PrusaSlicer profiles. PrusaSlicer 2.2.0 ,released a few weeks ago, allows the creation of profiles for other printers.If you need help say it but update the official software so we all get the updates, each time you help you just give a little information instead of correcting the error. This machine is beautiful and well made but the software and customer support is lacking strongly.

After some tinkering in the firmware I got it working with the best answer in this thread, here is it . Dual extruder is working wonderful and the stock servo was working well.

I'm building the dual extruder and all the steps seems to be correct until I tried to test the servo. So it seems you all got problems with the servo being dead(probably including me) or not correctly calibrated in configuration.h. There is a best answer here from @Molotov suggesting changing the limit values and there is also a very good explanation by @denishungnguyen (i think?) in Guide/DSE+Stage+07 step 4 and I will probably go for that. I will by trying to fix it in the coming days and I wanted to ask ppl how is it going with the DSE? Do you like it? doesn't work? Last time someone made a comment about it is from months ago. Also if there is an obvious fix please share it or make the changes in the firmware, till this day it hasn't been updated in the builds neither in the instructions.

Thanks for this =)

I believe the issue is solved. I had a lot of successful prints and the failed ones most got a reason. Please put a date in your updates release page! I want to use the printer with the octopi, seems that I could have more control. Is the communication between the board and octopi and touchscreen working well now? or should I disconnect the touchscreen to use octopi better?

@Ernie Bausch You can never get all the pi you need haha. With what you say I believe is the board or the sd-card reader in the printer. Thats my opinion, I hope someone can advice you better.

I would have said you to check the sd-card writer but if your other printer is working with the sd-cards then the issue is not there. @Ernie Bausch I also think your problem is related to data corruption. I have read what you write so let me ask. All your test have been run from the sd-card? Have you run the gcode file from octoprint? or directly from the computer (don't know if this is possible)? Also try with nothing connected to the printer. As you have worked with other printers maybe the error is as you mention it, the board =S, or the sd-card reader in the printer. Maybe there is way to debug the board. But it seems this types or freezes only happens to you. We have other freezes.

Z leveling can be tricky. I have heard of people having problem with it in other printers. I don't have the new bed level but using the original I see that sometimes it gets un-calibrated. Don't know the reason , could be many factors like heat, I also got some tiny bubbles in my bed, maybe a hit or a loosen bolt. When I got the bed calibrated it last for some weeks but sometimes need adjustment, adjusting and testing are time consuming. I would like to know how the auto bed leveling works, don't know if it really makes something. I haven't installed the dual extruder yet.

Great! no worries, glad to have you back.

Since I connected a raspberry I'm having new strange behaviors like printing starting before reaching the target temperature. Seems possible that having this 2 connected is causing more interference and errors. But I also had freezes not connected to the raspberry nor my computer. Please let it be a temporal advice and not the final solution.

So we don't have a word, then we should proceed and ask for forgiveness after! There should be no problem as they are only configurations of cura, the rights are of cura, as long as we keep the makertech and Proforge name but declaring that it is not yours. The only part that could a conflict will be the images but you said you will not include that, as they aren't necessary. I don't know if there is a separate configuration for the printer and for the materials used. @Molotov can your contact help us with this? getting this to be an official configuration? or giving us some light about the changes made to cura so we can apply this to newer version of Cura or even other softwares. Getting a PR will be the best for the future.

I'm with deró on this, I don't thing simplify3D developers should be looking for all printer to be compatibles with their software. I'm sure there open and responsive but in this times there are too many printers. Also, @deró would you share this profiles? hehehe. What where your configurations? I haven't really used the software but if there was support I will probably get it.

@deró I will definitely be happy with a Proforge3, but if it comes soon that will make me pretty mad! hahaha. I think a Proforge3 needs that technology advances a couple of years; if they wanted they should be focusing in creating a business with the already modern printer they made. Just thinking about it. But yeah where is @Makertech ? Are you a team or a person?

I got an idea of what is happening, at-least when almost all your prints fails. Its gonna sound stupid at first but bear with me and comment about it; Did you make a tower temperature test? using the extension -> post-processing menu. And did you erase this configuration after? For me this (almost) fixed the constant failures in the prints. I have made like 10 prints with only one failure(obviously the longest print, after 9h) after cleaning this configurations. Maybe leaving this configuration after changing the model and/or closing the program causes weird behaviors. Hope this help! I also added some damper to the motors, did some necessary adjustments to the z axes and installed a raspberry zero for debugging. I was getting the same error as @Robert Steele in octoprint, it was necessary to select an option in advance settings because octoprint gets disconnected and a pop-up window won't let you copy the error in the terminal, and remember to click auto-scroll to get the latest messages in case you wanna debug the errors. The errors in the octoprint terminal gave me a hint of what was happening because of this line: Recv: ok Recv: T:235.44 /245.00 B:75.13 /75.00 @:85 B@:127 Recv: ok The first value was "235.~ /235.00" at the beginning of the print but changed to "235.44 /245.00". This indicated that my extruder was at 235 but expected to be at 245, so that made me remember the temperature tower tests I did. I think that there are other things that are causing the stops, maybe I will make some threads about the touchscreen errors that seem related. I will also try to connect cura, octoprint and my PC to the printer in order to debug the problems. Maybe separating the freezing problems in other threads with more information will help us run this printer nice and smooth! =)

So gcode...l its a kind a programming language but more primitive. Its like giving specific instruction to the printer with code difficult to recognize, but it doesn't have much logic like general programming will have. Gcode programs are read once from top to bottom by the machine, no repeating code neither thinking by the 3d printer. Stage 11, step 5. Here you can see the machine settings menu. To the bottom left the gcode executed before the printer stars and to the bottom right the code that is run after the print stops. You can add all sort of crazy stuff in here. https://makertech-3d.dozuki.com/Guide/Stage+11+-+First+Print/17?lang=en Lets analyze the following gcode, this is my starting gcode and should me equal to most people: ;----------Proforge 2S Start G-code---------- M201 X900 Y900 Z50 E5000 M140 S{material_bed_temperature_layer_0} ;Set Bed Temp M104 S{material_print_temperature_layer_0} T0; Heat up Hotend 1 (T0) M109 S{material_print_temperature_layer_0} T0; Wait for Hotend 1 (T0) G28 ;Home G29 ;Autolevel Bed G1 F8000 X10 Y3 ;Move hotend to bottom left corner G1 Z3 ;Move Hotend to assumed Z Home ; ---Unique to your setup--- G92 Z0.47 ;Set Z-offset in 0.1mm incriments (increase if first layer too high, decrease if too low) ; -------------------------- G1 Z{layer_height_0} ;Set to first layer height M82 ;absolute extrusion mode G92 E0 ;Zero Extruder G1 F1500 X290 E12 ;Prime Hotend ; ----------Proforge 2S Start G-code---------- Pretty strange code isn't it? But thanks to Makertech that made a comment in each line we can figure this out faster, check this part of the code: G29 ;Autolevel Bed G1 F8000 X10 Y3 ;Move hotend to bottom left corner G1 Z3 ;Move Hotend to assumed Z Home First line seems to call to the autolevel function, this will trigger the 9 point readings. Question, is the probe(blue thing) always on top of the bed surface when you are printer autolevels? Second line is the code we wanna change, this code tells the extruder to move to this point, somehow in your setup Daryl this is making your extruder go too far. So you have to investigate in the internet what each of this codes "G1 F8000 X10 Y3" means and modify the numerical values to a value that works for you. You can test this codes with pronterface remember, Stage 10: https://makertech-3d.dozuki.com/Guide/Stage+10+-+Programming/16?lang=en So test playing with this code in pronterface and if you find out values that work for you then change the machine settings so you get a correct test line before printing. Unless you like living a dangerous life research the codes before using them in pronterface. I don't really know gcode, you have to study it and solve the problem yourself =), but I can guide you if you have more doubts or problems, just ask. And if someone knows gcode and what I just said is wrong then please correct me hehe xD.

@Daryl Smith ok, I will give you more information about the gcode soon, but I have to insist first, have you try flashing all the software again(arduino, toushcreen, and downloading cura again)? we need to discard this first. Another thing that comes into mind is that when you choose wish printer you have first time using Cura (proforge 2, proforge 2s, proforge 2s dual....) you have to choose the one you build! For example if you haven't build de dual extruder then you have to select "proforge 2s" as your printer, not the "proforge 2s dual extruder " option. Check this things before getting in the code, because code is more difficult and almost everyone get it to work without this error. Check the building guide again if necessary.

@Jonas Lastname Appimage is used for Cura Software creators and others to compile "easy to run" programs for different operative systems. It generates like a .exe that runs without installing. For this printer there was a custom version of cura made, so Makertech had to compile the image themselves. They failed in linux as it needs to be made in a linux environment. I also failed. Don't worry about the linux instructions for flashing the printer. Its the same steps as other operative systems with the exception that no driver needs to be installed, it just works.

I just left you a quick comment in the thread you made.