I got tbs micro V2 starter kit and am trying to get my receiver and G3 F4 setup in betaflight.

 Here’s a picture of how I have it wired up.
 
 I did have it setup up for rxsr sbus and S.Port by using softserial on uart 3.

  I am getting betaflight to recognize receiver but I still have Tx3 set up for softserial for RXSR S.Port  and typed in some commands to CLI and I will probably need to change a few settings to get telemetry to crossfire.
 Telemetry sensors didn’t work properly with this G3 F4 but whether it was FrSky firmware rxsr or buggy F4 I don’t know.
 I did change to crossfire in configuration under serial based receiver and betaflight receiver bars move.

 I have all the sensors but current,voltage and another sensor sensor is 0% but quad is not armed and in betaflight with no motor spinning.

  I probably need to start over from default settings so the CLI commands for softserial for rxsr are no longer in effect.
 
 

That picture does not look right. Just wire from the crossfire nano ch2 to tx3 and ch1 to rx3 and it should just work.

Why it shows it going to two different uarts is dumb unless I am really missing something.

(10-Nov-2020, 10:35 AM)UrbanJungle1966 Wrote: That picture does not look right. Just wire from the crossfire nano ch2 to tx3 and ch1 to rx3 and it should just work.

Why it shows it going to two different uarts is dumb unless I am really missing something.

That's because Philippe's wiring diagram is showing the Crossfire Nano RX connected to the Hobbywing XRotor F4 G3 for SBUS. I have no idea why you would use the SBUS protocol instead of CRSF unless there is something funky about the Hobbywing FC that we're not aware of. There's an inverter on both UART3 and UART6 so that might be why, but those are software switchable anyway. Unless of course there is some known issue with switching off those inverters. Either way, UART is inverter free so that could just be used.

@Rob3ddd

To revert SoftSerial back to a hardware UART on the Hobbywing XRotor F4 G3 FC, run the following block of commands in the CLI...


I would advise you to connect the Crossfire Nano RX to UART1:-

1. CH1 pad to RX1
   
2. CH2 pad to TX1
   

Then run the following block of commands in the CLI...


Then go into the Ports tab in Betaflight Configurator and make sure that "Serial RX" is only switched on for UART1.

I reflashed my G3 F4 last night and I switched ch2 to Tx1 pad on FC.
I have serial Rx uart 1 turned on in ports.
I used configuration and choose serial RX crossfire and below choose telemetry.
I already had these settings from another video and by soldering ch2 to tx 1 I get 18 telemetry sensors and current,LiPo voltage are now giving values.
Everything seems to be working properly.
I wasn’t ignoring your instructions Snow I was mainly curious what would happen because it was such an easy quick solder job.

Do I still need to use CLI commands?

No, what you have done is fine. The reflashing set everything back to defaults. So it looks like you are up and running. Easy peasy  Now you know why people are abandoning FrSky in their droves. No more headaches with Crossfire and OTA firmware updates are a doddle

(10-Nov-2020, 04:06 PM)SnowLeopardFPV Wrote: No, what you have done is fine. The reflashing set everything back to defaults. So it looks like you are up and running. Easy peasy  Now you know why people are abandoning FrSky in their droves. No more headaches with Crossfire and OTA firmware updates are a doddle

 It’s the best 120.00 bucks I’ve spent.
 If my usb plug wasn’t acting up yesterday I would have had CF up and running in 5 minutes.
 My usb c plug must have had dust in it and I couldn’t get connected to black sheep but after I blew it out in 5 minutes I had all 3 receivers tested,updated and bound.
 
  I had a feeling it was FrSky rxsr firmware that was causing the problems earlier.Different number of sensors for different versions of firmware is fairly strong evidence.

A question I have about CLI commands.
Does using CLI commands sometimes cause sliders to turn yellow in betaflight?

(10-Nov-2020, 04:27 PM)Rob3ddd Wrote:  It’s the best 120.00 bucks I’ve spent.
 If my usb plug wasn’t acting up yesterday I would have had CF up and running in 5 minutes.
 My usb c plug must have had dust in it and I couldn’t get connected to black sheep but after I blew it out in 5 minutes I had all 3 receivers tested,updated and bound.
 
  I had a feeling it was FrSky rxsr firmware that was causing the problems earlier.Different number of sensors for different versions of firmware is fairly strong evidence.

FrSky have dug themselves a grave with all the different permutations of receiver versions and firmware versions. FrSky receiver related questions (headaches) probably form quite a big percentage of the questions asked on this forum.

I just received my Crossfire Micro TX V2 today as well I already have the Micro TX V1 but I thought I would take advantage of the $25 discount for V1 owners. I'm not sure whether to keep the V1 as a backup, or try and sell it. I did consider going for a TBS Tracer module instead but in the end I decided to just stick with what I already know and have confidence in.

(10-Nov-2020, 04:32 PM)Rob3ddd Wrote: A question I have about CLI commands.
Does using CLI commands sometimes cause sliders to turn yellow in betaflight?

Only if you run specific CLI commands that are related to PID or filter settings. Everything you see in the GUI can also be changed using CLI commands.

(10-Nov-2020, 04:44 PM)SnowLeopardFPV Wrote: FrSky have dug themselves a grave with all the different permutations of receiver versions and firmware versions. FrSky receiver related questions (headaches) probably form quite a big percentage of the questions asked on this forum.

I just received my Crossfire Micro TX V2 today as well I already have the Micro TX V1 but I thought I would take advantage of the $25 discount for V1 owners. I'm not sure whether to keep the V1 as a backup, or try and sell it. I did consider going for a TBS Tracer module instead but in the end I decided to just stick with what I already know and have confidence in.

  It sounds like you got a sweet deal to me plus your V1 is still good reliable equipment and it would likely sell with no problems if you choose too.

  One reason I choose XF after ordering Ghost was it already had proven itself.
 
 Ghost and Tracer are the future but will likely take a year before reaching XF 900 reliability.I’m speculating but it works now so I went with XF.

 I have wasted hours and probably days because of FrSky firmware.I learned a lot but wasted valuable time.
 If time could be bottled up and marketed the results would be priceless.
 
 So it turns out the Hobbywing G3 combo stack is working great now.
 I do like the 60amp 4n1 it gives a good solid spin up after arming.
  
 I haven’t set up bi directional on my ESC.
 
 I don’t know what it is for sure.
I’ll read up on it.
 I may cancel Ghost and start looking at printers.

(10-Nov-2020, 06:15 PM)Rob3ddd Wrote:   It sounds like you got a sweet deal to me plus your V1 is still good reliable equipment and it would likely sell with no problems if you choose too.

  One reason I choose XF after ordering Ghost was it already had proven itself.
 
 Ghost and Tracer are the future but will likely take a year before reaching XF 900 reliability.I’m speculating but it works now so I went with XF.

 I have wasted hours and probably days because of FrSky firmware.I learned a lot but wasted valuable time.
 If time could be bottled up and marketed the results would be priceless.
 
 So it turns out the Hobbywing G3 combo stack is working great now.
 I do like the 60amp 4n1 it gives a good solid spin up after arming.
  
 I haven’t set up bi directional on my ESC.
 
 I don’t know what it is for sure.
I’ll read up on it.
 I may cancel Ghost and start looking at printers.

  I ended up canceling Ghost.
  I really hope to see it fully functional and integrated into FPV and if it does then I’ll maybe get Ghost.
 Tracer is getting some interesting reviews and there’s a group working on a long range Express firmware that supposedly fixes R9M problems.