Well what I sent as the wiring diagram is what I flew 4 times with and had no issues other than getting no display at all, and having to unplug and plug back in.
Other than that issue, I had no problems.
Last night, plugged in, had display with the wrong distance and altitude.
Unplugged, plugged back in....no bottom display.
I am confused as well Sander because nothing was changed from the 4 times I had success.
What do I do? How do I get this fixed?
Sounds like a connector/bad cable issue somewhere to me, I would revert back to a bare bones configuration on the bench and verify all individual parts are working.
Purveyor of the FPV secret sauce at ImmersionRC
I agree, but Sander, how do I get it fixed?
Is it something you can circle in a picture and show me what I should get someone to fix, or what are my options.
I am wondering if this would cause a problem.
If I was plugged in to the current sensor , but when I unplugged, and plugged back in, if I accidentally unplugged and plugged in from the output of the current sensor, would that cause a problem? I have the same type of connectors so I am trying to find what may have happened on my end.
You said probably the ic2 chip? We have some people here who are pretty good with soldering, is it something you feel can be done by someone here? That would be the fastest fix, but if not, how much is it to get someone else to fix it. Is there anyone in NA that I can send it to.
Last edited by Shadrackc; 6th June 2012 at 09:33 AM.
On the wiring diagram you redid, what difference does it make moving the BEC power/gnd from closer to the ESC to closer to the current sensor? Trying to learn as I go.
I'm having the same problem, and my EzUHF and EzOSD have been to Sander for inspection too...
At one point I had a Eureka moment... and switched the TBS 69 from PAL to NTSC. This made the bottom lines show up!
Now that I've built my next fuse... I'm not getting the bottom two lines again. I think my TBS 69 camera is taking a moment to warm up... and in that moment the EzOSD is defaulting to PAL... But the time at 1:00 and 2:00 does seem to show up in roughly the correct place. The camera is definitely in NTSC mode.
My next suspicion is that I didn't wire my EzBUS correctly to my EzUHF, and somehow burned something out.
But in the meantime... I just do short flights without the current info.
See I don't want to take that chance. I spent the money on all immersion gear so I could have that info. If I didn't want that info, there are other OSD's that work as well that give you other features. I had to add other hardware to do RTH for example. Plus circle mode. Makes it a lot easier to take off without goggles, get up to height, then put the plane in circle mode as I get my goggles and earphones on, then switch it off and fly.
Then when coming back, have it circle above while I take off my goggles and let my eyes get used to the light, before landing.
When I am flying at fields without any power lines or trees around I will try doing all this with goggles on, but not there yet.
If it is the ic2 buffer chip and sander can show me what has to be done, sure I can get some people who are good enough at that type of thing to replace it.
I know you are busy.
I am trying to be as patient as possible.
I spent my hard earned money on all immersion product.
This was because of the help I saw you giving on the forums, and wanting to keep it plug and play.
So far I have had one unit have a problem and sent it to you.
It took a while, but you sent me a replacement and that was really appreciated.
That replacement got the same problem.
Think I have figured out what caused the problem, and have put what I thought above.
Have asked 3 times now how do I get it fixed. If it is possible for me to have someone skilled with a soldering iron fix it here.
I actually sent you my wiring diagram first on april 30th asking you to take a look to make sure I am safe.
Then again on May 28th, same question.
I am trying to do this properly as it obviously costs a lot of money.
If I caused the problem by making the mistake I did above, you may want to document that so others don't do it as it seems that a few people have lost information, and perhaps made the same mistake I did.
We rely on you for answers as you are the "purveyor of the secret sauce".
I really just want to get my plane flying again and the OSD is pretty important at giving me the info I need.
Can you either:
1)Tell me I am too stupid to use Immersion product and tell me to #$% off.
2)Show me what chip needs to be checked and replaced and I will try find someone to do it.
3)tell me where I can send it to get speedy response on getting it back as I don't want to wait a few months like before.
4)Give me a deal on a replacement.
I have no problem paying for repairs, or for my mistakes.
I just want to get an answer so I can get flying again.
I don't mind offering support, but the retailer is your first point of contact. If I start offering direct support nothing gets done here and everything grinds to a halt.
However I don't intend to leave you hanging, I'm just going to have to ask you to be patient as I familiarize myself with your issue. There's something going wrong on your end, as I've never seen this before. On top of that I personally repaired and checked you returns, so something on your plane is making them fail again.
I'm really busy right now, so I can't offer any advice now, but ping me in a few days and we'll go over things.
Purveyor of the FPV secret sauce at ImmersionRC
I think it may have been caused by the way I unplugged/plugged back in.
That is what I was saying, could it have been caused by me unplugging/plugging in AFTER the current sensor instead of BEFORE.
Would that not have left power to some of the system and have caused that surge that might have blown the ic2 chip?
On paper, looks like it could have.
If that is the case, then at least I know what I did wrong so I can mark my connectors to make sure I don't get mixed up again.