Category: Spektrum Telemetry

Part I of this post is here.

When I reconfigured my Spektrum AR636A and reloaded code to make it into (essentially) a standard AR636 receiver and used it as a non-AS3X model by setting all the gains to zero… all was well.  But when I then decided to add back in some AS3X functionality in certain flight modes I overlooked one important plot point.  Luckily while reading some forum posts on the subject of the Timber in general one comment about reversing the servo direction got me thinking.  So I ran up to the shop and checked and guess what?  My elevator and aileron were responding exactly the opposite of what I would want when I tested the AS3X reaction to uncommanded roll and pitch movements!!  This could have been disastrous had I flown in this mode.

Here’s the problem.  When I went back to what I’m calling “standard” receiver mode with no gains so no AS3X functionality at all, I decided to treat this just like every other receiver.  I relied on my transmitter to make all servo adjustments including centering, movement direction and speed, expo etc…. That’s great in standard mode.  The problem comes when I decided to re-institute a switchable AS3X mode.  With the servos all set to standard (not reversed) and the servos reversed as needed (Aileron and Elevator) in the transmitter the stick command work fine.  But, when the AS3X is on and sees an un-commanded pitch change it command the elevator in the opposite direction.  Unfortunately since it does not know the transmitter is acting in reverse it command what it thinks is the opposite direction from the pitch but (the way these servos are connected and linkage attached) is simply more of the same!!  This would result in a sudden increase in whatever uncommanded pitch occurred.  I’m guessing the plane would try to loop… continuously.  For the ailerons a constant roll would likely have occurred and in my case both would have happened and things might have gotten ugly from there.  Of course I could have overridden those command but as soon as I neutralized the sticks it would have just reoccurred and we would have been off to the races again.

Honestly my only shot to control the plane might have been if I could have reached the switch to shut off the AS3X function in time.  Since this likely would have occurred quickly after launch… I imagine there would have been some unscheduled contact with the earth and a lot of cursing and gnashing of teeth!

Lucky for me I have been reading a lot of posts and so this came to mind before an ugly incident forced me to learn the hard way!  So lessons… 

1.  When working with the AS3X receivers, servo reversing is best done “on board”
2. Make sure you have a known good working flight mode to use when changing these things.  Take off in that mode and test up high in the air so you have time to switch back to the known good mode if anything seems amiss.
3. Don’t trust anything you read or are told if the person telling you has not flight tested his tweek/update or whatever!

OK, so quit wasting your time reading on line and go fly!!  🙂

 

Saturday was my first 2 flights on the new Extreme Flight Laser 200.  It’s not even quite “finished” but I deemed if safe to fly and took it out for the clubs “Electric Only Fly”.

All I can say is WOW!  The plane flew very well with perhaps 2 clicks of aileron trim and nothing else…  I need to experiment with balance as I think I had the batteries a bit to far forward as the nose wanted to fall  during inverted flight or inverted 45 degree up lines… but otherwise the Laser drew a line just like it’s namesake.  It also flew light while still handling a bit of wind without issues. The smooth power from the 35cc Xpwr/Castle 120HV and 12S 4500 45C Pulse battery setup was awesome to behold.  Using a Xoar 20×10 for these first flights and the prop noise is minimal.  I love being able to hear that and the air over the air frame instead of the din of a gas motor.

The 4500mah Pulse batteries seem to be able to give me about 7 minutes of mixed IMAC style flying and time to land with 35% or so of capacity left over… which is sufficient though I might wish for a tad more flight time.  I’m thinking of moving to 5000s as the plane only weighs 11lbs 4oz +/- so I think an extra 4-6oz of battery pack wouldn’t make a big difference.

A new item of note that I am running in this bird is the Castle Creations Telemetry Link for Xbus.  Here’s a link if you have to have one after reading this:

This nifty gadget feeds back information like the current draw, voltage, watts, RPM and FET temperature based on information directly from the speed controller.  Getting all this information from a standard Spektrum telemetry setup required a lot more work and several sensors that cost a lot more than this module.  Based on the information it provided I was able to get pretty graphs like this out of my telemetry viewing program on my PC:

Some interesting information can be had by examining this data closely… for instance at on peak point during the flight, the motor was pulling around 86 Amps!  This was at a point just a minute or two before landing and this caused the battery to sag to about 40.5 Volts.  At this point the prop was turning slightly above 11,300 rpm!  At another point after some sustained mid-throttle flight, the FET on the speed controller reached 145 degrees Fahrenheit.  The reported max power was just over 3600 watts!  For this light an aircraft that is almost insane… which is fine with me!  I’m not in full throttle very often and certainly won’t need to be with this bird.  To quote an old friend “To much power is almost enough.”

The FET temp reading tells me that the 20×10 Xoar is not over stressing the electrical system when flown in this manner though the RPMs seem a bit high so perhaps the 21×10 or 22×8 that I have may be more suitable.  It will be fascinating to run those and get some comparison data.  This kind of data is priceless when you consider it is going to allow me to choose a propeller that maximizes speed or torque or battery life as I see fit and to insure that I’m keeping the power system in a “happy place” while doing so.  Not having to worry about the health of that system is going to keep money in my pocket (not buying more components to replace the burnt out ones!) and give me one less thing to be concerned about.  That makes me happy.

I will update some more and do some comparisons as I try out more/different prop choices.  I’m really hoping the 22×8 works well as I’m thinking that it will give me more low end pull and less speed overall (which is fine with me) while giving me a bit more down line braking effect…  time will tell.

So far, I’m loving the information this little module provides.

I’m also using the arming lockout key from Castle.  This little gadget signals the speed controller to enter the lockout state whenever the key is inserted into the socket.  It’s another layer of security for the very powerful motor and attached prop.  Between this and the throttle cut I have programmed into my transmitter, I feel much more safe plugging in the two 6S packs!  This system is nearing the 5HP level and spinning a 20 inch prop at 11000 plus RPM.  What that can do to unprotected hands, arms, legs, etc… is worth considering.  An extra measure of safety is always welcome.

 

In an earlier post I related my misfortune with my Carbon Cub motor having failed.  Another covered the issue of channel cross interference in a Spektrum receiver.  Well I’m happy to report that both issues are now resolved.

The Carbon Cub motor was replaced with no charge by Horizon Hobby.  In fact it came back in something like 4 days which allowed me to get a test flight in at the club field before slapping the floats on and making a trip back down to Lake Lemon near Bloomington, IN for the fall float fly.  Once again the Cub performed great.

I would still recommend the Carbon Cub, but I would certainly advise keeping a close eye on the BL52 motor from E-flite.  I love the Power 60 on my Extra 260 but this motor is not that same quality in my opinion.

On the receiver, once again Horizon finally came through, and not only replaced but upgraded me to a new AR9020 DSMX receiver.  I was a tad disappointed the tech still couldn’t recreate the issue after I sent them a video and exact transmitter settings that allowed me to recreate the issue using both my Spectrum radios!  The important thing I suppose is they did right by the customer and that seems to be the way they tend to  operate which is not always the case with all businesses.  Kudos to Horizon on that front.

It’s getting to be late in the flying season here so expect to see some building projects, indoor/micro electrics and similar discussion soon.

 

 

 

I recently got my hands on what seemed to be one of the first batch of the new Spektrum SPMA9605… known as the Flight Pack Battery Energy Sensor.  Where the earlier options had been a current sensor and a voltage sensing lead, the new sensor promised to not only read instantaneous current, but to keep accumulated current draw and pack temperature as well.

I installed it into my AeroWorks Extra 260 (60-90 size) powered by a Power 60 E-Flite motor by the expedient method of simply plugging in the two EC-3s and the xbus connector from the earlier installed current sensor.  Upon testing I was dismayed to find I could see no option to display the new information…  Only after fussing with it at the field for 30 minutes or so did I recall that I had declined to upgrade the software in my DX-18 months before, seeing no need for any of the fixes that centered mostly on helis and sail planes.  I especially did not want to rebind all of my aircraft since every previous version had required that.  The latest versions promise that it might not be necessary but I had not been interested in testing that assertion.

A couple days later (tonight in fact) I downloaded the latest version and after backing up the DX-18s memories… placed the updated file on the memory card and hit the proper keys…  After a couple of minutes the radio finished the process and miraculously upon power up, I had full control of the little Extra!

Even better, I now had the option to include the battery pack sensor in my display and set thresholds and alarms.  I set up appropriate levels and tested the current readings and all looked promising.  Since my built in temperature sensor was already in use monitoring the motor, I wanted to take advantage of the temperature capability of the new sensor.

Now, I became confused as the port labeled temperature on the side of the sensor was clearly 4 pins and the only temperature probe I had available was clearly a three wire connector… and actually only used two of them!  I chatted with a supposed expert on the Horizon web site and they had not physically seen the sensor and could not help, nor did the documentation that came with the unit so much as mention the temperature port.

I had nearly given up hope of finding an answer when I finally noticed the top label of the sensor was (at least apparently) applied upside down…  Where the label says X-Bus 1 and X-Bus 2 there is but one port and it is 3 pins…. X-Bus is a 4 pin connection.  On the opposite side is a label Temp and on that side are dual 4 pin ports…  Clearly these are the two X-Bus ports and the one 3 pin is the temp sensor!!  I had already plugged in the single X-Bus port into one of the two ports on the side labeled temp it could only fit on that side.  I went to look at pictures and realized that all must be this way!  Someone should tell the folks on the assembly line… 🙂

Here is a picture showing the labeling and the correct wiring.

Turning in the radio after this revelation shows the following…

I now look forward to actually flying and testing the capacity measurement capability and am excited that I will no longer endanger my batteries by over discharging them.  The closest I could do before was to set a low voltage limit which often meant I would get a warning that would sound at anywhere from 5-35% of capacity remaining depending on throttle setting at the time.  I have great hopes that with this new capability I can set the alarm for a calculated 80% of battery capacity used and expect a much more accurate accounting.

I will post more as I get time to fly and test this capability.