Determining channel output

[Xrayted]

Hi guys. After autoing into a wheat field recently, and spending almost an hour trying to locate my heli, I decided to place a simple switch activated location alarm on my heli.

It simply plugs into any channel and is switch activated with any negative side of the channel starting the alarm.

I have GPS and are filled up on my FBL unit, however Im using IO-B and C for dual power from flight my pack, and SW-A is being used by my GPS LED, so there are channels that I could tap into that are currently only being used for power and nothing else.

My issue is trying to figure out how to match up my TX to one of those channels I have Aux2 available to me on my DX9 and can easily assign my switch of choice, but how do I get that available channel connected up so I'm driving a specific one on my FBL unit since there is no way to assign specific channels such as this in the UI.

I would assume anyone who is using retracts, lights or any other non flight function on an open channel has done this successfully

Thanks!

EDIT: I took a servo and randomly tried various ports until my Aux2 switch moved the servo in one of them, so at least I now know that Aux2 controls the IO-B channel on my FBL unit by default.

Not sure if this is the only way to figure this out, but it will work for me since that channel is only being used for power, so I can tap a servo Y into it for the alarm.

[rickn816]

My Taranis has a signal strength function - I used that to find lost aircraft.

Rick

[ticedoff8]

Use a Y cable on the throttle output of the FBL.
When you lose it in the wheat field again, turn off the transmitter.

The fail safe setting would be set to drop the throttle channel to 0.

All you need is an model locator that has a pulse width decoder and a load speaker to send out a tone when the throttle goes to 0

I see them advertised in the AMA magazine

[Xrayted]

Originally Posted by ticedoff8

Use a Y cable on the throttle output of the FBL.
When you lose it in the wheat field again, turn off the transmitter.

The fail safe setting would be set to drop the throttle channel to 0.

All you need is an model locator that has a pulse width decoder and a load speaker to send out a tone when the throttle goes to 0

I see them advertised in the AMA magazine

That is what I have and managed to get it working well.

The simple little plug in device will alarm if it loses TX connection or activated by switch.

http://www.lostmodelalarm.com/Products.html

I considered tapping into the throttle, however there is no zero throttle in TH when using a Castle ESC with auto bailout activated. I do have a switch set to give me zero to arm the ESC, but I don't want the alarm screaming every time I have the switch set to zero to arm or for safety reasons.

I was able to determine that my TXs AUX2 channel is controlling the IO-B port on the SK, so I tapped into that lead since it was only being used for power from my flight pack and can now trigger the alarm anytime I wish by switch or it will be automatic in the event of lost TX connection

[Xrayted]

Originally Posted by rickn816

My Taranis has a signal strength function - I used that to find lost aircraft.

Rick

I thought of this concerning the GPS option as I walked a grid pattern through the field. It should be easily possible to track the helis precise position using the GPS module if we had a remote Bluetooth app to read the RT data coming from it........hint , hint Art

[ticedoff8]

Bluetooth range is maybe 50' - so you would ave to be close to the model and a GPS wouldn't be much help.

But, a cellular dongle for the 720? That would do the trick.

Or a HUD unit with the 2.4Ghz downlink. Add in real time FPV with OSD and bob's your uncle.

Or, don't crash. Cheaper all around.

[Xrayted]

Originally Posted by ticedoff8

Bluetooth range is maybe 50' - so you would ave to be close to the model and a GPS wouldn't be much help.

But, a cellular dongle for the 720? That would do the trick.

Or a HUD unit with the 2.4Ghz downlink. Add in real time FPV with OSD and bob's your uncle.

Or, don't crash. Cheaper all around.

Good point on the BT. I didn't factor in its usable range.

Just don't crash is the best option In this case it wasn't really a crash, but just a unplanned and early landing. I pulled a bone head move and grabbed an already flown pack when getting distracted by talking to someone. This despite having flown/unflown markers on my packs, so Im not sure how I managed this one

I got way out and about 200 feet high and head the LVC kick in so I dropped throttle and just autoed down. Unfortunately I didn't have the distance to avoid landing in the tall grass area.

I also learned that my eyes are damn liars! The heli wasn't found anywhere near where I "thought" I set it down!

[rickn816]

These work very well. Good range.

http://www.loc8tor.com

Rick