alpc32/arducam-osd

Automatically exported from code.google.com/p/arducam-osd

arducam-osd's Issues

update charset stuck

What steps will reproduce the problem?
1. updated last firmware
2. updated last charset
3. "UPDATE CHARSET" is showing when booting and stays there

What is the expected output? What do you see instead?
"UPDATE CHARSET" is showing when booting and stays there

What version of the product are you using? On what operating system?
19

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 2 Mar 2012 at 10:41

MinimOSD firmware missing?

What steps will reproduce the problem?
1. Can't connect with setup software


What is the expected output? What do you see instead?
- Failed to talk to bootloader.

What version of the product are you using? On what operating system?
MinimOSD v1.1

Please provide any additional information below.
- Seems it doesn't have firmware inside. 
Any help how to flash it? Just hex file or do I need to flash bootloader? 
Please help ASAP. Thanks!

Original issue reported on code.google.com by [email protected] on 6 Sep 2012 at 6:59

Minim OSD without TX from APM is not updating values on screen, everything is 0

What steps will reproduce the problem?
1. Remove the TX cable from MinimOSD (I also have a 3DR Radio onboard)
2.
3.

What is the expected output? What do you see instead?
If I only have 3 wires connected to MinimOSD, without TX from APM2, the values 
on the screen are not updating anymore, only the MODE is changing, and after 
arming the APM Lipo voltage is also updated on the screen, but the other values 
are all 0

What version of the product are you using? On what operating system?
I tried with APM2 Tricopter firmware 2.6 and latest 2.7.1 (I installed it using 
MP on 16 august 2012)
For MinimOSD I tried 3 different firmwares:
a. MinimOSD_19_MAV10.hex / MinimOSD_19.mcm (has the bug with charset update, 
only after reset is showing something on the screen)
b. MinimOSD Extra 1.28.2_NTSC.hex / Gabor.mcm
c. ArduCAM_OSD_.rssi.time.status.mavlink1.0.hex / MinimOSD_20.mcm

Please provide any additional information below.
If I connect the TX wire everything is ok, the OSD values are updated few 
seconds after powering up the sistem, but if TX wire is not connected the 
values are not changing even after 30 minutes.

Original issue reported on code.google.com by [email protected] on 17 Aug 2012 at 11:58

OSD glitches on throttle

What steps will reproduce the problem?
1. MinimOSD with power bridged (all off 5V)
2. APM2


What is the expected output? What do you see instead?

I get throttle-related glitching on the OSD display, ranging from none to 
unusable.  Generally the glitching increases with throttle.

Underlying video is stable, it's just the overlay.

It's definitely a noise/interference issue, changing the relative arrangement 
of power and servo/OSD cables increases or decreases the severity.

I am running an independent UBEC, with 5 turns on an RF choke providing power 
to the APM, I also have a 10uF capacitor across the 5V rail of the APM.

minimOSD is powered from the APM2.

Would appreciate any suggestions.

Original issue reported on code.google.com by [email protected] on 8 Apr 2012 at 9:30

Garbled Panel 2

Panel 2 is broken and results in a garbled display with Arducam v2.0.

I expected to see just items I checked in the tool: speedometer, variometer, 
home arrow, and coords on panel 2. Instead I have what looks like an artificial 
horizon and tuning list garbled together on the top left corner of the screen. 
Both items are not even checked in the config tool. Panel 1, config screen, and 
the "off" screen work as expected; only Panel 2 has this problem.

There was a similar known issue in MinimOSD-extra that was recently fixed with 
a prerelease firmware update. Perhaps a similar fixe needs to be applied to 
Arducam 2.0.

Original issue reported on code.google.com by [email protected] on 5 Dec 2012 at 9:47

Characters blurred with 2.0?

What steps will reproduce the problem?
1. Uploaded new firmware and new charset
2.
3.

What is the expected output? What do you see instead?

The camera image is sharp, however, the minimosd text is not, it's blurred .. 
or somehow doubled..

What version of the product are you using? On what operating system?
firmware 2.0, uploaded new charset

can anyone help me please?

Original issue reported on code.google.com by [email protected] on 7 Nov 2012 at 11:19

Add compact versions for some of the outputs

Arducam shows 2 decimal points for voltage and current consumption, with the 
second decimal point being completely extraneous.  I doubt anyone needs voltage 
information down to .01v and current information down to .01A.  Most setups 
have sensitivity of about 0.1v and 0.1A, so why waste an additional character 
and valuable screen space?

Voltage and current are just two examples.  I'm sure there are others.

Original issue reported on code.google.com by [email protected] on 26 Dec 2012 at 7:56

Battery goes from empty symbol - to full.

my first flight with arduplane, voltage & current sensor installed, and 
properly selected, only voltage - not current *calibrated* with fluke, but the 
curent sensor should not be very off, (selected attopilot 90A - which this is)

4,2Ah 3S pack, configured in Planner as 4Ah

I assume the battery symbol presents measured power consumption vs predefined 
capacity.

Anyway - took off, full battery, the battery symbol got reduced to empty during 
5-10 minutes, yet voltage at full throttle proved it to be good. - then I got 
the battery symbol with exclamation mark.   Few minutes after that, got the 
battery full symbol. 


I will calibrate the Attopilot 90A current sensor voltage per ampére once I 
find where Planner displays it's idea of current, but assuming it cannot be 
that much off something can be wrong.
It's a dangerous error if the OSD can go from critically empty to full battery 
symbol.

Original issue reported on code.google.com by [email protected] on 11 Feb 2012 at 3:09

Compilation issues under Linux due to Case mismatch in include statements

When I try to build under Linux (i.e. Ubuntu), the build fails due to two 
include statements whose case does not match the filename:

src/Max7456.cpp:3:17: error: Spi.h: No such file or directory

and

src/ArduOSD.cpp:25:20: error: config.h: No such file or directory

This was in Revision 53

I change the include in Max7456.cpp to "spi.h" and the one in ArduOSD.cpp to 
"Config.h" and the compile worked without any problems. 

Original issue reported on code.google.com by [email protected] on 29 Apr 2012 at 4:10

chinese characters with clone

i made update to charset snd to firmware and my minimosd stills have chinese 
characters ...the proggraming made with FTDI basic 3,3v with usb 

the minim osd is V 0.1 and it s clone what to do ?? 

Original issue reported on code.google.com by [email protected] on 7 Jan 2013 at 8:53

Failed to talk to bootloader

What steps will reproduce the problem?
1.Connecting to minimosd through Arducam 2.1.2.0
2.Using DIYDRONES FTDI cable ttl-232r-3v3
3.Running Windows 7

What is the expected output? What do you see instead?
trying to read from osd and upload, getting the "failed to talk to bootloader" 
message

What version of the product are you using? On what operating system?
2.1.2.0 Arducam config and version 1.1 minimosd operating system Windows 7

Please provide any additional information below.

I'm converting fromn using the Remzibi OSD by 3DR to the minimosd.  Using the 
same cable from DIYDrones that worked on the Remzibi.  Verified the connection 
still works to Remzibi and does.  I have both 12volt and 5 volts supplied to 
board.  Both red led's on.
I get overlay from osd just fine when connected to APM 2.5. and veiwing on 
monitor.  Mavlink heartbeat detected and all messages appearing on osd overlay.

Appears to be in the linkup between the config program and FTDI.  Since the 
communications between the FTDI drivers detect the Comm port and when connected 
back to the Remzibi OSD all functions of read and writing to Remzibi work fine.

Original issue reported on code.google.com by [email protected] on 30 Jan 2013 at 5:08

Compilation error on Linux

SimpleTimer.cpp

Change 
#include "simpletimer.h"

To
#include "simpleTimer.h"

Unix based OS are case sensitive.

Original issue reported on code.google.com by [email protected] on 13 Jan 2012 at 10:23

Battery percent

1.When you start the APM the Battery percent will shows 99%, although when  the 
battery Voltage is not near to 12.6V==100%

2.I found the problem at the APM Code GCS_Mavlink.pde at line 196 :
" battery_remaining = (100.0 * (g.pack_capacity - current_total1) / 
g.pack_capacity);"
This means no matter how full the battery is it will start every time with 99%

3.So my idea is to show the consumed mAh and the percent does not depend on 
consumed mAh but of the voltagelevel (I know its difficult because a lipo 
battery has no linearly discharge curve)

I hope you understand my problem and i am sorry for my english

regards from germany

Original issue reported on code.google.com by [email protected] on 8 Feb 2013 at 11:40

How to connect the osd with fatshark

I just bought the mini osd with the apm 2.5.
In this diagram says that Is only FOR versión 1.0 (i HAVE 1.1) so if my camera 
works with 5 volts, how can i connect the fatshark to de osd??

Do i HAVE to solder the jumpers?

Original issue reported on code.google.com by [email protected] on 12 Jan 2013 at 3:55

Attachments:

• image.jpg

Please add configurable low-voltage warning.

subject says all.

Original issue reported on code.google.com by [email protected] on 11 Feb 2012 at 12:00

Panel 2 not working correctly

What steps will reproduce the problem?
1. Upload your Panel 2 settings to OSD
2. Enable OSD toggle channel
3. Toggle OSD channel through Tx

What is the expected output? 
To see the Panel 2 settings that I uploaded

What do you see instead?
"OVERSPEED" 100 with an hourglass symbol next to the 100.

What version of the product are you using? 
OSD Config 2.1.2.0 w OSD_20.hex

On what operating system?
Win7 64bit

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 30 Dec 2012 at 8:03

Voltage is showed on OSD is different from on GroundStation.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 14 Dec 2012 at 8:58

connection on mavlink 1.0

this is not exactly an issue. my problem is that i don't have the FTDI cable, 
and the new mav1.0 got my minimOSD out, because i haven't found a way to get 
this working.

my options are: i have a ZRTech USB to TTL converter (wich i was trying to get 
working, without sucess) or a 3DRadio, wich i believe is much more complicated. 
also, i believe it's not possible by the APM2 usb.

last option, i also have USBASP isp programmer. is it possible to get it 
working?

at last, my final option would be buying the cable. i'm thinking of buying it 
from sparkfun, so i can get a maestro for antenna tracking and an attopilot 
current sensor.

Original issue reported on code.google.com by [email protected] on 29 Jun 2012 at 3:11

Feature Request: Static Text

Need a way to add static text. People using amateur radio to transmit the video 
are required by the FCC to display their call sign at least every ten minute on 
any video signal they are transmitting.

Being able to add a line of static text to the OSD would allow them to do this.

Original issue reported on code.google.com by [email protected] on 28 Jun 2012 at 3:26

Feature request:

Visualize flight mode by flashing it upon change.
That would make it easier to "analyze" flight videos. 

Original issue reported on code.google.com by [email protected] on 21 Feb 2012 at 11:52

Enhancement Request - OSD Control On / Off

A feature to control the OSD overlay in MinimOSD with a Mission Planner command 
or via a RC channel, perhaps Arducopter may output a Mavlink command that 
miniosd snoops in order to enable disable the overlay.

That would be a very good feature to do FPV but also have the ability to change 
to a clean video feed while flying.

Original issue reported on code.google.com by [email protected] on 18 Mar 2012 at 1:56

Black screen

What steps will reproduce the problem?
1. Connect correctly the Vin/Vout/RX/BLK between APM, MinimOSD and video 
transmitter
2. Power on the APM
3. Connect the battery balance connector 12V to the MinimOSD


What is the expected output? What do you see instead?
At point 2, the ST led (orange) blink and the D PWR (red) led power on and 
still.  When I do the point 3, the ST led shut off and the A PWR led power on 
and still.
After that, I just have a black screen...
It's weird because the system worked at least once!

What version of the product are you using? On what operating system?
19

Please provide any additional information below.
I use a XBee but I've not connected the TX port on the minimOSD.

What's wrong ?

Original issue reported on code.google.com by [email protected] on 10 May 2012 at 12:50

Possible Regression with video format detection in V2.0

OSD Setup:

Minim OSD (First version board)
PAL jumper soldered
Separate power sources for video and MCU side

Cam setup:
Keychain camera (808 #16 - probably PAL but not sure)

On startup, Cam powered down - everything is OK. When the camera is powered up 
and the cam video commences, the OSD appears to lose sync somehow, and the text 
is crunched up into the top half. See demo here:

http://www.youtube.com/watch?v=-rzhpBWejhU

Reset while the cam video is running does not help.

This behavior does not happen in V1.9 - hence this is probably a regression of 
some kind

Original issue reported on code.google.com by [email protected] on 4 Nov 2012 at 3:28

MinimOSD always shows "Update Charset" on power up, requires hard reset before use.

What steps will reproduce the problem?
1. Apply power to all components simultaneously (APM, OSD, etc)
2. After a few seconds, OSD will show "Update Charset" and stop
3. In order to use OSD, must hard reset it or wait ~20 seconds to apply power 
after powering the APM.

What is the expected output? What do you see instead?
-> OSD should boot and be usable without a hard reset first.

What version of the product are you using? On what operating system?
-> APM 2.0 with 2.8.1, minimOSD 2.0.

Please provide any additional information below.
-> This problem is fairly well documented here: 
http://diydrones.com/forum/topics/minimosd-says-update-charset-on-bootup-must-re
set-first?id=705844%3ATopic%3A805912&page=1#comments
-> Basically the APM is sending 3 returns, causing the OSD to go into Update 
Charset mode.  I imagine this method is required for getting into update mode, 
but it would be very beneficial if there is a good way to avoid the false 
positive when simply booting up to fly.

Original issue reported on code.google.com by [email protected] on 30 Oct 2012 at 3:12

In Firmware 1.5 : max throttle is displayed as 74%

What steps will reproduce the problem?
1. Apply full throttle (after calibration from GCS)
2. Observe that the displayed throttle level is 74%
3.

Original issue reported on code.google.com by [email protected] on 10 Feb 2012 at 11:23

self - making problem

Hi!
i try make this hardware. im order at factory PSB and sucsessfily make and 
download firmware - the first copy of OSD at max7456eui+.
ОК! 

Then, at next time i bye max7456eui+w from polida2008 at ebay, PSB arduino cpu 
and other components as in first copy, 
i make 2 PCS board, but both show filling screen with 777777456 repitable 
sequence. two weeks of cheking and resolding and changes spi parameters of spi 
in src havnt result.
do you know what difference between  max7456eui+ and max7456eui+w ?
Thanks

Original issue reported on code.google.com by [email protected] on 15 May 2012 at 8:36

Horizontal noise in overlay.

Please see the horizontal noise in this video:
http://youtu.be/F-t7Y4tqq5k

-5V is provided by a switchmode BEC (usually very clean power)
-no servos moving

No difference no matter what I tried:
-both parts of MinimOSD running on 5V (no camera)
-adding 10UF, 1uF or 10nF capacitor across GND/VCC on the MiniOSD
-using a separate 12V source (another battery)  - with only GND in common

Where is this noise coming from ?
judging by how often the noise appears, may it be the Atmel working  - 
receiving MAVLink ?

Original issue reported on code.google.com by [email protected] on 13 Feb 2012 at 1:42

Use defines instead of one line functions (low priority improvement)

In CONFIG_Func.pde

Change this type of functions:

boolean ISa(byte whichBit) {
  return getBit(panA_REG, whichBit);
}

to "defines"

#define ISa(whichBit) getBit(panA_REG, whichBit)

The first method requires more CPU cycles than the second one.

Original issue reported on code.google.com by [email protected] on 13 Jan 2012 at 10:18

Call sign field requires 6 digits - should allow as few as 3

What steps will reproduce the problem?
1. Enter a call sign with less than 6 digits.
2. Click save tab
3. Will not save callsign less than 6 digits.

What is the expected output? What do you see instead?
-> In USA, callsigns can be as short as 3 characters, so this should be 
allowed, or pad with spaces, etc.

What version of the product are you using? On what operating system?
Version 2.1.2.0 with 2.0 firmware.

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 14 Oct 2012 at 8:42

Arducopter rssi

It is impossible to include instructions Arducopter rssi 2.8.0/2.8.1
http://code.google.com/p/arducam-osd/wiki/Cfg_RSSI
How to do it now

Original issue reported on code.google.com by [email protected] on 3 Nov 2012 at 4:51

Stuck at waiting for mavlink after upgrade to 1.5

Just flashed Minim OSD 1.5 - in hope of fixing the voltage problem.
(I guessed, and only way I could read or flash was by clicking the button about 
at the same time as applying power to the OSD)

When it boots, Splash screen says "1.0" - then it's stuck at "waiting for 
MAVlink heartbeats" (ArduPlane 2.28 - current version)
I don't have the 1.0 Firmware it came with - so I am stuck unless you can help 
me.

Original issue reported on code.google.com by [email protected] on 9 Feb 2012 at 8:53

OSD Config tool +mono = working path problem, and a transparency issue.

When executing using MONO, (Linux) - it complains about not finding Gabor.mcm 
and displays no graphics(background/instruments)

When executed using mono by first entering it's folder, - it works fine, except 
transparency (see screenshot)

Please make sure it looks for it's files in it's working folder.

Original issue reported on code.google.com by [email protected] on 16 Aug 2012 at 7:36

Attachments:

• [Screenshot from 2012-08-16 21:21:32.png](https://storage.googleapis.com/google-code-attachments/arducam-osd/issue-26/comment-0/Screenshot from 2012-08-16 21:21:32.png)

Connection errors

What steps will reproduce the problem?
1.Connect OSD to CPU via FTDI cable
2.Open and run osd config tool and try to update charset or firmware
3.

What is the expected output? What do you see instead?
I just want to be able to configure my osd but I keep getting the error message 
"Failed to talk to bootloader"

What version of the product are you using? On what operating system?
Latest minimosd
Latest config tool
Windows XP

Please provide any additional information below.
Both sides of my minimosd are powered. Also, when I try to go into device 
manager to find the correct COM port, it does not show up there.

Original issue reported on code.google.com by [email protected] on 12 Jan 2013 at 3:55

Osd conection (2 bateries)

This Is how i HAVE to connect my fatshark with  the osd, but do i HAVE to 
connect both negatives together?
Im going to use 2 bateries.
Some one said that Is necesary....

Tks

Original issue reported on code.google.com by [email protected] on 21 Jan 2013 at 10:57

Attachments:

• image.jpg

too low battery voltage displayed

What steps will reproduce the problem?
1. connect battery sensor
2. read APM planner voltage; in this case 11,7volts
3. observe that the reading is calibrated, real voltage is 11,7v
4. observe that OSD says "11.0V"

Original issue reported on code.google.com by [email protected] on 9 Feb 2012 at 7:20

Failed to talk to bootloader.

What steps will reproduce the problem?
1. Try to update firmware with osd-config.
2. Any other operation that has to communicate with minimosd.
3.

What is the expected output? What do you see instead?
msg : Failed to talk to bootloader

What version of the product are you using? On what operating system?
minimosd 1.1

Please provide any additional information below.

Hi,

I have a problem similar to issue #28. I received a minimosd without a 
bootloader. So, using a USPasp programmer with avrdude I flashed successfully 
the ATmegaBOOT_168_atmega328.hex bootloader.

Now I am trying to upgrade the firmware with osd-config. I am using an FTDI 
cable but I get the failed to talk to bootloader. When connected with the FTDI 
cable, the minimosd has its red led on, and the yellow led blinks slowly around 
once every second.

I tried to press the reset button after initiating the update without success. 
I will try to put a scope on the lines to have a better idea of what is going 
on.

Any idea what could be wrong ? Any suggestion would be appreciated.

Thanks.

JL

Original issue reported on code.google.com by [email protected] on 9 Oct 2012 at 9:17

Bottom symbols get chopped of when connecting a PAL Video camera.

What steps will reproduce the problem?
1. Connect no camera, display should be correct
2. Reboot with PAL camera connected, bottom symbols should be cut off.
3.

What is the expected output? What do you see instead?

Expected symbols to be in the same positions when camera is connected.


What version of the product are you using? On what operating system?
MinimOSD V0.1

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 28 Jan 2012 at 8:52

Miniosd information

Hello, i wanna know if i need something else to make it work.
I ordered the apm 2.5 and the miniosd, do i need the xbee?

Original issue reported on code.google.com by [email protected] on 14 Jan 2013 at 12:20

MinimOSD not displaying and getting very hot on 5v chip.

What steps will reproduce the problem?
1. Setup in basic mode and nothing
2. Solder all the jumpers for the APM to power the board (successful power up) 
Still no image
3.

What is the expected output? What do you see instead?
OSD display, Black screen no OSD information

What version of the product are you using? On what operating system?
MinimOSD

Please provide any additional information below.

I just received my MinimOsd and I have a pal camera. I soldered all the pins 
and jumper pads to have the APM 5v provide power to the whole board and the 
camera and transmitter with their own power and ground. When I have the 5v only 
plugged in the whole board lighted up but the chip on the APM side gets pretty 
hot.(is this normal) I also soldered the pal pad on the board. All soldered 
points are clean and perfect not sloppy. The video feed just shows a black 
screen and no data is showing on the screen. I unplug the power to the camera 
and it goes fuzzy. I have the video in the corrected input and outputs. I am at 
a loss what do I need to do to get this working. 

Original issue reported on code.google.com by [email protected] on 3 Feb 2012 at 2:30

Altitude error

What steps will reproduce the problem?
1.Boot up ardupilot and minimosd at the field
2.Altitude shows 256m when it is in my hand. My feild is 256m above sea level
3.

What is the expected output? What do you see instead?
I wish it would display the altitude relative to launch position instead of 
height above sea level
What version of the product are you using? On what operating system?
APM 2.5
Minimosd
Mission planner
windows xp

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 21 Jan 2013 at 3:31

Please add airspeed and current

Feature request:
Please display current and airspeed.

Original issue reported on code.google.com by [email protected] on 11 Feb 2012 at 11:59

Missing chars

What steps will reproduce the problem?
1. Upload newest firmware
2. Update charset from installation folder

What is the expected output? What do you see instead?
Expected the display to be like in the configurator, was as per attached 
screenshot

What version of the product are you using? On what operating system?
2.0

Original issue reported on code.google.com by [email protected] on 23 Dec 2012 at 11:45

Attachments:

• osd_01.png

Miniosd and fatshark attitude

What steps will reproduce the problem?
1. How can i connect the fatshark camera with this osd if the camera works with 
5v, and the osd manual says that it works with 12 volts

Original issue reported on code.google.com by [email protected] on 8 Jan 2013 at 4:30

Attachments:

• image.jpg
• image.jpg

Battery voltage bug

In MAVLink.pde (line 62) change:

osd_vbat = (mavlink_msg_sys_status_get_vbat(&msg) / 1000); // It's loosing the 
decivolts (tenths of a volt)

to:

osd_vbat = mavlink_msg_sys_status_get_vbat(&msg) / 1000.;

Original issue reported on code.google.com by [email protected] on 16 Jan 2012 at 10:54

No video output without serial link

What steps will reproduce the problem?
1. Turn on minimosd and video cam/rx, but no APM connection.
2.
3.

What is the expected output? What do you see instead?

When the OSD is powered on with a video signal, but without an active mavlink 
link, there is no video output.

Consider initializing OSD always, and at least pass-through video without 
overlay.

What version of the product are you using? On what operating system?

MinimOSD just released from diydrones 

Please provide any additional information below.

I expect this is just a case of moving some init code around so that the OSD is 
always enabled first. Thanks!

Original issue reported on code.google.com by [email protected] on 27 Jan 2012 at 11:55

No throttle use displayed. (permanent 0%)

I upgraded to 1.9 for MAVlink 0.9 today.
My first flight failed to display any throttle, it was stuck at 0%

Original issue reported on code.google.com by [email protected] on 26 Feb 2012 at 4:34

Feature request: telemetry data(serial) encoded in video/sync

Please consider encoding telemetry serial stream into the video stream, that 
would be a long range, easy, one-way telemetry link.
Another minimOSD on the ground could extract the data.

Original issue reported on code.google.com by [email protected] on 15 Feb 2012 at 7:59

Two battery symbols when voltage drops below 10.0V (gets one digit shorter)

What steps will reproduce the problem?
1. Connect a 3s battery and load it until voltage drops from 11.x to 9.x volts.
2. Observe that you get two battery signals (full signals) when low on power.

Imagine "B" = "full battery symbol" 
I see:  10.1VB 
then after the voltage drops:
9.8VBB   < two battery signals.

Is there a way, or is the OSD supposed to flash or otherwise warn about low 
battery voltage ?

Original issue reported on code.google.com by [email protected] on 11 Feb 2012 at 8:42

Can't get correct display

I updated the latest firmware and charset. I put the elements on my panel and 
saving. 
Then I'm connecting minimOSD to ardupilot and I'm powering up both boards. 
MinimOSD it's not working until I push reset button or wait 20 seconds to power 
minimOSD after powering Ardupilot (like someone have mentioned). 
Then I only see Artificial Horizon (working properly) and not the other 
elements. 
I tried to use another Charset and I got more elements but still it's not 
working properly.

Please let me know if you need screenshot or if it's known issue I'd be glad to 
know how to solve. 

Original issue reported on code.google.com by [email protected] on 27 Sep 2012 at 4:36

How to build arducam-osd

Hi,

I've added a small improvement to firmware to unconditionally switch OSD to 
panel 2 if RTL is engaged.  The problem is that I can't find any documentation 
on how to build arducam-osd for minimosd.  Most of the building steps are the 
same as for any other Arduino project, but I can't figure out which Arduino 
board to select in Arduino IDE as the target.

Which board in Arduino IDE should be selected to produce firmware for minimosd?

For reference, the patch to switch OSD to panel 2 on RTL is attached.  The 
rationale is to show GPS coordinates and other information that would help with 
rescuing the plane only when RTL is engaged.  In normal flight panel 1 is used.

Thanks.

Original issue reported on code.google.com by [email protected] on 6 Jan 2013 at 12:32

Attachments:

• 0001-Switch-to-panel-2-on-RTL.patch