EzOSD - No current sensor data

[KnightHawk]

I setup up my EzOSD last night and everything appeared to be working well. All current sensor data was displaying properly (mAh used, current, battery voltage), satellite reception was working, etc. After the initial check, I disassembled the parts, rewired them nicely in my 60" Ritewing and reconnected everything. Once I powered the system back up, I noticed the current sensor data no longer appeared across the bottom of the screen. No voltage, current or mAh-used. I've rechecked all my connectors & soldering and all looks well.

Has anyone experienced a similar issue?

[Reverand Blue Chip]

All too many time.

[KnightHawk]

Any ideas to solve the problem or does this typically indicate some type of failure within the OSD?

[Reverand Blue Chip]

I'll be honest - I simply don't know. I have shorted my system which led to the bottom lines completely disappearing. I have something going on now where the bottom lines simply aren't reading anything... 0's for voltage, current, amp draw, and RSSI. I have gone through this with both of my EZOSD setups - and 4 additional current sensors.

I had a ground loop in my system however - so maybe that was it. I have on current sensor left to test with the new wiring sorted out... I'm a bit hesitant to try it.

[KnightHawk]

Thanks for the feedback. I've read about your ground loop issue but it's hard to determine if this was the cause of your failure. If your ground loop produced a current significant enough to burn a conductor in the PCB of the EzOSD, then I believe you would find some indications (burn marks or similar) somewhere else in the system (perhaps the servo lead that connects to your EzUHF). Still seems strange that all your systems have failed. I'd be hesitant to fire up your newest current sensor as well.

As for me, I'm certain that I've not created a ground loop. I do not have an EzUHF yet (please ship them soon ... haha) and my failure occurred when everything was working just fine. No smoke, fire, explosions, sparks, fumes, sounds, feels, innuendos, mementos, Mentos, Skittles, m&m's,.... nothing. I'm knowledgeable about the system and understand the fundamentals (everything is connected exactly as TBS suggests - not blaming TBS, just clarifying)... right now it seems that I've experienced a simple failure. Although unrelated, I've updated to firmware v1.14.

[ssassen]

KnightHawk,

Got your PM, but allow me to reply here. What you've done is hook up the TBS supply, camera, Vtx etc. to the Tx output of the current sensor whereas it is only designed to handle a Tx. that's why it is labelled 'Tx output'. It could be that this resulted in a power drain which is simply too high, causing for the fuseable trace to burn out. I'm writing 'could be' as I'm not 100% sure. What is the wiring schematic TBS provided? As I'd like to see what they've done exactly. Lets go from there and debug this issue.

Cheers,

Sander.

[ssassen]

Blue Chip,

Can you send the broken sensors to me? I'll replace them with new ones at no charge, I just would like to see what's wrong with them.

Cheers,

Sander.

[Reverand Blue Chip]

Blue Chip,

Can you send the broken sensors to me? I'll replace them with new ones at no charge, I just would like to see what's wrong with them.

Cheers,

Sander.

Yes... address? As always - thank you Sander. The Immersion customer service is (and has been) outstanding.

[Reverand Blue Chip]

HOLD ON... let's hit the brakes.

So I went to test the last brand new CS... same thing. 0 votage, current, RSSI. That makes 5 current sensors all doing the same thing.

On a whim - I took out a new BUS cable - one that hadn't been spliced into the EZUHF RX... voltage came up on all 5 and displayed as it should. I tested this on both setups. What is odd is that both planes have been set up the same way since the start - and both have worked and displayed information on current and RSSI as they should... this has simply been a new development. Of other interesting note is that the RX's clearly work - as they control the planes as they should.

So now what? It appears that this only happens when the BUS is hooked between the CS, OSD, and UHF RX...

[ssassen]

In that case the BEC for the EzUHF comes up after the rest of the stuff received power/is initialized. What kind of BEC are you using? Is this a Castle Creations ESC/BEC by any chance? Some BECs have a delay where their output voltage comes on after x seconds.