Hi Freefly, can you give us some insight on how you handle over-current protection for motors in the MoVI Pro lens controller? Thanks Brian
Brian: While the tech support mages at FF do read the forum, you might want to email them directly with your question. support@freeflysystems.com. Andy Forensic Software & sUAV / Drone Analyst : Photographer : Videographer : Pilot (Portland, Oregon, USA): Trees=2, Ground=1, Props=11. The Ground Is The Limit™ ---------- Forensic Drone Analyst : Forensic sUAV Analyst : Forensic Unmanned Aircraft Analyst : Forensic Drone Expert
Hi Eric. Still not sure what the cause is. I have emailed both Freefly and Redrock. Will keep you updated.
I had an issue with having the maximum torque setting too high on the movi controller. My Heden motors were getting VERY hot. Turned down this setting, and the motors no longer get hot.
Chris, Were you able to determine what burned up your motors? Do you know where you had your maximum torque value set to?
Chris I checked with our support department and we don't see anything logged from you? we've responded to all questions and there's a separate thread here with some of our observations. It looks like current MoVi Pro does not have a way to view or set the torque levels without a tabletop controller, and the default torque value seems to be very high. If you run a motor at 100% long enough it can cause overheating and potential issues. Hoping for an upate from Freefly soon that addresses this.
Hey All, Has there been any update from Freefly about the overheating issues. We are thinking of getting a Torque Motor and pairing it up with a Bush Pilot. Any info would help. Thanks
If you are using Redrock motors, recommending to get the latest beta firmware which addresses an issue with Redrock Torque Motors https://freeflyeng.s3.amazonaws.com/MoviProv1_2/ios.html This firmware will be going into stable release in about a week. TSU v1.3.1 Bugfix: Fixes and improvements to an issue reported by customers using Redrock Torque Motors. Added a time based fault that protects in all motion states. It also modifies the over current limit of the Redrock Torque Motors to be lower than what it was previously set to. Bugfix: FIZ settings wouldn’t save properly in earlier versions of the TSU firmware.
This update does nothing for the Red Rock Calibration FIZ issues. The MoVI Pro firmware problems could have burned up my Red Rock Motor though, and that's why I can't get it to turn anymore.
MoVI Pro is still faulting or not calibrating. Tried different lens motor cables now. Anyone else having this issue?
Freefly plan to do a major update adressing this issue in the next firmware release. Our CDM-100M was not having any issues in case you need a working version right now.
I'm hoping for a couple of technical fixes in the next update. Who did you hear this info from? Deniz? Customer Support?
The motor profile for CDM-100M has not yet been integrated. Updating this motor profile wasn't part of our v1.3 scope. Development of this release has been complete and is about to be released. Our next development cycle (v1.4) will start right after v1.3 is released. We will make sure to have CDM-100M integration is part of the v1.4 scope
I have a torque motor i have only played around with. Guess I should i put it on the shelf until next firmware?
We were contacted by the guys at 1A about the issue they were having with the API, after we completed the development cycle for this release.