old non-functional guide #30
Comments
|
Unfortunately, I am unable to actively maintain this project due to my work NDA. I’m sure that the challenge of figuring some things out will be rewarding for you :) |
|
When I find something on Github I look to see when the last modification to
the files was made. When it is longer than a year, I figure the project is
abandoned. Nonetheless, there might be ideas and code snippets I can
use. Such is the case here.
In general, Micro Spot is like that. You have to look at many
implementations of the hardware and software and borrow the best you can
find and run from there. You put your own work on Github and
eventually someone finds it and moves the ball a little farther along.
I ended up redrawing all the CAD files with some design ideas borrowed
from different places, and the same with the software.
So my thanks to the creator of this (abandoned) site and many others who
did the same.
…On Wed, Oct 5, 2022 at 8:28 AM kennydedavion ***@***.***> wrote:
who runs this mess of links that lead nowhere??? spot mini mini
unmaintained pages, old non-functional guide.
—
Reply to this email directly, view it on GitHub
<#30>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQKNRQLKNSZY3BW7GC7ZCDWBWNCHANCNFSM6AAAAAAQ5V43LI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Chris Albertson
Redondo Beach, California
|
|
Maurice, looks like your passion for spot was well worth the time and effort for yourself and the public with this development. Best wishes to your continued developments at BD, contributing to state of the art Robotics. Thanks for sharing and keep up the great work. |
Although I did not finish my OpenQuadruped completely I can confirm that instructions found in https://github.com/OpenQuadruped/spot_mini_mini/tree/spot/spot_real work including code for Teensy microcontroller and calibration instructions. Dead links may be caused by merging code from the two original repositories (by adham-elarabawy and moribots) into this one. |
|
Thanks for the supportive comments :) This project was a lot of fun for me in addition to being educational. I hope that you’ve received similar value from it. I’ll make sure there’s a note in the main README indicating the unmaintained status of the project. |
|
it is possible to write that this spot is teensy something fucked up and not that repo is allowed for everyone. if it is not written there and the spot does not run on rpi, like the others, what is the correct repo. give this guide to all your friends, or the most beautiful woman, and you will see what is wrong and what is missing. for example, I consider the instructions for a successful launch to be those where everything is really stated, EVERYTHING! not just what I consider sufficient. instructions on how to proceed to launch, including all absence steps. and if the repo is no longer maintained, I recommend deleting it immediately, especially if the issue is open and the author doesn't care about it! |
|
@kennydedavion - Clearly more than this repo is troubling you and I hope you find peace soon. I realize I'm turning your blowtorch on me, however speaking up to abuses was one of my new year's resolutions. If you genuinely desire functionality from this repo @domcross - chimed in on the specifics. In reference for myself, I found the details of the Bezier gait proofs interesting and useful without attempting to build out the bot. |
|
The CORRECT thing to do is to FORK this repository and then fix it
yourself. Then after testing, post a pointer to the forked repository.
But then notice what you have done. You now have a "job for life" because
you don't want people 20 years from now to complain of broken links.
…On Thu, Oct 6, 2022 at 4:44 AM kennydedavion ***@***.***> wrote:
it is possible to write that this spot is teensy something fucked up and
not that repo is allowed for everyone. if it is not written there and the
spot does not run on rpi, like the others, what is the correct repo. give
this guide to all your friends, or the most beautiful woman, and you will
see what is wrong and what is missing. for example, I consider the
instructions for a successful launch to be those where everything is really
stated, EVERYTHING! not just what I consider sufficient. instructions on
how to proceed to launch, including all absence steps. and if the repo is
no longer maintained, I recommend deleting it immediately, especially if
the issue is open and the author doesn't care about it!
—
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQKNRWAJQWG543SSBYKLFLWB23SPANCNFSM6AAAAAAQ5V43LI>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Chris Albertson
Redondo Beach, California
|
|
Yes. My Spot Micro is usig spline curves only because I understand them
and now I think I want to try bezier curves. So I too am reading this
repository or rather my forked copy of this repository.
This is how the project advices, grab the best ideas for the dozen or so
active Sptot Micro projects out there.
About the hardware. My opinion is the Pi4 is the way to go. You need the
PCA9685 and also an I2C gyro/acceloometer and also pressure sensors on the
feet. And I think the shoulder design of this "Spot is ugly, too wide and
not strong enough and that mine is better. But to get there I looked at
this one and said. "I can improve it"
https://github.com/chrisalbertson/SpotMicroModular/tree/main/Hardware
…On Thu, Oct 6, 2022 at 7:57 AM MrRobotoW ***@***.***> wrote:
@kennydedavion <https://github.com/kennydedavion> - Clearly more than
this repo is troubling you and I hope you find peace soon. I realize I'm
turning your blowtorch on me, however speaking up to abuses was one of my
new year's resolutions.
If you genuinely desire functionality from this repo @domcross
<https://github.com/domcross> - chimed in on the specifics. In reference
for myself, I found the details of the Bezier gait proofs interesting and
useful without attempting to build out the bot.
—
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQKNRSPTV6EPBIO7ZJ5FSTWB3SFVANCNFSM6AAAAAAQ5V43LI>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Chris Albertson
Redondo Beach, California
|
|
@chrisalbertson - Thanks for sharing your link and insight. |
who runs this mess of links that lead nowhere??? spot mini mini unmaintained pages, old non-functional guide.
The text was updated successfully, but these errors were encountered: