So, I’m trying to upgrade to the new Marlin 1.1.0-RC4. Their new code for the Z probe seems to be causing me some grief. When I go to home, the Z probe server is not getting activated to lower the probe pin on my BLTouch. I have triple checked the settings. So I wonder if anyone has got RC4 to work with the BLTouch and can tell me if they had to do something special to get the servo to work on probing again.
In FACT, it appears that the firmware is completely ignoring the servo commands… M280 P0 S10, M280 P0 S90.
Nevermind. Just found the issue. I missed the RAMPS board type. Was set to 1.3 instead of 1.4.
I’ve been working with RC5 for a couple of days, I skipped RC4. I took a working RC3 config and manually transferred the config using diffs. It broke a few things including induction probing.
These aren’t release candidates as the rest of the software world refers to an RC. These are more like lightly tested betas. An RC should be feature and code complete, just looking for issues prior to shipping. In the case of Marlin they change and even add features between RCs. They need to freeze a version, release it then keep working.
Agreed.
@dstevens_lv I stopped paying attention to Marlin development, as the main devs working on it seem to be more about shiny stuff and 100.000 features then reliability and quality. (Talking them into enabling the watchdog by default was tiresome enough)
I’m very glad our Ultimaker fork is stable, even when the code is still quite a mess. But manageable.
@Daid_Braam Last year when some of the RC s wouldn’t build under the current IDE I went to see what you guys were doing, figuring you were working from your own fork. Your fork is stable, well maintained and uses good repo practices.
I’d been using the same package for over a year though when I upgraded to Arduino 1.6.x and started to use Mini Rambo as a default choice for the mid range kits, I had to either hack that version or upgrade. I still use the older version and older IDE on the RAMPS kits. To compound more and more users want bed probing so that requires a newer build.
Smoothie shows a lot of promise, easy to use though the hardware is a bit on the expensive side and availability in the US is poor.
Replicape from a technology standpoint looks good but it’s difficult to implement for most and expensive.
Archim isn’t quite done but still relies on Marlin Due. I understand a G2 port is coming. Other G2 hardware, or even 3d printing support is vapor and is going to need probably a year to get to the point where everyone can use it.