Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
"No valid receiver signal" after crash
#1
Ok, I made a mistake regarding X8R receiver. I thought I can test quad as-is and fastened X8R weakly. It got under a prop and was damaged. 

   

At least, I should remove this huge plastic cover someday, isn't it? Ok, I've attached antennas back (they are easy to be glued later), straightened pins, resoldered SBUS pins to make sure and current state is:
1. Receiver's LED is green, and I have telemetry on X9D from the receiver
2. "No valid receiver signal" Betaflight says
3. I've tested continuity of each 3 wire between F4 board pins and X8R SBUS pins - ok
4. There is NO ANY mark of props have touched inners of the receiver, I've looked very thoroughly and there is no visual damage at all
5. There are 1.4-1.6 volts between black and yellow SBUS pins on flight controller board, so looks like some signal is presented? 

Please help me investigate issue since I don't have any spare parts. Flight controller has been damaged or X8R receiver? I didn't see any strange things in Betaflight configurator, f.e. accelerometer works fine. Maybe I missed something? How do I know if I can switch quickly controls to FrSky smart port? How can I make sure it's problem of X8R for sure? Thank you in advance.
Reply
Login to remove this ad | Register Here
#2
Sounds like you were using PWM. Bend the pins back and reconnect everything. You can check the receiver tab in BFC to see if you are getting any signal. If you do not get any signal, then you can test the receiver. Use an oscilloscope to see if you getting any PWM signal. You can also wire an LED to ground and signal. It should light up brighter when you increase the PWM.

If you confirm that receiver works, then maybe something is wrong with your FC.

Let start there.
Reply
#3
Voodoo614, I'm using SBUS so it's a serial method of data transfer, right? Switching to PWM looks like not very fast movement. Can we test SBUS or switch to Smart Port (if it sends controlling signals) quickly?
Reply
#4
SBUS is hard to test. I believe it is too fast for most oscilloscope. S. Port is for telemetry. It will not give you controls.

F. Port would be an option, but X8R doesn't have F. Port firmware, so you are out of luck.

Let me think about it for a bit.
Reply
#5
You can test SBUS output using an ISDT BG-8S battery tester. I've got one but I've never used it to test a receiver output with. However, there are plenty of videos on YouTube showing how to use that feature.

I guess it depends if you already have an ISDT BG-8S, or if you're prepared to invest in one to try and test your X8R to find out if it's that or the FC at fault.
Reply
#6
I can really think of how to rule out problem without spare parts.
Reply
#7
(24-Mar-2019, 11:02 PM)SnowLeopardFPV Wrote: You can test SBUS output using an ISDT BG-8S battery tester. I've got one but I've never used it to test a receiver output with. However, there are plenty of videos on YouTube showing how to use that feature.

I guess it depends if you already have an ISDT BG-8S, or if you're prepared to invest in one to try and test your X8R to find out if it's that or the FC at fault.

Here you go. Lee has a really good demonstration on how to test a receiver using the ISDT BG-8S. Just fast forward to 3:48 in the video below to see it in action...

Reply
#8
Guys, I don't have ISDT BG-8S, but looks like this https://oscarliang.com/diy-sbus-usb-converter/ is the fastest way. There are STM32F103C8T6 in my town's shops. What do you think?
Reply
#9
(25-Mar-2019, 06:17 AM)savinovalex Wrote: Guys, I don't have ISDT BG-8S, but looks like this https://oscarliang.com/diy-sbus-usb-converter/ is the fastest way. There are STM32F103C8T6 in my town's shops. What do you think?

Yes, I guess that's an option. I read through the article and thought to myself that it seemed a lot of work just to test the SBUS outputs, but then I read the first comment by Ched999uk right at the bottom of the article which I've quoted below:-

Ched999uk Wrote:There is a much easier way to do this for FRsky and FlySky rx. Basically just connect the rx to an FTDI set to 5V for power and the rx signal pin to the rx pin on FTDI. then use a piece of free software called VJoy!
vjoystick.sourceforge.net/site/index.php/download-a-install/download
and the plugin
github.com/Cleric-K/vJoySerialFeeder/releases
Then run the software and set to SBus or iBus and add axis and buttons as necessary, calibrate and away you go.
You just run the VJoy software then start your sim.

So no soldering to do and no extra STM32F1 Development Board or resistors and soldering…

So it looks like if you get yourself an FTDI adapter you can just use that along with the vjoystick software mentioned. You should then still be able to test the channel outputs in Windows using the same method in Oscar's article under the "Check If It Works" heading although the joystick device will likely have a different name than "Maple". Take note that the first link appears to be broken so just go the vjoystick the home page instead: https://sourceforge.net/projects/vjoystick
Reply
#10
SnowLeopardFPV, wow, I was inattentive. Thank you very much for finding this comment! I'll test receiver in nearest time. Don't know I wish it to be broken or not, lol.
Reply
#11
Guys, looks like X8R is dead. I was able to get signal from smart port with Device Monitoring Studio. On baud rate 56000 it keeps saying "7%" line-by-line. I also flashed receiver firmware. Interesting sign is: there is ~0.80 volts on Smart Port signal pin, and USB-TTL converter lighting with blue LED. When the transmitter is off the SBUS signal PIN has the same 0.8 volts and USB-TTL lights blue. No messages came, but I think it's correct. When transmitter is ON - telemetry OK - there are 1.5-3.5 volts on signal PIN, USB-TTL blue is off and still not signal. Looks like there is some parasite connection inside receiver between radio receiver circuit and SBUS circuit. Strange, still don't see anything been damaged.
Which FrSKY receiver for X9D+ I should buy instead? Maybe go to the CROSSFIRE from the start?

UDP. Have read Oscar's article, I'm going with R9M.
Reply
#12
There are a few of us that use the R9M. I have had mixed luck with mine, though it was on an old firmware. It is since updated and have not had a chance to test it. I have had it out to a few kilometers without issue and at the same time, I have had it failsafe inside of 500 meters, though this was at 10mw.

Anyway, if you choose to go with the R9 system, we are here to help with any issues we have experienced so far!
SoCal Kaity :D
OMG, no one told me it would be this much fun!  Addicted :)
Reply
#13
(30-Mar-2019, 01:17 AM)kaitylynn Wrote: There are a few of us that use the R9M.  I have had mixed luck with mine, though it was on an old firmware.  It is since updated and have not had a chance to test it.  I have had it out to a few kilometers without issue and at the same time, I have had it failsafe inside of 500 meters, though this was at 10mw.

Anyway, if you choose to go with the R9 system, we are here to help with any issues we have experienced so far!

Hi! Sooo I need some assistance now. I've bought R9M + R9M Slim and I'm installing it now:
1. I've connected it to the flight controller with kind of long circuit (didn't want to damage a wire) and it becomes like a 40 cm aluminum wire and the receiver hasn't enough power for telemetry! So it requires 100mA@5V, and want I'm thinking about is maybe I should power it up from PDB directly? Or there is no such constraint? I'll test short wires from FC later, now just thinking how to do it in the "right" way.
2. Should I fear power engine wires? How much interference is for 900 MHz signals?
Reply
#14
(02-Apr-2019, 09:03 AM)savinovalex Wrote: Hi! Sooo I need some assistance now. I've bought R9M + R9M Slim and I'm installing it now:
1. I've connected it to the flight controller with kind of long circuit (didn't want to damage a wire) and it becomes like a 40 cm aluminum wire and the receiver hasn't enough power for telemetry! So it requires 100mA@5V, and want I'm thinking about is maybe I should power it up from PDB directly? Or there is no such constraint? I'll test short wires from FC later, now just thinking how to do it in the "right" way.
2. Should I fear power engine wires? How much interference is for 900 MHz signals?

Provided the power supplied is between 3.5 and 10 volts DC, you can power it from the PDB.  I have the Slim+ installed on my 7" and the power is pulled from the dedicated 5vdc that is for the camera.  Those pads were available as I power the camera through the VTX.  No issues at all.

I would trim the wires down so that there is less a chance that they will migrate into the props.
SoCal Kaity :D
OMG, no one told me it would be this much fun!  Addicted :)
[-] The following 1 user Likes kaitylynn's post:
  • SnowLeopardFPV
Reply
#15
(02-Apr-2019, 01:24 PM)kaitylynn Wrote: I would trim the wires down so that there is less a chance that they will migrate into the props.

Yes, and not just that but the shorter the wires the less electrical noise there will be on them.
[-] The following 1 user Likes SnowLeopardFPV's post:
  • kaitylynn
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  SpeedyBee Not Talking to Spektrum Receiver BobMaine 7 2,483 20-Jun-2024, 10:01 AM
Last Post: SnowLeopardFPV
  GPS not in betaflight after Crash ToasterBox 0 77 19-Jun-2024, 03:38 AM
Last Post: ToasterBox
  Receiver doesn't show up in Betaflight asdvcd 3 192 10-Jun-2024, 11:22 PM
Last Post: asdvcd
  Cinelog20 just hovers after crash flaqfpv 14 461 05-May-2024, 06:22 PM
Last Post: SeismicCWave
  2 Receiver on FC Eyes.fpv 9 281 28-Apr-2024, 09:50 PM
Last Post: Pathfinder075


Login to remove this ad | Register Here