A brief history of Solidoodle firmware:
- Solidoodle alter Marlin in the early days to change it to suit Solidoodle specs.
- Some time later I get my printer and want to add a Panelolu but the 'official' Solidoodle firmware is too old to support it. I end up trying to update parts of the code to suit but it's simply too out of date versus the latest Marlin. Solidoodle show zero interest in updating their firmware to suit users who want the most out of their printer.
- I fork the official Marlin on github and implement the Solidoodle configuration changes, as well as some other tidbits to make the Panelolu run nicely.
- I continue to update my github implementing the latest mainstream Marlin updates. Everyone that uses it is happy, Solidoodle show little interest to the people who don't trust a community release and want them to update their official firmware to have newest features. Eventually they change their official how-tos to point to my github.
- I add a pre-prepared version of Arduino 022 to make the whole process of updating firmware much easier.
- Somewhere around this time Solidoodle launch their own github, which starts as a Solidoodle incompatible version of Marlin and then becomes a copy/paste of the my github but not forked (which means they can't implement updates easily in future).
http://www.soliforum.com/topic/1007/sol … al-github/
- Many others from this great community join the collaboration and implement great additions to the firmware. Neil Martin, Rincewind, Tealvince and Adrian added things like hysteresis compensation, banding fixes, Solidoodle 3 compatibility and filament alarms.
- Adrian updates everything to the latest Marlin spec and prepares a version of the newest Arduino IDE for download.
- Solidoodle releases 'their' new motherboard which is quickly revealed to be a derivative of a printrboard from printrbot. No attribution, instructions or source files are posted despite repeated requests from Adrian and others in the community.
- Solidoodle eventually put up a page with the required content but it is not particularly user friendly for users to update their firmware.
I know I sound very anti-Solidoodle but in my opinion they have been sloppy the whole way with their firmware handling (and other software):
-There was the bad batch of bootloaders saga, where they said there was no problem because users didn't need to update firmware.
- They never really acknowledged mine and others contributions, having denied the need to update firmware for months and then taking our work to their github without credit or permission. Forking would have fixed this because the source stays on the github page.
- At one stage they were going to switch back to the older Sprinter firmware for some crazy reason.
- They also would not switch their support from Pronteface to Repetier-Host until the likes of Ian Johnson paved the way on his blog and most of the community were already using it.
- The whole printrboard update was the poorest yet, I wonder how the printrbot people felt about that?
/end rant.
The first link goes to the current version from my github that Adrian updated 4 months ago. It is a non-official community wiki and as such points to the most recent version.
The second link from the official instructions points to a year old version of my github (Oct 2012), hence not being up to date.
Hazer wrote:Personally, I would turn that off. The newest Marlin does not have that defined, its handled in the homing. Second, I would comment out the ENDSTOPS_ONLY_FOR_HOMING. That is another reason why it grinds. Your tests have all shown the firmware sees the homing switches, you simply have the firmware ignoring them.
Although changing these two settings could fix the problem, as you can see in the history I have posted above, the settings have been in place for a long time. All Solidoodles from October 2012 to when they changed to the printrboard shipped with my firmware and hence with this setting in place. My money is still on some sort of physical obstruction or misalignment.
