Corrections: I'll mention this in the macro video and probably should have done it here too. There is no evidence of temp sensors on these controllers. I know the STM32F103 has one internally, but that's useless for the mosfets. There really ought to be at least 2 of them. I'd put them, central as possible and physically on the MCPCB's.
Good day. I read about that at endless-sphere. If I understood all correct, temperature of mosfets is MEASURED not by thermocouple or similar device, but using same method that sometimes used to measure temperature of the LED`s - by measuring of voltage drop at MOSFETs during they are warm-up\change temperature. Didn't verify that myself. But opinion like that exist’s. Also, there is one "bug". One of the users of that forum (at youtube his nickname\channel SilentEnduro) had reported that controller significantly reduce power after some abuse in mountains\uphills. I am saying "bug" because MOSFET`s actually cold, but controller thinking they are hot and reduce power. At endless-sphere there is one post with "settings" that are changing the way how internal temperature is calculated. They are works for him, but he is not recommending to copy them because of risk that controller will be "brickt" (in case of different version, etc). (However,I did copy them to hidden menu inside VOTOL-EM-V3 Software)
@@viko2812 I can't speak about how it might do temp sensing. Just me, but assuming the mosfets are behaving XYZ way may be unreliable. Proof is in the multiple points of truth and this is one area where the EM150 is lacking in my opinion. It REALLY needs at least one temp sensor on the high side and one on the low side. What is this "hidden menu" you are referring to?
@@de-bodgery youtube keep removing links((( even at own youtube videos. omg....( Will try to just type... Open Votol-EM-V3 software... Than switch to PAGE3..... After that inside EditBox: "error_count:" remove all digits and type twice using keyboard sybmol "~". You will see "hidden menu" - Temperature protection. Or maybe you know how I can share link to youtube video. I captured a video with that process and with WEB page about settings at endless-sphere site.
A few optimizations and it can probably do close to 300 battery amps. This would make for an interesting add-on video to the 3 I do for the controller. AKA...how to beef up amperage.
@@patrickmckowen2999 Not sure, never seen the 300 version! I'd like to see one of the /2 and find out what is different between the EM-250 and EM-150/2. No idea what the EM-300. Votol isn't exactly forthcoming with information about their controllers!
So to recap suggested upgrades to the EM-150...fill the gap in the "L" of the thick copper battery+ plate, shorten the leg attachment on the MOSFETs, More high-frequency filter capacitors, add a temp sensor...
I noticed in a teardown of the EM260 model that 2 phase current sensors are used so they must have implemented a more complete version of FOC on those models
Same basic FOC capability as Far Driver or KO. They all use the same STM32F103 CPU and the same basic FOC libraries. This is a lower power CPU that can't handle the full set of FOC capabilities like VESC or Nukular can on the much more powerful STM32F405 CPU.
About firmwares of controllers, including Kelly: This whole mess started around 2006-2010. At the request of the growing market, many manufacturers have created their own controllers. At that time, there were no FOC libraries/SDKs (which are now offered by microcontroller manufacturers themselves). And each controller manufacturer had to develop its own firmware. Which is what they did. This is not a super difficult task but not a super easy one either. Yes, in recent years, microcontroller manufacturers have realized that they can attract more people if they release ready-made SDKs for implementing FOC. But, controller manufacturers could not use it this way (it simply did not exist in the past). They tested/developed and added new functions to their own firmware. And later, even with the advent of SDK FOC from microcontroller manufacturers, there was no point in switching to them. And therefore, it is logical that controller manufacturers continued to develop their own firmware. They have already been tested and work well.
This is exactly why you see wide spread adoption of the STM32F103 in Far Driver, Votol, Sia, KO and others. They are all using the FOC SDK from STM for this CPU. As a result, you can also see many of the same motor control glitches in all these controllers. About the only people doing their own work is VESC (STM32F405), Nukular (STM32F405), Kelly (MCF51AC128) and ASI (TI F302). I'm sure there are others too. Pretty much everybody else is using the STM F103 and the SDKs for it or they are stealing VESC like Torp does.
Hey there, so I have a Talaria Sting, the original controller broke so I wanted to get a KO but after your videos I'm wondering if this isnt a better option? Not looking for crazy power, just longevity and reliabilaty.
Hi! How did you removed the plastic lid? I have a EM100 which is very similar but can't remove the lid after obviously removing the screws. Any help would be helpful!
slipped a knife between the plastic and the aluminum all the way around to make sure it wasn't stuck down with silicon anywhere and then it pried up easily. There was a controller that had a weird set of studs on it. I'd watch all my tear down videos on the EM-150 to make sure it's not that one.
@@de-bodgery For some reason, I can't get the plastic off. Already did what you said but it is still attached. My guess is that it is glued, so I'll try to use a little bit of acetone.
Small world: i just have a Votol EM-150/2 on the bench. Low- and highside Fets blown on th U-phase. Five Fets desintegrated, nearly zero ohm between all three legs. I wonder why the 6 big caps are only rated 63V and the Fets are 100V types (MDP10N027). But it has gatedriver ic (IRS2127)
@@de-bodgery I think you are right: zero ohm between gate and source and fourty ohms between phase and battery plus. I hope I can fix it. Right now I only opened the controller to look what caused the fourty ohms.
hi, in case a unit brings always overcurrent and phase current at 0 no matter how many times I write parameter with different values, means the unit is bricked?? can you tell me in case of em50 if an sdm resistor may be the culprit for this issue? or a cap or bad component to check?
I don't know the EM-50 at all. If it is constructed like the EM-150, then I can give you advice based on the EM-150. The EM-150 has shunts for battery current, but not for phases. If I was seeing your error on an EM-150, I'd check the circuitry around the shunts and up to the CPU.
Sir... How it's not FOC controller?!?! The current on phases can be measured by the voltage drop across the mosfets themselves. This seems to be exactly what it does in Kelly KLS Chetah series and many other models of Kelly Controllers.
No direct phase current sensing is usually a good sign that something isn't FOC. Battery shunts only is usually a good sign of NOT being FOC. However, in the case of this CPU, there are libraries that are used by Fardriver/KO and others that all use this same CPU. It's jsut a matter of when you make your firmware what parts of it you implement or don't implement. So there is pretty good chance that Votol is using some form of basic FOC control. BTW, using mosfets to sense phase current is seriously unreliable. As the mosfets warm up, their resistance changes. If you want to consistently measure phase amps, you need a reliable resistance to do that with! You can go look at data sheets for many mosfets and see Rds graphs vs temperature. This is a VERY unreliable way to measure a voltage drop and use that to calculate phase amps!
@@de-bodgery First of all thank you for answer sir. I would not recommend you to say "FOC libraries". That sounds I don’t know - a little weird. It is more appropriate to say "FOC implementation" instead. Programmers who create firmware with FOC implementation for the controller do not take any libraries(in most cases), but instead create everything from scratch. It's just fun for programmers to stretch their "muscles", it's an interesting task in general. This is the case when the program code is directly connected to the real physical world and affects it (I mean through the motor). That is, it's like creating a robot/Frankenstein. Yes, I guessed that using mosfets to measure current might not be accurate enough. Thanks to the information from you, I now understand what some of the compensation tables I see in the firmware mean. Kelly controllers have a fairly decent number of temperature sensors. And most likely these sensors plus compensation tables are used to compensate for temperature changes in mosfets parameters. Despite the fact that measuring phase currents on mosfets is theoretically unreliable, in practice Kelly controllers work great. If, of course, they are configured correctly and the controller and the specific motor are balanced. Then Kelly begins to work magically and cosmically softly. What is interesting is that it is impossible to completely balance Kelly and a specific motor using the Kelly program for configuration. There is some kind of chaos going on in the company in terms of software. But it doesn't matter, I'm almost finished with my project, which solves all many of these problems, saving owners of Kelly controllers from a lot of headaches.
@@KellyControllers I'm sure Kelly probably created their own firmware. I've used several Kelly controllers and the layout of the software and general controller functionality set leads me to believe that Kelly probably did their own firmware. Also, only other place I've seen the CPU kelly uses is in a Sabvoton. I've taken apart a ton of controllers and not seen it elsewhere. There's a good chance that Kelly developed their own libraries for the different controller types they sell.They have a large enough staff and been around a long time that they probably have on staff programmers. They probably have compensation tables to account for mosfet temperature. I'd just use phase shunts and not have to deal with any of that! Before I commented on temp sensors, I went and looked at my own pics of the 4 different Kelly controllers I've taken apart. I find a single temp sensor on the center phase on the high side mosfets only. That's hardly anything! It's at best an average of the total heat of all 3 phases. *** ASI, Sevcon and maybe one or 2 other companies that have been around a long time have done their own firmware from scratch for smaller controllers. Probably many big cost inverter makers have done their own work. There's a lot of money in that type of thing that doesn't exist in controllers you'd put on a Surron or e-bike! I know elevator, commuter bus and electric locomotive inverter companies that use VESC because this is such a huge challenge! The numbers of truly independent companies doing controller firmware development all on their own are quite few! *** BTW...as someone that actually works in software development, they are called "libraries". What you do with those libraries to make a functioning controller is your "FOC implementation" In the case of Votol, Far Driver, Ko Moto and others that are all based on the STM32F103 CPU, they are using the same FOC libraries on all of their products. This greatly reduces the amount of development they have to do! Tweak some stuff for how you measure current and timing and it probably runs. You can see the exact same firmware glitches in Far Driver, KO and Votol thanks to the exact same FOC libraries!!! Some time back, I asked several VESC developers about independent firmware development. I do mingle with the VESC development people pretty often! Talking to the likes of Benjamin and Frank, the founders of VESC, they tell me a very different story about developing firmware from scratch. Sure it can be done as that is exactly what they did for VESC. I know one other guy that does VESC development that has created his own FOC firmware tat runs on the STM32F405. He's quite active in VESC development too. He's the only other person I know of that has done this! Everyone else, they steal VESC like TORP or Electro and Company tried to do! All the others using the STM32F103 CPU, they steal or borrow from each other or use the ready made FOC libraries that exist for this CPU. I bet there is a handful of Chinese programmers that actually modify all the firmware for all the Chinese controllers that use the STM32F103! Copying in China is RIFE! Far Driver has done a lot of work with those FOC libraries and KO moto denies it, but they are using FD firmware almost as is! I don't know if that's true for Votol, but minor changes to those libraries is easy compared to "stretching your muscles" and starting from scratch! I imagine others like SIA and a dozen other China brands with basic FOC capability are mostly copies of each other and all based on those exact same STM32F103 libraries! Every VESC developer I know of says this is a monumental task to take on from scratch. China where there is no intellectual property laws and copying is so rife, most of those companies would rather copy/steal instead of try to tackle this from scratch! *** It would be amusing to buy one controller from every China brand that claims FOC. I'm betting 100% of them use the STM32F103. I'm also betting the same glitches that are common to FD and KO and Votol also exist in all those other brands! AKA...it's all the same firmware!
Not really. If you blow mosfets, a gate driver may also blow. An IC with a part number on it is usually easy to find replacements. A tiny transistor or diode or whatever might not be something you can find the part. I often times can't find replacement discrete components by their 2 or 3 letter part code.
@@de-bodgery Thanks. This is the type of thing I like about your channel. Its easy to say one device is crap and the other one is awesome, but without the details as to why, someone who is not into electronics can't make an wise decision.
For what it is worth, the Votol EM-100 is identical with the exception of 3 MOSFets per group instead of 4 for this controller. Even though the EM-100 is only a little bit less in current, it is well lower than half the price of the EM-150.
@@de-bodgery Probably, better to get just get rid of the100 and lower price of the 150 by 20%, you will save far more on that back end than you will lose on the 20% off the150. Cheers
Hi I have a question about a daymak em2 controller was wondering if I can run 96v batteries full charge is 108v Model: Daymak - DMK1892 Voltage: 48V-72V (72V) Current: 25A-50A (38A) Power: 500W-1000W Low Voltage Cutoff: 40V(63V) BLDC Controller (Bluetooth) Code: A180189203 7353-XF D DAYMAK DRIVE TURBO
No More than likely over voltage will occur at 88v in my experience with basic controllers. Fardriver 72v models are capable of 106.1v over but u should order a 96/108v controller that makes full use of 26S cell config. Cylindrical cells drop V a lot during max draw so starting with >106.5 helps A LOT. Pouch cells drop much less but don't take abuse as well. 87.9v /26 is comically low. 3.3v per cell? Ur only drawing 50 A so maybe but it's a temp solution to be avoided.
Not the reason. Recycling comes after economics and always has. It's slightly abrasive and wears out injection molds faster. It's more expensive material. It's harder to mold. The cost of using glass reinforced materials is significantly higher than using cheap ABS. This is why it isn't used. Most manufacturers don't care about recycling. This is forced on them and not something that most companies do voluntarily since it isn't economically beneficial to them to recycle.
besaue of this videoo I chose to purchase the Votol over a Fardriver. I would love to have 29.6% of your knowledge on electronics. I am new and self taught, sometimes sparks fly:)))))
Corrections:
I'll mention this in the macro video and probably should have done it here too. There is no evidence of temp sensors on these controllers. I know the STM32F103 has one internally, but that's useless for the mosfets. There really ought to be at least 2 of them. I'd put them, central as possible and physically on the MCPCB's.
Good day. I read about that at endless-sphere. If I understood all correct, temperature of mosfets is MEASURED not by thermocouple or similar device, but using same method that sometimes used to measure temperature of the LED`s - by measuring of voltage drop at MOSFETs during they are warm-up\change temperature. Didn't verify that myself. But opinion like that exist’s. Also, there is one "bug". One of the users of that forum (at youtube his nickname\channel SilentEnduro) had reported that controller significantly reduce power after some abuse in mountains\uphills. I am saying "bug" because MOSFET`s actually cold, but controller thinking they are hot and reduce power. At endless-sphere there is one post with "settings" that are changing the way how internal temperature is calculated. They are works for him, but he is not recommending to copy them because of risk that controller will be "brickt" (in case of different version, etc). (However,I did copy them to hidden menu inside VOTOL-EM-V3 Software)
@@viko2812 I can't speak about how it might do temp sensing. Just me, but assuming the mosfets are behaving XYZ way may be unreliable. Proof is in the multiple points of truth and this is one area where the EM150 is lacking in my opinion. It REALLY needs at least one temp sensor on the high side and one on the low side. What is this "hidden menu" you are referring to?
@@de-bodgery youtube keep removing links((( even at own youtube videos. omg....( Will try to just type... Open Votol-EM-V3 software... Than switch to PAGE3..... After that inside EditBox: "error_count:" remove all digits and type twice using keyboard sybmol "~". You will see "hidden menu" - Temperature protection. Or maybe you know how I can share link to youtube video. I captured a video with that process and with WEB page about settings at endless-sphere site.
th-cam.com/video/0usEsRcJOBE/w-d-xo.html
@@viko2812 PM me on facebook...Richard Gumfaw
Nice! Looks like it can handle a lot of amps!👍
A few optimizations and it can probably do close to 300 battery amps. This would make for an interesting add-on video to the 3 I do for the controller. AKA...how to beef up amperage.
@@de-bodgery
If that is the case I wonder what the 300a ver would do if tweaked😍.
@@patrickmckowen2999 Not sure, never seen the 300 version! I'd like to see one of the /2 and find out what is different between the EM-250 and EM-150/2. No idea what the EM-300. Votol isn't exactly forthcoming with information about their controllers!
So to recap suggested upgrades to the EM-150...fill the gap in the "L" of the thick copper battery+ plate, shorten the leg attachment on the MOSFETs, More high-frequency filter capacitors, add a temp sensor...
yup!
I noticed in a teardown of the EM260 model that 2 phase current sensors are used so they must have implemented a more complete version of FOC on those models
Same basic FOC capability as Far Driver or KO. They all use the same STM32F103 CPU and the same basic FOC libraries. This is a lower power CPU that can't handle the full set of FOC capabilities like VESC or Nukular can on the much more powerful STM32F405 CPU.
Another question my friend, where I could buy original Magnachip mosfets? Thank you!
mouser, digikey, arrow
About firmwares of controllers, including Kelly:
This whole mess started around 2006-2010. At the request of the growing market, many manufacturers have created their own controllers. At that time, there were no FOC libraries/SDKs (which are now offered by microcontroller manufacturers themselves). And each controller manufacturer had to develop its own firmware. Which is what they did. This is not a super difficult task but not a super easy one either. Yes, in recent years, microcontroller manufacturers have realized that they can attract more people if they release ready-made SDKs for implementing FOC. But, controller manufacturers could not use it this way (it simply did not exist in the past). They tested/developed and added new functions to their own firmware. And later, even with the advent of SDK FOC from microcontroller manufacturers, there was no point in switching to them. And therefore, it is logical that controller manufacturers continued to develop their own firmware. They have already been tested and work well.
This is exactly why you see wide spread adoption of the STM32F103 in Far Driver, Votol, Sia, KO and others. They are all using the FOC SDK from STM for this CPU. As a result, you can also see many of the same motor control glitches in all these controllers. About the only people doing their own work is VESC (STM32F405), Nukular (STM32F405), Kelly (MCF51AC128) and ASI (TI F302). I'm sure there are others too. Pretty much everybody else is using the STM F103 and the SDKs for it or they are stealing VESC like Torp does.
Hey there, so I have a Talaria Sting, the original controller broke so I wanted to get a KO but after your videos I'm wondering if this isnt a better option? Not looking for crazy power, just longevity and reliabilaty.
Hi I have a 72850,do you want buy?
Hi! How did you removed the plastic lid? I have a EM100 which is very similar but can't remove the lid after obviously removing the screws. Any help would be helpful!
slipped a knife between the plastic and the aluminum all the way around to make sure it wasn't stuck down with silicon anywhere and then it pried up easily. There was a controller that had a weird set of studs on it. I'd watch all my tear down videos on the EM-150 to make sure it's not that one.
@@de-bodgery Thank you!
@@de-bodgery For some reason, I can't get the plastic off. Already did what you said but it is still attached. My guess is that it is glued, so I'll try to use a little bit of acetone.
Small world: i just have a Votol EM-150/2 on the bench. Low- and highside Fets blown on th U-phase. Five Fets desintegrated, nearly zero ohm between all three legs. I wonder why the 6 big caps are only rated 63V and the Fets are 100V types (MDP10N027). But it has gatedriver ic (IRS2127)
Are you in the USA? Care to send your controller to me for a tear down video? I may even repair it!
you probably have blown drivers too if all 3 phases are torched.
Those 63v caps sound like a mistake! I'd replace them with 100v. The EM-150/2 is rated for 100v max so those 63v caps must be a mistake!
@@de-bodgery No, sorry, i am from germany and the controller isn`t mine (yet).
@@de-bodgery I think you are right: zero ohm between gate and source and fourty ohms between phase and battery plus. I hope I can fix it. Right now I only opened the controller to look what caused the fourty ohms.
hi, in case a unit brings always overcurrent and phase current at 0 no matter how many times I write parameter with different values, means the unit is bricked?? can you tell me in case of em50 if an sdm resistor may be the culprit for this issue? or a cap or bad component to check?
I don't know the EM-50 at all. If it is constructed like the EM-150, then I can give you advice based on the EM-150. The EM-150 has shunts for battery current, but not for phases. If I was seeing your error on an EM-150, I'd check the circuitry around the shunts and up to the CPU.
Sir... How it's not FOC controller?!?! The current on phases can be measured by the voltage drop across the mosfets themselves. This seems to be exactly what it does in Kelly KLS Chetah series and many other models of Kelly Controllers.
No direct phase current sensing is usually a good sign that something isn't FOC. Battery shunts only is usually a good sign of NOT being FOC. However, in the case of this CPU, there are libraries that are used by Fardriver/KO and others that all use this same CPU. It's jsut a matter of when you make your firmware what parts of it you implement or don't implement. So there is pretty good chance that Votol is using some form of basic FOC control. BTW, using mosfets to sense phase current is seriously unreliable. As the mosfets warm up, their resistance changes. If you want to consistently measure phase amps, you need a reliable resistance to do that with! You can go look at data sheets for many mosfets and see Rds graphs vs temperature. This is a VERY unreliable way to measure a voltage drop and use that to calculate phase amps!
@@de-bodgery First of all thank you for answer sir. I would not recommend you to say "FOC libraries". That sounds I don’t know - a little weird. It is more appropriate to say "FOC implementation" instead. Programmers who create firmware with FOC implementation for the controller do not take any libraries(in most cases), but instead create everything from scratch. It's just fun for programmers to stretch their "muscles", it's an interesting task in general. This is the case when the program code is directly connected to the real physical world and affects it (I mean through the motor). That is, it's like creating a robot/Frankenstein. Yes, I guessed that using mosfets to measure current might not be accurate enough. Thanks to the information from you, I now understand what some of the compensation tables I see in the firmware mean. Kelly controllers have a fairly decent number of temperature sensors. And most likely these sensors plus compensation tables are used to compensate for temperature changes in mosfets parameters. Despite the fact that measuring phase currents on mosfets is theoretically unreliable, in practice Kelly controllers work great. If, of course, they are configured correctly and the controller and the specific motor are balanced. Then Kelly begins to work magically and cosmically softly. What is interesting is that it is impossible to completely balance Kelly and a specific motor using the Kelly program for configuration. There is some kind of chaos going on in the company in terms of software. But it doesn't matter, I'm almost finished with my project, which solves all many of these problems, saving owners of Kelly controllers from a lot of headaches.
@@KellyControllers I'm sure Kelly probably created their own firmware. I've used several Kelly controllers and the layout of the software and general controller functionality set leads me to believe that Kelly probably did their own firmware. Also, only other place I've seen the CPU kelly uses is in a Sabvoton. I've taken apart a ton of controllers and not seen it elsewhere. There's a good chance that Kelly developed their own libraries for the different controller types they sell.They have a large enough staff and been around a long time that they probably have on staff programmers. They probably have compensation tables to account for mosfet temperature. I'd just use phase shunts and not have to deal with any of that! Before I commented on temp sensors, I went and looked at my own pics of the 4 different Kelly controllers I've taken apart. I find a single temp sensor on the center phase on the high side mosfets only. That's hardly anything! It's at best an average of the total heat of all 3 phases.
***
ASI, Sevcon and maybe one or 2 other companies that have been around a long time have done their own firmware from scratch for smaller controllers. Probably many big cost inverter makers have done their own work. There's a lot of money in that type of thing that doesn't exist in controllers you'd put on a Surron or e-bike! I know elevator, commuter bus and electric locomotive inverter companies that use VESC because this is such a huge challenge! The numbers of truly independent companies doing controller firmware development all on their own are quite few!
***
BTW...as someone that actually works in software development, they are called "libraries". What you do with those libraries to make a functioning controller is your "FOC implementation" In the case of Votol, Far Driver, Ko Moto and others that are all based on the STM32F103 CPU, they are using the same FOC libraries on all of their products. This greatly reduces the amount of development they have to do! Tweak some stuff for how you measure current and timing and it probably runs. You can see the exact same firmware glitches in Far Driver, KO and Votol thanks to the exact same FOC libraries!!! Some time back, I asked several VESC developers about independent firmware development. I do mingle with the VESC development people pretty often! Talking to the likes of Benjamin and Frank, the founders of VESC, they tell me a very different story about developing firmware from scratch. Sure it can be done as that is exactly what they did for VESC. I know one other guy that does VESC development that has created his own FOC firmware tat runs on the STM32F405. He's quite active in VESC development too. He's the only other person I know of that has done this! Everyone else, they steal VESC like TORP or Electro and Company tried to do! All the others using the STM32F103 CPU, they steal or borrow from each other or use the ready made FOC libraries that exist for this CPU. I bet there is a handful of Chinese programmers that actually modify all the firmware for all the Chinese controllers that use the STM32F103! Copying in China is RIFE! Far Driver has done a lot of work with those FOC libraries and KO moto denies it, but they are using FD firmware almost as is! I don't know if that's true for Votol, but minor changes to those libraries is easy compared to "stretching your muscles" and starting from scratch! I imagine others like SIA and a dozen other China brands with basic FOC capability are mostly copies of each other and all based on those exact same STM32F103 libraries! Every VESC developer I know of says this is a monumental task to take on from scratch. China where there is no intellectual property laws and copying is so rife, most of those companies would rather copy/steal instead of try to tackle this from scratch!
***
It would be amusing to buy one controller from every China brand that claims FOC. I'm betting 100% of them use the STM32F103. I'm also betting the same glitches that are common to FD and KO and Votol also exist in all those other brands! AKA...it's all the same firmware!
They have current sensors on two phases for the EM260.
Should take a look on the new version the sp2
If one comes my way, I'll do a tear down! I'd like that! Probably pretty good, like the EM-150.
Does the use of discrete components instead of the gate-driver IC option mean that these are also more "repairable"?
Not really. If you blow mosfets, a gate driver may also blow. An IC with a part number on it is usually easy to find replacements. A tiny transistor or diode or whatever might not be something you can find the part. I often times can't find replacement discrete components by their 2 or 3 letter part code.
@@de-bodgery Thanks. This is the type of thing I like about your channel. Its easy to say one device is crap and the other one is awesome, but without the details as to why, someone who is not into electronics can't make an wise decision.
@@ronroberts110 Thanks Ron...glad I could empower you!
For what it is worth, the Votol EM-100 is identical with the exception of 3 MOSFets per group instead of 4 for this controller. Even though the EM-100 is only a little bit less in current, it is well lower than half the price of the EM-150.
They probably have to do that to get it to sell
@@de-bodgery
Probably, better to get just get rid of the100 and lower price of the 150 by 20%, you will save far more on that back end than you will lose on the 20% off the150.
Cheers
@@patrickmckowen2999 It's thier business model, not sure why they did what they did.
Hi I have a question about a daymak em2 controller was wondering if I can run 96v batteries full charge is 108v
Model: Daymak - DMK1892
Voltage: 48V-72V (72V)
Current: 25A-50A (38A)
Power: 500W-1000W
Low Voltage Cutoff: 40V(63V) BLDC Controller (Bluetooth)
Code: A180189203
7353-XF
D DAYMAK DRIVE
TURBO
What's the manual say?
No
More than likely over voltage will occur at 88v in my experience with basic controllers. Fardriver 72v models are capable of 106.1v over but u should order a 96/108v controller that makes full use of 26S cell config. Cylindrical cells drop V a lot during max draw so starting with >106.5 helps A LOT. Pouch cells drop much less but don't take abuse as well.
87.9v /26 is comically low. 3.3v per cell? Ur only drawing 50 A so maybe but it's a temp solution to be avoided.
I think that the reason others do not use glass reinforced poliwster is that id is much harder to recycle
Not the reason. Recycling comes after economics and always has. It's slightly abrasive and wears out injection molds faster. It's more expensive material. It's harder to mold. The cost of using glass reinforced materials is significantly higher than using cheap ABS. This is why it isn't used. Most manufacturers don't care about recycling. This is forced on them and not something that most companies do voluntarily since it isn't economically beneficial to them to recycle.
Do you know anyone who does repairs?
Repairs of what?
besaue of this videoo I chose to purchase the Votol over a Fardriver. I would love to have 29.6% of your knowledge on electronics. I am new and self taught, sometimes sparks fly:)))))
I blow up hardware too! In order to succeed, you will have failures!
@@de-bodgery can you recommend a good reliable display to go with the Votol EM150S? I have been searching but the info is very dry. thanks
@@giorgikhodeli3633 I don''t know, but I have asked a freind that is way more knowledgeable about all things Votol than I am about this.
@@giorgikhodeli3633 Look in my comments for the video. I added a URL to a display for them.
Sir. I will answer you here, with separate comments. This will help to promote your youtube channel. If you agree, up to you.
Ping me on Facebook...Richard Gumfaw.