I ran into an issue that I didn't notice until I started looking closer at the Home Dist, Alt fix on my V3 board. I have my primary alt widget set to show alt above Home and not to GPS or Terrain. When I first power up It shows 0 alt in the dial and then a -200 min to 200 max. As I armed and took off i noticed that both the alt widget and the home widget showing home alt shows the GPS alt. (about 4300 MSL). it just changed mid flight. I think this has been happening for a while because I know that I have always had the alt widget set for home. I will post this in Git as well. Attached is my V3 config on the latest firmware.
alceosd_config.txt

Hi Luis,

it seems it isn't a voltage issue; OSD is affected by noise... When we shield it with bare hands or move it farther from airframe, it works. When not shielded or close to airframe video disappears.

a minimOSD in exact same location with everything else same, doesn't have this issue.

We tried different power source for camera/TX, put ferrite coils on all wires, still same.

Do you have any recommendations?

please check also the configuration file.

alceosd_config_custom.txt

Wouldn't it be easier to have Mavlink as a sub-module and pull whenever needed ?

Just tried an upgrade of the bootloader to v0.55 on my square AlceOSD. After loading bootloader_updater_0v5.hex file, started to load alce-osd_0v9.hex file and still see bootloader 0.4 (step 2). Is this OK?

After that I see the loaded firmware version is 0v9 and I can read config until I disconnect the board from the USB adapter. When trying to connect again, I cannot read config but still can flash an old firmware. Strange, but reading config is working very well with FW 0.7.1.

Brightness and Sync Testing Video.
Is this how the brightness widget should look?
https://www.youtube.com/watch?v=Ew70vBrdoTc

could the speed widget be updated to give the option to display ground speed instead of air speed? (Useful for multirotors, and planes without pitot sensor)

Also perhaps (but not essential) the Speed widget could have a 'text' mode like the altitude widget, for those who want to have a minimal OSD on another tab but still keep some info

Thanks!

This is not really to report an issue but make a feature request for the throttle widget. While flying my quad racer i noticed that while flying in altitude hold that the throttle being displayed looked like the actual percentage being sent to the motors. It would be really useful to be able to set the widget to display throttle input so that while flying with goggles i can tell right when i reach midpoint to keep altitude. This is also useful for a number of other flight modes as well.

I think you may have already caught this but I just wanted to make sure. In the Home Widget the Alt is actually the distance from Home and the Dist is equal to the Alt measured int he Alt widget if using the home Alt not GPS alt.

Currently only channels RC1 to 8 can be used for tab switching. Other mavlink based OSDs (ex. playuavosd) allow up to channel 16.
Depending on configuration it can be quiet handy to shift switches to the upper channels.

Hello!

I am just making ABSOLUTELY sure that the alceosd 0v3, the only one available, can be fully functional with PX4 on a pixhawk. I have been stuck on this with other osds for months, so a one and done solution would be amazing!

Thanks,

Owen

when I try to connect to OSD appears me this error

"Error wainting for config"

this is my config file

alceosd_config 0.6.4.txt

In widgets.c

struct widgets_mem_s {
    unsigned int mem[MAX_WIDGET_ALLOC_MEM];

You're defining a 4 byte array. Shouldn't that be a char array? You're using four times more memory than specified in MAX_WIDGET_ALLOC_MEM.
And so,

void* widget_malloc(unsigned int size)
{
    unsigned int *ptr;

Needs to be changed to char *ptr;

Very nice work. Alceosd is quite a beautiful piece of code. I'm very impressed.

im getting this error

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: The parameter is incorrect.

at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
at System.IO.Ports.InternalResources.WinIOError()
at System.IO.Ports.SerialStream.set_BaudRate(Int32 value)
at System.IO.Ports.SerialPort.set_BaudRate(Int32 value)
at AlceOSD_updater.AlceOSDconfigForm.reset_board(Boolean flash, Boolean mavlink)
at AlceOSD_updater.AlceOSDconfigForm.flashFirmwareToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

AlceOSD
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/alceosd/AlceOSD_0v12RC3/AlceOSD_0v12RC3.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I have been using AlceOSD 0v3b successfully for a while. Last fall I decided to purchase a AlceOSD 0v4 and then move my AlceOSD 0v3b from my plane and replace it with AlceOSD 0v4 with the exact same setup I had with 0v3b. Today I just installed the 0v4 and found that on first power up the video pass through is good and the OSD overlay looks good for a short while but then starts to flicker and over time eventually disappears altogether. no matter what I do I cannot get the OSD to show up again unless I power it off and wait a long while then when I power it up the same thing happens. It will show up for a while then flicker and then disappear again. The video remains constant without any problems. It is just the OSD information that goes away. When I first started to use the 0v3b I found a flicker issue that I reported a while back and found that the flicker was caused by some interference. The solution was to replace all the video feed cables with a shielded cable and the interference went away. In an attempt to solve the 0v4 issue I reran all the cables making sure that all were shielded but this does not help. Right now the 0v4 is completely unusable. Any suggestions?

Please see video comparison: https://www.youtube.com/watch?v=Pyyy_vQ670Y

No problems with fw0.7.1 but wrong sync and offsets with fw0.8.1. default settings were used for both firmwares.
I switched boards and used the same plane setup. Fpv cam is HS1177 which has no issues with MinimOSD (which is pretty picky).

I noted you commited a lot since last release, but maybe this still helps.

I'm very much enjoying my new Alce OSD. However I have observed white, horizontal bars wherever the overlay features appear. I've attached an image from the web. The OSD is something different, but the video artifact is exactly the same.

When I put my old minimOSD back into the same aircraft, there is no issue.

Aircraft info:
TBS Disco Pro
RunCam Eagle 4:3 NTSC
Alce OSD 0v3
ImmersionRC 600mW, 5.8Ghz VTX
Dragonlink Micro RX
Pixhawk 2.1
ArduCopter 3.4.6

Any idea what would cause the white lines?