451 replies to this topic

[Mr.RC-Cam]

You are headed in the right direction. I highly recommend adding the Toroids to the GPS host cable and A/V Tx, per the summarized instructions mentioned earlier. They have helped in just about every 900Mhz / GPS combo that I have been involved with that had problems. Honestly, the extra insurance they provide is worth the effort. Lot's of wire turns on them is best, as close to ten tight wraps as you can get. Don't use the convenient split core (snap-on) Toroids -- one piece donut types are needed.

It's just odd that I have to set it 30 minutes behind the actual time offset to obtain correct time, since I live in California and we're in -8:00 offset.

Seems weird to me too. But, it's great it is working out. Success is sweet!

[ThomasScherrer]

>>setting the UTC offset to -7:30 certainly fixed the clock problem

what ??
try with a zero offset, that should read out the GPS clock unaltered !
does that work ?

else I bet you have an old ByteInfo.config
open the file just use a txt editor, and find the UTC Offset section

<option name="-8:30">32</option>
<option name="-8:00">33</option>
<option name="-7:30">34</option>
<option name="-7:00">35</option>
<option name="-6:30">36</option>
<option name="-6:00">37</option>

check the hidden numbers looks like this, else fix it :-)

[Steph280]

>>setting the UTC offset to -7:30 certainly fixed the clock problem

what ??
try with a zero offset, that should read out the GPS clock unaltered !
does that work ?

else I bet you have an old ByteInfo.config
open the file just use a txt editor, and find the UTC Offset section

<option name="-8:30">32</option>
<option name="-8:00">33</option>
<option name="-7:30">34</option>
<option name="-7:00">35</option>
<option name="-6:30">36</option>
<option name="-6:00">37</option>

check the hidden numbers looks like this, else fix it :-)

Thomas,

I did find the options in the ByteInfo.config file:
<option name="-12:00">25</option>
<option name="-11:30">26</option>
<option name="-11:00">27</option>
<option name="-10:30">28</option>
<option name="-10:00">29</option>
<option name="-9:30">30</option>
<option name="-9:00">31</option>
<option name="-8:30">32</option>
<option name="-8:00">33</option>
<option name="-7:30">34</option>
<option name="-7:00">35</option>
<option name="-6:30">36</option>
<option name="-6:00">37</option>
<option name="-5:30">38</option>
<option name="-5:00">39</option>

I am not sure what is wrong, or what to fix.

But like I said, if it works then it doesn't matter why it works.

I know you are not obligated to help, but I do appreciate all the suggestions you have provided thus far. Thanks again.

[ThomasScherrer]

>But like I said, if it works then it doesn't matter why it works.

it does to me, I am constantly seeking perfection in all I do,
no matter if I cant fix some thing, I still prefer to know why,
when I fail I learn more, wisdom is strange.

[Steph280]

ok did a couple more flights this weekend with GPS away from the 500mw TX. Got more satellite counts (between 5 to 10), but altitude is still off. Even right after powered up and satellites were located, the GPS shows negative altitude before plane is flown.

I will add a toroid to the wire after I make a longer extension for it.

Where can I buy a current sensor for IFOSD?

Thanks again for all the help.

[Gary Evans]

ok did a couple more flights this weekend with GPS away from the 500mw TX. Got more satellite counts (between 5 to 10), but altitude is still off. Even right after powered up and satellites were located, the GPS shows negative altitude before plane is flown.

I will add a toroid to the wire after I make a longer extension for it.

Where can I buy a current sensor for IFOSD?

Thanks again for all the help.

My IFOSD (1.16f) maintains strong satellite counts but the altitude has never worked right. Both altitude and distance home only display in meters even when feet is selected. Altitude would jump all over (straight flight and shallow turns) sometimes looking correct and some times being way off and I finally just removed it from the display. Distance home appears to be correct except for the meters issue.

[ThomasScherrer]

when people have problems it is often incombinations with the EB85 GPS,
try to borrow another gps type from a friend and see if better.
I was newer able to recreate any of the mentioned problems,
look at all my videos are with smooth and stable and correct readouts
(but ok I use meters, and so should you)

[Gary Evans]

Your right about the GPS. The LS20033 provides a much better sat acquision.

The conversion between meters and feet in a program being just math is there any reason why using meters would provide a more accurate reading?

[ThomasScherrer]

you get about 3 feet pr meter, so the feet value will jump 3 times as much :-)
a GPS have 9m accuacy on the position if good fix,
but about 5 times as much on the height,
multiply this by 3 and add flyind angle jitter to the gps
and you should get jumping numbers :-)

[Steph280]

I have been using Meters since Thomas mentioned the bug. If GPS has 35m of accuracy on height, then my reading is probably within the normal tolerances. I have not attempted FPV because of this, since I have problem judging the height of plane through goggles. I am going to search for the firmware update per Mr. RC-Cam to see if that helps.

I have been trying to avoid LS20033 since it requires 4.2v operation. Using it on my plane would mean a 5v step down voltage converter for the OSD, and another 4.2v one for the GPS. Or can the OSD operate on 4.2v?

[ThomasScherrer]

first of all !! you should not use GPS height as landing indication,
you will most likely crash !
first learn to fly good and stable FPV, then perform takeoff via FPV,
to land is hardest, use landscape to learn the height and maybe have helpers near by to guide you down telling you the height is good or bad, also the right lens is important,
normaly the open angle is too small, I have got different lences from rangevideo and found out this is smarter with the widest, get a more natural feeling.

you can simply add a diode in series with the 5V supply to make the 4ish volt required for the smaller GND, then you are within safe area, some even use two diodes, but measure the voltage when it is running, the diode drop voltage is a bit different pr size and type of diode, you can get anything from 1V to 0.1V

[Steph280]

Looks like I have a lot more practice to do. I need to get a foamie to learn how to land FPV.

Question on volt1: The power battery connects to the two outer pins (signal and ground), and leave the middle pin unattached correct?

Thanks again for all your help Thomas.

[ThomasScherrer]

Question on volt1: The power battery connects to the two outer pins (signal and ground), and leave the middle pin unattached correct?

YES please look in the manual, so you do not do this wrong !!
most of the connectors are like normal servo leads
GND
+5V
signal (can be volt in the volt meter inputs)

[sebiss]

Hello,

I have a intelligentFlight OSD.
The software version I have is the 1010, and the firmware is 1.16F.
Did you update software and firmware?
Second question:

I have no idea how to configure the OSD.
Can someone send me the configuration?
My GPS chip is a 5Ghz Cirocomm.

The function of software update does not work.
(In the menu "Tools" "OSD Firmware Update" and "Help" "Check for software updates)

Last question:
Did you address a forum dedicated to the DSO?

Best regards,

Seb

[Doofer]

Hi Sebiss. I see no-one's replying, let me try.
1. Those sound like the most recent versions to me.
2. You're a little vague about exactly what the problem you're getting is - can you describe what you do, and what the result (or non-result) is in a little more detail?
3. This is the IFOSD thread - although it may take a while, most questions about the IFOSD are probably asked & answered somewhere in these 22 pages. I think you'll find a thread on the IFOSD on RC Groups, too.

[JMS]

http://www.webx.dk/o...information.htm

[Steph280]

I just got a LS20033 but am afraid to plug it in!

Is anybody using the tiny LS20033 GPS module on IFOSD? Can you check the voltage for me?

I have board version 2.05 so it's supposed to supply 4v for GPS. But when measured with voltmeter it shows 4.8v. Could it be 4v under load? Is this safe for the GPS module?

Thanks.

Edited by Steph280, 27 April 2009 - 02:56 PM.

[Kilrah]

It depends on what IFOSD version you have. Some hardware revisions had a 5V output, some had a diode added to reduce voltage. Maybe add a diode externally, connect the GPS and measure. If it's too low there is already one on the OSD

[Steph280]

I guess my question is, what is an acceptable voltage when measured with no load on volt meter? All pins have 5v output except GPS port have 4.8v, so I suspect this does have a diode. Maybe under load it will be in the 4.2v range?

I guess I just need somebody with the same board to measure and see what the no-load voltage is.

[Mr.RC-Cam]

what is an acceptable voltage when measured with no load on volt meter?

When using a LS20033, it must be less than 4.2V. Keep in mind that 4.2V is the *absolute* max voltage for the LS20033. In a perfect world, it is intended to be operated at a nominal 3.3VDC. If your unloaded voltage is 4.8V then I highly recommend that you do not use the GPS as-is.