Hello,

Sounds good but I was not being too harsh on Seeed Studio from my 
perspective. I guess people get busy and languages collide at times. I can 
chalk up the issues over the years to that idea. 

...

Nothing is perfect and I may be in limbo but I think the Cape should have, 
from what I understand, a couple drivers (four or five) for handling heavy 
motors. I mean, why purchase a ton of extra equipment when the BBAI and 
Cape can handle it?

Seth

P.S. And sir, I am not by any means telling you or the rest of the 
community to not purchase products from Seeed Studio. That is not my aim. I 
just wanted more communication and less typos without explanations. Now, 
are we looking for specific drivers or do you have any in mind? I mean, is 
it okay to "quarrel" about this issue or is anything set in stone? I would 
like to help find some drivers that are easily accessible, i.e. 120v? I 
know the replicape handles 24 volts but may be a little too small in 
wattage for what this group may want. I am not speaking for anyone outside 
of myself, I guess. If that is too much to inquire over, that is okay. I 
steadily give out info. when I can on specific BBB related issues and 
ideas. "Take the good w/ the bad, supposedly." Sounds good.

On Thursday, March 12, 2020 at 4:05:14 PM UTC-5, Jason Kridner wrote:
>
>
>
> On Thu, Mar 12, 2020 at 2:59 PM Mala Dies <[email protected] <javascript:>> 
> wrote:
>
>> Hello,
>>
>> I am a novice in most fields of study regarding brushless stepper motors 
>> and drives. If anything, I think allowing people like me, the novices in 
>> this category, to establish as domain in the field with not only hardware 
>> but a temporary to permanent wiki support would be what Open Source 
>> initiatives are made of currently.
>>
>> ...
>>
>> I know about Machinekit and how it offers specific uses to users like me. 
>> Although, and this is the truth, I have not used Machinekit with my 
>> RepliCape, I have been wanting to test out these images for use in a 
>> particular manner.
>>
>>
>>    - Key Takeaways 
>>       - Ease of use
>>       - Open Source Hardware and Source (the BBB.io persons' ways)
>>       - An updated Wiki of ideas all relative to this specific hardware, 
>>       source, and middleware
>>    - Stated Opinions 
>>       - Although my opinions may fall short of technological at times, 
>>       ease of use is always a need
>>       - I would make lists and hold a meeting
>>          - Hardware
>>          - Source (Machinekit)?
>>          - Wiki (who will have advanced knowledge to pick apart the 
>>          wiki)?
>>       
>> Now...I am sure Seeed Studio can handle, w/ the current state of 
>> machinery, the needs of me, myself, and I (and other users like me too). 
>>
>> But...
>>
>> So, sockets or pins or connections:
>>
>>
>>    - I say that actual connections should be made outside of the screw 
>>    terminals, i.e. either soldered or a terminal block that is severely 
>>    equipped to handle people moving around the machinery and electronics.
>>    - I also say that there should be a couple of people at least that 
>>    are dedicated to the project, e.g. more knowledgeable people than I on 
>>    these subjects.
>>    - I also say that the computer needs to be the source of the UX, GUI, 
>>    UI, or whatever we call them these days.
>>
>> ...
>>
>> Now...I am not affiliated but I am definitely a community member that has 
>> "outlandish" goals for specific projects. I have been here since the A5C 
>> BBB. I think it has been since 2014/15. 
>>
>> Why am I telling you these ideas and reaching out? 
>>
>>
>>    1. I have seen specific ideas go to waste and not catch any ideas 
>>    from other community members on many of the Capes produced. 
>>    2. Either the Capes produced, were before my time, circa '14/'15, or 
>>    I have been paying less attention to what is needed regarding the Capes.
>>    3. I think the Capes are a big part of the community and ideas 
>>    circulating are more than a start.
>>
>> I hate to down Seeed Studio because of their popularity and ease of 
>> motive to act on making nice equipment but...
>>
>> Sometimes, I think because of their wikis not being updated frequently, 
>> people lose interest or find that support is not viable for them. 
>>
>> I have been to the Seeed Studio wiki many times in my life and sometimes 
>> I have been rewarded for asking for support. Other times, the community was 
>> more needy than I and I had to provide what I learned.
>>
>> All I am typing here is that interest gets lost when people are not 
>> updating due to whatever reason. Do you or do we want another Cape to get 
>> lost attention when it is a piece of GOLD?
>>
>
> Let's look to Seeed for what we know Seeed is good at. They do good design 
> work, they manufacture on-time at good prices at varying volumes for long 
> periods of time, if given the right constraints of a well-defined 
> functionality they do good quality control, they solve difficult component 
> challenges with good visibility into what is available and they work well 
> in the open source world as information is requested from them they give 
> very freely. That said, they aren't Machinekit experts and this community 
> would be educating them on that. Documentation on using Machinekit should 
> be coming from the Machinekit community and documentation around new 
> hardware should be done in a way that meets this community's standards. I'm 
> asking if we can work together to leverage Seeed's strengths to solve a 
> gap--the gap of while there are lots of cool solutions around BeagleBone 
> and Machinekit, the add-on hardware to make them is not readily available 
> in distribution with ready-to-go software images.
>
> Sound good?
>  
>
>>
>> Seth
>>
>> P.S. Now, I understand that beagleboard.org is not a major subsidiary of 
>> Lexus or whatever large company. I am not talking about 24/7 support by way 
>> of email, phone, chat, and face time or live meetings online and in person. 
>> I would ask but I am too scared. Anyway, please try to make this venture w/ 
>> ease of access in mind, sturdy (durable) power and pin connectors, and w/ 
>> access to extra i2c pins on the AI if they are indeed available by way of 
>> Machinekit. Phew. Okay, I think that is enough opinion to make anyone 
>> cringe. Sorry and please consider my needs versus the power hungry 
>> machinists that already know up from down. 
>>
>>
>>
>>
>>
>> On Thursday, March 12, 2020 at 8:38:53 AM UTC-5, Jason Kridner wrote:
>>>
>>> Seeed is looking to not only build a Machinekit-focused Cape for 
>>> BeagleBone Black and BeagleBone AI, but to:
>>> * Take in features and feedback from the community
>>> * Contribute the design to open source and certify it as such
>>> * Manufacture the design under the BeagleBoard.org name to support the 
>>> BeagleBoard.org Foundation and community
>>> * Help assemble and provide software images configured for an open 
>>> source 3D printer and CNC machine (with BeagleBoard.org and community 
>>> guidance and support)
>>> * Offer a collection of additional accessories which might commonly be 
>>> needed
>>>
>>> I am very excited about this because I know Seeed cares about open 
>>> hardware and also knows how to deliver solutions reliably and cost 
>>> effectively.
>>>
>>> So, what are your ideas about where to start on such a cape?
>>> -- 
>>> https://beagleboard.org/about
>>>
>> -- 
>> website: http://www.machinekit.io blog: http://blog.machinekit.io 
>> github: https://github.com/machinekit
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Machinekit" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/machinekit/36936efa-6887-4762-9982-1c2ac3dc3af7%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/machinekit/36936efa-6887-4762-9982-1c2ac3dc3af7%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> https://beagleboard.org/about - a 501c3 non-profit educating around open 
> hardware computing
>

On Thursday, March 12, 2020 at 4:05:14 PM UTC-5, Jason Kridner wrote:
>
>
>
> On Thu, Mar 12, 2020 at 2:59 PM Mala Dies <[email protected] <javascript:>> 
> wrote:
>
>> Hello,
>>
>> I am a novice in most fields of study regarding brushless stepper motors 
>> and drives. If anything, I think allowing people like me, the novices in 
>> this category, to establish as domain in the field with not only hardware 
>> but a temporary to permanent wiki support would be what Open Source 
>> initiatives are made of currently.
>>
>> ...
>>
>> I know about Machinekit and how it offers specific uses to users like me. 
>> Although, and this is the truth, I have not used Machinekit with my 
>> RepliCape, I have been wanting to test out these images for use in a 
>> particular manner.
>>
>>
>>    - Key Takeaways 
>>       - Ease of use
>>       - Open Source Hardware and Source (the BBB.io persons' ways)
>>       - An updated Wiki of ideas all relative to this specific hardware, 
>>       source, and middleware
>>    - Stated Opinions 
>>       - Although my opinions may fall short of technological at times, 
>>       ease of use is always a need
>>       - I would make lists and hold a meeting
>>          - Hardware
>>          - Source (Machinekit)?
>>          - Wiki (who will have advanced knowledge to pick apart the 
>>          wiki)?
>>       
>> Now...I am sure Seeed Studio can handle, w/ the current state of 
>> machinery, the needs of me, myself, and I (and other users like me too). 
>>
>> But...
>>
>> So, sockets or pins or connections:
>>
>>
>>    - I say that actual connections should be made outside of the screw 
>>    terminals, i.e. either soldered or a terminal block that is severely 
>>    equipped to handle people moving around the machinery and electronics.
>>    - I also say that there should be a couple of people at least that 
>>    are dedicated to the project, e.g. more knowledgeable people than I on 
>>    these subjects.
>>    - I also say that the computer needs to be the source of the UX, GUI, 
>>    UI, or whatever we call them these days.
>>
>> ...
>>
>> Now...I am not affiliated but I am definitely a community member that has 
>> "outlandish" goals for specific projects. I have been here since the A5C 
>> BBB. I think it has been since 2014/15. 
>>
>> Why am I telling you these ideas and reaching out? 
>>
>>
>>    1. I have seen specific ideas go to waste and not catch any ideas 
>>    from other community members on many of the Capes produced. 
>>    2. Either the Capes produced, were before my time, circa '14/'15, or 
>>    I have been paying less attention to what is needed regarding the Capes.
>>    3. I think the Capes are a big part of the community and ideas 
>>    circulating are more than a start.
>>
>> I hate to down Seeed Studio because of their popularity and ease of 
>> motive to act on making nice equipment but...
>>
>> Sometimes, I think because of their wikis not being updated frequently, 
>> people lose interest or find that support is not viable for them. 
>>
>> I have been to the Seeed Studio wiki many times in my life and sometimes 
>> I have been rewarded for asking for support. Other times, the community was 
>> more needy than I and I had to provide what I learned.
>>
>> All I am typing here is that interest gets lost when people are not 
>> updating due to whatever reason. Do you or do we want another Cape to get 
>> lost attention when it is a piece of GOLD?
>>
>
> Let's look to Seeed for what we know Seeed is good at. They do good design 
> work, they manufacture on-time at good prices at varying volumes for long 
> periods of time, if given the right constraints of a well-defined 
> functionality they do good quality control, they solve difficult component 
> challenges with good visibility into what is available and they work well 
> in the open source world as information is requested from them they give 
> very freely. That said, they aren't Machinekit experts and this community 
> would be educating them on that. Documentation on using Machinekit should 
> be coming from the Machinekit community and documentation around new 
> hardware should be done in a way that meets this community's standards. I'm 
> asking if we can work together to leverage Seeed's strengths to solve a 
> gap--the gap of while there are lots of cool solutions around BeagleBone 
> and Machinekit, the add-on hardware to make them is not readily available 
> in distribution with ready-to-go software images.
>
> Sound good?
>  
>
>>
>> Seth
>>
>> P.S. Now, I understand that beagleboard.org is not a major subsidiary of 
>> Lexus or whatever large company. I am not talking about 24/7 support by way 
>> of email, phone, chat, and face time or live meetings online and in person. 
>> I would ask but I am too scared. Anyway, please try to make this venture w/ 
>> ease of access in mind, sturdy (durable) power and pin connectors, and w/ 
>> access to extra i2c pins on the AI if they are indeed available by way of 
>> Machinekit. Phew. Okay, I think that is enough opinion to make anyone 
>> cringe. Sorry and please consider my needs versus the power hungry 
>> machinists that already know up from down. 
>>
>>
>>
>>
>>
>> On Thursday, March 12, 2020 at 8:38:53 AM UTC-5, Jason Kridner wrote:
>>>
>>> Seeed is looking to not only build a Machinekit-focused Cape for 
>>> BeagleBone Black and BeagleBone AI, but to:
>>> * Take in features and feedback from the community
>>> * Contribute the design to open source and certify it as such
>>> * Manufacture the design under the BeagleBoard.org name to support the 
>>> BeagleBoard.org Foundation and community
>>> * Help assemble and provide software images configured for an open 
>>> source 3D printer and CNC machine (with BeagleBoard.org and community 
>>> guidance and support)
>>> * Offer a collection of additional accessories which might commonly be 
>>> needed
>>>
>>> I am very excited about this because I know Seeed cares about open 
>>> hardware and also knows how to deliver solutions reliably and cost 
>>> effectively.
>>>
>>> So, what are your ideas about where to start on such a cape?
>>> -- 
>>> https://beagleboard.org/about
>>>
>> -- 
>> website: http://www.machinekit.io blog: http://blog.machinekit.io 
>> github: https://github.com/machinekit
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Machinekit" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/machinekit/36936efa-6887-4762-9982-1c2ac3dc3af7%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/machinekit/36936efa-6887-4762-9982-1c2ac3dc3af7%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> https://beagleboard.org/about - a 501c3 non-profit educating around open 
> hardware computing
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/96aebdae-6f87-49bf-bd6c-f21813910b06%40googlegroups.com.

Reply via email to