I keep seeing these great VESC designs from different people. Seems like half of the design is "common" VESC brains and the other half is the power section.
1. Would it make sense to split the brain from the muscle in these designs to add flexibility in making and evolving these designs?
This would allow the common parts to be assembled by a board assembly house and the driver section to be hand soldered / fiddled with to keep building the next level or what specs someone needs.
I'd also love to see this with a Lebowski version too.
Part 2 of this splitting it up question is considering a standardized control pinout and connector that could make these units plug and play. The sealed (TE?) connector galp used for BESC G4 could be a great (but maybe a bit pricey) choice to kick this off. Idea is common parts / assemblies / harnesses could bring the costs down and availability / access up.
Part 3. One area I keep seeing repeating is trying to route the gate traces away from this and that. Would it make sense to use short cable harnesses kind of like https://www.digikey.com/en/products/detail/jst-sales-america-inc/A02SR02SR30K152A/6009377 (or a 3 wire version) twisted then connected to a remote brain board for each drive section? I realize its still required to route to the gate(s). Stacking headers could work but are less flexible.
I think these 3 if agreed upon and done properly could be helpful for the developer and user community here. What do you guys think?
1. Would it make sense to split the brain from the muscle in these designs to add flexibility in making and evolving these designs?
This would allow the common parts to be assembled by a board assembly house and the driver section to be hand soldered / fiddled with to keep building the next level or what specs someone needs.
I'd also love to see this with a Lebowski version too.
Part 2 of this splitting it up question is considering a standardized control pinout and connector that could make these units plug and play. The sealed (TE?) connector galp used for BESC G4 could be a great (but maybe a bit pricey) choice to kick this off. Idea is common parts / assemblies / harnesses could bring the costs down and availability / access up.
Part 3. One area I keep seeing repeating is trying to route the gate traces away from this and that. Would it make sense to use short cable harnesses kind of like https://www.digikey.com/en/products/detail/jst-sales-america-inc/A02SR02SR30K152A/6009377 (or a 3 wire version) twisted then connected to a remote brain board for each drive section? I realize its still required to route to the gate(s). Stacking headers could work but are less flexible.
I think these 3 if agreed upon and done properly could be helpful for the developer and user community here. What do you guys think?