(13-Mar-2020, 10:45 PM)SnowLeopardFPV Wrote: That's better  

Your image of the Slim+ is for a Slim so that's a little bit confusing.

Unless you have a good reason to use SBUS/S,Port, then I would recommend using FPORT instead (you will need to flash the FLEX FPORT firmware to the Slim+). That will only use a single wire from the RX1 pad on the Slim+ to the T4 pad on the Kakute F7 instead of two wires, and means you can do away with a wire from S.Port to the T4 pad or a wire from SBUS to the R6 pad.

You don't need the RSSI connection which is for analog RSSI data. RSSI data gets sent with the serial SBUS or FPORT data connection which makes analog RSSI redundant.

I'm sure I've had the above conversation before (?) Maybe it was with someone else   

The solder joints look acceptable although one of the white wires has a little bit too much insulation cut off meaning there is a risk of shorting it out.

Oh i am so inattentive i didn't notice that i am using Slim yeah there are extra tx1+rx1 pins on slim+ ota. And yeah we have talked about F.port before so i meant to use F.Port but accidentally soldered s.bus out too(didn't solder rssi). I soldered S.port instead of RX1 should i use S.Port or RX1 for F.port?

edit:
*I will resolder or improve some of them.
*I have downloaded Slim+ ACCESS Firmware, in the file there are FCC, LBT and Flex firmwares no such thing as F.port and also didn't show up sth. like that when trying to flash receiver.

I didn't realise you were using ACCESS firmware, so there is no separate firmware to install on the Slim+ for that because SBUS/S.Port and FPORT are all bundled into the same ACCESS firmware. You switch between using either SBUS/S.Port and FPORT using the transmitter by long pressing on the receiver entry under the model and you then get to choose which of those two protocols to use. I don't have any ACCESS equipment to verify that myself, but credit goes to majestynl for that information (HERE).

However, if you just want to continue using SBUS/S.Port then your wiring is correct

(14-Mar-2020, 10:12 AM)SnowLeopardFPV Wrote: I didn't realise you were using ACCESS firmware, so there is no separate firmware to install on the Slim+ for that because SBUS/S.Port and FPORT are all bundled into the same ACCESS firmware. You switch between using either SBUS/S.Port and FPORT using the transmitter by long pressing on the receiver entry under the model and you then get to choose which of those two protocols to use. I don't have any ACCESS equipment to verify that myself, but credit goes to majestynl for that information (HERE).

However, if you just want to continue using SBUS/S.Port then your wiring is correct

I wanted to use F.port but couldn't figure it out how to use it. Oscar explained and wired in this way :https://oscarliang.com/setup-frsky-fport/ just by s.port that's why i am confused but now i get it RX1 is inverted S.Port signal so F.port can directly be used by rx1 instead of using s.port and type "set serialrx_inverted = ON". Right?

Actually, I just realised your FC is a Kakute F7, so for FPORT all you need to do is remove the SBUS OUT wire that is connected to R4. You can leave the S.Port wire connected to the T3 pad as it currently is. F7 boards can handle inverted signals natively so there is no need to use the (un)inverted signal from RX1 on the Slim+. Once you've done that you need to apply the following settings in the CLI and it should work once you select to use FPORT as the protocol on your transmitter.

(14-Mar-2020, 04:05 PM)SnowLeopardFPV Wrote: Actually, I just realised your FC is a Kakute F7, so for FPORT all you need to do is remove the SBUS OUT wire that is connected to R4. You can leave the S.Port wire connected to the T3 pad as it currently is. F7 boards can handle inverted signals natively so there is no need to use the (un)inverted signal from RX1 on the Slim+. Once you've done that you need to apply the following settings in the CLI and it should work once you select to use FPORT as the protocol on your transmitter.

Code:

serial 2 64 115200 57600 0 115200
serial 3 0 115200 57600 0 115200
set serialrx_provider = FPORT
set serialrx_halfduplex = ON
set serialrx_inverted = ON
save

Thanks   Should i try betaflight and check the motors, vtx. etc w/o receiver or wait for the receiver?

(14-Mar-2020, 10:22 PM)Frenzi3d Wrote: Should i try betaflight and check the motors, vtx. etc w/o receiver or wait for the receiver?

It's entirely up to you. You won't do any damage by testing those things without a receiver connected. Just make sure you do the usual continuity checks before plugging in a LiPo and use a smokestopper.

(15-Mar-2020, 12:15 AM)SnowLeopardFPV Wrote: It's entirely up to you. You won't do any damage by testing those things without a receiver connected. Just make sure you do the usual continuity checks before plugging in a LiPo and use a smokestopper.

Alright, i will make a smokestopper then try. Thanks a lot for your help.

(15-Mar-2020, 12:15 AM)SnowLeopardFPV Wrote: It's entirely up to you. You won't do any damage by testing those things without a receiver connected. Just make sure you do the usual continuity checks before plugging in a LiPo and use a smokestopper.

My new receiver has just arrived (luckily in 12 days from AE   ). I don't wanna fry anything again so just to be clear, i will be using S.PORT in battery compartment ( X9D+ SE 2019) and will be using VCC - GND - S.port on Slim+ OTA right? And again i will use the same connector that i have made from CON2.

Yes, just wire as shown below. There doesn't seem to be any close-up photos anywhere of the S.PORT connector in the battery bay of the X9D+ 2019 so I will trust that you know which pin on that is 5V, GND, and S.PORT.


XD9+ 2019 S.Port Connector   Slim+ CON 1
==========================   ===========
5V -------------------------> VCC
GND ------------------------> GND
S.PORT ---------------------> S.PORT

(02-Apr-2020, 04:18 PM)SnowLeopardFPV Wrote: Yes, just wire as shown below. There doesn't seem to be any close-up photos anywhere of the S.PORT connector in the battery bay of the X9D+ 2019 so I will trust that you know which pin on that is 5V, GND, and S.PORT.


XD9+ 2019 S.Port Connector   Slim+ CON 1
==========================   ===========
5V -------------------------> VCC
GND ------------------------> GND
S.PORT ---------------------> S.PORT

I thought i have uploaded photo of the battery compartment anyways here it is ; https://imgur.com/a/MHnp9XU

And as you may see i have dropped my gps on the floor(laminate floor) while trying 3d printed parts and the edge of the circuit board damaged a lil bit would it be a problem?

Thanks for posting that photo. It's probably the only photo that exists on the internet showing the pinout of the S.Port connector on the X9D+ 2019, so it might help others.

That damage to the GPS is nothing to worry about. It's just the edge of the laminated fibre of the circuit board.

(02-Apr-2020, 05:14 PM)SnowLeopardFPV Wrote: Thanks for posting that photo. It's probably the only photo that exists on the internet showing the pinout of the S.Port connector on the X9D+ 2019, so it might help others.

That damage to the GPS is nothing to worry about. It's just the edge of the laminated fibre of the circuit board.

Thanks for your help, i have successfully updated my receiver and bind it. Now i will jump to betaflight setup however when i connect FC to PC i got an error usb device not recognized there is a solid green and blinking blue led on FC. (holybro kakute f7)

(04-Apr-2020, 06:38 PM)Frenzi3d Wrote: Thanks for your help, i have successfully updated my receiver and bind it. Now i will jump to betaflight setup however when i connect FC to PC i got an error usb device not recognized there is a solid green and blinking blue led on FC. (holybro kakute f7)

No problem and one issue now solved  

Try a different USB cable and make sure it is one that is a data cable because some are charge-only cables without the data pins connected. If that doesn't work, reboot your computer before doing any further investigations. Also, try a different USB socket

(04-Apr-2020, 06:41 PM)SnowLeopardFPV Wrote: No problem and one issue now solved  

Try a different USB cable and make sure it is one that is a data cable because some are charge-only cables without the data pins connected. If that doesn't work, reboot your computer before doing any further investigations. Also, try a different USB socket

I have tried 3 different ports which didn't work but worked on laptop so i'm good now   Sorry for asking too much basic questions however i want to be more cautious as i started with a fail. I have watched lots of betaflight setup videos (JB, Oscar, Drone Mesh etc.) however i didn't see any f.port. So again, i have binded my receiver and connected to betaflight and "turned on" Serial RX on UART4 but i can't see any stick movements. Do i need to type the commands first, that you have told before for F.Port?

My steps; 1. Updated Taranis, R9M module and Slim+
               2. Register&bind receiver
                3. Connect BF (current bf fw: BTFL 4.0.4)
                 4. Update BF to latest (don't know the version)
                  5. Get the receiver working and check ESC, motor direction and then other settings such as arm/disarm, flight mode, gps, osd etc.

http://prntscr.com/rt1mgs

Which KAKUTEF7 should i choose? CLI is below.