What happened? I have ordered this ESC because I have only the best experience with Kontronik-s products. It was a good idea having such a great ESC like Kosmik for my Logo 600SX and be prepared for potential bigger helicopter in the future. I have decided to it together with my best setup. Anderson BLS servos with hall sensors, Futaba BLS256HV tail servo, Hacker Turnado motor and FBL system Spirit. I was flying with this helicopter literally hundred of flights only the ESC was Kontronik JIVE 80+ HV. I must say I have played with this helicopter a little so there was fully carbon frame from Mikado and few others bling stuff.
Well first problems started on the bench. I have set the switch on my radio for Auto Rotation bail out according to manual. I have also set the mode 1 than mode 4, BEC to 8.0V by ProgDisk, motor Ri and capacity limit. Nothing else was set.
I wanted to try the bail out on the bench for sure. So I have spooled up the helicopter without main blades and hit the AR Bail out. Motor turned off as it supposed to do. But I disable the AR switch and the helicopter should normally spool up back again very fast. Well, this didn-t happen. Instead of that there was a total ESC restart! I was able to reproduce it so I have decided to upgrade my ProgDisk to the latest version and the Kosmik as well. Nothing has changed and this issue was still there.
I don-t need this AR Bail out mode so I have decided to fly it. Everything else was working like it should. It wasn-t the best idea because the Kosmik reset happened again while I was just hovering close to the ground. Total Kosmik-s restart was followed by BEC off and Motor off. I was just hovering se there was almost zero current draw on motor and BEC as well. I have logs from every single case and from that flight too. There-s nothing unusual to see in those logs. Only the error logfile is full of this error code: selftest error #32 error FET off
I have found this error code in the manual and there-s written to send in this ESC to service. OK. It-s not a problem and I might have some malfunction Kosmik. It can happen.
My LHS was that kind to send me a very new Kosmik 160+ HV as exchange while this one is going to service. I must say it was very kind of him.
I did a long tests with this very new Kosmik on bench like with the previous one. Autorotation bailout was working fine.
Maiden was awesome and there were zero issues. Even the capacity limit worked like expected. Nothing strange in the logs so far just the information there-s capacity limit.
I just did some changes in FBL system and went flying again. Some tictoc and other things but three and half minutes later â?¦.once of a sudden Kosmik restarted itself. You can imagine what followed. Motor OFF and BEC OFF = total super crash. There was again this exactly the error code in error logflie: selftest error #32 error FET off.
There-s the logfile from that flight which is suddenly cut when the Kosmik restarted and the new logfile was created few seconds later. It-s strange isn-t it.
This time it was total damage worth around USD 1500$! I have a video from that flight/crash.
I have decided to send this Kosmik back to Kontronik but this time I want my helicopter back if they won-t be able to explain to me I did something wrong. For sure I can make mistakes like anybody else and I can also take responsibility for my stupidity. I have no idea what I can do wrong here. This helicopter with this setup was flying with JIVE 80+ HV and those logs tells me there-s something wrong in the Kosmik.
My vendor had a long conversation with Kontronik and even with Kontronik-s CEO Mrs. Sabine Konrath. They say there-s nothing in the video which says it-s the Kosmik-s failure. It looks like motor turned off but it might have been some signal from receiver what turned this motor off.
Kontronik-s statement about these strange error logs is very simple. Those error codes are there to protect and can happen only while booting up. It can-t happen in flight. It-s good to send the Kosmik in to check if there-s something wrong with the hardware. The hardware in both cases are 100% functional and there-s nothing wrong with both Kosmiks.
Regarding the restart while flying or operating they say the only explanation should be the power supply was interrupted. It-s impossible as these packs were working and is still working on another Logo 600 I have. All soldering is and was in a very good shape so if the power supply was interrupted it must have been in the ESC from my point of view.
I don-t like when someone wants to me a fool out of me and this is my current feeling.
I write this whole story to let you know how good customer care you can get from such a high-class company such as Kontronik. I-m thinking to give this to my lawyer and talk to Kontronik company only this way.
Here-s the log from that last flight. Look like it has been cut once of a sudden.
Both ESC has been send back from Kontronik with statement there nothing wrong with them and both are 100% functional. They are not 100% OK from my point of view and for sure I will not give it back to any of my helicopters ever! So the experience is $1500 and one Kosmik 160+ HV I can give only to some boat but not a helicopter anymore.
Well first problems started on the bench. I have set the switch on my radio for Auto Rotation bail out according to manual. I have also set the mode 1 than mode 4, BEC to 8.0V by ProgDisk, motor Ri and capacity limit. Nothing else was set.
I wanted to try the bail out on the bench for sure. So I have spooled up the helicopter without main blades and hit the AR Bail out. Motor turned off as it supposed to do. But I disable the AR switch and the helicopter should normally spool up back again very fast. Well, this didn-t happen. Instead of that there was a total ESC restart! I was able to reproduce it so I have decided to upgrade my ProgDisk to the latest version and the Kosmik as well. Nothing has changed and this issue was still there.
I don-t need this AR Bail out mode so I have decided to fly it. Everything else was working like it should. It wasn-t the best idea because the Kosmik reset happened again while I was just hovering close to the ground. Total Kosmik-s restart was followed by BEC off and Motor off. I was just hovering se there was almost zero current draw on motor and BEC as well. I have logs from every single case and from that flight too. There-s nothing unusual to see in those logs. Only the error logfile is full of this error code: selftest error #32 error FET off
I have found this error code in the manual and there-s written to send in this ESC to service. OK. It-s not a problem and I might have some malfunction Kosmik. It can happen.
My LHS was that kind to send me a very new Kosmik 160+ HV as exchange while this one is going to service. I must say it was very kind of him.
I did a long tests with this very new Kosmik on bench like with the previous one. Autorotation bailout was working fine.
Maiden was awesome and there were zero issues. Even the capacity limit worked like expected. Nothing strange in the logs so far just the information there-s capacity limit.
I just did some changes in FBL system and went flying again. Some tictoc and other things but three and half minutes later â?¦.once of a sudden Kosmik restarted itself. You can imagine what followed. Motor OFF and BEC OFF = total super crash. There was again this exactly the error code in error logflie: selftest error #32 error FET off.
There-s the logfile from that flight which is suddenly cut when the Kosmik restarted and the new logfile was created few seconds later. It-s strange isn-t it.
This time it was total damage worth around USD 1500$! I have a video from that flight/crash.
I have decided to send this Kosmik back to Kontronik but this time I want my helicopter back if they won-t be able to explain to me I did something wrong. For sure I can make mistakes like anybody else and I can also take responsibility for my stupidity. I have no idea what I can do wrong here. This helicopter with this setup was flying with JIVE 80+ HV and those logs tells me there-s something wrong in the Kosmik.
My vendor had a long conversation with Kontronik and even with Kontronik-s CEO Mrs. Sabine Konrath. They say there-s nothing in the video which says it-s the Kosmik-s failure. It looks like motor turned off but it might have been some signal from receiver what turned this motor off.
Kontronik-s statement about these strange error logs is very simple. Those error codes are there to protect and can happen only while booting up. It can-t happen in flight. It-s good to send the Kosmik in to check if there-s something wrong with the hardware. The hardware in both cases are 100% functional and there-s nothing wrong with both Kosmiks.
Regarding the restart while flying or operating they say the only explanation should be the power supply was interrupted. It-s impossible as these packs were working and is still working on another Logo 600 I have. All soldering is and was in a very good shape so if the power supply was interrupted it must have been in the ESC from my point of view.
I don-t like when someone wants to me a fool out of me and this is my current feeling.
I write this whole story to let you know how good customer care you can get from such a high-class company such as Kontronik. I-m thinking to give this to my lawyer and talk to Kontronik company only this way.
Here-s the log from that last flight. Look like it has been cut once of a sudden.
Both ESC has been send back from Kontronik with statement there nothing wrong with them and both are 100% functional. They are not 100% OK from my point of view and for sure I will not give it back to any of my helicopters ever! So the experience is $1500 and one Kosmik 160+ HV I can give only to some boat but not a helicopter anymore.
Kommentar