(25-May-2016, 03:50 PM)Trollhammered Wrote: Of course... But if your already flying acro I'd think that switching to horizon to land is a crutch. Not criticising just trying to be encouraging

I was concerned because of what the web site says.
"This X-Racer flight controller only comes in one version...ACRO! This is not a flight controller that is designed to fit the needs of everyone, it is a flight controller designed to fit the needs of racers and free style flyers."

(25-May-2016, 05:23 PM)LannyT2 Wrote: I was concerned because of what the web site says.
"This X-Racer flight controller only comes in one version...ACRO! This is not a flight controller that is designed to fit the needs of everyone, it is a flight controller designed to fit the needs of racers and free style flyers."

Ahhh. It's mostly because it doesn't have a barometer

So its "Acro" only. Think I will stick the Naze32 until I get better at acro.

(25-May-2016, 06:03 PM)LannyT2 Wrote: So its "Acro" only. Think I will stick the Naze32 until I get better at acro.

It has an accelerometer and hence can be used for angle/horizon mode. Hard to find a board without accelerometer these days, as they are bundled with the IMU.

Hey fpvers,
Just got my xracer v2.1 and it seems very well made.
I connected x4r via sbus and have osd on uart2.
I want to connect smart port as well and i want it not to be on uart1 so:
Been trying to config my xracer bord with soft serial but failed, i think i might have used the wrong pins. Have any one got it working and say which pins are to be used?
Fpvmodel said it should be pins 6,5 for soft1 and 7,8 for soft2 bu they might be wrong..
Appreciate your help
Barak

(19-Jun-2016, 07:52 AM)barakk9 Wrote: Hey fpvers,
Just got my xracer v2.1 and it seems very well made.
I connected x4r via sbus and have osd on uart2.
I want to connect smart port as well and i want it not to be on uart1 so:
Been trying to config my xracer bord with soft serial but failed, i think i might have used the wrong pins. Have any one got it working and say which pins are to be used?
Fpvmodel said it should be pins 6,5 for soft1 and 7,8 for soft2 bu they might be wrong..
Appreciate your help
Barak

I've given up trying to get soft serial to work. So any time I need to update firmware, use BLHeli, or download blackbox logs, I simply pull the X4R/XSR's JST. Fortunately mine sits in such away this is possible without tearing anything open. The biggest annoyance with that is forgetting to plug it back in. How ever if anyone out there can confirm they got soft serial working, I'd sure like to know how.

(31-Mar-2016, 08:31 PM)Oscar Wrote: i can confirm pass through works

hi oscar,
i have trouble with passthrough
got littlebee 20A on blheli with xracer flashed with BF 2.7.1
when trying to connect via FC i get :
"initialization of serial 1 wire failed! please check BF revision for serial 1 wire passthrough"

is there some configuration needed on the betaflight to fix it?

---

(19-Jun-2016, 01:52 PM)Trollhammered Wrote: I've given up trying to get soft serial to work. So any time I need to update firmware, use BLHeli, or download blackbox logs, I simply pull the X4R/XSR's JST. Fortunately mine sits in such away this is possible without tearing anything open. The biggest annoyance with that is forgetting to plug it back in. How ever if anyone out there can confirm they got soft serial working, I'd sure like to know how.

sorry for my ignorance.. do have to unplug anything for blheli passthrough to work?
thanks for reply

(22-Jun-2016, 08:10 AM)barakk9 Wrote: hi oscar,
i have trouble with passthrough
got littlebee 20A on blheli with xracer flashed with BF 2.7.1
when trying to connect via FC i get :
"initialization of serial 1 wire failed! please check BF revision for serial 1 wire passthrough"

is there some configuration needed on the betaflight to fix it?

---

sorry for my ignorance.. do have to unplug anything for blheli passthrough to work?
thanks for reply

Make sure you get out of cleanflight gui before opening BlHeli Suite and ensure your lipo battery is plugged in (props off of course)

(22-Jun-2016, 08:10 AM)barakk9 Wrote: hi oscar,
i have trouble with passthrough
got littlebee 20A on blheli with xracer flashed with BF 2.7.1
when trying to connect via FC i get :
"initialization of serial 1 wire failed! please check BF revision for serial 1 wire passthrough"

is there some configuration needed on the betaflight to fix it?

---

sorry for my ignorance.. do have to unplug anything for blheli passthrough to work?
thanks for reply

I have to unplug my smart port because it's hooked up on Uart 1. It interferes with my USB with things like BLHeli, downloading black box logs, or connecting to the bootloader.

thanx Trollhammered
will try that/.

hello , I got a big problem tonight,
I tried to flash the FC ( I didnt used it before , jsute soldered some pins) , and it stopped in the middle !!!
 I used cleanflight with all the lastest updates but the flashing stopped with an error . Now i can't even switch it ON , the blue LED won't light anymore ! What i have to do ?

I tried too retrieve a connection with the cleanflight tutorial but i don't manage to put it in Bootlader mode , and so I couldn't replace sTM32 drivers with zadig.

Purchase protection just went off yesterday ...

(04-Aug-2016, 10:34 PM)Boutbou Wrote: hello , I got a big problem tonight,
I tried to flash the FC ( I didnt used it before , jsute soldered some pins) , and it stopped in the middle !!!
 I used cleanflight with all the lastest updates but the flashing stopped with an error . Now i can't even switch it ON , the blue LED won't light anymore ! What i have to do ?

I tried too retrieve a connection with the cleanflight tutorial but i don't manage to put it in Bootlader mode , and so I couldn't replace sTM32 drivers with zadig.

Purchase protection just went off yesterday ...

First off I find it's good practice to flash an FC before you solder a thing. That way you know that if there's something wrong you didn't do it and you didn't spend the time installing just to take it apart again.
If the blue LED doesn't come on it sounds like your not getting power to it anymore. Can you tell if your computer sees it when you plug it in

sounds like you might have burn a component on it, or spilled solder on some pins... check carefully for any trace of that...
I would suggest in future always cover the board with tape when doing soldering, don't leave iron on the board for too long to avoid over heat... also like Trollhammered said, flash the board before soldering

(04-Aug-2016, 11:43 PM)Trollhammered Wrote: First off I find it's good practice to flash an FC before you solder a thing. That way you know that if there's something wrong you didn't do it and you didn't spend the time installing just to take it apart again.
If the blue LED doesn't come on it sounds like your not getting power to it anymore. Can you tell if your computer sees it when you plug it in

PC "beeps" when i plug it , and I can see on Zadig that the driver CP210 from STM is used . But not the STM32 ( used when in bootloader mod)

I didn't plug any lipo on it , and soldering seems good ?

I could connect it with CF before flashing, even if i did fully tested id , it seemed OK .

(05-Aug-2016, 07:54 AM)Boutbou Wrote: PC "beeps" when i plug it , and I can see on Zadig that the driver CP210 from STM is used . But not the STM32 ( used when in bootloader mod)

I didn't plug any lipo on it , and soldering seems good ?

I could connect it with CF before flashing, even if i did fully tested id , it seemed OK .

Okay try to power the board with an external 5V power supply on the 5V rail? I have a feeling it could be a burn diode...