Yes, the Dual FSESC6.6 available now, and can be shipped right away after done your order, but don’t forget $51 coupon promotion till 24:00 pm 2018/9/10 (CST), how to get? Follow our FB page and PM us for code:smile:
1 Like
@BarbaraZ why not make the heatsink like the dual escape esc heatsink or dual focbox heatsink from @Kug3lis , in that way the PCB is more protected, and we can cut out in the enclosure for better heat dissipation, and it also gives a little more space in the enclosure. If it increases the price a bit, so be it.
5 Likes
Labor Day Sales Off, Click here, https://www.facebook.com/FlipskyTech/ Follow and PM us for special code. 51usd for Dual ESC6.6.
Maytech’s new dual VESC. It looks very compact but expensive.
With no heatsink 
1 Like
I also wondered. However, there are MOSFETs on both the upper and lower sides. How does this work?
Haha do you even know what you talk about?
Enertion focbox available Trampa itself is official maker of vesc6 but still schematic available Maytech and etc uses basic 4.12 schematic without changed values. Other ones mention what was changed.
Evolve wtf? 
Do we even have details on what ESC Evolve uses? Would be kinda interesting to see specs and stuff
8 Likes
I am not picking up it’s required by license… Your “brother” has created forked version of open source project which by it’s license requires to publish all the changes made from original…
3 Likes
I agree price should be lower if possible without significant reduction in quality. But what Kug3lis is saying is that the modified opensource schematics should be released. He was actually asking FLIPSKY people to publish the modified schematics as is the law, your brother came in FLIPSKY’s defence when Kug3lis commented that they didn’t reply.
2 Likes
Yep its required by law, they agreed to it when they used the VESCs design which comes with the creative commons Attribution-ShareAlike 4.0 International license that states,
If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
BUT… whos gonna make them share it? @Kug3lis U gonna hire a lawyer to make them? In reality they don’t have to do jack shit cause they in china and i bet vedder got more important things to do than go after some vendor lmao
3 Likes
Uuhh, what? I will simplify things for you. An increase in accidents leads to an increase in regulations. Incident reports can be caused by a number of things, including faulty equipment. Badly designed parts will influence the rep of esk8 in the long run. There are plenty of examples where this has happened to other industries, e.g balance boards catching on fire.
But a least we know now why the other hyperlon was defending this product furiously. Family. Always good to mention such things to ensure an unbiased view.
Time will tell if this vesc will be a contribution or the exact opposite.
2 Likes
Hyperlon2 has not posted here until recently and only just now identified himself as the developer, so yes… it was hard to notice at first due to a complete absence.
In my company, the sales reps are in close contact with tech pre-sales and the development department. The lack of such a structure and the unawareness of @Kug3lis that such a structure is non-existent in your case is hardly indicative of his intelligence.
The structure here is most likely that you off sourced manufacturing to flipsky, but even then there is no reason why communication is restricted to sales rep to customer.
I really do think the back and toward bashing needs to end here. Nothing but short sighted replies. Please stay factual and if you can, supply the requested info.
3 Likes
To clarify one thing: If you distribute GPLed code (convey the code) you have to pass on the GPL license to the customer. You need to sow the copyright (in this case Benjamin Vedder and relevant other contributors) and you need to offer the exact source code that is being distributed. Since the Hardware comes with the firmware installed, you distribute the GPLed firmware code together with the hardware. It’s like selling a computer with pre-installed GPLed operating system or flashed GPLed bios. So you need to make sure that you meet all requirements of the license. If you don’t meet the license requirements, your license terminates itself automatically (section 8 GPL) and a case of copyright infringement is the consequence whenever you distribute the code together with the hardware.
So make sure that your supplier can offer you the exact source code of the firmware used, so that you can re-distribute it to your customers. It’s a chain that doesn’t want to break up somewhere. As a distributor it’s your liability to follow the terms of the GPL-License! If your supplier can’t hand over the exact source code used, you better stay away from selling the devices.
8 Likes
@trampa : Teaching lessons when you are not able to keep your own word (publish a fully functionnal reference design of the VESC 6 with all PCBs and BOM) is simply ridiculous. you were asked 10 times and you said yes. At the end, you enforced your trademark and did not publish it. That is the fact.
You cannot parade like the knight of the open-source when you (mis-)use this concept to make profit.
1 Like