Here’s the story as I think about it… not trying to make excuses for the slow code turn time, just lay out the events/process. The work I did was take the EBS triangular code that was not in github and merge it with the holey firmware I was working on that has a few more changes to it. It was a bit more than just a merge and it was only for holey firmware not for the triangular calibration that he recently completed. It included doing a diff of each file individually and sorting out what needed to merge and what was superfluous. Once I completed that, it had to be tested and verified before it could be pulled in. It took some time to get feedback that it didn’t work the first couple iterations.
After some time I was able to work out a trade to borrow a board to speed up the cycle and my available time to spend on it decreased dramatically. My system has the high speed z axis motor, so I had to deal with that and it took more time. In that time EBS merged the code with maslowcnc, so triangular calibration of an easbay motor shield on mega should work with webcontrol as it did before, but now it will also work with the firmware flashed from the maslowcnc repository. EBS users don’t have to get the firmware soley from EBS now and it should work with most of the shields. The process of the Holey firmware for EBS motor shield admittedly has taken more time than it should both in testing and in the time elapsed given my availability, but we press on. If it doesn’t pass my testing, I can’t PR it because it will fail the code review and not get pulled in. If it does get pulled in and doesn’t work, then there will be a number of unhappy EBS users that want to use holey as we have seen those that attempted to use it already and it doesn’t work.
There was a pwm frequency issue that is controlled by the firmware that was specific to the TBS chip that EBS worked out in that time and I have taken his changes for that and it should be good to go now, but I still have to test it completely, submit a pr, get it reviewed and THEN it should be incorporated in the next webcontrol build and be available as a webcontrol action menu button press upgrade.