search

andrew0968 / minimosd-extra

Automatically exported from code.google.com/p/minimosd-extra
0 stars 0 forks source link

white streaks behind osd text with fatshark 250mw tx #40

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Fatshark 5,8ghz 250mw tx

changing black level to 10% in the code resolves the issue.

is it possible to add black level adjustment to the code? I can deliver the 
code if needed.

Original issue reported on code.google.com by degraaf...@gmail.com on 26 Aug 2013 at 9:34

GoogleCodeExporter commented 8 years ago 
same problem here with the same fatshark 250mW vtx. Would be great if you point 
me to where in the hex file we can change the black level to 10%....

Original comment by gojibogy...@gmail.com on 1 Sep 2013 at 7:19

GoogleCodeExporter commented 8 years ago 
Change 

// set all rows to same charactor white level, 90%

    for (x = 0x0; x < 0x10; x++)

    {

        Spi.transfer(x + 0x10);

        Spi.transfer(blevel);

    }

to

 // set all rows to same charactor white level, 90%
  for (x = 0; x < 15; x++)
  {
    Spi.transfer(x + 0x10);
    //Spi.transfer(0xd); //OK
    Spi.transfer(0xb);
  }

in file ArduCam_Max7456.cpp. And the minimosd will be working fine with your 
fatshark 250mw tx 

When changed you cannot set the white level anymore with te config program.

If you want i can create a new HEX file for you.

Original comment by degraaf...@gmail.com on 2 Sep 2013 at 8:20

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
has this been fixed?

Original comment by BSRBulle...@gmail.com on 9 Mar 2014 at 1:30

GoogleCodeExporter commented 8 years ago 
Same problem here, degraaf...@gmail.com I would be very grateful if you could 
create a hex that I could use to try and fix this.

Original comment by mark.god...@gtempaccount.com on 20 Mar 2014 at 10:34

GoogleCodeExporter commented 8 years ago 
Same thing with same transmitter.

Original comment by nick.gul...@gmail.com on 24 Mar 2014 at 7:49

GoogleCodeExporter commented 8 years ago 
same issue here.

Original comment by r.wijnho...@gmail.com on 30 Mar 2014 at 7:19

GoogleCodeExporter commented 8 years ago 
Does anyone have the modified hex so we won't have to compile? I'm using the 
same vtx as well as everyone who have FatSharks that aren't Dominators.

Original comment by nevi...@gmail.com on 10 May 2014 at 3:59

GoogleCodeExporter commented 8 years ago 
Hey Nevi, 

Can you please send me your hex? I hope its based on the latest regular 
firmware (none EXTRA firmware)

Thanks

T

Original comment by telmo2...@gmail.com on 16 May 2014 at 10:11

GoogleCodeExporter commented 8 years ago 
can anyone send me this .hex? my fatshark 250mW and minimOSD have this same 
issue. I am using in for a copter (if that matters). thank you

email squid10r@yahoo.com

Original comment by d.zhurak...@gmail.com on 27 May 2014 at 5:15

GoogleCodeExporter commented 8 years ago 
Here hex for copter version 2.4.1. Use low brightness setting in config tool to 
get rid of streaks.

Original comment by nick.gul...@gmail.com on 27 May 2014 at 7:41

Attachments:

GoogleCodeExporter commented 8 years ago 
thank you man, will try soon

Original comment by d.zhurak...@gmail.com on 27 May 2014 at 7:53

GoogleCodeExporter commented 8 years ago 
Thanks!  I don't get the white streaks anymore.  Unfortunately, I'm not seeing 
the correct characters.  Has anyone else had this same problem?

Original comment by DanielBB...@gmail.com on 28 May 2014 at 5:27

GoogleCodeExporter commented 8 years ago 
I had to update the charset in the config tool and then it worked well for me. 
Unfortunately I need the plane version. Is there any way to get the Plane 
version with the white streaks fix? Thanks

Original comment by four...@gmail.com on 28 May 2014 at 6:17

GoogleCodeExporter commented 8 years ago 
Ok If I started this, let's continue. This is just "Extra" version. I think 
it's for planes :-)

Original comment by nick.gul...@gmail.com on 28 May 2014 at 5:18

Attachments:

GoogleCodeExporter commented 8 years ago 
nick,

i just tried the copter 2.4.1 that you attached in comment #11. the lines 
disappeared on "low brightness" settings. However, when i plug it in, the OSD 
does not overlay the exact arrangement of data like I set it up in pnal 1 and 
panel 2 in Config Tool. When i plug it back up to the USB, the settings are 
just as I set them from before. 
I also tried general 2.2 hex, but here i still get the lines even on the low 
brightness setting. 
Any advice on how i can make the Config tool settings correspond to the actual 
data shown in my goggles? (I do press the "save tab to OSD button" in Config 
tool every time).
THank you

Original comment by d.zhurak...@gmail.com on 31 May 2014 at 2:51

GoogleCodeExporter commented 8 years ago 
Nick, can you attach your charset .mcm file?  I don't get the right characters 
to show up with your hex.

Original comment by DanielBB...@gmail.com on 31 May 2014 at 4:24

GoogleCodeExporter commented 8 years ago 
four...@gmail.com, what charset did you upload?  I have tried every one that I 
can find, but none of them have worked.  I know that it isn't hardware as I can 
get the charsets to work with other firmware builds.

Original comment by DanielBB...@gmail.com on 31 May 2014 at 4:59

GoogleCodeExporter commented 8 years ago 
I think I figured out the poor charset.  It is my hardware.  It seems as though 
the latest .hex files are giving some hardware builds problems.  

Nick, is there any way you can help guide me to get the arduino projects set up 
correctly, or send me a modified 2.2 hex (with the modified white streaks)?

Original comment by DanielBB...@gmail.com on 9 Jun 2014 at 5:00

GoogleCodeExporter commented 8 years ago 
Daniel, which version of 2.2 do you need? plane or copter? Any particular 
revision? I will compile it for you little later.

Original comment by nick.gul...@gmail.com on 9 Jun 2014 at 6:07

GoogleCodeExporter commented 8 years ago 
About charset, one of mcm files in
trunk/tools/OSD/bin/Release
works for me. Can't tell which exactly, because it's hard for me to take OSD 
off my copter right now.

Original comment by nick.gul...@gmail.com on 9 Jun 2014 at 6:16

GoogleCodeExporter commented 8 years ago 
Thanks, Nick.  If you have the time to build a 2.2 copter version with the 
lower brightness, that would be awesome.  

Do you know of a resource that helps to guide the process of setting up the 
different arduino projects?  I am having problems setting up and building.  
There seems to be missing files or not enough info in the project.  

Thanks for the help!

Original comment by DanielBB...@gmail.com on 9 Jun 2014 at 2:16

GoogleCodeExporter commented 8 years ago 
Daniel, I'm using  arduino 1.0.5 or 1.0.3 and TortoiseSVN to work with code 
repository.
I assume that you can work with SVN to get version you need.
In trunk folder make folder named ArduCAM_OSD and copy code from 
MinimOSD-Extra_Copter there. You can also just rename foder.
Open Arduino
In Preferences/Sketchbook location choose folder with source code.
Restart Arduino. In File/Sketchbook choose ArduCAM_OSD and try to compile it.
If you will use 504 revision as I did for you, open file OSD_Vars.h and 
uncomment defenition of batt_capacity variable.

And main thing. Go to ArduCAM_max7456.h and change 
#define MAX7456_WHITE_level_80 0x03
to
#define MAX7456_WHITE_level_80 0xb

Original comment by nick.gul...@gmail.com on 9 Jun 2014 at 4:40

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks, Nic!  Your hex worked great!  I really do appreciate your help with it!

Original comment by DanielBB...@gmail.com on 10 Jun 2014 at 2:12

GoogleCodeExporter commented 8 years ago 
Why hasn't this fix been implemented in the main code? Is there some reason why 
0x03 is better than 0xb for non Fat Shark transmitters?

Can someone explain exactly what the bit settings are in the 0xb? (00000011 
becomes 00001011) Is it possible to change the same bit in the other brightness 
settings? I'm happy to fix this in the main code and close the issue but I want 
to understand the problem in more detail before I do.

It seems silly that users have to compile code to fix this when it could be 
incorporated in to the brightness settings. (especially since I just bought a 
fat shark 250mw tx, lol)

Original comment by efu...@gmail.com on 27 Aug 2014 at 2:47

GoogleCodeExporter commented 8 years ago 
Ok, I checked out the data sheet for the video chip. The black levels work the 
same as the white levels, using bits 2 & 3.

So for 100% brightness you have
0% black level 0x01
10% black level 0x05
20% black level 0x09

Testing with my Fat Shark Tx, you need 20% black level on all levels except 80% 
white level which works ok with 10% black level. So a temporary fix would be to 
replace the white levels in ArduCam_Max7456.h with the following defines.

//Fat Shark 250mw Tx white streaks fix
#define MAX7456_WHITE_level_80 0x07 //Black level 10%
#define MAX7456_WHITE_level_90 0x0A //Black level 20%
#define MAX7456_WHITE_level_100 0x09 //Black level 20%
#define MAX7456_WHITE_level_120 0x08 //Black level 20%

I'm no longer a committer, so I can't add them to the code for you.

Also, as a more permanent fix, these could be added to the windows config 
program which could write the selected white/black level byte to the eeprom. 
Then you wouldn't need any defines, you just read the eeprom and write the 
value to the Max7456. Cleaner and you save some memory.

Original comment by efu...@gmail.com on 30 Aug 2014 at 4:19

GoogleCodeExporter commented 8 years ago 
Thanks, I was able to compile the hex file and the result is perfect!!

Original comment by fbu...@gmail.com on 16 Nov 2014 at 9:07

GoogleCodeExporter commented 8 years ago 
Closed as we have a new version.

Ifthe problem is still present please reopen it.

Original comment by gabek...@gmail.com on 28 Nov 2014 at 11:44

GoogleCodeExporter commented 8 years ago 

Lines 56 to 60 of ArduCam_Max7456.h r802:

//VM1 command modifiers
#define MAX7456_WHITE_level_80 0x03
#define MAX7456_WHITE_level_90 0x02
#define MAX7456_WHITE_level_100 0x01
#define MAX7456_WHITE_level_120 0x00

The black levels have not been added so the problem remains.

What about the new version made you think the problem was fixed?

Original comment by efu...@gmail.com on 29 Nov 2014 at 4:25

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I used the MinimOSD-Extra-copter-FS.hex given by nick.gul...@gmail.com and that 
fixed my issue, although the letters are certainly dimmer than before.  Better 
to have dimmer letters than white streaks, though!  I used charset 
MinimOSD_2.4.0.0.mcm along with it, and didn't have any messed up letters.

Original comment by TJHa...@gmail.com on 1 Apr 2015 at 1:31

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi guys I am seeing the same issue on a Rembizi s-osd. I have the rembizi 
configuration tool but unsure how I get in the settings you guys are 
discussing. Can somebody here please if you don't mind, giving me a quick guide 
on how to get into these configure files?

Thank you 

Jonny

Original comment by jar...@gmail.com on 19 Apr 2015 at 6:36

GoogleCodeExporter commented 8 years ago 
Got this issue using an aomway500mw 5.8tx. Downloaded the fixed copter hex. 
Solved the problem. Also tried the plane spesific hex as im using this on a 
plane,but it doesnt work. No overlay. And when i try to update char set i get 
an error. Anyway, thus far, the hex from post #11 seems to work. Will test more 
later and update if i run into any issues :)

Original comment by Akuji...@gmail.com on 16 Aug 2015 at 2:21

GoogleCodeExporter commented 8 years ago 
well lines are gone, but i got an issue with the summary screen. it appears in 
flight. idk if its related to the firmware. or the fact that im using copter 
firmware in a plane.

Original comment by Akuji...@gmail.com on 22 Aug 2015 at 3:31