Update: Ok, so it seems nobody has attempted running anything other than Marlin. In the two replies below, I have place the pins.h and Configuration.h modifications to Repetier Firmware 0.91. If it works, it would allow you to take advantage of the latest versions of repetier host and firmware. The down side is that (1) you would not be able to rely on Velleman documentation to help with problems, and (2) it is untested, because I don’t have one of these.
At any rate, repetier has excellent support through is user community.
Old Post:
I have not done an extensive search on this, but it seems that nobody has added K8200 support to the latest Repetier firmware.
I don’t have one to test on, so if anyone would care to try it, let me know. Only the pins.h and configuration.h files are changed.
This sounds very interesting. I have a problem to get a THB6128 (1/128) Driver running properly with Marlin. It prints very smooth and noiseless but like the Tower of Pisa. Each Layer get an position add of 1/10mm in X & Y direction. In Github comments of Marlin some guys wrote that it works with Repetier FW out of the box.
The Main question is: Works Repetier FW with Velleman LCD display standalone with SD Card or only together with Repetier Host? This would be a nogo for me
you have a Syntax Error #elifdef K8200BOARD I have replaced this by #endif followed by #ifdef to get the sketch compiled
Stepper XYZ seem to work correctly -> Tested via USB from Repetier Host. Extruder not tested
Heating Bed doesn’t work
Heating Hotend works but the temperature from Bed goes up too. Seems that you use the same sensor pin. I have to say that I set HEATED_BED to 1 in config
The file is not up to date with the version, number on the website download page, then I edit manualy the language.h file and check for MARLIN V1 to replace it. After upload on the board, U will have ur own version of the firmware
Excuse my extreme ignorance, but why do I need to change firmware just to use the latest version of a host program that does nothing more than generate G-Code? Is it perhaps because of the manual commands built into the host?
In addition to generating gcode, we’ll you get better G code from newer slicers from skeinforge, slic3r, and cura. You also get finer control of firmware values, like pod control of hot end and bed, support for arcs in gcode, there is a lot that’s been added to the guy as well.
I’m going to take another stab at this, and try and bring the support in through the official channels for Repetier. I have a Velleman distributor close by that will allow me to test on their floor model.
You know that we talk about the Repetier FIRMWARE and not Repetier host which generates G-Code with Slic3r?!
The reason to load Repetier FIRMWARE is that Marlin fails on 1/128 Stepper drivers while Repetier deals with. See also github.com/ErikZalm/Marlin/issues/1041
I upgraded to the latest open source Repetier host (1.0.6) and the latest Slic3r (1.1.7) without any changes to the firmware. (Oct 2014)
I asked before, but now I will answer my own question. YOU DO NOT NEED TO CHANGE THE FIRMWARE TO UPGRADE TO THE LATEST OPEN SOURCE REPETIER/SLIC3R![/b]
As long as you choose the RepRap version of G-Code in slic3r, the firmware handles it just fine.
Why is there an urban legend going around that K8200 owners are stuck with Velleman Repetier Host unless they change the firmware???
There sure is a lot of misinformation going around on the Internet.
As you maybe have seen in the post before your post - I have a problem to use the THB6128 Stepper drivers which are not working properly with Marlin. I have posted a link where you can see, that a ticket is open for this bug IN MARLIN FIRMWARE
The problem is that this thread discouraged me and others from trying to upgrade to the latest desktop software because it implied that a firmware change was required to do so. A firmware change is NOT required as long as you stick with reprap flavor G-Code.
A desire to move to cura as a slicer or to use a different flavor G-Code are not reasons to tell others they are locked into the Vellerman Host. No K8200 owner is locked into the Vellerman Host.
The Vellerman Host does not support cura anyway, so why should it be a problem to move to more current software and continue to use slic3r?
Anybody reading this - by all means abandon the Marlin firmware if you have a good reason to do so. BUT…Upgrading to the latest Repetier/Slic3r is NOT a reason to abandon Marlin firmware.
The original post asked why nobody has tried other than Marlin firmware on the K8200. The answer is that there is no reason to do so if you are happy with the latest version of Repetier/slic3r.
I haven’t a Problem with G-Code which is by the way more efficient if done by Cura which results in 20% shorter printtime. Also Cura makes drills/holes/diameters in expected diameter and not smaller as slic3r does. There is no reason to use Slic3r. Also because the cura engine is in the newer Repetier host versions available. Also I use the SD Card Option with Display without USB connection.
But I have a Problem by using a THB6128 1/128 Step driver which is a piece of hardware which doesn’t work properly with the Marlin Firmware (see this video youtube.com/watch?v=NoMIsG6EOQg ) but with Repetier Firmware because the acceleration ramp calculation is done on an other way. Nobody have to change the Firmware if everything is running fine but it doesn’t in MY SPECIAL CASE with MY HARDWARE MOD.
The Subject “Repetier Firmware Port to K8200” don’t want people to do that without a reason!
But if they need it, eg. to use noiseless 1/128 (see Video, only noises are from E3D fan) steps instead of noisy 1/16 Pololu stock drivers they COULD do it with this manual. Finally I hope that Marlin get fixed but as long this is not done the repetier Firmware could be a solution. Marlin Firmware has the better Auto Bed leveling procedure than repetier FW has. So Marlin is the no.1 choice for me but as long 1/128 doesn’t work no option. I have double ballscrews on Z, GT2 belts, E3Dv6, capacitive Sensor for automated Bed Leveling and many other things tuned on my K8200. (see my profile on Thingiverse) I’m not willing to stop the improvements because of a lousy firmware bug!!!
