Why no soft cut? Come on Kontronik.........

[Pitch-Itch]

Originally Posted by Wh1teAfr1can

read what i said. I said there is no way for it to reduce power aka do a soft shut down on over amp, BUT when it detects too much temperature it can do a slow down and reduce power til the temp begins to reduce.not sure what you are trying to get at here.

I'm just trying to get a clear answer, no offense meant. I always knew that the esc would slow down for over temp. That was never my question so I'm not sure why we are talking about it.

So just to be clear, there is no slow down for over amp. The reason I was confused is because some say there is a soft cut for over current, and some say there is not.

Obviously, there is much confusion over this as evident by the contradictory posts in this thread.



I'm glad to finally know that there is absolutely no option for soft cut.

My next question is, who do we petition to get an option for soft cut added? I see absolutely no logical reason to refuse the option of having a soft cut.

[Vinger]

There is a distinct relationship between current and heat in the FETs. In all my experience with spool downs it always showed warnings of current limit reached and then warnings of over temperature, WHICH then spools down the ESC in 30 seconds. Check the error in log 32.

Error log attached, I just changed it to a text file to enable upload here.

[Pitch-Itch]

Originally Posted by Vinger

There is a distinct relationship between current and heat in the FETs. In all my experience with spool downs it always showed warnings of current limit reached and then warnings of over temperature, WHICH then spools down the ESC in 30 seconds. Check the error in log 32.

Error log attached, I just changed it to a text file to enable upload here.

Not in my case. I'd have peak Imot values of 380a and my FET temp would never exceed 75c.


Got to know that if the kosmik sees too much current you get to crash your heli.

[Pitch-Itch]

Originally Posted by Pitch-Itch

I'm just trying to get a clear answer, no offense meant. I always knew that the esc would slow down for over temp. That was never my question so I'm not sure why we are talking about it.

So just to be clear, there is no slow down for over amp. The reason I was confused is because some say there is a soft cut for over current, and some say there is not.

Obviously, there is much confusion over this as evident by the contradictory posts in this thread.



I'm glad to finally know that there is absolutely no option for soft cut.

My next question is, who do we petition to get an option for soft cut added? I see absolutely no logical reason to refuse the option of having a soft cut.

So there's no one to petition to get a soft cut feature added? I have to believe that kontronik actually listens to their customers, right?

I know of 4 people who would second my request in minutes, and that's just the people I know personally.

[Wh1teAfr1can]

Originally Posted by Pitch-Itch

So there's no one to petition to get a soft cut feature added? I have to believe that kontronik actually listens to their customers, right?

I know of 4 people who would second my request in minutes, and that's just the people I know personally.

I am currently investigating it with the lead engineer in Germany. It is not an easy problem to solve hence why no other esc has it.

[jrwalte]

Originally Posted by Wh1teAfr1can

It is not an easy problem to solve hence why no other esc has it.

No other esc has what exactly? The user option of soft or hard cut on over amperage?

[Pitch-Itch]

Originally Posted by Wh1teAfr1can

I am currently investigating it with the lead engineer in Germany. It is not an easy problem to solve hence why no other esc has it.

How exactly is it not an easy problem to solve? Kontronik already has a logic code written for slow down in regards to temp.

It's a basic logic code. If X happens then initiate Y (obviously this is not actual code, for the programmers here that were going to call me on it). Right now temp is X and slow down is Y.

Change the logic from X being temp to X being a certain threshold of current, then let Y still be slow down.

I really can't imagine how that would be overly difficult, considering they *have* already done it for temp.

[Wh1teAfr1can]

Originally Posted by Pitch-Itch

How exactly is it not an easy problem to solve? Kontronik already has a logic code written for slow down in regards to temp.

It's a basic logic code. If X happens then initiate Y (obviously this is not actual code, for the programmers here that were going to call me on it). Right now temp is X and slow down is Y.

Change the logic from X being temp to X being a certain threshold of current, then let Y still be slow down.

I really can't imagine how that would be overly difficult, considering they *have* already done it for temp.

Its not that simple. Temp is easy because it is not changing nearly as fast so you have time to react and reduce power.

In the case of over amperage it is a split second decision because it can run away very quickly. so developing the logic so that it can effectively do it without people complaining that it is kicking in and reducing power too early is a challenge.

[Wh1teAfr1can]

Originally Posted by jrwalte

No other esc has what exactly? The user option of soft or hard cut on over amperage?

yes

[Pitch-Itch]

Originally Posted by Wh1teAfr1can

Its not that simple. Temp is easy because it is not changing nearly as fast so you have time to react and reduce power.

In the case of over amperage it is a split second decision because it can run away very quickly. so developing the logic so that it can effectively do it without people complaining that it is kicking in and reducing power too early is a challenge.

My point is that the logic is already there, but the result of the if/then is a complete loss of power.


Why not use the same logic for the threshold, yet give the user the option of having a crash vs being able to land?



It seems like a no brainer to me. Use the *exact same* logic codes, but have the option of substituting a slow down in place of hard cut.

If hard cut happens at 280a+ sustained for .5 sec (or whatever the actual threshold is), then use that same threshold but have the option for slow down. It absolutely cannot be as difficult as you are making it seem.



The real question is, why would you NOT want more options?

[Wh1teAfr1can]

Originally Posted by Pitch-Itch

My point is that the logic is already there, but the result of the if/then is a complete loss of power.


Why not use the same logic for the threshold, yet give the user the option of having a crash vs being able to land?



It seems like a no brainer to me. Use the *exact same* logic codes, but have the option of substituting a slow down in place of hard cut.

If hard cut happens at 280a+ sustained for .5 sec (or whatever the actual threshold is), then use that same threshold but have the option for slow down. It absolutely cannot be as difficult as you are making it seem.



The real question is, why would you NOT want more options?

Like i said if it was easy everyone would be doing it... It is not the exact same logic.

We can go round and round about how hard it is so i am going to leave this discussion by saying I am investigating it with the lead engineer and if it is possible we will do what we can to make it a reality.

On a side note I need my progunit back that you promised to ship back 3 weeks ago and haven't responded to any of my PM's about.

[Pitch-Itch]

Originally Posted by Wh1teAfr1can

Like i said if it was easy everyone would be doing it... It is not the exact same logic.

We can go round and round about how hard it is so i am going to leave this discussion by saying I am investigating it with the lead engineer and if it is possible we will do what we can to make it a reality.

On a side note I need my progunit back that you promised to ship back 3 weeks ago and haven't responded to any of my PM's about.

I've been out of town since Thursday of last week. I'll ship it out in the morning. Thanks again for letting me borrow it.


And thank you, thank you, thank you for taking this to the developers. If this became a reality I would basically have nothing that bothered me about the kosmik. It really is my only complaint.

[helicraze]

jive had slow down from over current and hard cut from heavy overcurrent, im sure kosmik is the same.

And yes slow down from overtemp.

I lost a model too from either packs dying mid flight or this hard cut phenomenam

[Wh1teAfr1can]

Originally Posted by helicraze

jive had slow down from over current and hard cut from heavy overcurrent, im sure kosmik is the same.

And yes slow down from overtemp.

I lost a model too from either packs dying mid flight or this hard cut phenomenam

It is not a phenomenon it is simply the same cut off that jive had. At extreme over current the esc will do a hard cutoff to save itself. Can you link logs so we can tell what happened to yours and please open another thread or pm them to me

[GimpyGolden]

As helicraze mentioned Jive did have Soft Cut for Peak Current reached, 2 LED flash error and Over Current Cut off 8 LED error flash.

It's all right there in the 'In Use Error's' section of the Power/Heli/Jive manuals.