Forum Replies Created
I know it’s not the same as a merge, but the last release (candidate) of iNav adds support of the RCEXPLORERF3 target.
Yepp, it should have arrived by now. I’m sure David will report back as soon as he has had a chance to look into it.
My experience is exactly like @mcstan‘s. I’ve tested Beta 3 (which come with the boards), Alpha 2 and finally the 0.5 release. I’m not entirely sure all releases behaved the same way as I wasn’t aware that the problem was related to UART2 until august 1 (http://rcexplorer.se/forums/topic/f3fc-reports-extreme-current-draw/#post-31824), at which point I was using the final 0.5 release.
@david, if it’s of any help I can send you the micro minimOSD I’m using. It seems as many people experiencing this type of problems are using that model.
Since I’m in Sweden you could have it by tomorrow or at latest by Thursday. Let me know!
I did some furter testing and it seems that the problem only occurs when connecting the OSD to UART2:
OSD on UART3 – powered from UART3: 2A
OSD on UART3 – powered from separte UBEC: <1A
OSD on UART2 – powered from UART2: 7.8A
OSD on UART2 – powered from separate UBEC: 8.5A with beeper sounding while only USB connected
OSD on UART1 – powered from UART1: 1.5A
OSD on UART1 – powered from separete UBEC: <1A
Connecting other things such as GPS to UART2 does not produce the same result, even with OSD connected to UART3.
Reading the other thread I noticed that the OP is also using UART2 for OSD.
I’m using this (cheap) OSD: http://www.banggood.com/MICRO-MinimOSD-Minim-OSD-Mini-OSD-W-KV-Team-MOD-For-Naze32-Flight-Controller-p-990556.html
Drame, what type of OSD are you using, and which UART is it connected to?
Have a look at this thread: http://rcexplorer.se/forums/topic/f3fc-reports-extreme-current-draw/
I send David a mail regardig this problem. Because this was the same day that he left for FliteFest, followed by a trip to Pripyat, I only received a breif answer asking me to have a look at the components surrounding the current sensor on the board, checking if any of them might not be properly grounded.
Since I’m far from qualified dealing with that kind of troubleshooting, and wanting to get the copter flying while on vacation, I decided on ordering another board. The new board was delivered just two days later, but unfortunately it exhibits the exact same behavior.
Before reading about you discovering that the faulty current measurements shows up from merely connecting the RX/TX my plan was to put all UART peripherals on a separate UBEC. I guess you saved me an hour or two. Thanks! 🙂
I have submitted a ticket referring to this thread. The ticket number is 129.
I just did some more testing and it’s clear that current drawn from the UART’s power connections gets multiplied by a factor of 16 or something like that. I’m pretty sure the GPS does not draw 6 amps. And if it would, the BEC providing power to the UART power connections would not take it for even a second.
Edit: The VTX is connected directly to the motor soldering pads on the board, it’s not fed from the raw output.
I’m going to ask David to take a look at this, it must be a hardware problem with the F3FC board.
@maz, I have tried everything I can think of in terms of fiddling with scaling and offset, including setting it to David’s default values. I was hoping for some kind of “coarse” or “basic” tuning that could be done though CLI in order to bring the values into proximity of the actual current draw.
According to the product description you have to use the injection molded front spacer. I’m actually not sure whether the one I’ve already got fits or not, but since I’m not keen on tearing my copter apart just to find out, I ordered a new one just to be sure.19 June, 2015 at 21:42 in reply to: Where in the world is your RCExplorer Copter? Link to map #16261
Ekerö, Stockholm, Sweden