Home › Forums › Everything about everything else › Matek 405-STD – For Bi and Tricopters
Tagged: Matek 405 STD telemetry
- This topic has 65 replies, 8 voices, and was last updated 5 years, 9 months ago by Fosch.
-
AuthorPosts
-
16 November, 2018 at 19:40 #60200jihleinParticipant
I’m going to finish the V4 this weekend (add the GPS) and will post more pictures. Then I’m going to start on the mini with the Kakute F4 V2, and when that’s completed pull the F3Fc from the Baby and convert to Kakute F4 V2….. 🙂
And somewhere in there test the “BiFlight” mixer I wrote that schedules mixing as a function of servo position….. 🙂
17 November, 2018 at 00:56 #60204jihleinParticipantHere’s some photos of the completed V4 with GPS. GPS is responding, so is the external mag. Need to calibrate both, and then we’re ready to fly.
As I noted earlier, I used the MatekSTD and associated PDB because I had them on hand. Turns out for the bigger tricopter this isn’t a bad combination, easy and very clean installation.
I should add that with the nav functions enabled, it’s running between 45 and 50 percent cpu load.
Attachments:
17 November, 2018 at 10:37 #60214Kevin_ErikModeratorThis could be a rather powerful setup with this combination of hardware. (looks clean too) I’ve wanted to rebuild mine for 6S-Lipo’s both for the longer flight times and the greater avalible thrust. Mayne this summer…
18 November, 2018 at 12:48 #60222krkljanParticipantNice stack! How you attached it to upper plate?
2 December, 2018 at 13:56 #60364FoschParticipantHi All,
I’m new with dRonin. I built KK2 Tricopters in the past, then several Quads with Betaflight, especially for LOS acro.
Now I’m back to tricopters, and after a post on rcgroups.com, jihlein told me about dRonin 🙂I’ve just received my MATEK F405 STD board. I’ve connected the servo to S5 pad and the servo is working fine with dRonin GCS (at the moment I’ve nothing else connected to the board, it was just a servo test)
I’m building a light carbon frame in parallel with a special design for the yaw tail, I will share it later.
About the tail tune, I have a normal servo (no feedback wire). Compared to the setting video, I believe I will have to “ENABLE Triflight” but to keep “EnableVirtualServo ENABLE” and “Servo Feedback Pin NONE”. Is that correct ?
Then I will have to learn more about Dynamic Yaw…
Please see the attached picture.Thanks
Attachments:
2 December, 2018 at 16:18 #60368jihleinParticipantYes, you have it correct. Two things to note when not using the feedback wire:
1)The on ground portion of the tailtune function will not work, only the airborne tailtune will function.
2)If you have anyway of measuring your servo’s speed, enter that value in the ServoSpeed field. I used to take a video of the full speed servo slew and count the frames before I installed feedback enabled servos. You could also enter the manufacturer’s spec, but I’ve found them to be grossly inaccurate.If your confident with your soldering ability, it’s not hard to install the feedback wire.
And last a note about the Matek405 target. If you want, you can use S1 for the tail servo signal, it will work just fine, as S1 is on a separate timer bank from S2/S3/S4, which will be used for the ESC signals. It sometimes can lead to a neater wiring job, and it’s easier than soldering to that tiny pad.
I’m not sure if this will be backwards compatible with BetaFlight, so if that’s important to you, stick with S5.
2 December, 2018 at 17:47 #60369FoschParticipantThanks for the advise !
I thought a signal convertor would be needed after added a feedback wire…
Thus I just had a look inside the tiny EMAX ES3352 servo, and I believe I have to weld the feedback wire to pin 2 of the potentiometer ?
From picture :
Pin 1 = Ground
Pin 2 = from 0.45V to 1.82V along the total stroke
Pin 3 = 2.5V constantWhat do you think ?
And then, to which pad of the MATEK F405 can I weld it please ?Attachments:
2 December, 2018 at 19:22 #60372Kevin_ErikModeratorYes, just like the BMS385 mod i did a few months ago.
That Emax Servo may not be the best choice as Emax is known for reliability issues and the torque is low. The upside i see here is that it response time is better as is its cost. Which is a good thing as your likely to go threw a few of them.
ES3352 12.4g Mini Metal Gear Digital Servo For RC Airplane Gilder
2 December, 2018 at 19:36 #60373jihleinParticipantYes, pin 2 is the signal you want. The max voltage for an ADC input is 3.3 volts. Looks like that’s requirement is met here, so all is good.
Connect it to the RSSI pad on the Matek405Std. Disable virtual servo, set ServoFdbkPin to ADC2, and you will be all set.
2 December, 2018 at 20:46 #60374FoschParticipantThank you both for your prompt reply 🙂
Feedback wire added, I will test it later on.
I took this opportunity to improve the cooling around the servo motor. Maybe I will test it later @7.2V to increase the speed, it seems possible based on comments I found on internet.About the EMAX ES3352 releability, I don’t know. I bought this one because it’s light, powerful enough for my build I think and Banggood rating is very good. Let’s see…
https://www.banggood.com/EMAX-ES3352-Servo-Ultra-thin-Steering-Gear-Emax-Servo-p-940118.html?rmmds=myorder&cur_warehouse=CNAttachments:
11 December, 2018 at 19:05 #60501FoschParticipantHi
I have some telemetry issue, not working.
I have a FrSky R-XSR receiver with un-inverted hack for Smart-portI tried to connect to TX2 pin then TX4 pin + select “Frsky SPort non inverted” for UART hardware setting, wihtout success.
Any proposal ?
11 December, 2018 at 20:48 #60502jihleinParticipantThe sbus signal should go to the sbus pad, UART2 protocol to S.Bus should be set to S.Bus (this is the default). I should also note that with the sbus signal connected to the sbus pad, there should be nothing connected to to the UART2 RX or TX pads.
The non-inverted SPort telem can be connected to UART1, 3, or 4 TX. I think I used UART3 TX, setting it’s protocol to FrSKY SPory Non Inverted. Don’t forget to save and power cycle.
I haven’t used the R-XSR, only the X4R-SB, but I would think the protocols would be the same.
11 December, 2018 at 21:43 #60503FoschParticipantI just tried Tx3 / UART3 / non-inverted, but still not working (while the telemetry was working fine with the same receiver on another betaflight build). I don’t know, maybe I’m doing something wrong or forget to setup something…
Maybe I should try “inverted” protocol, without hacking the receiver ?
12 December, 2018 at 03:27 #60504jihleinParticipantFWIW, I just checked my setup. I have Sbus connected to the SBus pad, which is UART2, and non-inverted SPort telem (hacked X4R-SB receiver mod) to UART3 TX. The hardware pane looks as attached. With the X4R-SB, everything works as expected. I’d look at the non-inverted wire to make sure it’s wired correctly, otherwise I fear there might be an incompatibility with the R-XSR.
Attachments:
12 December, 2018 at 12:29 #60507FrederooParticipantI am absolutely sure R-XSR works with F405-CTR on BetaFlight – without any modifications to either piece of gear. Not sure to which pad I hooked it up, it’s via SoftSerial, dumped config says:
resource SERIAL_TX 11 A15
serial 30 32 115200 57600 0 115200They also have a guide picture for F405-STD and BetaFlight that uses the same pin on the MCU as I do:
http://www.mateksys.com/?portfolio=f405-std#tab-id-3I know you are trying to setup dRonin, I’m just saying it is possible, hardware side. 😉
-
AuthorPosts
- The forum ‘Everything about everything else’ is closed to new topics and replies.