I have a XPS X-24 that started acting up. I can only plug the right side battery lead in to get power to the screen and have a semi - operational board.
I say semi-operational because the power switch on the outside of the aircraft doesn't completely shut off the unit. The screen says it is powering down and the servo's stop working but the screen stays on.

The board seems to function fine with only the right side battery hooked up with the exception of the power switch not completely turning off the X 24.

If I plug the left side battery in, either by itself or with the right side battery plugged in,  the only thing that happens is a solid white LED but nothing else, the screen stays dark and no power goes to the servos. I did notice that the receiver gets powered up though.

I pulled the back cover off the X 24 and found one of the FET's was chipped and broken open. I believe it is the #2 one.
There are two FET's for each side right next to the power leads on either side for a total of four FETs. The one that is broken is right next to the power wires on the left side of the unit that seems to be problematic.

I was wondering if this could be the issue and if it could be replaced?

The FET's have these numbers on them: 4P04L11 GBL650

I know very little about these things but was wondering if that single FET could possibly fix this board or if possibly there may be more damage that I'm not seeing.

Any tips or ideas greatly appreciated as I really like this board and all it is capable of.

I'll try to attach a picture showing the FET.

Chris K.    
Lake Havasu, AZ.

The new version of the X10+ is in final testing.  This version offers substantially more features than the original, including full setup all of those features wirelessly via any smart device or PC web browser - no more cables or specific software needed!  Wireless firmware updates too!

The size is 0.150" taller, but the same width as the existing unit.  There are now two LEDs to show the status of both receivers independently.

The X10+ supports up to 40V now, so you can use it with 24V robotic setups safely.

Hello.
Don't understand why X16 Mlink flickers a lot with many lost frames. Doesn't matter if I use Mpx Mlink or Radimaster Boxer and their ER receivers.
How should I interpret the LF values that count at a fast rate, what is acceptable? Is there anything I can do to make the green light shine with a steady light and avoid all lost frames?
My X10+ behaves the same. Otherwise, everything works as it should, all the servos move smoothly and well.

/Ville

Jim,

I "learned" (just internet so I do not know how reliable the information is) that Futaba's SBUS uses 3.3v or 5v to represent a zero logic value in the bitstream and ground as a logic one in the bitstream.

FrSky's SBUS uses the opposite:  They have ground as a zero value and 3.3v or 5v as the one value.

In my experiment where I fed SBUS to the X10+v2 from an FrSky receiver, the old analog servo did not work, but the digital servo worked.  When I fed the X10+v2 SBUS from a Futaba receiver, both the old analog and the digital servo worked.

We concluded that the frame rate used by FrSky was too fast for the analog servo.  Could it also have something to do with the FrSky SBUS voltages being opposite to that of the Futaba standard SBUS signal?

I had the X10+v2 configured to accept "Futaba SBUS" as the input (not the inverted choice).

Thanks for your opinion,

Paul

I tried this experiment again, this time with a Futaba R2000SBM S-FHSS/SBUS receiver and got an interesting result.

I connected the SBUS output of the Futaba receiver to the X10+v2.

When I powered up the transmitter and receiver, I immediately got a green light on the X10+v2.  I connected the old S148 servo and it worked perfectly!  (It didn't work with the FrSky SBUS receiver).  The digital servos, as expected, also worked perfectly. 

The Transmitter is not even a Futaba transmitter, it is an OpenTx set with one of those 4in1 chipsets that includes the S-FHSS option.

I suppose that the S-FHSS protocol sent by the transmitter, in conjunction with the Futaba receiver and its SBUS link to the X10+v2 results in a frame rate that the S148 can handle.

I'll bet the FrSky SBUS uses 9ms frames and they are too fast for the S148.  The Futaba SBUS receiver probably uses 14ms frames and the S148 can accept that.

My conclusion is that I have solution if my XPS-J1 transmitter module dies and I can no longer use my XPS receivers - I can use Futaba SBUS receivers with X10+v2s (or v3s and beyond) with my airplanes that still have analog servos.

Jim,

I hope this note finds you and your family well.

I did an experiment where I used an FrSky "SBUS output" receiver connected to an X10+v2.  I configured the X10+v2 to accept an SBUS input.  Then I bound the receiver to my Taranis using its internal radio's D16 protocol.  There was no XPS transmitter module involved in this test.

There were interesting results:

With the transmitter, X10+v2, and receiver powered up, the X10+v2 showed a steady green led which indicated a good connection to the receiver (and transmitter).

An old Futaba S148 servo ran when connected to the X10+v2, but it ran a little notchy.  It also vibrated and hummed while sitting idle.  I reckoned that being a 25-year old analog servo, it perhaps had a problem with the SBUS frame rate.

Then I tried a relatively modern digital servo, an MKS DS95, and it worked very fast and very smoothly and without any vibration or humming.

Can you speculate why the S148 servo did not work well with the setup?

Thank you,

Paul

Over the last mounth we have had three crashes two with the old 8 channel rx with the hard plastic antenna and on the sailplane rx. So far the nano's and the rfu's are good. Is there a way to set the telemetry station to read the rssi that the reciever is see? Maybe missed frames all three were complete lockout 2 to 3 seconds to impact with terrafirma. Up untill this year we have never had a problem while the spektrum guys droping airplane frequently due to lockout. I have a RF Explrer hand held spectrum analyser most of the the time we see -90 to - 70 dbm in signal strength with frequent spikes into the -30 dbm range.
thanks for your time.
don king
i did look to find instructions for the telemetry station but could not locate them.

i want to place 2 nanos in a glider. it is a tight fit. the question is do i need to keep the master and slave rx apart? i thought of using a thin piece of foam or card board. they would be stacked. maybe they could be end to end. what say you?
thanks, ron

is it possible to set it up to send rssi to the telemetry station
thanks don king

Currently I am using an XPS JR module in a RadioMaster Tx16s with 16+ nano receivers.  Before this I was using the Futaba module in my 9c radio.  I have used the RM setup for the last three seasons. Last season I crashed my funjet due to loose of control.  Unable to determine the cause I replaced the nano Rx and gyro and moved on.  I had no issues till about two weeks ago, I tried to fly my funjet on a hot ~85-degree day and during my preflight I noticed the servos movement was choppy and lagged the stick movement.  I had several flights before this on other models.  I assumed it was either the nano receiver or possibly the gyro in the plane.  I could not reproduce the issue on the bench, so again I replaced both the rx and gyro (installed another nano rx) and had no issues for several flights since.   

This past weekend I was out (again a hot 85 degree day) and tried to fly 71” Slick about mid day after 3 previous flights.  I experienced the same laggy choppy servo movements.  This time I immediately switched to the funjet and had the same issue making me think its an issue with the XPS module.  I wish I had then immediately switched to my small heli with a Spektrum rx (to rule out the radio) but this didn’t occur to me.  I later (same day) flew the heli for several flights and had no issue.  Both sessions were hot sunny days and I sometimes leave the radio on while changing packs.   Till I resolve this issue I don’t feel confident in using my XPS equipment.  Do these symptoms sound familiar?  Could this be a heat issue or just a failing module?  I see the JR modules are out of stock.  What are my options?  Thanks for any assistance.