izeman
1 GW
Great. So the quote on PSWPOWER page is only related to original firmware limitation and NOT hardware (like CAPs or FETs inside the controller)?casainho said:There is an user testing 15S. So far it seems to work ok.
Great. So the quote on PSWPOWER page is only related to original firmware limitation and NOT hardware (like CAPs or FETs inside the controller)?casainho said:There is an user testing 15S. So far it seems to work ok.
I highly doubt you have much headroom with some 63V Capacitors and a 15x4.2v fully charged battery.Great. So the quote on PSWPOWER page is only related to original firmware limitation and NOT hardware (like CAPs or FETs inside the controller)?
Do we know it's 63V CAPs? I assume so, but haven't opened the controller yet. More clever guys here have already done that i guess. With 63V CAPs i wouldn't go for 15S. But my planned 14S should be save.Speady said:I highly doubt you have much headroom with some 63V Capacitors and a 15x4.2v fully charged battery.Great. So the quote on PSWPOWER page is only related to original firmware limitation and NOT hardware (like CAPs or FETs inside the controller)?
Let's do the maths...mmmmmh![]()
I doDo we know it's 63V CAPs?
eyebyesickle said:
famichiki said:If anyone here is running the VLCD5 with factory firmware, would you please be able to go into the torque signal service menu and tell me what readings you get? I have a range of 98 - 190.
Both the initial zero torque reading & the maximum reading you can achieve with your body weight etc.
I have posted details how to check this on the VLCD5 firmware thread here..
https://endless-sphere.com/forums/viewtopic.php?f=30&t=98281&p=1518298#p1518298
izeman said:Do we know it's 63V CAPs? I assume so, but haven't opened the controller yet. More clever guys here have already done that i guess. With 63V CAPs i wouldn't go for 15S. But my planned 14S should be save.Speady said:I highly doubt you have much headroom with some 63V Capacitors and a 15x4.2v fully charged battery.Great. So the quote on PSWPOWER page is only related to original firmware limitation and NOT hardware (like CAPs or FETs inside the controller)?
Let's do the maths...mmmmmh![]()
Motor shaft failure is often caused by bad alignment.casainho said:Another problem I got today while riding as usual, small trip of 5 kms around home. Suddenly, I could hear the motor working and see on display the motor ERPS speed at max values of 525 although no help assisting to pull the bicycle...
The motor shaft broke!!! Does anyone knows why did this happen?? -- then I exchanged for a new motor and seems to work fine again on a short ride but tomorrow I will do a long trip during the full day with my wife... I hope the motor shaft will not brake again.......
![]()
I thought FOC needed purpose-built hardware from the get-go, not least a powerful CPU to crunch the calculationsizeman said:Another question: Does the firmware add FOC features? That would eliminate the need of higher voltage for higher rpm.
FAQ says nothing about that.
casainho mentioned it in one the TSDZ2 threads. But no more details. I'm still going through the many hundred pages of several threads to become up to date 8)john61ct said:I thought FOC needed purpose-built hardware from the get-go, not least a powerful CPU to crunch the calculations
Yes, our OpenSource firmware implements "simplified" FOC while original does not, that is why users report motor being more powerful and use less battery.izeman said:casainho mentioned it in one the TSDZ2 threads. But no more details. I'm still going through the many hundred pages of several threads to become up to date 8)john61ct said:I thought FOC needed purpose-built hardware from the get-go, not least a powerful CPU to crunch the calculations
Ok. Thanks for explanation. Can you do advanced timing? So the motor can turn faster than it normally would do? Like eg. Lebowski's and Nucular's controller can do it? I know it doesn't make too much sense, as the front chain ring in relation to the smallest rear one determines max speed. And if you hit the max cadence you can pedal the bike won't run faster as the torque sensor won't sense any force anymore. Correct?casainho said:Yes, our OpenSource firmware implements "simplified" FOC while original does not, that is why users report motor being more powerful and use less battery.
That's not my focus to increase max possible cadence that is currently around 92 RPM.izeman said:Ok. Thanks for explanation. Can you do advanced timing? So the motor can turn faster than it normally would do? Like eg. Lebowski's and Nucular's controller can do it? I know it doesn't make too much sense, as the front chain ring in relation to the smallest rear one determines max speed. And if you hit the max cadence you can pedal the bike won't run faster as the torque sensor won't sense any force anymore. Correct?casainho said:Yes, our OpenSource firmware implements "simplified" FOC while original does not, that is why users report motor being more powerful and use less battery.
yes, I broke an engine in a similar way :-( Simply, in one of my 2 tsdz2 the engine did not want to disassemble and I beat it lightly with a hammer. I didn't notice anything but once reassembled, after 1km the engine broke exactly as in your photo.casainho said:Another problem I got today while riding as usual, small trip of 5 kms around home. Suddenly, I could hear the motor working and see on display the motor ERPS speed at max values of 525 although no help assisting to pull the bicycle...
The motor shaft broke!!! Does anyone knows why did this happen?? -- then I exchanged for a new motor and seems to work fine again on a short ride but tomorrow I will do a long trip during the full day with my wife... I hope the motor shaft will not brake again.......
![]()
AZUR said:I already use my 15S1P 21700 LG 5000mAh for more than 100km, 60% mountain.
Go and learn to do the basic math for calculate the cells / package wattage:frenchie said:That's sounds amazing for a 15 cell battery!!! So how many watts is that? How much do you and the bike weigh?AZUR said:I already use my 15S1P 21700 LG 5000mAh for more than 100km, 60% mountain.
andrea_104kg said:yes, I broke an engine in a similar way :-( Simply, in one of my 2 tsdz2 the engine did not want to disassemble and I beat it lightly with a hammer. I didn't notice anything but once reassembled, after 1km the engine broke exactly as in your photo.casainho said:Another problem I got today while riding as usual, small trip of 5 kms around home. Suddenly, I could hear the motor working and see on display the motor ERPS speed at max values of 525 although no help assisting to pull the bicycle...
The motor shaft broke!!! Does anyone knows why did this happen?? -- then I exchanged for a new motor and seems to work fine again on a short ride but tomorrow I will do a long trip during the full day with my wife... I hope the motor shaft will not brake again.......
![]()
I think it is a fragile alloy that does not allow the slightest decline.
knutselmaaster said:Motor shaft failure is often caused by bad alignment.casainho said:Another problem I got today while riding as usual, small trip of 5 kms around home. Suddenly, I could hear the motor working and see on display the motor ERPS speed at max values of 525 although no help assisting to pull the bicycle...
The motor shaft broke!!! Does anyone knows why did this happen?? -- then I exchanged for a new motor and seems to work fine again on a short ride but tomorrow I will do a long trip during the full day with my wife... I hope the motor shaft will not brake again.......
![]()
If a bearing is not well placed or at a slight angle, or if the axle isn't perfectly straight, this gives a small fluctuation in tangential force causing fatigue in the metal that leads to breakage of the weakest point.
This can be caused by a badly made motor part but also by bad mounting.
If the motor cover (with the bearing in it) isn't 100% "flat mounted", in exactly 90° angle with the axle, or when the center of the bearing isn't perfectly in the center of the axle for example.
Generally it is noticeable if something like this is happening, the motor vibrates more than it should with the exact frequency of the axle.
izeman said:Hmmm... The more I read the more concerned I become. Now that I have the motor delivered I see what a tiny little motor that really is. Not only compared to one of my DD Crystalyte motor, but also compared to a MAC hubmotor or even a Bafang BBS.
I also now see why this is REALLY only a 500W motor, and nothing more. 750W max for burst. Ok.
But not like the BBSHD that claims 750W and can be run at double the Watts. Or my MAC converted to mid drive that runs 3000W happily (with a modified cooling system of course).
So this motor is really a pedelec motor, something that helps you through head winds and light hills (not mountains). It seems it's not up to mountain biking of any kind. I see broken axles, broken cases, broken gears and burnt windings - even when run under rated conditions.
I bought this because I like tinkering and I LOVE what casinho and others did to the firmware. Looks amazing. And I recommended that motor over a BBSHD to a friend as I thought it's more advanced (which it is because of the torque sensor and advanced software) - I just hope it's up to his expectations and doesn't break after the first ride, and I hope my friend won't be disappointed.
All my fault of course, I should have gone through the several thousand posts and read BEFORE I buy/recommend. Let's keep the fingers crossed and hope that it will all be fine next year - tomorrow! 8) :lol: