what transmitter and receiver were you using? also what was happening when you lost signal?New nose, patch on rear of wing, patch on front of fuselage, one new nacelle, other nacelle glued… that’s all I can remember. Ready to re-maiden!
Oh, and I have to try to figure out why I lost my signal. I guess that’s the hardest part.
So, the only difference with an x-mount motor is the little x-shaped bracket that is wider than the motor itself.
View attachment 232766 View attachment 232767
The bracket screws to the back of the motor and then you screw the bracket onto the firewall. Without the x-mount you need access to the back of the firewall to screw through the firewall directly into the motor. That's all; neither style is inherently better or worse.
I see no reason not to go with the motor 3D lab print suggests, so long as it meets the criteria for your setup. (voltage, amperage, thrust, prop size, etc). I don't remember what plane you said this is for, was it the Storch?
@Inq - that looks like a great plane and the perfect motor for it. Can't wait to see it printed.
what transmitter and receiver were you using? also what was happening when you lost signal?
I usually have mine secured on either side of the reciever at a 180 degree angle to each other. Hope this helps!
If you are running more than 4 servos, put both esc wires in. THe fsia6b can handle it, and it might have caused the bec to cut out if it draws too much current. Also, if htere is a house even close, using 2.4ghz wifi it messes with the flysky systems a lot. Also, try putting your antennas 90 degrees to each other.My transmitter is a FlySky i6x. The receiver is a FlySky ia6b. I’ve never really thought about range before. I’ve only had the signal alarm beep at me a couple times in the past and I’ve flown way out so that I could barely see the plane. In this case I had just taken off and was about 50 feet up. My transmitter started beeping at me (low signal alarm) so I started turning around to come back, but part way into my turn I lost all connection. I didn’t have any failsafes turned on, so it stayed in the turn with the motors on and descended to the left and crashed. I <think> that’s what happened.
I was running two 2.2ah 3 cell batteries in parallel. Both fully charged but different brands. My motors and power packs are the Flite Test radial C packs with 40a ESCs. The positive wire on one of the ESCs is disconnected per the FT video. I’m using four nine gram servos and a fifth for the door.
We’ve had signal issues out past the left side of our runway before. The closest houses are about 1000 feet away on that side and they are much further away in every other direction. I suspect that maybe somebody has a really powerful router maybe. However, when I lost signal yesterday, it was closer than where we’ve seen issues before.
I definitely wasn’t thinking about my antennae orientation and was probable pointing it directly at the plane. I’ve always done that and never had a problem before, but maybe that was a contributing factor. I’ll try to keep my radio up next time.
I also wonder if my receiver antennae was part of the problem. Here’s a photo of how it’s arranged in the plane. This is on the drivers side of the plane. After reading up on them, I think maybe putting them both on the floor of the plane at 90 degree angles to each other might be more effective. Also, I read that I need to separate them more.
What do you think? Are any of my theories on the right track? Thanks!
If you are running more than 4 servos, put both esc wires in. THe fsia6b can handle it, and it might have caused the bec to cut out if it draws too much current. Also, if htere is a house even close, using 2.4ghz wifi it messes with the flysky systems a lot. Also, try putting your antennas 90 degrees to each other.
Motor Mount: There's no reason to use the X-mount if you're happy with the way you've been doing things. The big motor will have holes in the back for mounting screws just like the 2212s do. The hole spacing may be different, but it works the same.
I like using x-mounts because I don't always have good access to the back of the firewall in my builds and because it gives a little larger footprint for the mounting screws.
Happy to input! It's something to experiment with at the very least.I should look into incorporating the aluminum X-mount also. I noted in my motor thrust testing the plastic compressed behind the motor and caused the bolts to be a little looser than when I tightened them. I'd hope beside making it mounted from the front, that it might dissipate some heat before reaching the plastic.
Thanks for your input.
Another reason to use the X mount is that it is (typically) easier to put washers behind the top screws in order to achieve the optimum thrust angle for the plane. Typically a warbird needs down/right thrust which is achieved by putting washers between the X mount and the firewall. For example, one on the upper right and two on the upper left. Your printed plane might have that designed into the printed firewall. And some flight test planes have that built in the swappable mount. I don't use the swappable mount so I like the X mount to play with the thrust line. Especially on the swapable Spitfire. The Spitfire is a great first warbird BTW.
I've had huge luck with FlySky and rarely dropped a signal.
Yes. And the subsequent flight without changing anything was great!Umm you do test controls just before you toss it?